[RESOLVED] After migrating to 2.1, nothing but problems!

Questions about WAPT Server / Requests and help related to the WAPT server
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
Locked
User avatar
t.heroult
Messages: 307
Registration: December 8, 2020 - 10:13 AM

February 25, 2022 - 09:44

Hello,

I updated the server from 1.82 Community to 2.1 Enterprise, and after updating the agent on the workstations, we're getting all sorts of problems:
- The setup via waptdeploy returns errors:
The hash check goes well, but then I get this:
Unable to speak with waptservice... THttpClientSocket.OpenBind(12.0.0.1:8088)
The installation starts, then:
An unhandled exception occurred at $004327D2
EProcess: Failed to execute c:\wapt\wapt-get.exe --version: 2 (Why c:\wapt, when the installation is done in c:\program files (x86)\wapt?
$004327D2
$00401F42
$004050C0
and finally:
waptdeploy exited on xxxxxxx with error code 217.


Another problem:
- In After manually installing the agent, the Windows Server machines don't appear in the console, even though the host logs are OK.
- I just closed and restarted the console; I had over 100 machines, and now I only see 2!

I'm completely lost; nothing works anymore!
Last edited by t.heroult on Feb 25, 2022 - 10:24, edited 1 time.
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows

Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
User avatar
t.heroult
Messages: 307
Registration: December 8, 2020 - 10:13 AM

February 25, 2022 - 10:24

Okay, I went back to my snapshot of version 1.82 and restarted the whole process.
For now, it seems to be working...
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows

Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
Locked