I'm having great difficulties deploying Project Professional 2007. I have a correct XML config file (i believe).

<Configuration Product="PrjPro">

<Display Level="Full" CompletionNotice="yes" SuppressModal="no" AcceptEula="yes" />

<Logging Type="standard" Path="%temp%" Template="Microsoft Office Project Professional Setup(*).txt" />

<PIDKEY Value="xxxxxxxxxxxxxxxxxxxxxxxxxx" />

<USERNAME Value="IT xxxxxxx" />

<COMPANYNAME Value="xxxxxx" />

<INSTALLLOCATION Value="%programfiles%\Microsoft Office" />


<SOURCELIST Value="\\xxxxxx\gpoinstall\Project Professional\SW_CD_Project_Pro_2007_W32_English_1_PA_BP_MLF_X12-19204\PrjPro.WW" />

<DistributionPoint Location="\\xxxxx\gpoinstall\Project Professional\SW_CD_Project_Pro_2007_W32_English_1_PA_BP_MLF_X12-19204\PrjPro.WW" />

<OptionState Id="OptionID" State="absent" Children="force" />

<Setting Id="Reboot" Value="IfNeeded" />

<Command Path="%WINDIR%\system32\msiexec.exe" Args="/i \\xxxxx\gpoinstall\Project Professional\SW_CD_Project_Pro_2007_W32_English_1_PA_BP_MLF_X12-19204\PrjPro.WW\PrjProWW.msi" QuietArg="/q" ChainPosition="after" Execute="install" />


The issue is, when its deployed, and a user logs onto their workstation, there are no shortcuts displayed, almost as if the apckage is published and not assigned.

When a user loads a project 2007 icon, it tried to install the rest of the Project package and fails to load project itself, just a desktop blank screen. Then if you try again, "Do you want to try loading Office Project 2007 in safe mode?"

Now im screwed, i have to manually uninstall the package as its unuseable at this point.

Also, in event viewer, the following is displayed:

[center]Detection of product '{90120000-003B-0000-0000-0000000FF1CE}', feature 'PROJECTFiles' failed during request for component '{43C3CF66-AA31-476D-B029-6D274E46F86C}'


[center]The description for Event ID ( 2001 ) in Source ( Microsoft Office 12 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Microsoft Office Project, Project failed to start correctly last time. Starting Project in safe mode will help you correct or isolate a startup problem in order to successfully start the program. Some functionality may be disabled in this mode.

Has anybody got any ideas?

Ive tried a new msi file incase the old one was corrupt, permissions, elevating user permissions. installing manually from the CD works fine by running the setp.exe file.

Thanks Guys, be gentle, im new here.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Are you trying to deploy to users or machines? IIRC, the former is explicitly stated as not being possible on MSDN. This was one of my current client's prime motivations for looking at SCCM for deployment, which is currently done per-user via GP.
Answered 03/17/2009 by: VBScab
Red Belt

Please log in to comment

Thanks, its assigned to a computer group policy. User settings are disabled in the GPO, except for when i was testing the elevated privilages.

All help is apprichated.

Answered 03/17/2009 by: mrflash
Yellow Belt

Please log in to comment
Actually, I think my question was a red herring. The 'Command' element I can see in your CONFIG.XML file is there for running other programs as part of the install. See here http://technet.microsoft.com/en-us/library/cc179195.aspx#ConfigxmlElementReference for details.

Comment that line out and try it again.
Answered 03/17/2009 by: VBScab
Red Belt

Please log in to comment
thanks for your reply. I removed the line, re-tried again and the same problem occured, the second error message as above, Office 12 AUX Error.

This time, it did take a little longer, but till failed.

any other thoughtS?

Answered 03/18/2009 by: mrflash
Yellow Belt

Please log in to comment
okay, i have fixed the problem.

It has turned out to be the way i referenced the office directory, instead of referencing the ProjectWW folder, point the distribution point to the root of the setup files, e.g. where setup.exe resides.

Thanks for your help anyway.
Answered 03/23/2009 by: mrflash
Yellow Belt

Please log in to comment