Problems registering clients on the server

[Perfect-Dash]

Hello,

First of all, I want to thank you for this truly fantastic solution! Until now, I was using package deployment via GLPI/FusionInventory, and WAPT is much simpler to use and saves a lot of time when deploying a package.

However, I'm currently encountering a problem: on my network, I have two computers that absolutely refuse to register with the WAPT server, and I don't understand why.
They were registered before, but at one point I removed all the machines from my inventory (I'm still testing the solution), and as a result, I reinstalled all the agents on the client PCs, but only two won't register. Initially, I used Fusion Inventory to deploy the agents to the clients, but I also tried reinstalling them directly on the machines, and again, no registration! I also tried temporarily disabling the Windows firewall on the client just to see, but that didn't work either...

I've searched everywhere, but I can't find a solution. Do you have any idea what could be causing this?

Thank you.

[Yvan Karmouta]

Good morning,
Thank you for your encouragement and please feel free to spread the word about the project
In your case, several tests can be done

1. Is the WAPTService running on the workstations?
2. From your workstations, do you have access to the local WAPT interface: http://localhost:8088
3. from the workstations in a cmd.exe file returned by the wapt-get register command

[Perfect-Dash]

Thank you for your quick response

Is the WAPTService running on the workstations?

-> The WAPT service is activated

From your workstations, do you have access to the local WAPT interface: http://localhost:8088

-> The workstations do have access

from the workstations in a cmd.exe file returned by the wapt-get register command

However, I have an error here:

FATAL ERROR: 2: The key Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\????2014Beta1 can not be opened

I confess I'm really not sure I understand... ^^

In the meantime, I've encountered another problem (sorry), I'm testing to install Fusion Inventory by only changing the path to my server in setup.py.

To help you, I'll explain my method:

1. I go to "Private Repositories" and import the "tis-fusioninventory" package from the repository
2. Once imported, I right-click and select "Edit package," which opens it in PyScripter
3. I only change the server path, I save.
4. I run the command and do a wapt-get build-upload<le chemin du paquet> It works!
5. I launch the installation like any other package on a client machine, but it fails!
6. I get the following error message: "KeyError: "There is no item named u'WAPT/signature' in the archive"

Do you have any idea what the problem might be? I don't have the problem when I don't modify anything and I use the package from the repository.

Thank you

[Yvan Karmouta]

However, I'm getting an error here:
FATAL ERROR: 2: The key Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\????2014Beta1 can not be opened.

Okay. During the computer's registration with the WaptServer, the Wapt client retrieves the list of software from the registry path:
"Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\".
This is where the program uninstallation keys are stored. Apparently, Wapt can't read the registry key
"Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\????2014Beta1".
It might have special character issues or be corrupted. Check and correct this in your registry.

Your second problem concerns a Wapt package; please create a new topic in the correct section, and I will answer you.

[Perfect-Dash]

I'm having another problem, so I didn't want to double-post (I didn't see an edit button), so I deleted my previous reply

I'm reposting my old message:

Finally, the question marks that can be read here: ????2014Beta1 corresponded to Chinese characters on the client... I had to uninstall the software to get the PC to reappear in the inventory.

Thank you very much for your help.

No worries, I'll go create a new topic in the correct section for my second problem.

And here is my new message:

I'm encountering a similar problem with one of my clients, except this time I get this error message when I run `wapt-get register`:

FATAL ERROR: CalledProcessError: Command '('echo "" | wmic PATH Win32_ComputerSystemProduct GET UUID,IdentifyingNumber,Name,Vendor /VALUE',)' returned non-zero exit status 255

Do you have any idea what might be causing this error message? If I understand correctly, it's unable to retrieve the customer's information, is that right?

Thank you

[Yvan Karmouta]

Good morning,
The WMI command is unable to retrieve the BIOS UUID; some BIOS versions no longer have one.
In version 1.2.2 you will be able to generate one from the problematic machine in a command prompt:

Code: Select all

wapt-get generate-uuid

Then edit the file c:\wapt\wapt-get.ini to add the line

Code: Select all

uuid = "uuid  généré"

Sincerely