Link to home
Start Free TrialLog in
Avatar of shooby
shooby

asked on

Problems running asp pages in IIS 5.0

Hi there...  I'm having  a weird issue with IIS (running on windows 2000 server).  My asp pages are getting an "HTTP 500 - Internal server error " when i try to open them in my browser.  I tested by opening a simple "hello world" with an .htm extension and it opens just fine.  But when i change the extension of that very same page to .asp i get the HTTP 500 error.

I'm hoping someone can shed some light on this.  Thanks a lot!
Avatar of qh0st
qh0st

How are you accessing your page? If you have an asp file inside your IIS wwwRoot folder, you should access it by

http://your_ip_goes_here/file_name.asp

I think you are probably accessing it locally on you machine. You can't access an asp page by

C:\Inetpub\wwwroot\file_name.asp

However, an html extension file would show fine that way. This is just an assumption of what you are doing wrong. Let me know more about this if this isn't the case.

-qh0st

To see a more detailed error message than "HTTP 500 - Internal Server error", do this:

(In IE) Tools, Internet Options, Advanced tab, then UNcheck the "Show friendly HTTP error messages" box...

Then rerun your code and you should see a more detailed error description...
how did you view your .html page? something like this: c:\inetpub\folder\files.html ? i guess

if you saved your asp page in the c:\inetpub\wwwroot\ folder then try to open:
http://localhost/yourpage.asp ...
Avatar of shooby

ASKER

hi....

yes, i am accessing my page with:  http://localhost/default.asp

i took off the "friendly HTTP error message" and i got this error message instead:  "Server Application Error
The server has encountered an error while loading an application during the processing of your request. "

This is quite the pickle......<confused>  Can anyone tell me what that means, and how i can rectify it?
Avatar of shooby

ASKER

.....missed the last part of that error message....  "The specified metadata was not found."
Ok, I think some more information is necessary.

1.  Could you post your hello world code so we could see if there might be a problem there?

2.  If you want more detailed ASP error code,  add a virutal directory to IIS:
         Its Alias would be "IISHelp"  and it maps to c:\winnt\help\iishelp
         Then go to the default website folder's properties.  Take a look under the Custom Errors Tab.  
          Edit the 500;100 entry so that the message type is a URL and the URL is /iisHelp/common/500-100.asp

3  Once you have all this, let us know if there is anymore information available for your problem.

Best of Luck,
Michael E. Payne Jr.
Systems Developer
Avatar of shooby

ASKER

hello all....

this is my code for both .asp & .htm:

<html>
<head>
<title>Untitled Document</title>
</head>

<body bgcolor="#FFFFFF" text="#000000">
hello
</body>
</html>

I added the virtual directory, etc...etc... as you suggested and i'm getting the same error message:
"Server Application Error
The server has encountered an error while loading an application during the processing of your request. The specified metadata was not found"

Thoughts?

Thanks.....

ok, lets start by re-enabling the show friendly error messages.


I'm quite certain that something in you IIS config is not quite right, and almost guaranteed that its in the application configuration.  So if you could post what you have configured for that here, I may be able to get some more info on it.

Best of Luck,
Michael E. Payne Jr.
Systems Developer
Avatar of shooby

ASKER

Can u be a bit more specific please....  what kind of config info should i post?  u mean the website properties?

My apologies.  Sometimes I forget that I think too fast for my, and everyone else's own good.

The configuration you should look at first if the application configuration.

Open the properties for the directory where the pages are going to run (the root in this case I believe)

Go to the Home Directory Tab

We would need to see the Application Settings on the bottom part of that tab, as well as whats under the configuration button.


Did re-enabling the show friendly error messages display something different?

Best of Luck,
Michael E. Payne Jr.
Systems Developer
Avatar of shooby

ASKER

heyyyy....

i'm back to the "HTTP 500 - Internal server error "  message...   :(

The Application Settings are as follows:   Application name:           Default Application
                                                                 Starting Point:                <Dex '03>   ~~~this is what i named the site
                                                                 Execute Permissions:     Scripts and Executables
                                                                 Application Protection:   Medium (Pooled)

In the Configuration is the following:

(In App Mappings)
Extension                  Executable Path                                       Verbs

