T O P I C R E V I E W |
Alaundo |
Posted - 16 September 2011 : 08:06:51 HI
I am receiving the following error, which has rendered the forum unavailable for approx 36 hours. The web host are saying there is nothing they can do and it's down to the scripting.
Provider error '8000ffff'
Catastrophic failure
/inc_header.asp, line 134
Line 134 is the Open database command. They claim that there are too many open threads on the database and they have not been closed down properly. So now nothing else can connect.
I have checked the DB through PHPMyAdmin and all seems ok. I threw together a quick mysql_close($db_handle) scriipt but guess this wont help as it's not going to tie into a thread that it didnt open itself?
Please help |
15 L A T E S T R E P L I E S (Newest First) |
Doug G |
Posted - 22 September 2011 : 00:29:03 Ditto, I'm glad you got things working. |
ruirib |
Posted - 21 September 2011 : 10:46:31 I am glad it's sorted. It was a server issue, all along, as I said. Too bad it took them so long to sort. |
Alaundo |
Posted - 21 September 2011 : 08:58:10 Just to close this one off... the forum is back working again. Apparently, the issue was due to being on a busy "application pool". The host now moved to a less-busy pool and all is well again!
Thanks to all for all the help and support |
ruirib |
Posted - 19 September 2011 : 10:04:36 Well, no surprises there. That's info for php and you are not using php. PDO means PHP data objcts is of absolutely no use to access a MySQL database using ASP. |
Alaundo |
Posted - 19 September 2011 : 07:28:51 The host have returned to me with the following:
The driver version of Mysql is "PDO Driver for MySQL, client library version 5.0.51a".
Also, there is a bunch of information for their servers held here:
http://win.streamlinetrial.co.uk/phpinfo.php
It shows info on the MySQL and ODBC as well as a bunch of server variables, not not quite sure what I should look for to identify any incompatabilities or elements to go back to them with.
Any help very much appreciated
|
Alaundo |
Posted - 19 September 2011 : 04:36:47 quote: Originally posted by Doug G
You might double-check your line number, that error message is often caused by email code errors too.
Also often if a site updates the mysql version they will also update the mysql drivers version. I'd verify with your host what the mysql ODBC drivers version is that's installed.
Thanks, Doug
The line number is definately just the open command. I have a number of mods installed which may have changed the line number from the standard install.
I'll see if they will reveal the driver version.
Thanks all. |
Doug G |
Posted - 18 September 2011 : 17:57:35 You might double-check your line number, that error message is often caused by email code errors too.
Also often if a site updates the mysql version they will also update the mysql drivers version. I'd verify with your host what the mysql ODBC drivers version is that's installed.
|
ruirib |
Posted - 18 September 2011 : 14:28:40 Well, if they don't do something, this won't be solved. A script doesn't mean anything. If it is php, for example, shouldn't have a problem at all connecting to the database. It's even possible that even if they use asp and do it through another driver or on a site using another app pool, that all will be well.
This is their fault. If they don't solve it, I think your only option is to ditch them. |
Alaundo |
Posted - 18 September 2011 : 14:04:17 quote: Originally posted by ruirib
No, the driver version and the MySQL version are completely different things.
Ah, i see. So i guess they stating the MySQL version and that it has not changed recently is a moot point, as they may have updated some drivers.
So there is really nothing at all I can do, client-side to solve this issue, as it doesn't appear that they are going to do anything at all to assist and claim there is no issue at all.
In fact, they state they can open the database without issue by a simple script they have written.
|
ruirib |
Posted - 18 September 2011 : 13:30:57 No, the driver version and the MySQL version are completely different things. |
Alaundo |
Posted - 18 September 2011 : 13:06:15 quote: Originally posted by ruirib
Any MySQL version greater than 3.something is good for Snitz. I wouldn't accept a 5 day outage in any circumstances and it's something they would solve in less than a minute.
Might sound stupid, but would the issue be in that they are running v5+ of MySQL but my inc_header open string contains:
driver={MySQL ODBC 3.51 Driver};option=16387;server=mysql8..... etc
Should I set this driver in the string to be that of the version they stated? |
ruirib |
Posted - 18 September 2011 : 13:01:18 Any MySQL version greater than 3.something is good for Snitz. I wouldn't accept a 5 day outage in any circumstances and it's something they would solve in less than a minute. |
Alaundo |
Posted - 18 September 2011 : 12:27:24 quote: Originally posted by ruirib
The host refusal to acknowledge the issue is astounding. Been there and an IIS reset will solve the issue. You should also ask the host precisely that - how come it has worked for 10 years and now you claim this? And how come the site is not working and they can't do nothing about it?! What are you supposed to do?
There is a 5.1 version driver. Not sure if the host has it installed. Probably not. If not, you have to pressure them to solve the issue for you.
Indeed, I'm extremely frustrated with the host, and it's not the first time. I've had downtime now for 5 days. As it's running on a shared server, they are refusing to do anything at all.
Last communication was to confirm that nothing has changed recently (obviously response). They are running MySQL 5.2.6....is the ok for current Snitz? Anything else i can check\confirm with them?
I will obviously move hosts after this, but just want to get the forum up and running sooner rather than later if i can |
ruirib |
Posted - 18 September 2011 : 10:57:16 The host refusal to acknowledge the issue is astounding. Been there and an IIS reset will solve the issue. You should also ask the host precisely that - how come it has worked for 10 years and now you claim this? And how come the site is not working and they can't do nothing about it?! What are you supposed to do?
There is a 5.1 version driver. Not sure if the host has it installed. Probably not. If not, you have to pressure them to solve the issue for you. |
Alaundo |
Posted - 18 September 2011 : 10:37:15 quote: Originally posted by ruirib
This has nothing to with the MySQL version. MySQL drivers are not the best code that was ever created and such situations crop up sometimes.
Trying a different driver is something you can try, by changing the connection string, but that may solve this or not. If the host resets IIS, this will go away, at least for a while.
Thanks. The host have written a brief script to check the connection to the database and claim there is no issue.
What other driver options can I attempt in the connection string? I thought we had leave that at the MySQL 3.5.1 driver regardless. This has been functioning fine for me for 10 years so i'm baffled as to what has occured. I've asked the Host if they have updated any drivers lately, but expect they will deny anything.
Thanks again.
|