Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

URGENT!!!! Unspecified error message 1

Status
Not open for further replies.

Biffy13

Programmer
Oct 22, 2002
63
GB
Hi

This morning, all our websites that connect to a database suddenly started getting 'unspecified error' error messages. This started happening intermittently but is now a permanent error on any page that connects to a database.

Up until then, they were all working fine, using DNS-less connection strings. There are multiple Access 2000 databases, which all reside within different folders which all have the correct permissions.

Nothing has been changed on the sites or on the server.

The server is Windows 2000, running IIS 5.0. All the latest patches have been applied.

The only difference is that SecureIIS was left open all night (a firewall for IIS). When I discovered it this morning, I closed it, though I don't think it could affect anything. Soon after, the first errors were reported, though that could be a coincidence as we don't know for sure when the errors started happening.

The server was rebooted but it did not fix the problem. This would also have eliminated any problem with database connections being left accidently open.

We are currently running a virus scan but are pretty confident that our server is virus-free as a scan is run daily.

We are also going to try updating MDAC as apparently it can be corrupted.

Has anyone else ever come across this or have any ideas on how to solve the problem?
 
Addendum.

Restarting the web server seems to have temporarily solved the problem (even though a reboot didn't?).
 
Further addendum. It would appear that the server was fooling us into believing it had rebooted when it really hadn't (we remote in to it so we couldn't actually physically turn it off), which is why a 'reboot' didn't appear to fix the problem.

It would also appear that a script which kept going into an infinite loop on selecting from a database was causing the problems.

We never did update MDAC as reading further forum posts, we found that it didn't make any difference to other people receiving similar errors.

I will post more if I find anything else out or whether the problem was not just caused by this particular script.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top