Discussion Locked

IIS 5.0 doesn't display ASP pages.

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Ever since installing the CODE RED update for IIS 5.0, we have been unable to run ASP on our server. We get a 500 Internal Server Error displayed in the browser. With the friendly error message in the browser turned off we get "The RPC server is unavailable." After hitting refresh we then get "The requested resource is in use." We have uninstalled IIS, Re-installed IIS, Re-installed W2k SP2, Re-installed the Code Red Update, restarted the computer many times to no avail. Please advise.

10 replies

by cportman

This isn't what you want to hear, but you are most likely going to have to reformat the entire machine. Thats what we had to do after getting hit.

cp

by mk admin

Not what I wanted to hear. This is also our Exchange 2000 Server so a restore is not a quick task. OWA works fine, but it doesn't use ASP now.

There has got to be another way>>>

by cportman

Thats strange OWA works. You probably checked this, but make sure in IIS your execute permissions are set to scripts and executables.

good luck

cp

by mk admin

I have checked all permissions. OWA with Exchange 2000 doesn't use ASP. I can display HTML pages, but not ASP.

by curacao_dejavu

check MS KB Article ID: Q163166

SUMMARY
This article explains how to fix the following Microsoft Internet Information Server (IIS) error:

500 Server Error. Specified Module could not be found

MORE INFORMATION
When a Web browser (such as Internet Explorer 3.0) invokes an ISAPI DLL on the IIS, the server may display the above error message. The reason for this error is that one or more DLLs on which the ISAPI DLL directly or transitively depends is either not installed on the IISserver or the DLLs are located in a directory that IIS does not search. If this is the case, IIS sends back to the browser an HTTP status code 500, which the browser then displays as the above error message instead of the expected output from the ISAPI DLL.

To fix this situation, copy all the DLLs on which your ISAPI DLL directly or transitively depends to the System32 directory of the IIS server.

A very common cause for this problem is building an ISAPI DLL using the ISAPI Wizard in Visual C++, using the share libraries option, and then not having the Visual C++ and MFC runtime DLLs installed on the IIS server. The Visual C++ and MFC runtime DLLs typically needed are the following.

For Visual C++ 4.2 Debug:

Msvcrtd.dll
Mfc42d.dll
For Visual C++ 4.2 Release:

Msvcrt.dll
Mfc42.dll
For Visual C++ 4.1 Debug:

Msvcrtd.dll
Mfc41d.dll
For Visual C++ 4.1 Release:

Msvcrt.dll
Mfc41.dll
To generically determine which DLLs you need to install on your IIS server, use either the DUMPBIN utility that ships with Visual C++ (use the /imports option), or the Quick View facility of Windows Explorer (if it is installed) to view what DLLs your ISAPI DLL depends on. Either program provides you with a list of dependent DLLs. Remember you may need to repeat this process for any DLLs listed to determine transitive DLL dependencies.

regards,

Leopold

by mk admin

We are not using any custom ISAPI dll's. All asp does not work. Including pages that are really html pages with the asp extension.

by dc1

In IIS Manager check the default directory tab, click configuration and make sure that the app mapping for asp is configured. The IISLockdn tool by default (I will assume that the hotfix does the same) changes the .asp mapping.

This discussion is closed to new replies.