Troubleshooting Installation and Configuration Issues (Master Data Services)

Error when connecting to a remote database server

When you try to create or configure a Master Data Services database on a remote computer, you might encounter the following error message:

Unable to connect to server: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.

This occurs when you attempt to connect to a remote Database Engine instance from Master Data Services Configuration Manager and the instance is not configured to allow remote connections. To enable remote connections on the database server computer:

• Ensure that you enable the Named Pipes and TCP/IP protocols for the Database Engine instance you want to connect to, and then restart the SQL Server <instance> service. For more information, see How to: Enable or Disable a Server Network Protocol (SQL Server Configuration Manager).

• Configure the firewall to accept connections for the TCP port used by the Database Engine instance. For more information, see How to: Configure a Windows Firewall for Database Engine Access.

Database creation fails when user account cannot be resolved

When you try to create a Master Data Services database, you might encounter one of the following error messages:

• Could not obtain information about Windows NT group/user 'domain\account', error code 0x5.

• Unable to look up specified user account.

This issue occurs when the service account for the SQL Server service, MSSQLSERVER, has inadequate permissions to query Active Directory and cannot resolve the domain account of the user who is attempting to create the database. Ensure that the service is configured to use a service account that has domain access. For more information about the types of service accounts and access they have to domains, see Setting Up Windows Service Accounts.

Database creation fails with system catalog error

When you try to create a Master Data Services database, you might encounter the following error message:

Ad hoc update to system catalogs is not supported.

This issue occurs when the allow updates parameter of the sp_configure stored procedure is set to 1. To resolve this issue, set the allow updates parameter to 0 and then attempt to create the database again:

sp_configure 'allow updates', '0'
RECONFIGURE WITH OVERRIDE

For more information, see sp_configure (Transact-SQL) and RECONFIGURE (Transact-SQL).

Database creation fails with error “Invalid column name ‘ProductName’. Invalid column name ‘ProductVersion’.”

When you try to create a Master Data Services database, you might encounter the following exception:

Invalid column name 'ProductName'. Invalid column name 'ProductVersion'.

This issue occurs when there is a non-Master Data Services database on the same Database Engine instance that contains a table named tblSystem. As a workaround, temporarily rename the table until the Master Data Services database is created or create the Master Data Services database on a different Database Engine instance.

Database creation fails with error “Data is Null. This method or property cannot be called on Null values.”

When you try to create a Master Data Services database, you might encounter the following exception:

Data is Null. This method or property cannot be called on Null values.

This issue occurs when another database on the same Database Engine instance is either offline or in the process of being restored. When you create the Master Data Services database, make sure that all databases on the same Database Engine instance are online and not being restored.

Error when accessing the Web service

When you try to access the Master Data Services Web service, you might encounter the following error message:

Service 'service_name' has zero application (non-infrastructure) endpoints. This might be because no configuration file was found for your application, or because no service element matching the service name could be found in the configuration file, or because no endpoints were defined in the service element.

This occurs when Web services have not been enabled. For more information, see How to: Enable Web Services (Master Data Services).

HTTP 401.2-Unauthorized

When you try to access Master Data Manager, you might encounter an HTTP 401.2-Unauthorized error. This can occur for the following reasons:

• Windows Authentication is not configured on the Web server computer. For more information, see Web Application Requirements (Master Data Services).

• Windows Authentication is not enabled for the Master Data Manager Web application in Internet Information Services (IIS).

For more information, see Error message when you try to visit a Web page that is hosted on IIS 7.0: "HTTP Error 401.2 - Unauthorized" on the Microsoft Support Web site.

HTTP 500.19-Internal Server Error

When you try to access Master Data Manager, you might encounter the following error:

HTTP 500.19-Internal Server Error: The requested page cannot be accessed because the related configuration data for the page is invalid

This occurs when a required role, role service, or feature is missing from the Web server computer. Ensure that the computer is configured properly for the Master Data Manager Web application. For more information, see Web Application Requirements (Master Data Services).

HTTP 500.21-Internal Server Error

When you try to access Master Data Manager, you might encounter the following error:

HTTP 500.21-Internal Server Error: Handler “PageHandlerFactory-Integrated” has a bad module “ManagedPipelineHandler” in its module list

This occurs when .NET was installed before IIS. To fix this issue, open a command prompt and go to the .NET directory (for example %windir%\Microsoft.NET\Framework64\v4.0.30319). Run the command: aspnet_regiis –i.

HTTP 503-Service Unavailable

When you try to access Master Data Manager, you might encounter an HTTP 503-Service Unavailable error. This can occur when there is a problem with the application pool that the Master Data Manager Web application runs in. In IIS, ensure that the application pool is running, and verify that the application pool identity is configured properly. For example, if the account used as the identity recently required a password change, update the application pool credentials accordingly. For more information, see Managing Application Pools in IIS 7 on Microsoft TechNet.

See Also

Concepts

Change History