Good morning,
I just upgraded from version 1.8 to 2.2 and now one of my agent machines is no longer reachable, whereas in version 1.8 everything worked correctly.
I would also like to add that on the client machine I have a notification that says "WAPTService stopped"
Agent OK issue, but disconnected on the console
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
Hello Jitero,
I see this is your first post, so welcome!
If the service is stopped, then the machine will appear disconnected in the console.
We need to understand why the service isn't starting.
What does the log say on the machine in question?
Typically: "C:\Program Files (x86)\wapt\log\waptservice.log"
I see this is your first post, so welcome!
If the service is stopped, then the machine will appear disconnected in the console.
We need to understand why the service isn't starting.
What does the log say on the machine in question?
Typically: "C:\Program Files (x86)\wapt\log\waptservice.log"
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!
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
Hello to you too! And thank you for your welcome message!t.heroult wrote: ↑Apr 14, 2022 - 3:29 PM Hello Jitero,
I see this is your first message, so welcome!
If the service is stopped, then the machine will appear disconnected in the console.
We need to understand why the service isn't starting.
What does the log say on the machine in question?
Typically: "C:\Program Files (x86)\wapt\log\waptservice.log"
In the location you mentioned, I have a file named "wapt-get 20220414 145155".
And here is the last line that I see; I imagine this is the one we are interested in.
Installed WAPT version = 2.2.1
Server OS = Windows Server 2019
Administration/package creation machine OS = Windows 10
Server OS = Windows Server 2019
Administration/package creation machine OS = Windows 10
Okay, we'll have to wait for support to intervene because this isn't a message I can interpret 
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!
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Good morning
In a command prompt as administrator, can you run this:
Simon
In a command prompt as administrator, can you run this:
Code: Select all
runwaptservice -ldebugGood morning,sfonteneau wrote: ↑Apr 20, 2022 - 2:00 PM Good morning
In a command prompt as administrator, can you run this:
SimonCode: Select all
runwaptservice -ldebug
Thank you for your reply, the problem is solved, it was a problem with the antivirus.
Good day !
Installed WAPT version = 2.2.1
Server OS = Windows Server 2019
Administration/package creation machine OS = Windows 10
Server OS = Windows Server 2019
Administration/package creation machine OS = Windows 10
