Error following update to version 1.5

[MDM-SI]

Hello,

I had version 1.3 installed on a Windows server, and I wanted to install version 1.5.
The executable launched correctly, with no errors or significant lag.

I ran it following the configuration instructions, and I'm getting a pop-up message saying:
Error on the WAPT server
Socket Error # 10061
Connection refused.

I have no idea what the problem could be. It was working perfectly 30 minutes ago...

[dcardon]

Hello MDM-SI,

I had version 1.3 installed on a Windows server, and I wanted to install version 1.5.
The executable launched correctly, no errors or significant lag.

I ran it following the configuration and I get a pop-up saying:
Error on the WAPT server
Socket Error # 10061
Connection refused.

And I really don't know where this could be coming from. It was working without any problems 30 minutes before...

There are many background changes in the transition from version 1.3 to 1.5, notably the database change (from MongoDB to PostgreSQL) and the web front-end change (from Apache to Nginx). Could you please verify that the services have been restarted correctly (WAPTServer, WAPT PostgreSQL, WAPT Nginx)? Are there any entries in the logs?

Sincerely,

Denis

[MDM-SI]

Hello

, I just checked the services.
The WAPT service is running, but
WAPT NGinx and WAPT Server are turned off. However, when I try to start them, I get the following error:
For one:
"Windows could not start the Wapt Server service on Local Computer.
Error 1075: The dependency service does not exist or has been marked for deletion.

In the Event Viewer:
The service depends on the following service: WaptApache. This service may not be installed."


For the other: "
Windows could not start WAPT NGinx on Local Computer. See the Event Log. Specific error code: 4.
In the Event Viewer: "

The service stopped with the following specific error:
The system cannot open the file."

I also get the following error: "Error configuring I/O. The WAPT NGinx service will not be started."
This error is accompanied by: CreateFile() failed c:\wapt\log\nssm_nginx.log: access denied.

Regarding WAPT PostgreSQL, I can't find the service. So, has it been installed?

[dcardon]

Hello MDM-SI,

I just checked the services.
The WAPT service is running,
WAPT NGinx and WAPT Server are off, but when I try to start them, I get the following:
For one:
Windows could not start the Wapt Server service on Local Computer.
Error 1075: The dependency service does not exist or has been marked for deletion.

In the Event Viewer:
The service depends on the following service: WaptApache. This service may not be installed.


For the other:
Windows could not start WAPTNginx on Local Computer. See the Event Log. Specific error code: 4.
In the Event Viewer:

The service stopped with the following specific error:
The system cannot open the file.

I also get the following error: I/O configuration error. The WAPTNginx service will not be started.
This error is accompanied by: CreateFile() failed c:\wapt\log\nssm_nginx.log: access denied.

Regarding WAPT PostgreSQL, I can't find the service. So, has it been installed?

So the initial message you reported, "connection refused", is consistent with the state of the system (the WAPT Nginx service is not running), and therefore the installer and the console could not connect to it.

The WAPT Apache service is removed and replaced by the WAPT Nginx service. If the WAPT Server service still depends on the WAPT Apache service, the installation has completely failed.

The installer couldn't copy the files correctly, probably because it didn't have the necessary permissions. When you ran the installer, did you have elevated administrator rights? Could you try running the installer again as a local administrator with elevated privileges (right-click and select "Run as administrator")?.

Could you try upgrading directly to version 1.6? It works identically and takes more special cases into consideration.

Sincerely,

Denis

[MDM-SI]

I have the same problem with versions 1.5 and 1.6.

I'm on Windows Server 2012 R2, as a domain administrator, and I'm using "Run as administrator."

At worst, I'm willing to uninstall WAPT and start fresh, but what about the packages? What about the inventory of these packages on each workstation?

[MDM-SI]

Hello,

I uninstalled Wapt, cleaned up the folders, etc., restarted my server, and then reinstalled it cleanly.

I'm still getting the same error.

Either I'm forgetting to do something, or I'm configuring it incorrectly, but it's causing the problem.

In the meantime, I'll restore a backup of the server to reuse it.

[vcardon]

Note that a "Domain Administrator" account does not necessarily have the same rights as a "Local Admin".

WAPTserver must be installed with "Local Admin" privileges on Windows or "root" privileges on Linux.

Vincent

[MDM-SI]

Hello,

in this case, do you advise against using WAPT on a server joined to a domain?

I'm thinking of setting up a new server from scratch, but I have some questions about the agent (we'll ultimately keep the same IP address):
should I delete the old one before deploying the new one?
Do I need to deploy a new agent?

[vcardon]

Your server must be joined to a domain if you want to use Kerberos authentication for the initial workstation registration with the server.

I'm simply saying that you need to install the WAPT server as a "Local Admin," and that the privileges of a "Local Admin" can be different from those of a "Domain Admin." This difference might be enough to explain the observed behavior.

Vincent