locked
Having 2 Start-Process Scripts in the same package (App-V 5.0) RRS feed

  • Question

  • I have a package with 2 applications

    each one of the applications need to start a different start-process script

    so I can config the deploymentconfig to run sript 1 for application 1

    but how do I do it now for application 2\script 2?

    from what I saw - I can add only one start-process script .

    tried to add 2 and <Startprocess> and then it says the xml is damaged

    thanks


    Tamir Levy

    Monday, September 30, 2013 5:59 AM

Answers

  • The schema for the deployment configuration file only allows one StartProcess element.

    <xs:element name="StartProcess" type="v1.0:CT_ScriptWithArgsWithRunInVEAndAppID" minOccurs="0"/>

    Since there is no maxOccurs attribute, its value is one (1), meaning the StartProcess element can appear a maximum of one time.

    Wednesday, October 2, 2013 11:28 AM

All replies

  • Hello,

    Make a copy

    Change the script

    CHange the applicationID


    Nicke Källén | The Knack| Twitter: @Znackattack

    Monday, September 30, 2013 7:39 AM
  • that's what I did.

    this is how edited my deployment config file

    <StartProcess RunInVirtualEnvironment="true">
      <Path>[Script1]</Path>
      <Arguments</Arguments>
      <Wait RollbackOnError="true"/>
      <ApplicationId>[ApplicationID1]</ApplicationId>
    </StartProcess>
    <StartProcess RunInVirtualEnvironment="true">
      <Path>[Script2]</Path>
      <Arguments</Arguments>
      <Wait RollbackOnError="true"/>
      <ApplicationId>[ApplicationID2]</ApplicationId>
    </StartProcess>

    when I try to set the new deployment file via PowerShell locally or via Admin console I get an error message

    Set-AppvClientPackage : XML document could not be loaded because it is invalid. Please supply a valid XML document
    Please consult AppV Client Event Log for more details.
    Operation attempted: Configure AppV Package.
    AppV Error Code: 050009000A.

    when there's more than one <StartProcess> the deploymentconfig fails. you're welcome to try it yourself

    that's why I posted this question

    expecting to get some news :)

    thanks


    Tamir Levy

    Monday, September 30, 2013 11:09 AM
  • Hello,

    See this article;

    http://support.microsoft.com/kb/2778945


    Nicke Källén | The Knack| Twitter: @Znackattack

    Monday, September 30, 2013 11:15 AM
  • Hi Nicke.

    thanks for the try, even though this article has the same error description it has nothing to do with my issue if you noticed.

    the error is a general issue when something's wrong with the xml, and has nothing to do with case sensitive or not in my case.

    as I said.

    I can have an XML that has one <StartProcess></StartProcess>

    when it has more than one - I cannot import it !

    any help will be appreciate

    
    

    Tamir Levy

    Monday, September 30, 2013 12:38 PM
  • Hello,

    Well, apparently it seems unsupported. A design change could requested by opening a support ticket with Microsoft I suppose


    Nicke Källén | The Knack| Twitter: @Znackattack

    Tuesday, October 1, 2013 5:38 AM
  • that's a shame

    I must say it's about the 20th feature I found which is available in App-V 4.x and was removed or accidently removed from App-V 5.0 :/

    thank you for your help nick


    Tamir Levy

    Tuesday, October 1, 2013 12:38 PM
  • The schema for the deployment configuration file only allows one StartProcess element.

    <xs:element name="StartProcess" type="v1.0:CT_ScriptWithArgsWithRunInVEAndAppID" minOccurs="0"/>

    Since there is no maxOccurs attribute, its value is one (1), meaning the StartProcess element can appear a maximum of one time.

    Wednesday, October 2, 2013 11:28 AM
  • Thanks for your answer Aaron,

    are you saying it's something that can be changed?

    is that a normal limitation? have only one script type per package?


    Tamir Levy

    Wednesday, October 2, 2013 1:03 PM
  • That schema is embedded within the App-V client, so it would take Microsoft updating that to get it changed. That would, of course, mean that they would have to change the rest of the client to be able to handle multiple scripts.

    I'm not sure about the "normal limitation" question. The 4.x client could have scripts in each OSD, which would be similar to what you're trying to accomplish here. I'm not sure why the 5 client imposed this limit. Perhaps someone with deeper knowledge than I can answer that?

    Wednesday, October 2, 2013 1:21 PM