CP access problems
-
I keep getting this: Microsoft OLE DB Provider for SQL Server error '80004005' [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. /script/common/db.asp, line 108 *sigh*
Just doing a quick DB server update. Things got a little chaotic so I just let the webservers go crazy for the 4 mins the DB server was offline. Sorry 'bout that. cheers, Chris Maunder
-
Just doing a quick DB server update. Things got a little chaotic so I just let the webservers go crazy for the 4 mins the DB server was offline. Sorry 'bout that. cheers, Chris Maunder
-
Just a quick question. Do you not think it a security risk to let people see script errors like that?
I'm more than happy for everyone to know that line 108 in db.asp fails when the DB connection fails. Some background on all this: We had a consultant install a big, shiny new database server a few months ago and lately that server has been failing more and more. ASP is being a little uncooperative and the errors you see should actually be caught by our error handlers and not shown. Errors that occur are being reported to us, but are also showing up on the page - slightly annoying - but I'd rather track the errors to help with diagnostics than not. The first outage this morning was the DB server failing, the second was me preparing to move everything back to backup servers. There will be one more outage either tonight or tomorrow morning (4-5 minutes) while I complete the move. The carcus of the new DB server will then be hung out and left to the crows. :mad: cheers, Chris Maunder
-
I'm more than happy for everyone to know that line 108 in db.asp fails when the DB connection fails. Some background on all this: We had a consultant install a big, shiny new database server a few months ago and lately that server has been failing more and more. ASP is being a little uncooperative and the errors you see should actually be caught by our error handlers and not shown. Errors that occur are being reported to us, but are also showing up on the page - slightly annoying - but I'd rather track the errors to help with diagnostics than not. The first outage this morning was the DB server failing, the second was me preparing to move everything back to backup servers. There will be one more outage either tonight or tomorrow morning (4-5 minutes) while I complete the move. The carcus of the new DB server will then be hung out and left to the crows. :mad: cheers, Chris Maunder
Chris Maunder wrote: The carcus of the new DB server will then be hung out and left to the crows Is it by any chance a descendant of the evil Web2 that caused so much trouble ? The tigress is here :-D
-
Chris Maunder wrote: The carcus of the new DB server will then be hung out and left to the crows Is it by any chance a descendant of the evil Web2 that caused so much trouble ? The tigress is here :-D
I don't think it's a case of bad genes. I'm thinking more along the lines of possession. I don't think we ever exorcised Web2 properly and we're now paying the price. cheers, Chris Maunder
-
I'm more than happy for everyone to know that line 108 in db.asp fails when the DB connection fails. Some background on all this: We had a consultant install a big, shiny new database server a few months ago and lately that server has been failing more and more. ASP is being a little uncooperative and the errors you see should actually be caught by our error handlers and not shown. Errors that occur are being reported to us, but are also showing up on the page - slightly annoying - but I'd rather track the errors to help with diagnostics than not. The first outage this morning was the DB server failing, the second was me preparing to move everything back to backup servers. There will be one more outage either tonight or tomorrow morning (4-5 minutes) while I complete the move. The carcus of the new DB server will then be hung out and left to the crows. :mad: cheers, Chris Maunder
-
I don't think it's a case of bad genes. I'm thinking more along the lines of possession. I don't think we ever exorcised Web2 properly and we're now paying the price. cheers, Chris Maunder
:doh: Do not delay another second, go out and purchase a dead chicken and wave it over them, remember that an attitude of capering nihilism will add effectiveness to the dead chicken wave so go all out.
"A preoccupation with the next world pretty clearly signals an inability to cope credibly with this one."