Download automation studio pro 5 library free shared files from DownloadJoy and other world's most popular shared hosts. Our filtering technology ensures that only latest automation studio pro 5 library files are listed. Find Rockwell Software support and information from libraries, videos, downloads and our technical team.
Hello, I am trying to use SCCM 2012 to install Automation Studio 6.2 silently, in SCCM I simply navigate to the folder we have the files in on our UNC path and invoke 'setup.exe -s'. The setup is able to start on the PC (I actually see the setup in the task manager) but it does not finish. I can make it fully install when doing it manually. So I tried just invoking the setup.exe without silent install, it brings up the setup but seems to fail at installing the sentinel driver. Here is the part of the log file where it seems to fail, any ideas?
![Automation Studio Library Files Download Automation Studio Library Files Download](https://image.slidesharecdn.com/automationstudiopro-120426025106-phpapp02/95/automation-studio-pro-14-728.jpg?cb=1335408864)
[006C:1744][2016-05-26T13:39:43]i301: Applying execute package: SentinelDriver, action: Install, path: C: ProgramData Package Cache 9CB5F5CACB7C8B05D8660C990D04F9. Automation Studio Prerequisites SentinelDriver, arguments: 'C: ProgramData Package Cache 9CB5F5CACB7C8B05D8660C990D04F9. Automation Studio Prerequisites SentinelDriver' /s /V'/qn ADDLOCAL=Parallel_Driver,USB_Driver REBOOT=ReallySuppress' [006C:1744][2016-05-26T13:39:50]e000: Error 0x80070653: Process returned error: 0x653 [006C:1744][2016-05-26T13:39:50]e000: Error 0x80070653: Failed to execute EXE package. [11C4:0E60][2016-05-26T13:39:50]e000: Error 0x80070653: Failed to configure per-machine EXE package. [11C4:0E60][2016-05-26T13:39:50]i000: T1 Wpf UI execute package complete SentinelDriver [11C4:0E60][2016-05-26T13:39:50]i319: Applied execute package: SentinelDriver, result: 0x80070653, restart: None [11C4:0E60][2016-05-26T13:39:50]e000: Error 0x80070653: Failed to execute EXE package. [006C:1744][2016-05-26T13:39:50]i351: Removing cached package: SentinelDriver, from path: C: ProgramData Package Cache 9CB5F5CACB7C8B05D8660C990D04F9.
0x80070653 = 'This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.' The setup.exe is just a wrapper and is apparently extracting another installer, an MSI to be extract. It is then trying to invoke this MSI but is failing because it can't find the MSI it just extracted. You'll have to go to the vendor to figure out why this is happening as it's their setup.exe that is falling down. This is often do to ConfigMgr running things as the local System account. Some *bad* installers simply don't know how to deal with this and/or are making bad assumptions about the environment that are not true when running as the local System and you end up with errors like this.
There's nothing ConfigMgr itself can do about this. You may be able to monitor the activity with procmon and see exactly why the MSI can't be found and figure out a work-around, but that all depends upon what's going on. Jason|| @jasonsandys.