Troubleshooting Microsoft Error Messages - MACROMEDIA DREAMWEAVER MX 2004-USING DREAMWEAVER Use Manual

Troubleshooting Microsoft error messages

This section describes some common Microsoft error messages and ways to troubleshoot them.
These errors can occur if you use Internet Information Server (IIS) with a Microsoft database
system such as Access or SQL Server. These errors normally occur when you request a dynamic
page from the server.
Note: Macromedia does not provide technical support for third-party software such as Microsoft
Windows, and IIS. If this section does not fix your problem, please contact Microsoft technical
support or visit the Microsoft support website at http://support.microsoft.com/.
For more information on 80004005 errors, see "INFO: Troubleshooting Guide for 80004005
Errors in Active Server Pages and Microsoft Data Access Components (Q306518)," on the
Microsoft website at http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306518.
80004005—Data source name not found and no default driver specified
This error occurs when you attempt to view a dynamic page in a web browser or in Live Data
mode. The error message may vary depending on your database and web server. Other variations
of the error message include:
•
80004005—Driver's SQLSetConnectAttr failed
•
80004005—General error Unable to open registry key 'DriverId'
Here are possible causes and solutions:
•
The page can't find the DSN. Make sure a DSN has been created on both the web server and
on the local machine. For more information, see
•
The DSN might have been set up as a user DSN, not as a system DSN. Delete the user DSN
and create a system DSN to replace it.
Note: If you don't delete the user DSN, the duplicate DSN names produce a new ODBC error.
•
If you use Microsoft Access, the database file (.mdb) might be locked. The lock might be due
to a DSN with a different name accessing the database. In Windows Explorer, search for the
lock file (.ldb) in the folder containing the database file (.mdb) and delete the .ldb file. If
another DSN is pointing to the same database file, you may want to delete the DSN to prevent
the error in the future. Be sure to reboot the computer after making these changes.
80004005—Couldn't use '(unknown)'; file already in use
This error occurs when you use a Microsoft Access database and attempt to view a dynamic page
in a web browser or in Live Data mode. Another variation of this error message is "80004005—
Microsoft Jet database engine cannot open the file (unknown)."
The probable cause is a permissions problem. For more information, see
permissions problems" on page
•
The account being used by Internet Information Server (usually IUSR) might not have the
correct Windows permissions for a file-based database or for the folder containing the file.
Check the permissions on the IIS account (IUSR) in the user manager.
•
You might not have permission to create or destroy temporary files. Check the permissions on
the file and the folder. Make sure you have permission to create or destroy any temporary files.
Temporary files are usually created in the same folder as the database, but the file may also be
created in other folders such as /Winnt.
"Using a DSN" on page
489. Here are some specific causes and solutions:
Troubleshooting Microsoft error messages
751.
"Troubleshooting
491