|
| | | Forum Newbie
Group: Forum Members
Last Login: 3/14/2008 4:32:52 PM
Posts: 4, Visits: 10 |
| | We have been using scripts to deploy .pwc files for a very long time, through many versions of Prism Pack. Normally, we would call these packages from a windows .bat script using a command line like this... PAClient.exe /ip package1.pwc /norollback PAClient.exe /ip package2.pwc /norollback The script would always wait until package1.pwc was complete before moving on to install package2.pwc in the script. After upgrading to Prism 8.0 and switching over to PTClient, the script no longer waits for the package to complete, but just runs through all the packages, starting and completing multiple packages at the same time. PTClient.exe /ip package1.pwc /norollback PTClient.exe /ip package2.pwc /norollback Will result in package1.pwc starting, and then package2.pwc starting and installing while package1 is still running. If my script calls a reboot at the end, the reboot starts before the packages are done, or if package2 depends on something in package1, it's a big problem. Is there a way to make PTClient.exe wait until the installation of that package is complete before moving on to the next one, like PAClient.exe did? |
| |
| | | 
Supreme Being
Group: Moderators
Last Login: 10/8/2008 1:15:23 PM
Posts: 655, Visits: 810 |
| | |
| | | Forum Newbie
Group: Forum Members
Last Login: 3/14/2008 4:32:52 PM
Posts: 4, Visits: 10 |
| | It's not the PAClient that we had problems with. We've moved to version 8.0, and PAClient does not seem to install those packages. Using PAClient.exe, I can't reproduce this behavior either. Since the packages were created with version 8.0 of the Prism Deploy Editor, we changed to use PTClient.exe instead of PAClient.exe.
With PTClient.exe, the packages do not wait till one finishes before starting the next, including using the .pts script as you suggested. |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 10/8/2008 1:15:23 PM
Posts: 655, Visits: 810 |
| Ah yes sorry. That was a type-o.. We meant to say PTclient not PAclient... | We have not been able to reproduce this behavior in our lab. You should try installing your packages within a Prism script, because we think that method will work better. A Prism script is created with notepad and saved with the extension .pts. You then tell the PTClient to play the script by using this syntax:
PTclient.exe /PlayScript \\server\share\SomeScript.pts Within the script, you would use the following commands: /InstallPackage \\server\share\app1.pwc
/InstallPackage \\server\share\app2.pwc
/InstallPackage \\server\share\app3.pwc
etc.
|
New Boundary Technologies Support
support@newboundary.com |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 3/14/2008 4:32:52 PM
Posts: 4, Visits: 10 |
| I tried your method. It did the exact same thing.
The first package starts installing, the script moves right on to the next package and then straight back out to the script that called the .pts, while both packages are still running.
It is doing this on all packages (old ones created with Prism Pack 6 and brand new ones created with 8), all operating systems, all systems.
My PTClient.exe shows up with File version 8.0.0.817
Have I gotten hold of a strange one? |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 10/8/2008 1:15:23 PM
Posts: 655, Visits: 810 |
| | The version of PTclient you are using is the correct version. I do admit the situation you are experiencing is strange. This might be something we should look at with a Phone support call if you can. 612-379-1851
New Boundary Technologies Support
support@newboundary.com |
| |
|
|