[RESOLVED] After migrating to 2.1, nothing but problems!
Published: 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!
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!