Cyberherbalist's questions

I am being asked to resurrect a classic ASP application for temporary use. Wonderful. Well, the pay's the same, so I am now trying to get the thing to run on my localhost so I can test it and so on. I have copied all the files to c:\inetpub\wwwroot\ClassicASPapp. Using IIS 7.5 I set this folder as an Application I get handed a 503. Same result if I make it a Virtual Directory.

HTTP Error 503. The service is unavailable.

Note that there is a file in wwwroot called "iisstart.htm". If I double-click on the file from Windows Explorer, the browser displays the rendered HTML correctly. If I try to navigate to the file using:

http://localhost/iisstart.htm

I get the 503 then, too.

What is going on? Is there some global setting I need to change? Note that this is a new Windows 7 workstation.

I've checked and Classic ASP is definitely installed. The web site is associated with an application pool that has Classic ASP enabled, and 32-bit applications are also enabled.

Event Log:

Log Name:      System
Source:        Microsoft-Windows-WAS
Date:          8/8/2014 2:42:49 PM
Event ID:      5002
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESD71906.EClient.wa.lcl
Description:
Application pool 'DefaultAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" />
    <EventID Qualifiers="49152">5002</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-08-08T21:42:49.000000000Z" />
    <EventRecordID>40664</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>DESD71906.EClient.wa.lcl</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="AppPoolID">DefaultAppPool</Data>
    <Binary>
    </Binary>
  </EventData>
</Event>

It is true that the application pool gets stopped.

Test Connection / Authorization Detail:

The server is configured to use pass-through authentication with a built-in account to access the specified physical path. However, IIS Manager cannot verify whether the built-in account has access. Make sure that the application pool identity has Read access to the physical path. If this server is joined to a domain, and the application pool identity is NetworkService or LocalSystem, verify that \$ has Read access to the physical path. Then test these settings again.

When users want to log into one of our servers, the default domain is set to the machine name instead of the organization's domain, which is to say that the domain dropdown shows the machine name in the text part, while the organizational domain does appear in the dropdown (populated by the network, I assume).

I have heard that one may set a default domain to appear instead of the machine name, and I need this to be that way. I expect it's a registry entry, but I have given up finding one which applies.

Can someone please tell me how to do this?

I'm installing a custom application on a brand new Windows 2003 Server. A couple of DLLs need to be added and registered, and I have copied them to the server in the C:\WINDOWS\System32 folder -- which is where they have always been when we've had the application running on Windows NT and 2000.

However, when I try to register them using:

regsvr32 c:\windows\system32\nameoflibrary.dll

It gives back:

LoadLibrary("c:\windows\system32\nameoflibrary.dll") failed - 
The specified module could not be found.

The DLL is however right there. I can see it. If I copy the path to Windows Explorer and attempt to run it, it tells me that I can't run a DLL, so I know it's there. One minor complication is that the DLLs were built in VB5 -- but the VB5 runtime is installed on the server, so this shouldn't be a problem.

Any ideas?

An application under IIS6 on a Win 2003 server uses BROWSCAP.INI to detect browser and version, but it hasn't yet been updated to detect IE 9, so the code checking for browser and vesion can't find anything and presents an error message to the user that they need IE 4 or greater. I have been unable to find the information on MSDN or in a web search.

I did manage to find an entry on the IIS blog that said IIS7 detects both IE8 and IE9 just fine, but darn it we're still running IIS6.

Does anyone have or know where I can find the code for the BROWSCAP.INI that enables detection of IE9?

Edited to add: incidentally, I made what seemed would be the obvious additions to the text of BROWSCAP.INI (e.g. adding a node that reads:

[IE 9.0]
browser=IE
Version=9.0
majorver=#9
minorver=#0
frames=True
tables=True
cookies=True
backgroundsounds=True
vbscript=True
javaapplets=True
javascript=True
ActiveXControls=True
Win16=False
AK=False
SK=False
AOL=False
Update=False

... and this doesn't make any difference.

Edited further to add:

What is running on the web server in question is a classic ASP script in VBScript that uses the MSWC component to retrieve from IIS information on which browser the user is using. When the user's browser "hits" the server up for a file, it passes along this information to IIS via the "HTTP_USER_AGENT" string. IIS parses out the relevant information using its browscap.dll component and the browscap.ini file to do so.

Some sample code:

set objBrowserType = Server.CreateObject("MSWC.BrowserType")

MSWC.BrowserType passes an object with a number of properties, including the identity of the browser and its version, as well as other properties such as whether it understands javascript, and so on. The problem is, it is not detecting IE 9 properly and this seems most likely to be because the browscap.ini file doesn't contain the relevant information required to help it do so.

I have a server that is running all versions of .NET Framework, from 2.0 up to 4.0. An application I need to deploy won't run correctly on later versions, and was originally compiled for 1.1. Is it safe to install version 1.1 on the machine without causing any problems with the later versions?

Edited to add:

To the accepted answer I must comment on how it went after actually installing .NET 1.1. It went fine, except there was one problem that occurred. Sql Server 2005 Developer Edition was on the machine, and after 1.1 was installed, Sql Server Management Studio was no longer working correctly, and had to be removed and re-installed. Only a small problem, but noteworthy.