Creating a package issues

  • This topic is empty.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #7347
    AvatarIowa-Wyse
    Participant
    • Total Post: 17
    • Regular Joe
    • ★★

    I have used a packaging software to create my .msi file. I have also created my RSP script. I have my package imported into WDM and I have tried rolling it out. It fails with the following error “Agent not returning error text/line”

    I just want to copy the msi over to the WES7 device and run it. Here is my script:

    [Version]
    Number=Verant5.2.1
    Description=Verant
    OS=WES7
    Category=Other Packages
    USE_REMOTE=Yes
    ; Date: 5/11/2012

    [Script]
    LU
    XC “Verant5.2.1*” “Z:”
    EX “”Z:verant.msi /q” “+””
    EL

    #22347
    Avatarpufthemajicdragon
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    First off, there’s an extra set of quotes around your EX command that you don’t need. That could cause problems.

    Try using SF (send file) instead of XC. From the WDM admin guide re XC: “Support: XPe, CE 3.0, Linux”, WES7 is not mentioned. And in your SF command, specify the destination filename as so:
    SF “Verant5.2.1verant.msi” “z:verant.msi”

    This requires a SF command for every file you want to send, but that appears to be how WYSE does it in their default scripts.

    And “USE_REMOTE” should be “No” unless you’re specifically using a remote repository (enterprise edition only).

    #22375
    AvatarIowa-Wyse
    Participant
    • Total Post: 17
    • Regular Joe
    • ★★

    I still cant get this to run correctly. I have copied over the file manually to c:temp. I am now just trying to execute the file to install it. I can run the command just fine manually and it works. I just cant get it to work from the device manager script. here is my new script. I have tried putting “+” at the end of the EX line to give it time. I have also tried the Local Pause command after the EX command to give it time. The install just does not complete. I have also tried putting in the full path for msiexec.exe.

    [Script]
    LU
    EX “msiexec /q/i c:tempverant.msi”
    EL

    #22384
    ConfGenConfGen
    Keymaster
    • Total Post: 9813
    • Jedi Master
    • ★★★★★★★

    Try to execute a batch which starts the msi file, instead of directly starting the msi.

    CG

    #23524
    AvatarVguy
    Member
    • Total Post: 2
    • Newbie

    I was just going to reply to this but this thread is so old.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.