Error timeout 300

[raphaelm]

Hello,
I'd like to create a package for a software publisher's program.
I have no problem installing/uninstalling it using PyScripter.
The thing is, during the installation, the progress bar appears, but no interaction is requested.


When sending the package to a test computer (Windows 8.1 Pro and Windows 10),

I get a "Timeout after 300 seconds with output" error.

I tried setting the timer to 600 seconds, but the result is the same.

I don't know what it's expecting.


def install():
print('installing test-application1')
install_exe_if_needed('application1.exe',
silentflags='/s /sms /v" /qb ALLUSERS=1 INSTALL_TYPE=1 LIC_SERVER=srv-licence1 SQR_INSTALL=1 SQ_VBEXCEL=VBYes',
key='{4D26DC69-A81F-4F5F-A3AA-D09A5DD3b8D5}',
timeout=600,)


I've checked that this executable is a container for an MSI and the program prerequisites.
The application is downloaded correctly to the machine and then executed correctly;


there are no missing prerequisites because I already installed it.


Do you know if I can try using a RUN command? (because it works in the regular command prompt) However, I don't know Python.

Thank you





Version of WAPT installed (1,7,3,5)
- Server OS (Windows 2008 Enterprise)
- Administration/package creation machine OS (Windows 10)

[raphaelm]

So I managed to get around the problem
by looking inside the EXE container.
I saw there was an MSI file which was the application itself, and the others were the prerequisites: DirectX .NET, etc.
By using `install_msi_if_needed`,
I succeeded.

However, I'd like to know what was blocking the installation via the EXE.

Thanks.

[dcardon]

Hello Raphelm,

So I managed to get around the problem
by looking in the EXE container.
I saw that there was an MSI file which was the application, and the others were the prerequisites: DirectX .NET, etc.
By using `install_msi_if_needed`,
I succeeded.

However, I'd like to know what was blocking the installation via the EXE.

Thanks

Good idea to unpack it. With WAPT you can put the other executables as dependencies and the agent will manage the installation in the correct order without any problems.

Using a run() function is perfectly feasible. But the behavior will likely be the same.

Regarding tests that work in PyScripter but not through the agent, the best approach is to verify that the installer doesn't malfunction when running under a Local System account. WaptAgent performs its installations using this Local System account, which can behave slightly differently from a normal user account. For example, we saw an .exe installer that insisted on creating a shortcut on the desktop of the user running the installer (instead of placing it in "All Users"). However, the Local System account doesn't have a "Desktop" directory, which caused this faulty installer to malfunction.

You can test the installation as a system account using the psexec tool (tis-ms-pstools package). Once installed, open a command prompt with elevated privileges and then run:

Code: Select all

psexec -i -s cmd

You will then get another command prompt that will run as Local System (you can confirm this with the "whoami" command). And there you can launch your executable and check how it behaves.

Sincerely,

Denis

[raphaelm]

Yes, but the problem is that we don't know beforehand.
I thought when it worked with PyScripter, everything was fine.
But not at all.

In short, it's not that simple to deploy third-party, non-open-source applications.

[vcardon]

Finally, it's not that simple to deploy third-party, non-open-source apps.

At Tranquil IT, we have expressions for that:

- a podoware is software packaged with the feet

- A palmoware is software packaged with webbed feet

Understanding how to deploy software will remain an empirical science for a long time, and with experience, you will see that packaging will seem simpler and more intuitive over time.

Sincerely.

Vincent