.asp                           C:\WINNT\System32\inetsrv\asp.dll         GET,HEAD,POST,TRACE
.cer                            C:\WINNT\System32\inetsrv\asp.dll         GET,HEAD,POST,TRACE
.cdx                            C:\WINNT\System32\inetsrv\asp.dll         GET,HEAD,POST,TRACE
.asa                           C:\WINNT\System32\inetsrv\asp.dll         GET,HEAD,POST,TRACE
.htr                            C:\WINNT\System32\inetsrv\ism.dll          GET,POST
.idc                            C:\WINNT\System32\inetsrv\httpodbc.dll   OPTIONS,GET,HEAD,POST,PUT,DELETE,TRACE
.shtm                         C:\WINNT\System32\inetsrv\ssinc.dll          GET,POST
.shtml                         C:\WINNT\System32\inetsrv\ssinc.dll         GET,POST
.stm                            C:\WINNT\System32\inetsrv\ssinc.dll          GET,POST
.printer                        C:\WINNT\System32\msw3prt.dll                GET,POST

(In App Options)
checked are:  enable session state
                      enable buffering
                      enable parent path

(In App Debugging)
checked are:  enable asp server-side script debugging
                      send detailed asp error message to client

See anything wrong with it?
Okie Dokie, now I'm pretty sure I know whats up...

Try This:

1.  Click Start, click Programs, click Administrative Tools, and then click Computer Management to open the Computer Management console.

2.  In the left pane, expand Local Users and Groups, and then click the Groups folder.

3.  In the right pane, right-click the Users group, and then click Properties.  Click Add.

4.  In the Select Users or Groups dialog box, locate the Look in drop-down box, and then select the local computer.

5.  Select Authenticated Users, and then click Add. Select INTERACTIVE, and then click Add. Click OK, click Apply, and then click Close to close the properties for the Users group.

6.  In the left pane, expand Services and Applications, and then click Services.

7.  In the right pane, right-click IIS Admin Service, and then click Restart.

8.  In the Restart Other Services confirmation dialog box, click Yes.


The reason why IIS is doing this is because the NT AUTHORITY\Authenticated Users or NT AUTHORITY\INTERACTIVE entries have been removed from the Users group.

I bet that if you open event viewer you'll find an entry like so in the system log:

Event ID: 10010
User: NT AUTHORITY\SYSTEM
Description: The server {3D14228D-FBE1-11D0-995D-00C04FD919C1} did not register with DCOM within the required timeout.
This error message is followed in the event log by a warning message like the following:
Source: W3SVC
Event ID: 36
User: N/A
Description: The server failed to load application 'AppPath'. The error was 'Server execution failed'.

Hope that one works for ya.

Best of Luck,
Michael E. Payne Jr.
Systems Developer
Avatar of shooby

ASKER

Hi  Peign......

it didn't work out..  i checked my event viewer and the error message i got was:
"The server failed to load application'/LM/W3SVC/4/Root.  There was no such interface supported."

This thing is driving me crazy!!!!!  i even went as far as to re-install IIS once before hoping it would solve the problem, but it didn't change anything :(
ASKER CERTIFIED SOLUTION
Avatar of Peign
Peign

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
g1 Peign!
Avatar of shooby

ASKER

you rock peign!

:)

thanks a lot!  you have no idea how much i appreciate your help!!! (i was almost dying there.........)  ....and learned much on the way to the answer..  thanks, thanks, thanks!
I'm glad that worked, but there is a bigger issue, and it can be solved with some more work.  After you do it, you can set the application protection settings to anything you want.  Heres the problem (taken from technet)...

SYMPTOMS
When you browse to an existing Active Server Pages (ASP) page, the browser may return the "HTTP 500 - Internal server error" or "Server Application Error" error message. If you review the server's System Event Log after you receive the error message, two entries appear:
Source: W3SVC
Error: Configured identity is incorrect
-and-

Source: DCOM
Error: Unable to logon IWAM_ComputerName
If you enable only Basic Authentication for the application and set the Application Protection to Low, the application starts to work again as expected. In addition, if you create a new ASP application after you receive this error, you can browse to it without any errors.
Related Error Messages
You may also receive the following error messages:

In your browser:
HTTP 500 - Internal server error
-or-

Server Application Error
The server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for assistance.
In the System Event Log:
Source: DCOM
Error: DCOM got error "Logon Failure: unknown username or bad password" Unable to logon .\IWAM_SERVERNAME in order to run the server.
-and-

