Summary:

When running the EMF 5.x Installer on a server installed with SQL 2000 server, only the option to Connect to a fully-populated database exists.

Symptom:

All three options should exist. Since the SQL 2000 Database server is the first machine on which one should normally install EMF 5.x, one should select either the Create a new database or Connect to an empty database option.

Detailed Information:

The SQL 2000 Service Pack 3 installer removes a registry key on the database server on which the EMF installer depends.

Resolution:

Verify the registry key is missing and replace the key with a value if necessary.

1. Launch Regedit.

2. Go to HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Microsoft SQL Server.

3. The string value "SsrpActiveServer" may be missing or empty. This is the value that the EMF installer depends on.

4. Edit the string value and enter the SQL Instance name (e.g., INST1). It is typically the same string value as the "InstalledInstances" value found in the same registry subkey.

5. If the "SsrpActiveServer" and "InstalledInstances" values are missing, add a new string value named "SsrpActiveServer" and enter the SQL instance name. To determine the instance name, look in SQL enterprise manager. If your server instance is simply listed with the name of the server, use "MSSQLSERVER". If your server instance is listed with the name of the server and some other name (e.g., SERVER1/EMF), enter the name after the slash.

6. Close Regedit.

7. Restart the SQL Server instance.

8. Run the EMF 5.x installer again. You should now be presented with all three install options, as expected.

Additional Info:

This issue was uncovered during the validation of Windows 2000 SP3 against Tumbleweed EMF and IME.

NOTE: This technote was previously restricted to SQL 2000 SP3 clusters only. This behavior has now been seen with non-clustered SQL 2000 servers.