Unable to Open ODBC Registry Key

Ask a Question related to ASP Database, Design and Development.

  1. #1

    Default Unable to Open ODBC Registry Key

    Hi:

    Using MS Access in a server-side application (Win2k Adv.
    Server, IIS 6, ASP) we suddenly are getting the following
    error on most pages:

    Microsoft OLE DB Provider for ODBC Drivers
    error '80004005'

    [Microsoft][ODBC Microsoft Access Driver]General error
    Unable to open registry key 'Temporary (volatile) Jet DSN
    for process 0x5fc Thread 0x11c DBC 0xc79014 Jet'.

    This happens trying to open a database using a File DSN,
    such as:

    Set cnnActive = Server.CreateObject("ADODB.Connection")
    cnnActive.Open = "FILEDSN = c:\.....\Active.dsn","admin,""

    We checked the various knowledge base articles which all
    point to a permissions problem in the registry at:

    HKEY_LOCAL_MACHINE/Software/ODBC

    but the permissions appear to be correct on both
    workstation and server.

    Could the problem be linked to setting a database
    connection with the same name to nothing in previous
    pages, such as:

    Set cnnActive = Nothing

    Any suggestions?

    Thanks.

    GrahamC Guest

  2. Similar Questions and Discussions

    1. Problem connecting to local Access database - Unable to open registry key 'Temporary (volatile) Jet DSN ...
      Hi I get the following error sporadically when running a sample in an MSDN ASP tutorial: Microsoft OLE DB Provider for ODBC Drivers: General...
    2. Unable to open registry key 'Temporary (volatile) Jet DSN
      Hi Guys I was wondering if you could help. Basically I have an ASP page that inserts details from a standard form into an Access DB and even...
    3. Unable to Open Registry Key
      Hello; I've published my database using Frontpage and inserted a result query on a ASP page and I get the following error. Can anyone help me? ...
    4. IIS 5 - General error Unable to open registry key
      ( - also posted on inetserver.iis) Hi I am a web programmer with an ASP-based website on my webhosts server (Win2000, IIS 5) which references...
    5. ADODB.Connection - Unable to open registry key 'Temporary (volatile) Jet
      Jon wrote: http://www.aspfaq.com/show.asp?id=2062 - updatable cursor http://www.aspfaq.com/show.asp?id=2009 - 80004005 errors Bob Barrows
  3. #2

    Default Re: Unable to Open ODBC Registry Key

    Don't use a file dsn. Use an OLE DB connection string from
    [url]www.connectionstrings.com[/url]. If you must stick with your ODBC usage, give
    IUSR write permissions on %temp% (system, not user variable). I believe
    that can be a cause of this issue.

    Ray at work

    "GrahamC" <grahamc@inetix.com> wrote in message
    news:048e01c37706$83af51c0$a101280a@phx.gbl...
    > Hi:
    >
    > Using MS Access in a server-side application (Win2k Adv.
    > Server, IIS 6, ASP) we suddenly are getting the following
    > error on most pages:
    >
    > Microsoft OLE DB Provider for ODBC Drivers
    > error '80004005'
    >
    > [Microsoft][ODBC Microsoft Access Driver]General error
    > Unable to open registry key 'Temporary (volatile) Jet DSN
    > for process 0x5fc Thread 0x11c DBC 0xc79014 Jet'.
    >
    > This happens trying to open a database using a File DSN,
    > such as:
    >
    > Set cnnActive = Server.CreateObject("ADODB.Connection")
    > cnnActive.Open = "FILEDSN = c:\.....\Active.dsn","admin,""
    >
    > We checked the various knowledge base articles which all
    > point to a permissions problem in the registry at:
    >
    > HKEY_LOCAL_MACHINE/Software/ODBC
    >
    > but the permissions appear to be correct on both
    > workstation and server.
    >
    > Could the problem be linked to setting a database
    > connection with the same name to nothing in previous
    > pages, such as:
    >
    > Set cnnActive = Nothing
    >
    > Any suggestions?
    >
    > Thanks.
    >

    Ray at Guest

  4. #3

    Default Re: Unable to Open ODBC Registry Key

    [url]http://www.aspfaq.com/2154[/url]
    [url]http://www.aspfaq.com/2009[/url]




    "GrahamC" <grahamc@inetix.com> wrote in message
    news:048e01c37706$83af51c0$a101280a@phx.gbl...
    > Hi:
    >
    > Using MS Access in a server-side application (Win2k Adv.
    > Server, IIS 6, ASP) we suddenly are getting the following
    > error on most pages:
    >
    > Microsoft OLE DB Provider for ODBC Drivers
    > error '80004005'
    >
    > [Microsoft][ODBC Microsoft Access Driver]General error
    > Unable to open registry key 'Temporary (volatile) Jet DSN
    > for process 0x5fc Thread 0x11c DBC 0xc79014 Jet'.
    >
    > This happens trying to open a database using a File DSN,
    > such as:
    >
    > Set cnnActive = Server.CreateObject("ADODB.Connection")
    > cnnActive.Open = "FILEDSN = c:\.....\Active.dsn","admin,""
    >
    > We checked the various knowledge base articles which all
    > point to a permissions problem in the registry at:
    >
    > HKEY_LOCAL_MACHINE/Software/ODBC
    >
    > but the permissions appear to be correct on both
    > workstation and server.
    >
    > Could the problem be linked to setting a database
    > connection with the same name to nothing in previous
    > pages, such as:
    >
    > Set cnnActive = Nothing
    >
    > Any suggestions?
    >
    > Thanks.
    >

    Aaron Bertrand - MVP Guest

  5. #4

    Default Re: Unable to Open ODBC Registry Key

    Hi

    Check your web directory security.


    "GrahamC" <grahamc@inetix.com> wrote in message
    news:048e01c37706$83af51c0$a101280a@phx.gbl...
    > Hi:
    >
    > Using MS Access in a server-side application (Win2k Adv.
    > Server, IIS 6, ASP) we suddenly are getting the following
    > error on most pages:
    >
    > Microsoft OLE DB Provider for ODBC Drivers
    > error '80004005'
    >
    > [Microsoft][ODBC Microsoft Access Driver]General error
    > Unable to open registry key 'Temporary (volatile) Jet DSN
    > for process 0x5fc Thread 0x11c DBC 0xc79014 Jet'.
    >
    > This happens trying to open a database using a File DSN,
    > such as:
    >
    > Set cnnActive = Server.CreateObject("ADODB.Connection")
    > cnnActive.Open = "FILEDSN = c:\.....\Active.dsn","admin,""
    >
    > We checked the various knowledge base articles which all
    > point to a permissions problem in the registry at:
    >
    > HKEY_LOCAL_MACHINE/Software/ODBC
    >
    > but the permissions appear to be correct on both
    > workstation and server.
    >
    > Could the problem be linked to setting a database
    > connection with the same name to nothing in previous
    > pages, such as:
    >
    > Set cnnActive = Nothing
    >
    > Any suggestions?
    >
    > Thanks.
    >

    Mario b. Guest

  6. #5

    Default Solution: Unable to Open ODBC Registry Key

    Thanks to all; we did in fact switch to a OLE string and
    it it both solved the issue and improved database
    connectivity.

    For others interested, we switched from:

    Set cnnActive = Server.CreateObject ("ADODB.Connection")
    cnnActive.Open "FILEDSN=c:\<dsn
    path>\active.dsn","admin",""

    to:

    strOLEDB = "Provider=Microsoft.Jet.OLEDB.4.0;"
    strOLEDB = strOLEDB & "Data Source=C:\<database
    path>\active.mdb;"
    strOLEDB = strOLEDB & "User ID=admin;Password=;"

    Set cnnActive = Server.CreateObject ("ADODB.Connection")
    cnnActive.Open strOLEDB

    Thanks again.

    >-----Original Message-----
    >Hi:
    >
    >Using MS Access in a server-side application (Win2k Adv.
    >Server, IIS 6, ASP) we suddenly are getting the following
    >error on most pages:
    >
    >Microsoft OLE DB Provider for ODBC Drivers
    >error '80004005'
    >
    >[Microsoft][ODBC Microsoft Access Driver]General error
    >Unable to open registry key 'Temporary (volatile) Jet DSN
    >for process 0x5fc Thread 0x11c DBC 0xc79014 Jet'.
    >
    >This happens trying to open a database using a File DSN,
    >such as:
    >
    >Set cnnActive = Server.CreateObject("ADODB.Connection")
    >cnnActive.Open = "FILEDSN = c:\.....\Active.dsn","admin,""
    >
    >We checked the various knowledge base articles which all
    >point to a permissions problem in the registry at:
    >
    >HKEY_LOCAL_MACHINE/Software/ODBC
    >
    >but the permissions appear to be correct on both
    >workstation and server.
    >
    >Could the problem be linked to setting a database
    >connection with the same name to nothing in previous
    >pages, such as:
    >
    >Set cnnActive = Nothing
    >
    >Any suggestions?
    >
    >Thanks.
    >
    >.
    >
    GrahamC Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139