locked
Issue with sequencing of Office 2010 using a MSP file RRS feed

  • Question

  • Hello,

     

    I am sequencing Office 2010 Professional Plus for Windows XP SP3 following instructions available here: http://support.microsoft.com/kb/983462/en-us

    I have been able to complete the whole procedure and get a working APP-V package.

     

    Now I am trying to customize my Office 2010 setup using a MSP file.

    - setup.exe / admin

    - Creation of the MSP file and export to .\Updates directory

     

    If I execute setup.exe without APP-V sequencer monitoring, everything is working fine.

    If I am doing the same with APP-V, I am getting the following error message while setup.exe is loading:

    "A required ...\ProPlus.WW\OSETUP.DLL cannot be loaded. This may indicate that the file is missing or damaged".

    Any idea ?

    Tuesday, June 7, 2011 1:35 PM

Answers

  • Hello,

    Are you running the setup.exe from a local copy or from a network share?
    /Znack
    • Marked as answer by Sylvain06 Wednesday, June 8, 2011 7:50 AM
    Wednesday, June 8, 2011 5:21 AM

All replies

  • Hello,

    have you tried a different sequencer? 
    /Znack
    Tuesday, June 7, 2011 1:45 PM
  • Hello Znack,

     

    What do you mean ? Something else than APP-V (like Symantec product) ? 

     

    APP-V is my official solution in my context. I can't unfortunately affort to this kind of cross-check.

     

    Regards.

    Tuesday, June 7, 2011 5:25 PM
  • Hello,

    Different version, different machine (virtual v physical), different OS etc etc...
    /Znack
    Tuesday, June 7, 2011 5:37 PM
  • OK.... 

     

    I just did a new trial using a Virtual PC VM (was using VMWare ESX VM before). I got exactly the same behavior.

    In both trials, I used Windows XP SP3 (targeted platform, we are not using Windows 7 yet).

     

    Regards.

     

    Wednesday, June 8, 2011 4:38 AM
  • Hello,

    Are you running the setup.exe from a local copy or from a network share?
    /Znack
    • Marked as answer by Sylvain06 Wednesday, June 8, 2011 7:50 AM
    Wednesday, June 8, 2011 5:21 AM
  • I tried both assuming network share may be the root cause. But no change.
    Wednesday, June 8, 2011 7:13 AM
  • Thanks for the link but it does not apply in my case.

     

    However I did a new trial running setup.exe from a local drive and it works ! 

    I am not sure why it has not worked the first time, and why it does not work from a network share but it is an acceptable work-around for now.

    Thanks a lot for the suggestion.

     

    Regards.

    • Proposed as answer by znack Wednesday, June 8, 2011 8:01 AM
    Wednesday, June 8, 2011 7:50 AM