From MicroFocusInternationalWiki
Revision as of 17:21, 19 April 2007 by Jmarton (Talk | contribs) (High Level Install Steps - Scinario 1)

Jump to: navigation, search

> my other wikis

GroupWise Mobile Server Quick Start

GroupWise Mobile Server Documentation

  1. Methods for removing GroupWise Mobile Server
  2. GroupWise Mobility Online Documentation
  3. Secure Gateway PDF
  4. GMS Install Guide

Scenario 1

  • Secure Gateway Server (Private NIC x.x.x.12) (Public NIC x.x.x.5)
  • GroupWise Mobile Server (x.x.x.11)
  • MS SQL server (x.x.x.10)
  • POA (x.x.y.10)

High Level Install Steps - Scenario 1

  1. Install the Secure Gateway (Install the secure gateway 1st)
    1. REBOOT! Don't try to restart services, you MUST reboot
  2. After the Secure Gateway Server has been rebooted install the GMS on the GMS server
    1. With GMS 2, ensure IIS is disabled!!!
    2. Note that the NW client MUST be installed on the GMS Server if you plan to use "Trusted App".
    3. Note One can NOT select "Trusted App" during the install, this must be done later.
    4. Note, if you get MSI errors 1601 etc, try running chkdisk /f (run on next reboot)
    5. After the install go to Services and ensure all 4 Services have user credentials. Note that only one service has the correct credentials. Ensure all 4 have user credentials.
    6. Address to Secure gateway is very picky. Here is an example tcp://ipOfSecureGateway:8865 Note you need the localhost AND the Secure Gateway's address.
    7. Reboot the GMS server
  3. Setup Accounts
    1. Go the http://IpAddrOfGMSbox | login as a GroupWise user | set your timezone info | often you'll want to select the left hand side to send a text/SMS message to your phone in order to download the GMS client.


  1. Any changes requires a restart of services (Generally).
  2. netstat -na | more look for ports that are common
    1. Secure Gateway on the public NIC shoud be listening on port 3102, 80 and 443 (incoming from the Internet)
    2. Secure Gateway Private NIC should be listening on 8865
    3. Secure Gateway Private NIC should be listening on port 80
    4. POA should be listening on SOAP port 7191
    5. GMS Server should be listening on 80 and 8191
  3. Important GMS troubleshooting URLs
    1. From the GMS server go to: If you can go to this, with success then your system is registered with intellisync.
    2. http://IpAddrOfGMSbox/sgadmin
    3. http://IpAddrOfGMSbox/sgadmin/status.html One of the most helpful URLS
    4. http://IpAddrOfGMSbox/admin/diag
    5. Note, if your internal DNS is not correct. It appears to use some kind of v-hosting, so you'll need to go to it by DNS name! So hack the c:\windows\system32\driver\hosts put the IPaddress
  4. If the authentication source is removed in GMS then all of the users authentication sources will be changed to intellisync instead of GroupWise even if you repopulate the authentication source and each needs to be changed manually back to GroupWise.
  5. If a single user was syncing, and now it's stopped working, try a hard reset of the device. If that doesn't solve it, try to delete the user from GMS and perform a second hard reset of the device.
  6. If none of the users are syncing and nothing new appears in the WebPIM, yet a restart of GMS causes new items to appear initially but then no new additional items appears after that, verify that no firewall is blocking port 8191/tcp from the POA to GMS.
  7. Enabling sync on an address book where there are thousands of contacts in the corresponding mobile device's category may cause 820E errors on the user's user database to appear in the POA. If this happens, you will have to delete and recreate the user in GMS. Then do not enable syncing for that address book/category. The user will need to recategorize the contacts, making sure that the categories which are configured to sync do not contain as many contacts.
  8. When initially installing the client on PalmOS (e.g., Treo 700p), and you enable an address book to sync for an existing category, the contacts which exist on the mobile device in that category will not sync to GroupWise. You will have to "touch" each contact by clicking edit and then ok on the device. Even though no changes have been made, timestamps are updated allowing the contacts to sync to GW. (Note: This was true of GMS 1.0. I do not know if this still applies to GMS 2.0.)

Additional TIDs for GMS

  1. More then 2 gigs or memory on the server causing Internal Server Error - ASP error
  2. Methods for removing GroupWise Mobile Server
  3. Is GMS supported on VMWare?

Things needed to be done before a call is opened and escalated with Nokia

  1. Current log files when the problem is occuring along with any specific info regarding any users or occurance that is happening.
  2. GMS Version?
  3. How much memory on the server if more then 2 gigs have you changed the registry?
  4. Has a reset and or delete of the user with the problem made any difference?
  5. What database they are using.
  6. Do they have a multiple server setup ie do they have the database on a different server then the one gms services are running on?
  7. If they have just updated the server have they restarted the server?
  8. If database is running on a different server then the GMS services do the services have rights to the remote server?
  9. If issue seems to be device specific have they done a hard reset on the device?
  10. If using trusted app and mail flow stops working have you regenerated a trusted app key?