| Author |
 Topic Search  Topic Options
|
Iowarth 
Newbie
Joined: 03 December 2009
Location: UK
Status: Offline
Points: 14
|
 Post Options
 Thanks(0)
 Quote  Reply
 Topic: Database connection issues
Posted: 03 December 2009 at 7:52pm |
|
Hi
I run a Web Wiz forum which I took over about 6 months ago and it has run on my service provider's server perfectly ever since ...... until yesterday morning!
It now comes up with an Error 500 whenever trying to use any of the Forum pages which involve access to the database.
The detailed error message from the logs is:-
"ADODB.Connection error '800a0e7a'
Provider cannot be found. It may not be properly installed.
/forum/common.asp, line 260"
I have tried recycling the application pool and using both the virtual and physical database path - but the problem persists.
Incidentally, this is an old version of Web Wiz (Copyright 2001-2004) - I hope to upgrade to the latest ... when I can afford it!
My apologies if the answer exists within the forum - I have searched but failed to find this specific problem
Many thanks for any assistance.
Chris
|
 |
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 04 December 2009 at 9:11am |
|
This is a server issue. The database driver is either corrupted or has been disabled.
You would need to contact your hosting provider.
|
|
|
|
Iowarth
Newbie
Joined: 03 December 2009
Location: UK
Status: Offline
Points: 14
|
Post Options
Thanks(0)
Quote Reply
Posted: 04 December 2009 at 10:40am |
Thanks Bruce. This was also my supposition - but it's amazing how difficult it can be to persuade one's hosting providers to accept the problem might be with their server! They did provide me with an alternative connection string (ignoring the fact that the standard one had worked perfectly for 6 months!). This did produce a change of error message to :- Microsoft OLE DB Provider for ODBC Drivers error '80004005' Specified driver could not be loaded due to system error 193 (Microsoft Access Driver (*.mdb)). At least this seems to pretty conclusively prove a server issue - even to them one would hope! I will update this thread with the outcome or any developments for the benefit of any others who may get similar problems at some time. Chris
|
|
Iowarth
Newbie
Joined: 03 December 2009
Location: UK
Status: Offline
Points: 14
|
Post Options
Thanks(0)
Quote Reply
Posted: 04 December 2009 at 12:44pm |
|
Hi again
Simply an update as promised. The situation is now resolved and Bruce was (of course!) quite right!
In my response to my hosting provider I stated the following:-
"An internet search suggests that this problem may result from running 64bit server
without 32bit OLEDB manager. This, or variants of it (eg MDAC or OLEDB
corrupted) are also the most common, in fact, after connection string
errors, the only causes I can find on the net of both this and the
preceding errors. The software provider also states unequivocally that
this is a server
error. Bearing in mind that this application has run perfectly for 6
months and that I made no change whatsoever to it prior to its
extremely sudden cessation, might I suggest that the above be
investigated - particularly (but not exclusively) what server changes (eg updates etc) might have been implemented overnight on Tuesday prior to its sudden loss at 0841 on Wednesday"
I then received a response stating:-
"We've made some updates to your user on the server ........" and it worked.
This obviously demonstrates that a pro-active response to a support department can be of assistance.
Hopefully, this episode and its resolution might be of assistance to anyone else who might suffer similar problems at some time in the future.
Chris
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 04 December 2009 at 1:10pm |
|
When I first saw your error I thought exactly the same thing in regards to the issue as there is no 64bit JET Access driver, so unless you place the application pool in 32bit mode then on a 64bit machine you do get this error.
However in your case I would have thought this unlikely as you can not update a server from 32bit to 64bit, it requires that you have a new OS installed.
Migrating your account to a 64bit machine without notice is very bad as there are so many things that can break.
|
|
|
|
traumaplayer
Newbie
Joined: 15 December 2009
Location: NC
Status: Offline
Points: 2
|
Post Options
Thanks(0)
Quote Reply
Posted: 15 December 2009 at 8:02pm |
What odd timing! As of 12/11/09 I am having the same issue. However, I'm having a hard time getting help from the hosting company. This forum has been up and running for many years and this is the first time I've had an issue.
They sent an email a couple weeks ago letting me know of server maintenance on 12/11 at 2am. In the email is this: "The impact of this maintenance will be the removal of any 10.x.x.x IP addresses space bound to shared servers.
PLEASE NOTE: Action is needed to update any references to these internal IP addresses to maintain website and database functionality.
1)Data Source Names (DSN's)
2)Any references to internal address in code such as database connection strings."
I know this is the reason for the connection problem but I'm not sure I know what to do to fix.
Any ideas?
Thanks in advance,
Tyler
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 16 December 2009 at 11:27am |
|
This was quite a specific issue to using an Access database on an x64 system.
Is this what you are using? Are you using Access on an x64 OS and if not what database types are you using and what is the OS?
Also any error messages would be useful as well.
|
|
|
|
traumaplayer
Newbie
Joined: 15 December 2009
Location: NC
Status: Offline
Points: 2
|
Post Options
Thanks(0)
Quote Reply
Posted: 16 December 2009 at 1:12pm |
MS SQL database. This is the error message:
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
/forum/common.asp, line 260
Thanks!
|
|
