How to install GroupWise WebAccess on Windows 2003 server with IIS 6.

  • 7002400
  • 20-Jan-2009
  • 26-Apr-2012


Novell GroupWise WebAccess 5.5 EP
Microsoft Windows 2000 Server
Novell GroupWise WebAccess 6.5
Novell GroupWise WebAccess 6.0
Microsoft Windows 2003 Server
Novell GroupWise WebAccess


Install GroupWise WebAccess with IIS 6
Groupwise WebAccess with Windows 2003 Server
How to install GroupWise WebAccess on Windows 2003 server with IIS 6.


STEP ONE - Problem One with IIS 6: NO Scripts directory. Only Admin Scripts
Solution: Create a scripts directory
1. Go to c:\\inetpub\
2. Create a directory called "scripts"
3. Copy all files from AdminScripts to scripts
4. Go to IIS Services Manager
5. Expand Web Sites folder
6. Right Click on Default Web Site and select New--> Virtual Directory
7. Call the virtual directory "scripts" and point it to the directory created above.
8. Go into the Properties of the new "scripts" virtual directory.
9. Change the Execute Permissions to Scripts and Executables.
10. Change Application Protection to Low. (You will need to set the WWW service to run in IIS 5.0 Isolation Mode for this. See STEP THREE below to make this change.)

STEP TWO - Install WebAccess. Use the scripts directory. Replace default web page

STEP THREE - Problem Two with IIS 6.0: NO Application Protection
Solution: IIS 6 has a backward compatibility to IIS 5 Application protection. Here's how you get get the Low IIS Process option to show up.
1. Open IIS Manager.
2. Right-click Web Sites.
3. Click Properties.
4. Click Service tab.
5. There is a check box that says: Run WWW Service in IIS 5.0 Isolation Mode.
It is NOT checked by default. Check it.
6. You don't need to change Application Protection to Low because it does that by default. (To double check,do the following)
7. After IIS restart, right click on Web Sites.
8. Click Properties.
9. Click Home Directory.
10. You will see greyed out words at the bottom that say: "Application Protection" and then a drop down box that has selected in it: "Low IIS Process".

STEP FOUR - Problem Three When launching IIS and Web Access, you will get a 404, no file or directory found from the IIS server.
Solution: IIS 6 has extra security built up so that you can't run most service extensions unless you tell it to. This is new.
1. In IIS Manager, expand Web Sites folder
2. Click Web Service Extensions and in the right side of the screen, select allow access to all extensions.
3. Restart IIS to put setting into effect.
Alternatively you can add new extension instead of enabling all like statedabove inpoint 2. :
1. Go to Web Services Extensions (as stated)
2. In the right-hand pane, click on the link "Add a new web service extension"
3. In the "Name" field, call it GroupWise (name is not important)
4. In the "Required Files" field, the location of the file NSGISAPI.DLL needs to be listed. Browse to this file, which should be at C:\INETPUB\SCRIPTS\NSGISAPI.DLL.
5. Check the option that states "Set Extension Status to Allowed".
6. Click "Ok" and then confirm that the new extension shows up in the list of extensions and is "allowed".
7. Restart IIS to put setting into effect.

STEP FIVE - Problem Four Cannot Connect to Java Servlet Engine, no matter how you reinstall or what service pack you install, or what TID you use.
Solution: This one is complicated. Basically the JREW.exe that comes with the Web Access does NOT run on 2003. The answer is to find one that does. Check and find the latest available Sun Java code and install it. The J2SE 5.0 update 4 or later usually resolves a lot of issues.

1. A way to work around this is to run DNS/DHCP console on the 2003 server to see if that servlet works. In this case it did.
2. Copy the JRE, LIB, and NLS folder from the C:\\Program Files\\Novell\\DNSDHCP into the C:\\novell\\ directory.
3. Stop your web server and the WWW Publishing Service. Name the existing JVM directory to JVMold.
4. Rename the JRE folder to JVM. Restart your web server and WWW Publishing Service.

Note: If you receive the NULL screen (green screen) after selecting the 'GO' button, you may need to add ISAPI filter to your default web site.

1. Open IIS Manager
2. Right-click Web Sites
3. Click Properties
4. Select the ISAPI Filters tab.
5. Add "nsgisapi.dll" in the file name field.
6. Browse to the "Inetpub\scripts" folder and select "nsgisapi.dll"
7. Restart you web services

(The problem in STEP FIVE may also be due to a known Pentium 4 processor issue addressed in KB 10067216.)

STEP SIX - Problem with missing button names may occur (mainly seen in address books),Java AddressBook shows grey buttons, Speller doesshow only grey boxesand Java Calendar not showing appointments.Cause: The web server is not recognizing the .properties file extensions which hold that information.
Solution: MIME type map needs to be modified.
1. Open IIS Manager and expand Default Web Site.
2. Right click on the COM folder and go to 'Properties'.
3. Select 'HTTP Headers' tab.
4. Under MIME Type Map types add a new file type using "*" (without the quotes) for the associate extension and content type(MIME) fields.

Additional Information

Note** This is officially supported with Groupwise 6.5 Support Pack 3. 
If the setup starts and quits abruptly with no errors, the install location is missing subdirectories.  Makes sure the install is done from the complete SDD directory. 
Another Customer fixed their issue on Windows 2000 server by allowing ISAPI to run the NSGISAPI.dll as an allowed filter.
Formerly known as TID# 10085730