Source: W3SVC
Error: "The server failed to load application '/LM/W3SVC/1/Root/op.' The error was 'The serverprocess could not be started because the configured identity is incorrect. Check the username and password.
-or-

Source: W3SVC Error: "The server failed to load application '/LM/W3SVC/4/Root'. The error was 'c000003b'."
-and-

Source: W3SVC Error: "The COM Application '{3D14228D-FBE1-11d0-995D-00C04FD919C1}' at '/LM/W3SVC/4/Root' failed to activate out of process."
CAUSE
User names and passwords for the IUSR_ComputerName and IWAM_ComputerName accounts are stored in three locations:


Internet Information Server (IIS) metabase
User Manager for Domains (Windows NT) or Local Users and Groups (Windows 2000)
Microsoft Transaction Server (Windows NT) or Component Services (Windows 2000)
If the user names and/or passwords are not synchronized among these three locations, you receive the above-mentioned error messages.
RESOLUTION
To resolve this problem, you must make sure that the passwords for the IUSR and IWAM accounts are synchronized in all three of the above-mentioned locations. There are two ways to achieve this: you can set the password for IWAM and IUSR accounts in User Manager (Windows NT) or Users and Groups (Windows 2000) and change the passwords in IIS metabase to reflect the same password, or vice versa. Use one of the following methods to synchronize the passwords.

NOTE: Please refer to the "More Information" section for instructions on how to use the Administration Script Utility (Adsutil.vbs) and how to change the password in Microsoft Transaction Server (MTS) or Component Services.
Method 1: Change the Passwords in User Manager or Users and Groups to Match the IIS Metabase Password
In the Command window, locate the folder that contains the Adsutil.vbs file. Use the Adsutil.vbs tool to obtain the passwords for the IWAM and IUSR accounts from the IIS metabase.
To change the IUSR and/or IWAM passwords in Windows NT, follow these steps:


From the Start menu, point to Programs point to Administrative Tools, and then click User Manager for Domains. In User Manager for Domains, you can change the account information for all Windows NT user accounts and groups.
Double-click the IUSR_ComputerName and/or IWAM_ComputerName users, and modify the passwords so that they reflect the IIS metabase password that you obtained in step 1.
To change the IUSR and/or IWAM passwords in Windows 2000, follow these steps:
From the Start menu, point to Programs, point to Administrative Tools, and then click Computer Management.
Under the System Tools node, click to expand the Local Users and Groups and Users nodes. In the User node, you can change the account information for all Windows 2000 user accounts and groups.
Right-click the IUSR_ComputerName and/or IWAM_ComputerName accounts, and then click Set Password.
Modify the passwords so that they reflect the IIS metabase password that you obtained in step 1.
Browse to the ASP page that returned the error message to check if the problem has been resolved.
Method 2: Change the IIS Metabase to Match the IUSR and/or IWAM Passwords
To change the IUSR and/or IWAM password in Windows NT, follow these steps:


From the Start menu, point to Programs, point to Administrative Tools, and then click User Manager for Domains. In User Manager for Domains, you can change the account information for all Windows NT user accounts and groups.
Double-click the IUSR_ComputerName and/or IWAM_ComputerName accounts, and type new passwords.
To change the IUSR and/or IWAM password in Windows 2000, follow these steps:
From the Start menu, point to Programs, point to Administrative Tools, and then click Computer Management.
Under the System Tools node, click to expand the Local Users and Groups and Users nodes. In the User node, you can change the account information for all Windows 2000 user accounts and groups.
Right-click the IUSR_ComputerName and/or IWAM_ComputerName accounts, and then click Set Password. Type new passwords.
In the Command window, locate the folder that contains the Adsutil.vbs file. Use the Adsutil.vbs utility to set the passwords for the IWAM and IUSR accounts in the IIS metabase.
Browse to the ASP page that returned the error message to check if the problem has been resolved.
NOTE: Although the passwords in Microsoft Transaction Server (Windows NT) and Component Services (Windows 2000) usually match the IIS metabase, update the IWAM password in Microsoft Transaction Server (MTS) or Component Services if the problem still occurs. For more information, see the "How to Change the Password in MTS or Component Services" portion of the "More Information" section.