Office 2019

[sebastien.layssac]

Hello,

I have a package for deploying Office 2019 (created during training) that works, but it frequently encounters 300-second timeout errors. On-premises, it works fairly well, but via VPN to reach remote users, 300 seconds isn't always enough. If the installation is restarted after the error, it eventually completes, but it's really inconvenient.

Here's the error message:

So I modified setup.py with a timeout of 1200. Here's the relevant section of the script:

def install():
print("Installing %s" % softname)

install_exe_if_needed("Setup.exe",
silentflags="/configure Deploiement_MTP.xml",
key=app_uninstallkey,
min_version="16.0",
killbefore=app_list_kill,
timeout=1200)

But now it doesn't work at all...

Here's the error message:

return func(*args,**kwargs)
File "C:\Program Files (x86)\wapt\setuphelpers_windows.py", line 1172, in install_exe_if_needed
run(r'"%s" %s' % (exe,silentflags),accept_returncodes=accept_returncodes,timeout=timeout,pidlist=pidlist)
File "C:\Program Files (x86)\wapt\setuphelpers_windows.py", line 3718, in run
raise CalledProcessErrorOutput(proc.returncode,cmd,''.join(output))
CalledProcessErrorOutput: Command '"Setup.exe" /configure Deployment_MTP.xml' returned non-zero exit status -2146994855.
Output:
CalledProcessErrorOutput: Command '"Setup.exe" /configure Deployment_MTP.xml' returned non-zero exit status -2146994855.
Output:


Do you have any ideas? THANKS !

[l.costes]

Hello, regarding the same question,

are there other timeout variables in WAPT?

It seems that the one passed here as a parameter to the `install_exe_if_needed` is simply passed as an option in the `setup.exe` command.
In the case of Office, we're not sure if this option exists.

Can we extend the timeout in the WAPT script and not in the `setup.exe` command, and where would this setting be configured?
- Laurent

[dcardon]

Hello,

thank you for posting the requested information in the "forum rules" above.

There shouldn't be any major difference between the behavior of workstations used remotely and those used locally. WAPT packages are downloaded and cached on the workstation before being installed. If you experience longer installation times on your remote workstations, it's because the package isn't self-contained. We would need to see what it's looking for externally.

There's no timeout on the `def install()` function itself. There are timeouts on the `install_*()`, `run()`, and a few others, but not on `def install()`. There is a timeout on the execution of GPOs when the workstation shuts down (Windows timeout), which can be changed in the operating system itself.

Sincerely,

Denis