MS Jet DSN Error - unable to open registry key

Here is the error I am getting while trying to open a database with the help of a DSN file. I am opening an access2002 database from an asp script for getting the email addresses. Here are the details of the error.

Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0x9e8 Thread 0x9dc DBC 0x109699c Jet'.
/emailconnect.asp, line 4

and on line 4 all I am doing is opening the FILEDSN:
objConn.Open "FILEDSN=C:\Program Files\Common Files\ODBC\Data Sources\email_dsn.dsn"

My FILEDSN looks like this :
[ODBC]
DRIVER=Microsoft Access Driver (*.mdb)
UID=admin
UserCommitSync=Yes
Threads=3
SafeTransactions=0
PageTimeout=5
MaxScanRows=8
MaxBufferSize=2048
FIL=MS Access
DriverId=25
DefaultDir=C:\Inetpub\wwwroot
DBQ=C:\Inetpub\wwwroot\email.mdb

I looked up on the internet and found a few articles about this. They talk about setting the permissions on the TEMP dirs and on the DB files. I have tried all that. Somewhere I found this article which talks about IIS having permission to the registry keys. I am not sure how to check this.

"The error is also quite common if the permissions on the server are incorrect. Check that IIS has sufficient permissions to access the registry and that the correct permissions, read and write, are set on the directory containing the database and the database itself, for the IUSR account."

Please can someone advise me. I have been cracking my brains out to find a solution somewhere.

Maybe something here can help.

http://www.dougscode.com/forum4/topic.asp?TOPIC_ID=17

Thanks Doug,
I got the problem fixed. Thanks for your help.
I added IUSR_<PC_NAME> and gave it full rights to the TEMP folder used by the IIS server and also gave it full rights to the c:/Inetpub/wwwroot folder. Still it complained initially, but after giving it permissions to the database.mdb file, it ran smoothly.
Somehow the permissions were reset after installing some of the windows updates.
Thanks for all your help again,
Sammy