JReynolds
asked on
ODBC Drivers error 80004005
I am connecting to an Access database on a Novell 5.X server (using a mapped drive) from an NT Workstation running IIS4 via an ASP page. I get the following error when running the ASP page;
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Microsoft Access 97 Driver] Out of Ms-DOS File handles.
When I move the Access database to the local drive everything works correctly and I don't get the error. What can I do to get it to work correctly from the Novell server?
Thanks for your help,
John
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Microsoft Access 97 Driver] Out of Ms-DOS File handles.
When I move the Access database to the local drive everything works correctly and I don't get the error. What can I do to get it to work correctly from the Novell server?
Thanks for your help,
John
do you have read/write access there ?
You are leaving your recordsets and connection strinngs open in your scripts, ensure you use Close on your conn and rs.
conn.Close
rs.Close
conn.Close
rs.Close
i dont think you can use mapped drives with access and ADO. anyway the performace will be terrible. if your using access make sure its on the same machine as the web server.
ASKER
Yes, and the power is plugged in and the machine is turned on :-) The database can be opened using MS Access on the NT Workstation from the network drive. The tables from a local database can not be linked to the database on the network drive though.
you may be able to open the database in access, but that means nothing, in ASP you are not accesing it via MS Access front end but rather a driver and ODBC
You can access mapped drives with ADO, and yes, performance is degrating...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
See microsoft KB : Q189408
okay so you can access access via mapped drives. i was under the impression that was not possible, i stand corrected.
>>Out of Ms-DOS File handles
it sound like either the OS has run out of filehandles or the user account that the db is being accessed under has a restriction on the number of filehandle and this has been reached. (bloddy Novell :|)
>>Out of Ms-DOS File handles
it sound like either the OS has run out of filehandles or the user account that the db is being accessed under has a restriction on the number of filehandle and this has been reached. (bloddy Novell :|)
Icecube, haven't we already discussed the issue of answering questions, especially if you do not know the true solution! Your solution ~might~ be the answer, but ONLY if JReynolds is using MDAC 1.5, (highly unlikely since IIS4 loads 2.1). From the "answer" you provided;
"...this problem can be caused by a combination of password synchronization being enabled and a bug in the Odbcjt32.dll version 3.51.1029 (Microsoft Data Access Components 1.5). That particular problem has been fixed in MDAC 2.0 and later."
Please do not lock questions by posting a "answer", especially a wrong one.
"...this problem can be caused by a combination of password synchronization being enabled and a bug in the Odbcjt32.dll version 3.51.1029 (Microsoft Data Access Components 1.5). That particular problem has been fixed in MDAC 2.0 and later."
Please do not lock questions by posting a "answer", especially a wrong one.
ASKER
Yes, and the power is plugged in and the machine is turned on :-) The database can be opened using MS Access on the NT Workstation from the network drive. The tables from a local database can not be linked to the database on the network drive though.
ASKER
Hey Icecube,
I am rejecting this answer for now to unlock the question. I tried earlier to not allow IIS to control the password and that didn't work. It is using MDAC 1.5, I don't know why but, it is. I'm going to upgrade to MDAC 2.0 or greater. If it works I'll select your answer.
John
I am rejecting this answer for now to unlock the question. I tried earlier to not allow IIS to control the password and that didn't work. It is using MDAC 1.5, I don't know why but, it is. I'm going to upgrade to MDAC 2.0 or greater. If it works I'll select your answer.
John
go to M$ and download MDAC 2.6 and JET 4.0, it has imrpoved my performace and reliablity orders
I find it hard to believe that you have MDAC 1.5 installed on a NT 4 Workstation running IIS4... What service pack are you using?
ASKER
Hey Icecube,
I am rejecting this answer for now to unlock the question. I tried earlier to not allow IIS to control the password and that didn't work. It is using MDAC 1.5, I don't know why but, it is. I'm going to upgrade to MDAC 2.0 or greater. If it works I'll select your answer.
John
I am rejecting this answer for now to unlock the question. I tried earlier to not allow IIS to control the password and that didn't work. It is using MDAC 1.5, I don't know why but, it is. I'm going to upgrade to MDAC 2.0 or greater. If it works I'll select your answer.
John
ASKER
Hey Icecube,
You were right on! We upgraded to MDAC 2.5 and it works. I spoke with the guy who installed IIS 4.0 and he doesn't know why it wasn't upgraded to 2.1.
Thank you,
John
You were right on! We upgraded to MDAC 2.5 and it works. I spoke with the guy who installed IIS 4.0 and he doesn't know why it wasn't upgraded to 2.1.
Thank you,
John
IIS 4 installs MDAC 2.1.
Perhaps you have no idea what you are running JR... Bu I guess a stab in the dark is better than no stab at all...
Perhaps you have no idea what you are running JR... Bu I guess a stab in the dark is better than no stab at all...
ASKER
Sorry everyone but, I didn't install the OS, Service Pack, or IIS 4 so I don't know why it still had the MDAC 1.5. The Workstation has Service Pack 6 on it so something must have replaced the newer files with old ones (must be a Microsoft thing).
Anyway, what a rough crowd of people you are, don't hold anything back just tell me like it is :-)..... Maybe I won't quit my day job.
Thanks again for all your help,
John
Anyway, what a rough crowd of people you are, don't hold anything back just tell me like it is :-)..... Maybe I won't quit my day job.
Thanks again for all your help,
John
Your welcome !
If somebody thinks the same error can occur when all updates are there on the server, try to recreate that situation and give me some feedback on how to do that !
If somebody thinks the same error can occur when all updates are there on the server, try to recreate that situation and give me some feedback on how to do that !