3.4.3 MxDB for SQL Server Installation and Administration Guide

Chapter 4: Troubleshooting 80

To fix the registry keys, take these steps:

1. Run the command mx vsqlinstance dump. In the output, each VSQL

line contains a variable called masterdatabase. The following example

is for an instance named INST1:

masterdatabase=S:\<path_to_SQL>\Inst1\MSSQL$Inst1\data\master.mdf

2. Browse to the following location in the registry.

HKEY_LOCAL_MACHINE/SOFTWARE/PolyServe/MatrixServer/RegistryReplicat

or/MetaKeys

3. There should be a registry key for each active and inactive instance. If

the inactive instances are no longer in use, you can either delete them

or set Enabled 0.

For the active instances, ensure that the StoragePath key matches the

masterdatabase variable from the mx vsqlinstance dump output.

These variables need to match for each active instance.

The registry keys must be edited for each active instance on each node.

When each key matches the correct path to the instance, Matrix Server

will be monitoring the correct path and the error messages will not

reoccur.

Error When Creating a Virtual SQL Server

Because the installation of MSCS (Microsoft Cluster Services) modifies

key system files, you must completely remove MSCS before creating a

Virtual SQL Server. If you do not uninstall MSCS, you will see the

following error when adding a Virtual SQL Server: