Occasionally after upgrading vCommander you may receive a 500, 404 or 403 error when accessing the admin console or service portal.
This may be due to an issue with one of the files used to generate vCommanders webpages not expanding correctly.
You can force these files to re-expand by doing the following:
RDP to the vCommander server
Stop the vCommander windows service
Navigate to <install dir>\Program Files\Embotics\vCommander\tomcat\webapps
You will see a set of folders and a corresponding .war file of the same name.
Multi select the folders and delete them
Start the vCommander windows service
The folders will be recreated one by one as the service starts and unpacks the .war file
Chris Quimper
Occasionally after upgrading vCommander you may receive a 500, 404 or 403 error when accessing the admin console or service portal.
This may be due to an issue with one of the files used to generate vCommanders webpages not expanding correctly.
You can force these files to re-expand by doing the following:
RDP to the vCommander server
Stop the vCommander windows service
Navigate to <install dir>\Program Files\Embotics\vCommander\tomcat\webapps
You will see a set of folders and a corresponding .war file of the same name.
Multi select the folders and delete them
Start the vCommander windows service
The folders will be recreated one by one as the service starts and unpacks the .war file