Troubleshooting starting the Metadata Server

If the Metadata Server starts properly, you will see the text Ready to accept metadata clients in the Metadata Server log file. If this message does not appear, view the file for possible error messages and instructions. Possible reasons for this problem include the following:

• A supported version of SQL Server may not be running or available on your network
• SQL Server TCP/IP protocol may be disabled
• SQL Server 2005 Browser service may not be running
• Metadata Server configuration file settings may be incorrect
• Metadata Server repository (database) maintenance may need to be applied
• The Metadata Server may have been shut down improperly

A supported version of SQL Server may not be running or available on your network

A supported version of SQL Server must be running and available on your network. Verify that the required SQL Server service pack has been applied.

SQL Server TCP/IP protocol may be disabled

The SQL Server TCP/IP protocol may be disabled. If TCP/IP protocol disabled, a message similar to the following appears in the Metadata Server log file:

SQL Server may require that the SQL Server service is restarted after changing this setting.

SQL Server Browser service may not be running

If SQL Server's TCP/IP protocol is configured to use dynamic ports, verify that the SQL Server Browser service is running.

Metadata Server configuration settings may be incorrect

1. From the Metadata Analyzer Configuration dialog box's Database tab, do the following
2. Verify that the Server name field and Instance name field are correct.
3. If the TCP/IP protocol for your SQL Server instance is configured to use a static port other than 1433 (default), verify that the Port field is set to the port number specified in the TCP/IP configuration of the SQL Server instance.
4. If the TCP/IP protocol for your SQL Server instance is configured to use dynamic ports, verify that the Port field shows no value.
5. Verify the Authentication field, Login field, and Password field are correct.
6. If you are using Windows Authentication, the Windows login is use

7. If you are using SQL Authentication, you must specify a SQL Server login and password that has access to the database specified.

   Note

   If you want the Metadata Server to create your database, the login associated with the Metadata Server must have the authority to create databases (dbcreator privileges) on the specified instance of SQL Server. If you want to manually create your database, db_owner privileges are required.

8. Click OK. Changes do not take effect until the Metadata Server is restarted.

Metadata Server repository (database) maintenance may need to be applied

If you are upgrading DevEnterprise from a previous release, maintenance may need to be applied to the Metadata Server repository (database) via the runDBmaint utility.

The Metadata Server may have been shut down improperly

If the Metadata Server was shut down during its initialization phase, the temporary file mutex_databaseName.dat may exist in the UserDataPath specified during the installation (which is available in the About dialog box). If so, the Metadata Server log will contain instructions to delete this file before restarting the Metadata Server. Normally, this file is created during the startup and initialization phase of the Metadata Server and is automatically deleted when the Metadata Server initialization is complete. Do not delete this file if a Metadata Server is still initializing.