Timeout issue I believe (in addition to connection pool issues ?)
I just started getting this same error last week, now on 3 out of 15 client
machines.
It appears immediatly after a successful application specific login. One
connection was opened and closed for the login, then another is used to fill
a dataset.
On all machines it was preceded by a Crystal.Net Error. One, after running
fine for a week reported a missing Crystal DLL. After Re-Installing we got
this error AFTER the application is run once (for how-ever long you want with
as many CRUDs as you want) and then is tried to run again. One had a similar
error the first time it ran after installation. The other had the wrong
version of Framework at installation time and was re-installed after the
needed version of Framework.
Rebooting will allow you into the app again -AND- so will
re-installing the Crystal.NET merge modules... ?
Two of the Machines are on XP SP2, will learn about the 3rd machine
tomorrow.
This may not belong on this thread but since others and myself looked here
for it first I thought I would throw this out there too. I'm going to check
some other threads, treating my problem more as a timeout issue.
"Cor Ligthert" wrote:
Brian,
For me this sounds more as a TimeOut question.
http://msdn.microsoft.com/library/de...meouttopic.asp
When you get no answer here, than I advice you to place this same question
in the newsgroup
Adonet
news://msnews.microsoft.com/microsof...amework.adonet
Web interface:
http://communities2.microsoft.com/co...amework.adonet
With the same subject text as now.
Mostly Angel react in that newsgroup on any connection pooling problem and
handles it untill it works.
I hope this helps?
Cor