Wrox Programmer Forums

Need to download code?

View our list of code downloads.

| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Beginning ASP 3.0 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old November 6th, 2008, 02:31 PM
Registered User
Join Date: Apr 2008
Location: , , .
Posts: 5
Thanks: 0
Thanked 1 Time in 1 Post
Default Microsoft Jet connection problem

I am working on classic asp and using Microsoft JET Database Engine to connect to my Access database. It was working fine Windows XP pro, but now I upgraded to Vista with IIS7. I got an error message “Microsoft JET Database Engine error '80004005’ Unspecified error”
“Provider cannot be found. It may not be properly installed”

This is my connection string
MM_xx_STRING = "PROVIDER=Microsoft.Jet.OLEDB.4.0; Data Source=" & ("E:\wwwroot\xxxxx\xxx.mdb")

please help don’t know what to do here!!! :(

Thank you

The Following User Says Thank You to istcomnet For This Useful Post:
  #2 (permalink)  
Old November 6th, 2008, 03:47 PM
Wrox Author
Points: 13,255, Level: 49
Points: 13,255, Level: 49 Points: 13,255, Level: 49 Points: 13,255, Level: 49
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Oct 2005
Location: Ohio, USA
Posts: 4,104
Thanks: 1
Thanked 64 Times in 64 Posts
Send a message via AIM to dparsons

IIS 7 does not play well with ASP / Access by default.


From the article:
Access and Classic ASP
A lot of people use Access as a database - because it is small, can be copied around, and is easy to manage. One of the changes we made in IIS7 in Vista broke using ASP and Access by default. I described this change in more detail in this post, but essentially it has to do with the fact that Application Pools now use the Application Pool identity's profile and temporary directory, rather than \windows\temp by default. And since the only one that can write to Network Service's temp directory is the Network Service, anonymous or authenticated ASP applications break, since ASP uses the impersonated identity to access the database. If you use ASP and Access on IIS7, you've probably seen this error, or a variation of it:
Microsoft JET Database Engine error '80004005'
Unspecified error
The answer is pretty straight forward: turn off loadUserProfile, or ACL the temp directory to allow writes. As a result of this and other compatibility issues, we're considering reverting this change in Longhorn Server / Vista SP1. In the mean time, you can work around it by doing either of the following:
This appcmd command will turn off loadUserProfile for the Default Application Pool. if your application runs in a different AppPool, make the corresponding change:
%windir%\system32\inetsrv\appcmd set config /section:applicationPools /[name='DefaultAppPool'].processModel.loadUserProfile:false
This command will ACL the Network Service temp directory to allow creator write / read privledges. If you run your Application Pool under a different identity, you'll need to ACL that owner's temp directory:
icacls %windir%\serviceprofiles\networkservice\AppData\Lo cal\Temp /grant Users:(CI)(S,WD,AD,X)
icacls %windir%\serviceprofiles\networkservice\AppData\Lo cal\Temp /grant "CREATOR OWNER":(OI)(CI)(IO)(F)


================================================== =========
Read this if you want to know how to get a correct reply for your question:
================================================== =========
.: Wrox Technical Editor / Author :.
Wrox Books 24 x 7
================================================== =========
  #3 (permalink)  
Old July 1st, 2011, 04:54 AM
Registered User
Join Date: Jan 2011
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts

Thanks for sharing that reply.

I have however tried all of this and more, with no luck at all. I'm running Windows 7 IIS 7.5

SQL works fine, however I am just unable to get Access mdb files accessible from asp pages.

Any suggestions appreciated.
  #4 (permalink)  
Old February 27th, 2013, 09:31 AM
Registered User
Points: 6, Level: 1
Points: 6, Level: 1 Points: 6, Level: 1 Points: 6, Level: 1
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Jan 2013
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts

if you just updated your OS try to locate "c:\Windows\Temp" this folder might have been deleted.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Microsoft.Jet.OLEDB.4.0 not registerd on local m/c raychoudhury BOOK: Beginning Visual Basic 2005 Databases ISBN: 978-0-7645-8894-5 0 January 2nd, 2008 02:23 PM
Microsoft SQL Server 2005 Connection Problem dontknowmuch Java Databases 0 March 7th, 2006 11:49 PM
Microsoft JET Database Engine (0x80040E14) tks_muthu Classic ASP Databases 5 January 1st, 2005 10:17 PM
Microsoft JET Database Engine (0x80040E14) HaverkPJ Classic ASP Databases 2 November 16th, 2004 11:25 PM
Microsoft JET Database Engine (0x80040E10) knight Classic ASP Databases 12 June 9th, 2004 01:07 AM

All times are GMT -4. The time now is 03:29 PM.

Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.