Hello,
I have a rather strange problem.
Following the 1.7 update, a number of my workstations are no longer reporting their inventory.
However, in the console, I can push installations, but the configuration display for my workstations (also in the console) remains frozen.
And when I manually reinstall the agent by reverting to 1.6, my workstations report normally, then after a reboot, they revert to 1.7 (deployed via GPO) and no further reports are received.
On my problematic workstations, the service logs show this:
WARNING Unable to update server status: error: (87, 'NetLocalGroupGetMembers', 'Incorrect parameter.')
When I run `wapt-get update-status`:
2019-02-21 15:10:40,198 WARNING Unable to update server status: error: (87, 'NetLocalGroupGetMembers', 'Incorrect parameter.')
waptserver is not available or there is an error in inventory. Update status not properly sent.
Has the way the agent sends its inventory to the server changed with version 1.7?
Thanks in advance!
- WAPT version installed: 1.7.3.5
- Server OS: Linux
- Administration/package creation machine OS: Windows 10
FATAL ERROR: 87 'NetLocalGroupGetMembers'
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
The warning message appearing on the machine is not the source of the error.
The problem is on the server.
Could you check the /var/log/daemon.log file on the server when the machine registers? There should be a more explicit error message there.
The problem is on the server.
Could you check the /var/log/daemon.log file on the server when the machine registers? There should be a more explicit error message there.
Tranquil IT
