Configuration hints for MSII
Keywords: MS IIE
I am trying to get webbatch to work with IIS 2.0 on Windows NT 4.0 build 1381.
I believe I have successfully entered in the proper temporary ID and access
code, but whenever I do a simple command in webbatch the server returns: CGI
Error The specified CGI application misbehaved by not returning a complete
set of HTTP headers. The headers it did return are:
Then if I try and view the source, here is what I get:
Error in CGI Application
The specified CGI application
misbehaved by not returning a complete set of HTTP headers.
Any ideas as to what I am doing wrong?
Well, it's some sort of configuration problem. Here are some
data points to look into:
- 1) What is the physical directory name where webbatch is installed?
Should be on the server someplace.
- 2) What is the virtual directory name defined in the server manager?
We suggest webcgi
- 3) What are the read/execute setting defined for the virtual directory?
Should be execute
- 4) What are the NTFS file permissions for the physical directory?
The dummy user MSII users needs to be able to at least read the directory.
I have a similar setup and had similar problems.
There were two ways I could get webbatch to work.
1. Check Registry settings:
- Go into regedit32
- Check to see if you have a key
- CreateProcessAsUser: REG_DWORD
- If you don't have this key you can create it.
- Then set it's value to 0.
- This has security implications for CGI scripts,
- but check MSIIS help for more info.
2. You may be having file security problems.
- Webbatch needs to have read and execute permissions
on 5 (or is it 6) files in the WINNT directory.
- There are 800+ files in the directory. I had a list
of the requisite files but I lost it.
- To check you can either TEMPORARILY give full control
of the c: drive to the anonymous user or it is quicker to
use the Internet Service Manager WWW Service properties
to change the Anonymous Logon user to the systems administrator.
- If this works you have to work out how to give adequate
permissions and still be secure ???
The main issues to getting this working revolve around:
- Set up virtual directory with execute permission.
- Set security setting to directory so that the IIS default user can at least read the directory.
- Look in event log, webbatch log, and server logs for helpful error messages.
Article ID: W12485
Filename: MSIIS Installation Notes Volume 2.txt
File Created: 2017:07:28:13:58:13
Last Updated: 1999:04:15:16:47:34