10 replies
by chrandrob
Could be a code problem totally unrelated to the server. Are you declaring "option explicit"? If so, and I recommend that you do, then I sometimes get this error if I have an undimmed variable -- or if I have a redimmed variable -- instead of the expected runtime error. An incorrect include reference may also cause this.
Do you have another server you can test the page on to rule out the server? Even a Win 9x running PWS will do. I do local testing on a NT Workstation running PWS before moving code to a test NT Server running IIS without any problems related to system differences.
If you get the error on another server, then you need to go through your code.
by gtork
by gbworld
This is not, repeat, not an ASP not installed problem. You have some sort of error on the server, either in the script or something corrupt in the ASP engine.
Try running regsvr32 on asp.dll and rule out a corrupt ASP engine.
Next, you need tofind the error in your script. Best bet on this is to turn off all on error resume next and find the first spot of error. Repeat until all errors are eradicated.
I saw the suggestion of Option Explicit. I recommend this, but it is unlikely to find the error. It is great for discovering typos, which are more likely to cause logical errors (wrong answer) than syntax errors (500 error conditions - blow ups).
If you can use this with PWS and IIS 4- then you most likely you have some code that is ASP 2.0 (IIS 4) compliant that has been changed in ASP 3.0 (IIS 5).
It is also possible that you are missing some DLLs that your scripts rely on and have on error resume next set on the original instantiation.
If all ASPs blow up, a corrupt ASP.dll file is a possibility. If only some, another option is you do not have the proper provider for your database. Installing the latest MDAC from www.microsoft.com/data should solve this.
Gregory A. Beamer
MCP: +I, SE, SD, DBA
by gtork
by chrandrob
Are you using any include files? I upgraded my desktop to W2K this week and had to register .inc as an ASP include file before pages that included one could be displyed.
Save the following code as an ASP page on your server and see if it displaysokay:
<%@ Language=VBScript %>
<%option explicit%>
<%
Dim dbConn
Dim item
Set dbConn = Server.CreateObject("ADODB.Connection")
Response.write "ADO Version: " & dbConn.Version & "
"
For each item in Request.ServerVariables
Response.write "" & Request.ServerVariables.Key(item) & ": " & Request.ServerVariables.Item(item) & "
"
Next
%>
by gtork
by gtork
After digging deeper, I found that the following error shows up in the event log right after I try to access an ASP page:
"DCOM got error "Logon failure: unknown user name or bad password. " and was unable to logon .\IWAM_computername in order to run the server:
{3D14228D-FBE1-11D0-995D-00C04FD919C1}"
by gtork
by gtork
by gtork
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending