Hello,
some of my colleagues are experiencing a problem that renders the console unusable. When they launch the console, they get the following error:
"Division by zero.
Press "OK" to ignore and risk data corruption.
Press "Abort" to close the program.
"
I tried reinstalling the agent package from my console on one of these machines, but it didn't change anything. (This seems to have started since we recently upgraded from version 2.5 to 2.6.)
Thank you in advance for your help.
Waptconsole problem: "Division by zero"
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,
this might be a custom column they added. The data may no longer exist in the database since the update.
I have the impression that resetting the console display isn't working.
To unblock them, you would need to rename their c:\users\ file.
I'll discuss this with the development team regarding the display reset.
Best regards,
Bertrand
this might be a custom column they added. The data may no longer exist in the database since the update.
I have the impression that resetting the console display isn't working.
To unblock them, you would need to rename their c:\users\ file.
I'll discuss this with the development team regarding the display reset.
Best regards,
Bertrand
Thanks, we'll test that.
On a related note, I don't know if it's connected, but since this version, the display resets every time the console is reopened; that is, all the windows and columns are resized in a way that's not very visually appealing. If you have any tips for that too...
On a related note, I don't know if it's connected, but since this version, the display resets every time the console is reopened; that is, all the windows and columns are resized in a way that's not very visually appealing. If you have any tips for that too...
There is indeed a major bug with saving/reloading the grid and panel layout when not at 96dpi.
The design is created at 96dpi, and when the application loads, all elements are scaled if the screen is not at 96dpi.
The problem with saving the layout is that it saves a layout that is already scaled.
When it is reloaded in the next session, the scaling is reapplied to a layout already at the correct high dpi, so everything shifts exponentially.
Therefore, we need to save the layout upon exiting the application (file %APPDATA%/waptconsole/waptconsole.ini) by applying inverse scaling to return to 96dpi.
We are working on a solution as quickly as possible.
The design is created at 96dpi, and when the application loads, all elements are scaled if the screen is not at 96dpi.
The problem with saving the layout is that it saves a layout that is already scaled.
When it is reloaded in the next session, the scaling is reapplied to a layout already at the correct high dpi, so everything shifts exponentially.
Therefore, we need to save the layout upon exiting the application (file %APPDATA%/waptconsole/waptconsole.ini) by applying inverse scaling to return to 96dpi.
We are working on a solution as quickly as possible.
Tranquil IT
