Orkar inte skriva och förklara själv, men här får du lite svar som jag sprang på via google:
This error happened once again to me when I set up my ASP development environment on a newly installed Windows XP system. Here are possible causes for this error, which happens when you try to open a Jet DSN connection (or any connection to a MS Access database) from an ASP (or other) script:
1. the webserver environment needs "write" permission to the directory where the Access database resides. So, set permissions first. Go to Windows Explorer, Tools, Folder Options, View and turn off the very last entry in the list ("Use simple file sharing") if you haven't already done so.
2. Now, you'll have a "Security" tab when you right-click on a folder. Make sure you give write permission to the folder with the MS Access database to the "IUSR_***" account (with *** being your computer's name). This account is used by IIS, per default, to evaluate permissions for the default access to your local PWS website and scripts.
3. You can create your own User account by the way and set it as default for anonymous access of PWS. To do this, go to Control Panel, Administrative tools, Internet Information Server, expand "local computer," right-click on Websites (if you don't have this, add IIS from your Windows XP Pro CD. If you have Windows XP Home... tough luck you can't run a webserver, you have to upgrade.) Select "Properties," Directory Security, "Edit." Here you see the default account and logon. You can create another user account (under "Control Panel," "User Accounts") with another password and enter this here. BUT you don't have to do all this to take care of the error above; IUSR_<machine name> is fine for now. I digress...
4. Give the same user IUSR_<machine name> (or whatever is the default account) access to the TEMP directory of Windows. MS Access might need to write some stuff there.
5. Give the same account write permission in MS Access itself. These permissions can be reset by MS Access if you compact and repair the database so keep in mind to refresh this permission as necessary.
6. If you still get the error "[Microsoft][ODBC Microsoft Access Driver]General error Unable to open
registry key 'Temporary (volatile) Jet DSN for process", check that the database is really in the directory referenced by the DSN or the connection string in your ASP file! Also, check for misspellings in the file name. This was the reason for the error when I ran into it earlier this week.
