Update from 1.3.13.0 to 1.6.2.7 Windows Server 2008 R2
Published: November 2, 2018 - 5:36 PM
Good morning,
I attempted a complete migration of my WAPT server (1.3.13.0 to 1.6.2.7 Windows Server 2008 R2).
The update fails after the "WAPT server password" prompt during post-configuration.
Error message:
Wapt agent version exception (1.3.13.0). The post-configuration tool cannot continue...
After clicking OK on the error window, another error message appears:
It is impossible to focus on an invisible or disabled window...
I've attached the screenshots.
Logically, I should have a window offering me the option to launch the migration from MongoDB to PostgreSQL.
I restarted the setup several times, trying:
- disabling the antivirus
- restarting the server
I specify that the installation is launched from a domain user account that is a member of a group that is itself a member of the Administrators group locally on the server.
Do you have any suggestions for me?
I had planned to take a snapshot of the VM, so I ended up reverting to my initial configuration (the production server is also a print server). I won't be able to retrieve any log files.
THANKS
I attempted a complete migration of my WAPT server (1.3.13.0 to 1.6.2.7 Windows Server 2008 R2).
The update fails after the "WAPT server password" prompt during post-configuration.
Error message:
Wapt agent version exception (1.3.13.0). The post-configuration tool cannot continue...
After clicking OK on the error window, another error message appears:
It is impossible to focus on an invisible or disabled window...
I've attached the screenshots.
- 2018-11-02 17_34_50-error update wapt.docx - Word.png (32.06 KB) Viewed 7559 times
I restarted the setup several times, trying:
- disabling the antivirus
- restarting the server
I specify that the installation is launched from a domain user account that is a member of a group that is itself a member of the Administrators group locally on the server.
Do you have any suggestions for me?
I had planned to take a snapshot of the VM, so I ended up reverting to my initial configuration (the production server is also a print server). I won't be able to retrieve any log files.
THANKS