by The following configuration ran with no problem for months. For the
past 8 weeks, 1 of 3 problem situations now occur about every 7 days.
Server#1: W2K (SP2), vendor application calls my ADO 2.1 COM
component, COM component performs around 10,000 reads per day to SQL
Server DB#1/table#1, COM component performs around 10,000 inserts per
day to SQL Server DB#2/table#2, ASP reads DB#1/table#1 lightly (coded
"with(nolock)), ASP reads DB#2/table#2 (coded "with(nolock))
sometimes, heavily
Server#2: W2K (SP2), SQL Server 2K (SP2), PCanywhere 10.5.1, IIS 5,
DB#1/table#1, DB#2/table#2
About every 7 days, 1 of 3 problems will occur with about equal
probability:
1) "ALL" COM component inserts to DB#2/Table#2 get "timeout expired
-2147217871"; COM component reads to DB#1/Table#1 continue to be
successfull; ASP reads to both tables continue to be successfull; I
don't see any lock problems; event viewer shows nothing; problem goes
away by going into SQL Server Client/Enterprise Manager and inserting
1 row into DB#2/Table#2;
2) PCanywhere 10.5.1 from my workstation (W2K Pro) connects to
Server#2, gets the black message box, but does not get a login box
(ie. hangs); problem goes away by shutting PCanywhere down and
bringing it back up
3) both problems occur at the same time
The obvious question is "what changed", but to the best of my
knowledge, nothing. Any ideas on how to track down this problem would
be appreciated.
Jerry