EM 13c, 12c: Deployment of the Enterprise Manager 12c Cloud Control Microsoft SQL Server Plug-in Fails with Error: Test Connection failed: [MSSQL_NumClusterNodes;Failed to connect, Cannot open user default database. Login failed.
(Doc ID 1929987.1)
Last updated on AUGUST 19, 2022
Applies to:
Enterprise Manager for Miscellaneous Plug-ins - Version 12.1.0.3.0 to 13.2.1.0.0 [Release 12.1 to 13.1]Information in this document applies to any platform.
Microsoft SQL Server Plug-in Version 12.1.0.3.0 to 12.1.0.5.0
Symptoms
Deploying the Microsoft SQL Server Plug-in for Enterprise Manager (EM) 12c Cloud Control results in target deployment and Metric collection errors:
Test Connection Results in:
Test Connection failed: [MSSQL_NumClusterNodes;Failed to connect,
Cannot open user default database. Login failed.
, _Wbem_Remote_Determination_DynamicProperty;Can't resolve a non-optional query descriptor property [iscluster] (iscluster), _MSSQL_Instance_TestMetric_DynamicProperty;Failed to connect,
Cannot open user default database. Login failed.
, _OS_Type_TargetHost_DynamicProperty;Can't resolve a non-optional query descriptor property [STDINWBEM_HOST] (ms_sqlserver_host), MSSQL_NumClusterNodes;Failed to connect,
Cannot open user default database. Login failed.
]
or
Metric Collection Errors:
Error Querying:The server principal "SQL_ACCOUNT_LOGIN" is not able to access the database "<INSTANCE_1>" under the current security context.
com.microsoft.sqlserver.jdbc.SQLServerException: The server principal "<USER>" is not able to access the database "<INSTANCE_2>" under the current security context. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:197) at
com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1493) at
com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:775) at
com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:676) at
com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4575) at
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |