Hello,
viewtopic.php?p=13374.
The same problem occurred on the latest version, 24.1.10.4-16.
Unfortunately, I don't have access to the version of the post to see the difference.
However, I have opened a thread on the ltspice forum.
https://ez.analog.com/design-tools-and- ... lem/585792
Thank you in advance for your help.
[SOLVED] tis-ltspice 24.1.10.4-16 exit status 1603
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
Olivier Schmitt
- Messages: 44
- Registration: Oct 22, 2024 - 1:25 p.m.
Hello,
Following up on the topic viewtopic.php?p=13374
, a fix was recently released; it's available in version -16 and should permanently resolve error 1603.
I don't see how to work around the problem?
https://wapt.tranquil.it/store/fr/tis-ltspice
Do I need to change the properties on "ALLUSERS"?
Following up on the topic viewtopic.php?p=13374
, a fix was recently released; it's available in version -16 and should permanently resolve error 1603.
I don't see how to work around the problem?
https://wapt.tranquil.it/store/fr/tis-ltspice
Do I need to change the properties on "ALLUSERS"?
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
I checked the Git repository.
Between Jimmy's message and the current version, the .py code hasn't changed.
However, I just noticed that a Luti parameter has been changed: "run_with_psexec" was switched to false in September.
This allows testing the installation under the system account, and it was switched. This explains why the package failed Luti... (it shouldn't have).
I switched it back to true to see, and indeed, it still doesn't work (1603). This has been broken since version 24.1.10.4 (I'm removing the version from the WAPT repository).
Now we need to investigate why the installation of version 24.1.10.4 doesn't work... with the same parameters.
Between Jimmy's message and the current version, the .py code hasn't changed.
However, I just noticed that a Luti parameter has been changed: "run_with_psexec" was switched to false in September.
This allows testing the installation under the system account, and it was switched. This explains why the package failed Luti... (it shouldn't have).
I switched it back to true to see, and indeed, it still doesn't work (1603). This has been broken since version 24.1.10.4 (I'm removing the version from the WAPT repository).
Now we need to investigate why the installation of version 24.1.10.4 doesn't work... with the same parameters.
-
Olivier Schmitt
- Messages: 44
- Registration: Oct 22, 2024 - 1:25 p.m.
Thank you for your feedback.
In the meantime, we've reverted to version N-1 of the package.
I'll run some tests on my end to see.
Please keep us updated if there are any changes on your end.
Thank you!
In the meantime, we've reverted to version N-1 of the package.
I'll run some tests on my end to see.
Please keep us updated if there are any changes on your end.
Thank you!
Good morning,
We hadn't been following, but there's some new information:
https://ez.analog.com/design-tools-and-...ied/594188
The following MSI properties appear to work:
The package is being rebuilt.
Have a good rest of the day
Bertrand
We hadn't been following, but there's some new information:
https://ez.analog.com/design-tools-and-...ied/594188
The following MSI properties appear to work:
Code: Select all
properties = {
"ALLUSERS": "1",
"AI_INSTALLATIONTYPE": "Server",
}Have a good rest of the day
Bertrand
