WADS: The PC does not appear in the deployment console

[t.heroult]

Hello,

I have a new deployment problem.
Everything is up to date (WAPT, WINPE, etc.).
There were no deployment problems with this configuration until now.

The PC boots via PXE and the WAPT interface loads.
I enter the PC name and then...
nothing
. Although the window title says "Registration successful" and there's no error message, the PC simply doesn't appear in the console to allow me to select the configuration.
It's not a very recent PC (over 5 years old), and it has a Realtek LAN.

The WAPT system seems OK; I just tested it from a VM and everything works normally.

Any ideas to help me resolve this?
Thanks in advance.
Tom

[dcardon]

Hi Thomas,
you can use Alt-Tab to open the cmd.exe text console. We'll need to check if there's a network connection and if there's a specific error message at that point.
Regards,
Denis

[t.heroult]

Good morning
Here's the result: I don't see anything suspicious...

IMG_20230908_134833 blurred.jpg (217.37 KB) Viewed 18462 times

[bkolovljanovic]

Hi Thomas,

Is there a way to view the server-side logs?

Technically, once you get to a display like this: "Registering host on server" without any error message afterwards, it means the request was successfully sent to the WAPT server (api/v3/wads_register_host).

[t.heroult]

Good morning

Here is the relevant section of the log:

Code: Select all

Sep  8 13:48:06 SRVWAPT waptserver[3967428]: 2023-09-08 13:48:06,653 [waptserver.app ] ERROR Exception on /api/v3/wads_register_host [POST]
Sep  8 13:48:06 SRVWAPT waptserver[3967428]: Traceback (most recent call last):
Sep  8 13:48:06 SRVWAPT waptserver[3967428]:   File "/opt/wapt/lib/python3.8/site-packages/flask/app.py", line 2070, in wsgi_app
Sep  8 13:48:06 SRVWAPT waptserver[3967428]:     response = self.full_dispatch_request()
Sep  8 13:48:06 SRVWAPT waptserver[3967428]:   File "/opt/wapt/lib/python3.8/site-packages/flask/app.py", line 1515, in full_dispatch_request
Sep  8 13:48:06 SRVWAPT waptserver[3967428]:     rv = self.handle_user_exception(e)
Sep  8 13:48:06 SRVWAPT waptserver[3967428]:   File "/opt/wapt/lib/python3.8/site-packages/flask/app.py", line 1513, in full_dispatch_request
Sep  8 13:48:06 SRVWAPT waptserver[3967428]:     rv = self.dispatch_request()
Sep  8 13:48:06 SRVWAPT waptserver[3967428]:   File "/opt/wapt/lib/python3.8/site-packages/flask/app.py", line 1499, in dispatch_request
Sep  8 13:48:06 SRVWAPT waptserver[3967428]:     return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
Sep  8 13:48:06 SRVWAPT waptserver[3967428]:   File "/opt/wapt/waptserver/decorators.py", line 197, in decorated
Sep  8 13:48:06 SRVWAPT waptserver[3967428]:     return f(*args, **kwargs)
Sep  8 13:48:06 SRVWAPT waptserver[3967428]:   File "/opt/wapt/waptserver/decorators.py", line 275, in decorated
Sep  8 13:48:06 SRVWAPT waptserver[3967428]:     r = f(*args, **kwargs)
Sep  8 13:48:06 SRVWAPT waptserver[3967428]:   File "/opt/wapt/waptserver/wads.py", line 865, in wads_register_host
Sep  8 13:48:06 SRVWAPT waptserver[3967428]:     req = ujson.loads(request.data.decode('utf-8'))
Sep  8 13:48:06 SRVWAPT waptserver[3967428]: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x82 in position 1205: invalid start byte

[bkolovljanovic]

Hi Thomas,
On closer inspection, this seems to stem from a rather surprising encoding issue.
Byte 0x82 appears to be a "special single quote."

We'll look into ways to better prevent incorrect character input and improve the information sent to the server (creating a clearer summary for clarity).

Could there have been a copy-paste error somewhere regarding the hostname?

[t.heroult]

No, I didn't copy and paste; I manually entered the PC name into the interface.
The PC name was "LN0495", so there were no special characters.

[bkolovljanovic]

I suspect the issue stemmed from the WADS data retrieval the first time. Diskpart is used to list disks and volumes.
An improvement has been made to this and will be included in the next version. The encoding is a bit temperamental.
This problem didn't occur with an English WinPE installation.

[t.heroult]

Interesting...
To be continued

[jcdemarque]

Hello,

I seem to have the same problem, when is the next release scheduled please?