Page 1 of 1
Launching an executable file over the network.
Published: October 9, 2017 - 4:53 PM
by sdelpech
Hello,
I'm trying to create a package for the administrative installation of SolidWorks. I've placed the entire installation in a publicly shared directory. When I run the command `run(r'"\\10.XXX\Partage\solid\startswinstall.exe"/install /now')`,
I get an access denied error.
If anyone has already installed this software via WAPT, I would appreciate any information.

Re: Launching an executable file over the network.
Published: October 9, 2017 - 5:43 PM
by agauvrit
Hello,
The WAPT service runs on a local system account (NT_Authority\System) and may not have access to the network share specified in your WAPT package.
The solution would be to integrate the contents of the installation ISO into your WAPT package, making the installation less network-dependent since it would be local to each workstation, and to use the silent installation provided by SolidWorks via the MSI installer provided by Dassault Systèmes:
http://help.solidworks.com/2016/French/ ... d_line.htm
Your package will certainly be larger to deploy, but it will be complete and network-independent.
If you wish to maintain your remote network path method, modify the access rights of the share in question.
I would also like to inform you that the SolidWorks installation time exceeds the maximum time allowed by the WAPT agent; increase the timeout to at least 1500:
https://www.wapt.fr/fr/doc/Frequent-pro ... stallation
Sincerely,
Alexandre
Re: Launching an executable file over the network.
Published: October 10, 2017 - 8:05 AM
by sdelpech
For my tests, I ended up creating two packages. The first copies the installation files, and the second launches the installation. This already saves me from waiting an hour each time I run the build package.
I'll try using the msiexec commands.
Thanks for your help.
Re: Launching an executable file over the network.
Published: October 10, 2017 - 5:26 PM
by sdelpech
My problem stems from the fact that the installation is trying to contact a SolidWorks server via the web. Consequently, behind a proxy server with authentication, the installation is blocked.