Software Deployment

Hi Jim:

As the package is already in production u can go for modifying this registry key value. Try making the value of this registry key to blank

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-181\Products\XXXXXXXXXXXX\Features\Complete

where XXXXXXXXXXX is the product code (for word in ur case) and make the value of the key value of complete to blank.

What you have there is an application conflict. A component in Planet FM (a file, registry key or something) is "stepping on the toes" of a similar component in Office 2003 (again, a file, registry key or something). Planet FM makes a change to a key component of Office, and when launched Office detects the change, considers itself corrupted and tries to fix it.

The good news is the proper way to fix this is to leave Office 2003 intact. Focus on the Planet FM package. If you're using Wise or InstallShield, go over the conflict management documentation to use utilities that will find the overlap. If you're using a "budget" repacking tool, well... now you know why people shell out the $$$ for the good stuff. Going through it manually might be possible, but definitely akin to finding the needle in the haystack.

Start out by looking in the Application Log for the Windows Installer log event for the Office repair. It will tell you what Office component triggered the self repair. Look in your Office package to find out exactly what is in that component (without changing/saving anything). Then open your Planet FM package and find the stuff you found in the Office component and determine what change would be necessary to prevent the Office self repair.

You can also refer to the eventviewer after/ when the office goes to repair.. it will give you the product code of office and the component code which makes the self repair.. you can then check it out with the files/registry in the component..

Thanks for the advice; VikingLoki and slb;

I didn't want to have to re-post but am getting a bit of strange outcome to troubleshooting this damn self repair.

The PlanetFM application as part of its install also loads Crystal Decisions that gets installed to C:\ProgFile\Common Files\Crystal Decisions\2.0\bin
And also C:\ProgFile\Sybase\SQL Anywhere 7.

I have had a look at the Application log as suggested and identified the Component GUIDs it references.
I have since gone to the MSOffice MSI and opened it via Wise and identified the file the CompGUID references - C:\windows\IME\SOFTKBD.dll
From there I have also checked the PlanetFM wsi file for any reference to the component GUIDs and file - there are none.

I have also used the conflict DB within Wise to identify any files/reg keys that are displaying errors/warnings with Office and the only 2 files that I have since identified are;
GDIPLUS.dll
UNICOWS.dll
These are installed into the Crystal Decisions DIR that I mentioned above and therefore had thought these would be isolated components. Although in hindsight in my newer snapshots I have used the GDIPLUS and UNICOWS.dlls from the Wise repository that MSOffice uses to ensure these are not what are causing the conflict.

The next step of a Raw install of PlanetFM on standard build with MSOffice to see if this causes the self repair - It does not cause the same self repair within Office so obviously it is something caught during the setup capture process.

Finally the steps I am looking at to resolve this issue is firstly I have removed all the registry keys installed with the package to identify whether it is file or registry that is causing Office to self repair. Currently I have nailed to down to being one of the 1268 files that are resolved and am now removing these in different version of the package to see what fixes the problem.

Along side this I have repackaged the app again using a local Repackage.ini file which excludes no files as have had this catch me out with previous packages.

Seems a tad drastic and convoluted way of getting the answer but when you get no help from these app vendors what other alternatives do you have!?!?!?!

If you have any other advice I could use in the meantime I am always happily open to suggestions!!!!

Cheers
Jim

Hi VikingLoki,

I am using WPS 5.6 here so will have a look and see what I can find.

Much appreciated with the prompt post.

Jim

That's what I meant... sorry if it was unclear.

"Start out by looking in the Application Log" [in the Event Viewer]