Environment
Novell GroupWise 7 Support Pack 1
Novell GroupWise 7 Support Pack 2
Novell GroupWise 7 Client for Windows
Microsoft Windows XP Professional
Microsoft Windows XP Professional Support Pack 2
Novell GroupWise 7 Support Pack 2
Novell GroupWise 7 Client for Windows
Microsoft Windows XP Professional
Microsoft Windows XP Professional Support Pack 2
Situation
When a user wants to see the properties of a Groupwise message, they get
prompted for a download of the files such as GW}00001.TMP, GW}00003.TMP or
gwprops.css
This happens only in cases where the client was not installed properly by the administrator and the user rights to the Windows systems were limited to a minimum.
This can apply to both Workstation only and a Windows Network environment.
This happens only in cases where the client was not installed properly by the administrator and the user rights to the Windows systems were limited to a minimum.
This can apply to both Workstation only and a Windows Network environment.
Resolution
1] Install the GroupWise 7.01 IR1 or newer version of
the GW client for Windows, making sure that you have sufficient rights to do so
for all users
This means in a non-Microsoft Networking environment you need administrator rights to the workstation.
In a Microsoft Networking environment you need to be Administrator to the domain this workstation belongs to.
This means in a non-Microsoft Networking environment you need administrator rights to the workstation.
In a Microsoft Networking environment you need to be Administrator to the domain this workstation belongs to.
2]Install
MSXML 4.0 Service Pack 2
Available at Microsoft download page
3]Another way to have this fixed:
Available at Microsoft download page
3]Another way to have this fixed:
Add the following keys to the registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{88d969c3-f192-11d4-a65f-0040963251e5}\
@="XSL Template 4.0"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{88d969c3-f192-11d4-a65f-0040963251e5}\InProcServer32] @=hex(2):43,3a,5c,57,49,4e,44,4f,57,53,5c,53,79,73,74,65,6d,33,32,5c,6d,73,78, 6d,6c,34,2e,64,6c,6c,00 "ThreadingModel"="Both"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{88d969c3-f192-11d4-a65f-0040963251e5}\ProgID] @="Msxml2.XSLTemplate.4.0"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{88d969c3-f192-11d4-a65f-0040963251e5}\Version] @="4.0"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{88d969c3-f192-11d4-a65f-0040963251e5}\InProcServer32] @=hex(2):43,3a,5c,57,49,4e,44,4f,57,53,5c,53,79,73,74,65,6d,33,32,5c,6d,73,78, 6d,6c,34,2e,64,6c,6c,00 "ThreadingModel"="Both"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{88d969c3-f192-11d4-a65f-0040963251e5}\ProgID] @="Msxml2.XSLTemplate.4.0"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{88d969c3-f192-11d4-a65f-0040963251e5}\Version] @="4.0"
Make sure you test this
last solution in your test environment before mass distribution of these
keys