MS OFFICE error

[Gaschet]

Hello, I'm new to the forum and currently work for a research lab.
I have a virtual server running Windows Server 2012 R2 without IIS. I installed and configured WAPT and successfully imported and installed packages from the TranquilITsystems repository on my machines.
However, I've been stuck for a few days creating my Office package. I followed the tutorial, but the console displays: "
Office Standard 2013 Installation
Timeout Expired: Command ""setup exe" /adminfile "conf Msp"' timed out after 1200 seconds with output ''."
I've attached my folder and the script.

Thank you.
Folder: https://imgur.com/mj6MfaZ

[agauvrit]

Hello,

It's in the documentation: https://www.wapt.fr/fr/doc-1.5/Frequent ... tput-600-0

Regards,

Alexandre

[Gaschet]

Hello, thank you for your quick reply, but I've already set it to 1200 seconds, as indicated by my error code:

Timeout Expired: Command ""setup exe" /adminfile "conf Msp"' timed out after 1200 seconds with output ''

[agauvrit]

Oops, not awake yet.

In this case, it's most likely that something went wrong during the installation and caused it to pause.

Are you able to manually launch the installation and observe what happens?

Are you uninstalling the old versions from your transformation file?

[Gaschet]

No worries, yes, when I run `wapt-get install "my package name"` it works. Actually, when I run the package on one of my machines via the WAPT console, the client retrieves the package from its cache but doesn't install anything.
It gets stuck at the installation stage...
No, it seems to me that the script checks if I already have Office, and if it's already installed, it doesn't go any further and tells me that Office is installed.

[agauvrit]

Ah, there's been a misunderstanding. I understand "manual installation" to mean executing the command line launched by setup.py, which is:

Code: Select all

setup.exe /adminfile etab.msp

The command-line installation method wapt-get install mypackage works when you are a local administrator of the machine; installation from the console goes through the WAPTService service in a system account, therefore with more rights than the Administrator account.

Logically, the installation from the console should work correctly.

Is the service running on the workstation?
To restart it:

Code: Select all

net stop waptservice
net start waptservice 

[Gaschet]

Hello,
yes, the service is running correctly, and when I manually run the command "setup.exe /adminfile conf.msp", it works.
I get an error message on my machine, but that's because I already have Office installed.

[Gaschet]

New
observation:
• On my server, when I run my script via Python, everything works, and if it's not already installed, the installation window opens correctly (install now or customize).
• On my client, when I launch the package, my client retrieves the wapt package from its cache but doesn't proceed any further, resulting in a "Timeout 1200 seconds" error.
I hope this helps guide you towards a solution.

Thank you.

[Gaschet]

Up!
I found my problem. After checking my script several times and finding no issues, I focused on the silent.xml file. I took the configured options and looked at what they did. I saw that the options prevented a window from being displayed.
However, when I test with Python or when I install using WaptGet, I always get a window. I therefore conclude that it's not using my silent.xml file and is instead using the XML file located in "ProductName.WW"/config.xml.
So I modified that file, copied it to the root directory, uploaded it, ran my package, and the installation went smoothly.

[sfonteneau]

https://wapt.lesfourmisduweb.org/detail ... 1_all.wapt

Code: Select all

   
    if not installed_softwares('Microsoft Office Professionnel Plus 2016'):
            cmd = '"setup.exe" /adminfile "silent.msp"'
    else:
            cmd = 'msiexec.exe /p silent.msp'

Basically, if the product is already installed, you need to use msiexec.exe /p silent.msp and not adminfile