`HTTP Status 404’ Error Displays After Upgrading MVE

Issue description

When accessing the MarkVision Enterprise (MVE) site after upgrading from a previous version, an ‘HTTP Status 404’ error appears.

Solutions index:

• ‘HTTP Status 404’ error explanation
• MVE upgrade Do’s and Don’ts
• MVE upgrade process
• Fixing MVE Database Lock Exception
• Additional troubleshooting
• Troubleshooting MVE upgrade from 2.1 to 2.4 failure

‘HTTP Status 404’ Error Explanation

The HTTP 404 Status Error means that MarkVision Enterprise is unable to access a resource (most likely tables in databases or the database itself).

In this case, MVE is unable to:

• Access the database resource because you loaded the old database which is no longer compatible with the new version.
• Access the database because the credentials you provided do not match the database credentials.
• Access the database because a change lock was not released during an upgrade.
• Access the database because an upgrade failed due to an excess of system log messages.

Back to Index

MVE upgrade Dos and Don’ts

Dos in upgrading MVE:

• Create a backup of the database.
• Create a backup of the MarkVision Enterprise folder.
• Use the latest version of MVE.
• Read and go through each window of the upgrade process. Make sure to enter the correct credentials.
• Take note or remember the different credentials (for the database and for accessing MVE).
• Follow the upgrade path (incremental upgrade).
• After each incremental upgrade, run a quick test and make sure that MVE is working. Create another set of backup for each incremental upgrade. This should save the user the trouble of starting from a really old version, should the upgrade fail midway through the incremental upgrade process.

Don’ts in upgrading MVE:

• Never load a backup database with the previous schema after the upgrade is complete. Only use backups taken from the newly upgraded database schema.
• Never proceed with the upgrade while MVE service and other MVE services are stopped.

Back to Index

MVE Upgrade Process

Please consult the MarkVision Enterprise Administrator's Guide for the most up-to-date application and database back-up procedures.

• Markvision Enterprise Home Page with documentation

Ensuring that the following steps are performed before upgrading MVE will avoid issues.

1. Back up your database and use it to revert the MVE application to its previous state when upgrade fails.

   Notes:

   • There are 3 databases that you need to back up before upgrading MVE, such as FRAMEWORK.FDB, MONITOR.FDB, and QUARTZ.FDB.
   • Lexmark currently supports only two Backend databases, these are Firebird (This comes with the installer) and Microsoft SQL. For Microsoft SQL, please contact your Microsoft SQL administrator for assistance to back up your database.


2. Download the MVE executable file into a temporary location.



3. Run the downloaded file, carefully read and follow the instructions on the computer screen. Immediately following the License Agreement, you will be prompted to enter the BACKEND database credentials. See this sample message prompt screen shot:

   

   Warning—Potential Damage:  Make sure to input the correct Backend credentials since the most common mistake is entering the MVE access credentials instead of the Backend credentials.

   • There are two types of credentials entered during initial MVE installation;
   

   1. Backend database credentials (username: framework and password: rivet)

   

   2. MVE access credentials (username: admin and password: Administrator1)

   • Take note of any Warning message you may encounter as it will state one of the usual reason for the error message.


4. In the background, if you enter the correct credential, MVE will proceed with the upgrade and also make the necessary enhancements on the database, making it compatible with the new version of MVE. But if you enter incorrect credentials you will see the error message when accessing MVE.

Back to Index

Fixing MVE Database Lock Exception

Please refer to this article: Fixing Markvision Enterprise database lock exception for more information related to this topic.

Back to Index

Additional Troubleshooting

Fixing Problems Caused by Excessive System Log Messages

Warning:

• If the instance of Markvision Enterprise is a long-standing install with many printers and/or much usage, the System Log entries can accumulate and create problems with the upgrade process.
• If the size of the SYSTEM_LOG table is very large, it’s possible that alterations to the database schema during the installation process can time out, causing the upgrade to fail. When this occurs, it may cause an access failure to the Markvision Enterprise console.
• There is a control in the user interface in the Log settings that will allow the user to delete log entries prior to a specified date, but in the event that this wasn’t utilized, then it may be necessary to manually remove old messages from the log to reduce the database size.

For MSSQL Database administrators, follow the steps below for running a query.

Note:  Before proceeding with the steps below, make sure to verify if the user or service tech will still use the previous logs before the update.

1. Go to services.msc an Stop Markvision Enterprise Services.

   Note:  Click here to view a sample image.



2. Open MSSQL Studio.



3. Go to Database Engine, then select FRAMEWORK.



4. A window will then open beside the database list; copy and paste the following values into it:

   • DELETE from
   • [framework].[dbo].[SYSTEM_LOG] WHERE [framework].[dbo].[SYSTEM_LOG].[TIMESTAMP_] LIKE ('%2017%')OR[framework].[dbo].[SYSTEM_LOG].[TIMESTAMP_] LIKE ('%2019%');OR[framework].[dbo].[SYSTEM_LOG].[TIMESTAMP_] LIKE ('%2018%')

   Note:  In line 4, the SQL construct where the "LIKE" statement specifies a year, means removing the year's worth of data.



5. After copying the values above, press F5 or click on the Execute button.



6. Go back to services.msc and Start Markvision Enterprise Services.

For Firebird Database, use the following query:

DELETE fromwhere TIMESTAMP starting '2016'

Note:  This SQL query intends to clean out the system logs. This can be executed to each year's data to be removed.

Explanation

This error message could also occur when users perform a long-running install of MVE.

Note:  Some instances, the SYSTEM_LOG table reaches a size of up to 1.8 Gigabytes (GB); as a result, it will take a long time to process the file that causes the timeout error.

Back to xref_Solutions_xref

Troubleshooting MVE Upgrade from 2.1 to 2.4 Failure

When performing an update from MVE 2.1, MVE 2.1.x or 2.2 to 2.3 or higher, and using a MSSQL database, if a 404 error appears on the browser at MVE launch, it is possible that this is a database-related error. Check the LSAS logs to look for Trigger or connection errors and whether there are trigger related errors such as: com.lexmark.workflow.framework.service.scheduler.SchedulerServiceQuartzImpl [] - Trigger for destinationTask1504723911066909 is null

This is an indication of some kind of corruption in the Quartz database. The Quartz database is the location of the scheduler and schedule services. A corrupted scheduled task may have interfered with the update process. One possible corrective action is to execute a query against the Quartz database to remove the corrupted entries. Follow these steps below for the corrective action.

1. Stop the MVE service.



2. On the MSSQL Server's SQL Management Studio's Object Explorer, highlight the Quartz database. Right-click and select New Query from the context menu, and enter the following query and execute: USE QUARTZ;GODELETE from qrtz_simprop_triggersDELETE from QRTZ_SIMPLE_TRIGGERSDELETE from QRTZ_TRIGGERSDELETE from QRTZ_JOB_DETAILSGO

   Warning—Potential Damage:  This will remove all entries from the affected tables, any scheduled tasks that were previously assigned will be removed.



3. Restart the MVE service.