Unable to Login after creating a new Administrator Account with the Markvision Enterprise password utility

Issue description

After upgrading from previous versions of Markvision Enterprise to version 4.1.0, new Admin credentials added by the MVE Password Utility (mvepwdutility-windows.exe) cannot be used to login. If the USERS table is examined in the database, newly created users will have what looks to be encrypted “User Name” and “Name” fields.

This data corruption is caused by the installer leaving in place older versions of the installer-N.N.N.jar file in the same location as the MVE Password Utility (mvepwdutility-windows.exe).

Affected Products:

Software: Markvision Enterprise 4.1.0

Solution

1. Before removing or altering any data in the Markvision Enterprise installation directory, please ensure a good back-up of the current installation is taken. Refer to the Markvision Enterprise Version 4.1 Administrator's Guide for details on creating a back-up of the application.



2. Check the installation directory where the mvepwdutility-windows.exe utility is installed for multiple versions of the Installer JAR file. If previous versions of the Installer JAR file exist, manually delete all but the current version. In the example shown, the files installer-3.5.1.jar and installer-4.0.0.jar should be deleted and the file installer-4.1.0.jar should be retained.

   


3. Once the old files are removed, re-run the Password Utility and add a new Admin User.

   

Additional troubleshooting

In some cases, before logging into the Markvision console, it may be necessary to restart the MVE service. To do so, open the Microsoft Windows Services Manager:

1. Right-click on the Start button to open the Menu.



2. Select Run.



3. Type services.msc in the Run box, and click the OK button.



4. Windows Services Manager will open.

   


5. Locate the Markvision Enterprise (or MVE) Service, highlight it, then select Stop the service followed by Start the service, or Restart the service.



6. Once restarted, wait approximately 2-3 minutes for the server to fully initialize and try to log in again.