<％= ''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 server] login failed- user: reason: not defined as a valid user of a trusted sql server connection. cause ----- -
-integrated security is turned on in the sql enterprise manager, and the windows nt account being used has not been mapped to a sql account. –
-try changing sql to use standard security (in enterprise manager, select server/ sql server/configure[ascii 133]/security options/standard. - if running under iis 4.0, turn off 'password synchronization' for that project.
error message ------------- microsoft ole db provider for odbc drivers error '80004005' [microsoft][odbc sql server driver][dbmssocn] general network error. check your network document cause -----
-this may occur when a sql server computer is renamed. dsn's that reference the old name fail when the computer name cannot be located
which parameter listed below are store in metabase: (choose two)
iis help file location
virtual directory security settings
web site home directorylocation
microsoft management console snap-in definitions.
microsoft site server express content analyzer toolbar positions
answer:2,3