SCOM Connector installation fails with "Validation to SCOM server failed. Unable to connect to SCOM. Unable to validate SCOM credential" error.
search cancel

SCOM Connector installation fails with "Validation to SCOM server failed. Unable to connect to SCOM. Unable to validate SCOM credential" error.

book

Article ID: 31638

calendar_today

Updated On:

Products

CA Service Operations Insight (SOI)

Issue/Introduction

Problem:

We are trying to setup SCOM Connector version 4.3 on Win2008 SP1 server but during the

installation, we get "Validation to SCOM server failed. Unable to connect to SCOM.

Unable to validate SCOM credential" error.

Environment:

SOI 3.3

SCOM 2012 R2

SCOM connector 4.3

Cause:

SCOM Connector Installer log shows the following error messages:

Microsoft.EnterpriseManagement.OperationsManager.dll and Microsoft.EnterpriseManagement.OperationsManager.dll are required on the local host box to install SCOM connector.  Expected to find the required files in  
System's temporary directory = C:\Users\xxxx\AppData\Local\Temp
target = C:\Users\xxxx\AppData\Local\Temp\343807.tmp\SCOMServerAuthenticate.exe
extractWhatURL = jar:file:/C:/Users/xxxx/AppData/Local/Temp/I1442230481/InstallerData/Execute.zip!/com/ca/proxy/SCOMServerAuthenticate/SCOMServerAuthenticate.exe
Validation result : true
SCOM Version: 
SCOM Internal Version : 
Management Servers : 

SHUTDOWN REQUESTED
Exiting with exit code: 1000
====================STDOUT ENTRIES==================

versionTypeCatalyst versionNum:3.4.1.186
versionTypeCatalyst Installer versionNum:3.4.1.167
catalystVersion3.4.1.167
Container selected to install: 
Catalyst Exists:    true
Catalyst Container: D:\Program Files (x86)\CA\Catalyst\CatalystConnector\container
Catalyst dir: D:\Program Files (x86)\CA\Catalyst\CatalystConnector
Catalyst Version:   3.4.1.167
Major Version:      3
Minor Version:      4
Node Name:      CA-SCOM-CN_CatalystConnector
extracting  your.exe to temp location.
Server Socket created on port  53138
Waiting for a connection from SCOMServerAuthenticate.exe
SCOMServerAuthenticate started and connected to Socket 
Waiting for client to be ready
OK
Client is Ready to communicate 
Credentials given for connection 
 write complete 
Setting connected to false  Waiting for connection result
got the result Failed
Input line didn't start with Connected:
Wrong credential
Debug point 1
Connection failed
(X) commiting registry
(X) shutting down service manager
(X) cleaning up temporary directories

Resolution:

.NET Framework 3.5.1 has to be installed.

 

 

 

Environment

Release: SAMBDL99000-3.3-Spectrum-Service Assurance Manager-Promotional Bundle
Component: