Fix: Groupwise won’t install on Windows Server 2003


Groupwise typically will not install on Windows Server 2003 due to DEP incompatibilities.  Data Execution Prevention (DEP) is a set of hardware and software technologies that perform additional checks on memory to help prevent malicious code from running on a system.

To resolve this issue:

1) Right click on My Computer > Properties

2) Select Advanced > Performance Settings > Data Execution Prevention

3) Select Turn on DEP for essential Windows programs and services only  > OK > OK

4) Reboot the Windows 2003 Server

See TID 3131386 for details on the Groupwise client crashing, TID 3564700 for details about not being able to install the Groupwise agents or administration files on Windows Server 2003.

For more details on DEP, see MS KB 875352.

7 Responses to “Fix: Groupwise won’t install on Windows Server 2003”

  1. joopbraak Says:

    What the fuck are you disabling DEP for? Just because a lousy programmed Novell vehicle doesn’t use memory allocation properly? Add Groupwise to the exceptions, no need to change the settings.

    • Julie Says:

      joopbraak-

      If it worked by just adding Groupwise to the exceptions, I would have included it in the instructions. It doesn’t work. Thanks for pointing out the obvious in such a charming manner.

      -Julie

  2. Japi Says:

    Joopbraak… wish it could have been that simple.
    Thanks Julie for the post. My RDP server is now up and running.
    The only thing stopping me from rolling out our new server was Groupwise not installing.

    Thanks once again

  3. Aaron Says:

    You rock. Been trying to solve this for 4 days. Tried every version of GW to no end.

    Thanks again,

    Aaron

  4. joopbraak Says:

    It works, you just didn’t try hard enough.

    Add these exceptions (still necessary with version 7.04):

    See http://www.picamatic.com/show/2009/1…28_617x406.png

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
    “C:\\WINDOWS\\system32\\mapisrvr.exe”=”DisableNXShowUI”
    “C:\\Novell\\GroupWise\\gwreload.exe”=”DisableNXShowUI”
    “C:\\Novell\\GroupWise\\gwsync.exe”=”DisableNXShowUI”
    “C:\\Novell\\GroupWise\\instwms.exe”=”DisableNXShowUI”
    “C:\\WINDOWS\\system32\\ml3xec16.exe”=”DisableNXShowUI”
    “C:\\Program Files\\Windows NT\\Windows Messaging\\exchng32.exe”=”DisableNXShowUI”
    “C:\\Program Files\\Windows NT\\Windows Messaging\\mlset32.exe”=”DisableNXShowUI”
    “C:\\WINDOWS\\system32\\mapisp32.exe”=”DisableNXShowUI”
    “C:\\Program Files\\Windows NT\\Windows Messaging\\scanpst.exe”=”DisableNXShowUI”
    “C:\\Novell\\GroupWise\\addrbook.exe”=”DisableNXShowUI”
    “C:\\Novell\\GroupWise\\grpwise.exe”=”DisableNXShowUI”
    “C:\\Novell\\GroupWise\\htrsetup.exe”=”DisableNXShowUI”
    “C:\\Novell\\GroupWise\\gwimpexe.exe”=”DisableNXShowUI”
    “C:\\Novell\\GroupWise\\notify.exe”=”DisableNXShowUI”
    “C:\\WINDOWS\\system32\\mdisp32.exe”=”DisableNXShowUI”
    “C:\\Novell\\GroupWise\\pdaconnect.exe”=”DisableNXShowUI”
    “C:\\Novell\\GroupWise\\40comupd.exe”=”DisableNXShowUI”

    Unbelievable huh? Groupwise sucks.

  5. joopbraak Says:

    Sorry, URL should be:

  6. KennDenn Says:

    joopbraak…

    I think you got your statement backwards, it should say…

    It’s disabled because a lousy programmed Microsoft vehicle doesn’t use memory allocation properly?


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: