Vision Support

This section contains details of any common support issues and how they would be checked and resolved. This section will be added to over time.

Vision is not updating

Problem

The likely issue is that the Vision Data Mining process has stopped for some reason.

Resolution

• Log on to the machine and check that the Vision Data Mining processes are still scheduled, using the Windows Scheduler. If not, add or re-start them.
• If they are running, check the logs, found in {Vision}\Scripts\DataMining_*.log or through the Event Log Vision screen. This may point to errors or suggestions that the processes are scheduled by failing when run.
• If the processes are failing, pause all the scheduled jobs and kill any processes on the machine called Wscript.exe using the Windows Task Manager. When complete, start the Data Mining tasks again and force run them.

Vision is not updating WCS data (Log database has been renamed)

Problem

The cause of Vision not updating is is that a user renamed the WCS Logging database manually.

Root Cause Resolution

A script has been provided to do this easier and with Vision unaffected – a shortcut to this is usually in the WCS database folder, called WCS_Archive. When the WCS system has been stopped, simply double-click this script and the database will be archived into the ArchiveDB folder. Vision will be informed of this and take the necessary actions to mine any remaining data from here and continue in the new logging database.

The script is called WCS_Archive.vbs and is usually located in {WCS Program Folder}\Database\Upgrades\Xfer\Scripts.

If installing this manually for a new client, a short-cut is usually placed in the Database folder, with the following parameters in the Target:

"{WCS Program Folder}\Database\Upgrades\Xfer\Scripts\WCS_Archive.vbs" -LDB={WCS Database Folder}\log1.mdb -A -V

Resolution

Note: The Data Mining should be disabled before and enabled after the steps have been taken, or ensure that the steps are taken between data mines (usually every 5 minutes).

To resolve quickly (with possible data loss):

• Enquire on table System_Extracts, to find the WCS Data Mine that is affected. This will be records with:
  • Enabled = "Y"
  • Type = "WCS"
  • DB1_Folder will be the machine name or IP address.
• Edit all records on table System_Extract_Points. Blank (i.e. not Null, Change to value Space, then Delete) the Value field on the records with the following values:
  • Extract = "ra_wcs_new", Field "ID"
  • Extract = "RDT Activity", Field "End"
  • Extract = "RDT Activity", Field "Start"
  • Extract = "Exceptions", Field "ID"
• Apply all changes.

To resolve (with no possible data loss):

• Enquire on table System_Extracts, to find the WCS Data Mine that is affected. This will be records with:
  • Enabled = "Y"
  • Type = "WCS"
  • DB1_Folder will be the machine name or IP address.
• Note the Archive Database folder.
• Log onto the WCS server.
• Find the Log database that the user created and copy into the Archive Database.
• Create a file with the same name as the database, with the additional extension ".archive". For example, if the renamed database is called "log1_12345.mdb", create a file called "log1_12345.mdb.archive".

With either resolution, the next time Vision datamining runs, it will update correctly.