Connection to SS 2000 failing
Bill_Orova
You guys are the best,
I am having a problem with an instance of ss 2000 that has an accounting
use, this dept is using access as a front end to post checks to a
database. They do large amounts of checks like over 200 at a time. Last
week they were getting a time out error. So I instructed them to run
only one to see if that worked it did but took over 2.8 minutes that was
within .2 minute is timing out again, this will not work for the
hundreds of check that get posted. I went to try bring up EM and I got
the following message:
Entry Point Not Found
---------------------------
The procedure entry point ?ProcessExecute@@YAXPAUHWND__@@PBG1@Z could
not be located in the dynamic link library SEMSFC.dll.
SQL Server Enterprise Manager
---------------------------
Connection to application object failed. Ensure that no program modules
have been deleted.
When I went in through RDC I was able to bring up EM with no problem. We
did last night install sp4 on the server I am still experiencing the
same problem.
Do I need to install sp4 on my machine? and is there something else to
be done to the server.
The load is a little heavy for this server
it is running win 2000 server and quad 700 mhz intel Pentium 3 XEON
This server setup has worked fine in the past
HELP?
Wisord
*** Sent via Developersdex http://www.developersdex.com ***
Erland Sommarskog
> I am having a problem with an instance of ss 2000 that has an accounting
> use, this dept is using access as a front end to post checks to a
> database. They do large amounts of checks like over 200 at a time. Last
> week they were getting a time out error. So I instructed them to run
> only one to see if that worked it did but took over 2.8 minutes that was
> within .2 minute is timing out again, this will not work for the
> hundreds of check that get posted.
It seems that you have to tune this function. IS this a homegrown
application, or a third-party application?
In any case, the regular path for analysis apply. Is ithe delay due to
blocking, or is some query running slowly? IF the latter, is this because
an index is missing? Or are statistice out of date? Indexes fragmented?
> I went to try bring up EM and I got the following message:
>
> Entry Point Not Found
> ---------------------------
> The procedure entry point ?ProcessExecute@@YAXPAUHWND__@@PBG1@Z could
> not be located in the dynamic link library SEMSFC.dll.
>
>
> SQL Server Enterprise Manager
> ---------------------------
> Connection to application object failed. Ensure that no program modules
> have been deleted.
>
> When I went in through RDC I was able to bring up EM with no problem. We
> did last night install sp4 on the server I am still experiencing the
> same problem.
> Do I need to install sp4 on my machine? and is there something else to
> be done to the server.
The error appears to be a problem on your machine, which is completely
unrelated to SQL Server itself. It seems that some other component has
pulled the rug for Enterprise Manager. Installing SP4 solve the issue,
else I would try a repair from the original Setup, and then apply SP4.
> The load is a little heavy for this server
> it is running win 2000 server and quad 700 mhz intel Pentium 3 XEON
Those specs are indeed a bit timid.
--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Bill_Orova
I did install the sp4 and that finally solved my end of the problem, we
also installed sp4 on the server and that helped as well, but it seems
that the posting is still taking for only one check 45 seconds.... which
should be like 10-12 seconds as is regular
the real thing is that this situation came out of nowhere.... not like
it went slowly to bad perfomance it went from :12 to 2:45 now back to
:45 any other ideas??
It did not go like :12 to :20 to :45 to 2:45 ie.... gradual degradation
so it is not due to increases in data sizes right?
Erland Sommarskog
> I did install the sp4 and that finally solved my end of the problem, we
> also installed sp4 on the server and that helped as well, but it seems
> that the posting is still taking for only one check 45 seconds.... which
> should be like 10-12 seconds as is regular
> the real thing is that this situation came out of nowhere.... not like
> it went slowly to bad perfomance it went from :12 to 2:45 now back to
> :45 any other ideas??
>
> It did not go like :12 to :20 to :45 to 2:45 ie.... gradual degradation
> so it is not due to increases in data sizes right?
There is a multitude of possible explanations, and with the minimum
of information you have given, you cannot expect much useful help back.
Just a sample:
1) The queries was recompiled for one reason or another, and the new
query plan is less effecient than the old.
2) You have hit a resource threshold so any of these can be true: a) all
data that the query needs to access no longer fits in cache, b) a
sort needs to spill to disk c) a hash needs to spill to disk, and
maybe you get a hash bail-out.
3) Some other processes is hogging your system, and the posting of the
checks takes a hit.
4) Some other process causes immense locking, holding up the cache-
posting queries.
5) A hardware failure degrades performance of your box.
As for what to, refer to my previous post. I don't really have any more
detailed suggestions at this point.
Bill_Orova
Erland thank you so much
Yes I agree it is a little baffiling as nothing else has changed
according to the admins of that area
But I am on the trail
Once again thanx much