Novell is now a part of Micro Focus

Installing GroupWise WebAccess on Windows 2003 Server using IIS

Novell Cool Solutions: Tip
By Jamie Glendinning

Digg This - Slashdot This

Posted: 14 Apr 2005


When Installing GroupWise WebAccess on a Windows 2003 server using IIS and the Novell Servlet Engine, the install completes but does not work. Additional configuration needs to be carried out.


There is a tid that covers some of the issues in installing GroupWise 6.5 WebAccess onto 2003 server

I have found it very helpful but would modify the process slightly.



  • Windows 2003 Server STD edition
  • Server has a c:\ and d:\ drive.
  • IIS installed and wwwroot - set to default (C:\Inetpub\wwwroot)
  • All GroupWise components installed to d: (including WebAccess install)

Initial IIS Configuration:

  • The GroupWise WebAccess install application wants to install components to a "Scripts" Directory under the Default Website.
  • We need to set up a scripts folder: (this is the same as in the TID)
    1. Copy C:\Inetpub\AdminScripts to C:\Inetpub\Scripts
    2. Open "Internet Information Services (IIS) Manager"
    3. Right click on Default Web Site (under Websites)
    4. Select New --> virtual directory
    5. This will open the Virtual Directory Creation Wizard.
    6. Select Next
    7. Create an Alias called "Scripts"
    8. Select next
    9. Point this to C:\Inetpub\Scripts
    10. Select next
    11. Adjust the permissions to include Execute
    12. Select next
    13. Select finish

Install WebAccess:

  1. Next run the WebAccess Gateway Install pointing all paths to d:\ apart from IIS related paths.
  2. Select the Microsoft Internet Information Services (IIS) for NT/2000 install option (GW6.5 sp3 and above are supported on 2003 server)
  3. When prompted for Java Servlet Engine - accept Novell Servlet Gateway
  4. Complete the install with appropriate values.
  5. Restart your mta,poa,webaccess and iis.
  6. point your browser to the servers address. you should get the Novell GroupWise web services page.
  7. Select English from the drop down box. then select go.

You might get the GroupWise WebAccess login page. I don't. I get 404 error Page not found.

We now need to look at what needs to be changed to get this to work. I felt that more information was needed.

First of all some useful info - default log directories:

  • IIS logs to: C:\WINDOWS\system32\LogFiles\W3SVC1\
    ie: ex050407.log
    at the moment this log file has several 404 error messages.

  • Novell Servlet gateway logs to: D:\novell\java\servlets\
    These logs should indicate that the WebAccess and Spelling Servlet have loaded successfully.
    If there are any error messages - these will need to be resolved (and are beyond the scope of this article (at the moment)).

  • WebAccess gateway logs by default to: D:\novell\WebAccess\logs

In order to get rid of our 404 error we need to get the NSGISAPI.DLL to work properly.

The TID recommends allowing access to all the web extensions. this is not necessary.

If we configure the NSGISAPI.dll as a Web Service Extension - WebAccess should start to work.

To do this:

  1. Open "Internet Information Services (IIS) Manager"
  2. Right Click on "web Service Extensions" folder
  3. Select Add a new Web Service Extension
  4. Set Extension name: NSGISAPI
  5. Select Add - C:\Inetpub\Scripts\NSGISAPI.dll
  6. Put a tick in the "set Extension Status to allowed
  7. Select ok.
  8. Restart IIS and your WebAccess Gateway.

WebAccess should now run successfully.

Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions.

© Copyright Micro Focus or one of its affiliates