Article

johnso_j's picture
article
Reads:

13619

Score:
0
0
 
Comments:

8

Viewing Properties of a GroupWise Message prompts user to install GW}00001.TMP

Author Info

19 March 2009 - 1:10pm
Submitted by: johnso_j

Author Blog
Author Profile

Tags

Tags Map

(View Disclaimer)

Environment:

Novell GroupWise 7
Novell GroupWise 8
Novell GroupWise 8 Hot Patch 1

Problem:

When attempting to see the properties of a GroupWise message you are prompted to download the file GW}00001.TMP

Solution:

This is related to an issue with Microsoft XML.

A few ways to resolve the issue:

  1. Register MSXML4 DLL: run regsvr32 c:\windows\system32\msxml4.dll
  2. Install MSXML 4.0 SP2
    http://www.microsoft.com/downloads/details.aspx?di...
  3. If you’re deploying GroupWise with ZEN, update the GroupWise MSI to install the redistributable MSXML4 SP2.
    1. Using Admin Studio editor open the GroupWise MSI
    2. Under Redistributables select MSXML4 SP2 for XP and 2k if needed.
    3. Save your MSI

Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.



Related Articles


User Comments

ukdtom's picture

Nice, but wrong ;-)

Submitted by ukdtom on 19 March 2009 - 10:04pm.

The reason is, that the GroupWise.msi for some reason doesn't install the MSXML on some workstations :-(

Simply run the file named \client\win32\msxml.msi

If you are deploying using Zen, make this file a dependency, instead of messing with the actual MSI file

And note, that if talking about GW8, W2K is not supported

johnso_j's picture

I know MSXML is not

Submitted by johnso_j on 31 March 2009 - 12:14pm.

I know MSXML is not installed it is because inside the MSI it is not selected as a redistributable. Why would I want to create another application object or add a script to the object when I can just fix the issue?

ptenhoopen's picture

View files

Submitted by ptenhoopen on 27 March 2009 - 11:09am.

This happened to us after upgrading to 8.0.0 HP1 from 7.0.3 HP1. This only affected version 7 clients. I solved it by creating a new \ofviews\win folder for the PO, starting with the view files from version 7's SDD and overlaying the files from the 8 SDD.

jsepanik's picture

Anti-Virus Software Deleting Views

Submitted by jsepanik on 6 April 2009 - 7:37am.

We had the same problem. We found that several view files were missing. For some reason our AV software was identifying them as viruses and removing them. We used ZEN to restore any missing files, and the problem was fixed. We reconfigured the AV system not to scan the view files and the problem has not returned.

louwrie's picture

System Restore

Submitted by louwrie on 20 April 2009 - 4:18am.

I have tried registering XML (as in option 1 above) once before. It only worked for a day or so and the problem returned. I then disabled Windows XP System Restore and then fixed the problem again. This time it stayed fixed.

avanrav's picture

Might be the local profile

Submitted by avanrav on 8 October 2009 - 1:17pm.

I had this problem mysteriously crop up on just one machine. Tried the above solutions but no luck. I renamed the users profile and let workstation manager create a new profile and this solved the problem.

turky's picture

Copy over View files

Submitted by turky on 26 February 2010 - 10:15am.

As posted by ptenhoopen on 27 March 2009 - 1:00am.
I tried the same thing, I copied the 7.03HP4 view files into the 8.01 PO_DIR\OFVIEWS\WIN directory, then copied the 8.01 view files on top of them, seems to work OK so far.

This is on a test system, so unsure if it will "stay fixed", as other posters seem to indicate some of these fixes don't "stick"

lehner's picture

msxml4 sp3 solves problem

Submitted by lehner on 26 July 2011 - 6:00am.

After installing KB973685 (http://support.microsoft.com/kb/973685) properties work fine again

© 2013 Novell