driver specified.
the most common cause is that the connection string is a session variable initialized in the Global.asa and Global.asa is not firing. You may check to see that the variable is being initialized correctly by adding the following code to the .asp page: <%= "'auth_user' is " & request.servervariables("auth_user")%> <%= "'auth_type' is " & request.servervariables("auth_type")%> <%= "connection string is " & session("your_connectionstring")%>
- If the Global.asa is not firing, check to make sure it is in an Application Root for IIS 4.0, or a Virtual Root with the "Execute" check box selected if running under IIS 3.0. Also, a bug detailed in the Microsoft Knowledge Base article Q173742, may prevent the Global.asa from being fired when Windows NT permissions have restricted access to the folder.
- The DSN name is not found. Check to make sure a 'User' type DSN is not being used.
- If using a File or System DSN, try changing the connection string to "DSN=MySystemDSN" or "DBQ=MyFileDSN" as appropriate. Simplify!
- Check to make sure that the most current drivers are installed. If in doubt, download the latest MDAC (Microsoft Data Access Components) from the following Web site:
Error Message ------------- Microsoft OLE DB Provider for ODBC Drivers error '80004005' Microsoft][ODBC Microsoft SQL Driver] Logon Failed() Cause -----
-This error is generated by SQL server if it does not accept or recognize the logon account and/or password being submitted (if using Standard security) or if there is no Windows NT account to SQL account mapping (when using Integrated security).
-If you are using standard security, the SQL account name and password are incorrect. Try the system Admin account and password (UID= "SA" and NULL password). These must be defined on the connection string line. DSN's do not store user names and passwords.
-If using Integrated security, check the Windows NT account that is calling the page, and find out what account (if any) it is mapped to.
-SQL does not allow an underscore in a SQL account name. If someone manually mapped the Windows NT IUSR_machinename account to a SQL account of the same name, it fails. Map any account that uses an underscore to an account name on SQL that does not use the underscore.
Error Message ------------- Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server Driver][SQL Serve
上一页 [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] 下一页
|
