SCOM Alerts Connector run as failed

Hi
I have setup the SCOM alerts connector in SCSM but after that i starts to get wernings in scom on servers there are in a difrent domain.
werning:
Description:
The Health Service cannot verify the future validity of the RunAs account Domain1\SCOMAlertsConnectorUser for management group SCOMMG01. The error is Logon failure: the user has not been granted the requested
logon type at this computer.(1385L).
SCSM and scom is in domain1
the servers i got the werning on is in Domain2
what can i do to fix this?

The connectors runas account must be administrator in SCOM (as I recall). Is that the case for Domain2?
Cheers,
Anders Spælling
Senior Consultant
Blog:
Twitter: LinkedIn:
Please remember to 'Propose as answer' if you find a reply helpful

Similar Messages

SCSM to SCOM Alert Connector Error

Hello,
Long story short, the SCSM admin created an Alert Connector between SCSM and SCOM, then uninstalled SCSM and started over. That means I had an orphaned SCSM connector in SCOM.
In order to set up a new connection, I followed the instructions found in Kevin Holman's blog post:
http://blogs.technet.com/b/kevinholman/archive/2012/09/28/opsmgr-2012-how-to-delete-an-old-product-connector.aspx
Now, when I try to re-create a new Alert Connector, I get this error:
"Found at least one other alert connector in Operations Manager. Alerts may not be routed as expected if multiple connectors subscribe to the same alert."
I checked the SCOM server to make sure there were no orphaned connectors by running this SQL code against the OperationsManager database:
Aside from the copious number of SCVMM connectors, there were six connectors. Of those six, the previous SCSM connector is marked as "IsDeleted":
Next, I checked the "Microsoft.SystemCenter.Notifications.Internal" management pack to verify that there are no orphaned subscriptions. The ONLY alert referenced is for the "Advisor Data Connector".
At this point, my questions are as follows:
1) Will the System Center Advisor (now renamed Azure Operational Insights) connector cause the warning message I listed above when setting up an Alert Connector in SCSM?
2) Is there another orphaned entry in SCOM that I need to check for and remove before setting up the SCSM alert connector?

Hi,
I would like to suggest you remove the subscription that was orphaned. When remove a connector we should remove the subscriptions first.
And here is a similar thread
SCSM 2012 Cannot create SCOM Alert Connector
https://social.technet.microsoft.com/Forums/en-US/a5d0b921-bb0a-43b8-99ca-8b0112ab3bf0/scsm-2012-cannot-create-scom-alert-connector?forum=connectors
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

SCOM Alert Connector - not updating the start time and finish time

When I am monitoring the status of connectors in service manager console, I found that for SCOM Alert Connector the Start Time and Finish Time are not updating. Previously it was updated daily. As of now, service manager is working fine but would like
to check will it create any issues? Even I have cliked on Synchronize Now, but there is no update. Please guide me on this to trouble shoot further? Thanks.

Hi,
Based on my research, the Start Time and Finish Time values are not updated when an alert connector is synchronized. These values are only updated when alert data is transferred between Operations Manager 2007 and Service
Manager.
More details, please refer to the link below:
http://technet.microsoft.com/en-us/library/hh495609.aspx
In addition, here is a blog about troubleshooting for SCSM and SCOM alert connector:
http://blogs.technet.com/b/servicemanager/archive/2010/04/14/troubleshooting-tips-for-your-scsm-scom-alert-connector.aspx
Regards,
Yan Li
Regards, Yan Li

Error adding a SCOM Alert Connector

I have a SCOM 2012 SP1 and SCSM 2012 SP1 environment in production. I have had a working CI connector for some time, but we decided to try to add an alert connector to the mix.
At the point where I provide credentials for SCOM I get the following warning
"Found at least one other alert connector in Operations Manager. Alerts may not be routed as expected if multiple connectors subscribe to the same alert."
Hmm. That's interesting because there are no other alert connectors.
I checked the SCOM side for any alert connectors and any configured subscriptions on the internal connectors and came up blank.
I then ran the following queries on the SCOM and SCSM databases:
select DisplayName,IsInitialized,ConnectorID from Connector,BaseManagedEntity
where Connector.BaseManagedEntityID=BaseManagedEntity.BaseManagedEntityID
Neither shows an alert connector in place.
I pressed on and created the connector. I then added my subscriptions to the SCOM side.
I can see my Connector run every 30 seconds, but it never retrieves any alerts.
The state never flips to initialized on the connector either.
I have removed and recreated the connector and always see the same error.
Aside from checking SCOM and the connector tables in the operational databases, where else can I look for this mysterious other alert connector?
Thanks,
Joe

Dear Joe,
hope these links will help you:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/3075bbb7-59db-4671-994d-7540871a2a23/scom-connector-to-multiple-service-manager-environments?forum=connectors
http://www.thecloudbuilderblog.com/blog/2012/6/2/scsm-2012-connector-bugndashincidents-generated-from-rule-ba.html
Regards
Jreij12

Issue with SCSM to SCOM Alert Connector when AOI is Connected?

Hello Azure Operational Insights forum,
I'm trying to connect my Server Manager (SCSM) instance to my Operations Manager (SCOM) instance. However, I get this warning message when I create the connection:
"Found at least one other alert connector in Operations Manager. Alerts may not be routed as expected if multiple connectors subscribe to the same alert."
There "was" a connector previously, but I followed Kevin Holman's blog to remove it. Now everything looks okay (at least as far as I can tell).
At this point, I wonder if the System Center Advisor (now renamed Azure Operational Insights) connector is cause the warning message I listed above when setting up an Alert Connector in SCSM? It's the only "Alert Connector" in the list.
Has anyone else had this issue?

I have also found this warning message. In my case, this is a new connector to a new SCOM Mgt group. the management group in SCOM is connected to AOI.
Repo:
1. Install new OM
2. Configure AOI connection
3. Create SCSM OM Alert Connector
Warn appears after entering SCOM Server details and run as account and continues until Connector is created
The warning does not appear to affect the operation of the connector based on initial tests performed.

Enabling SCOM Alert Connector in SCSM

Hi,
Had a query regarding the Alert Connector in SCOM that forwards alerts in SCOM to SCSM (Service Manager) to create incidents.
Currently, we had SCOM and SCSM at the same level i.e 2012 SP1. But, in future we might have to upgrade to R2 so is there any compatibility matrix for the SCOM and SCSM versions for the Alert Connector. Like if we had SCOM on Sp1 and SCSM on R2 would it
affect or the vice-a-versa.
Regards,
Daya Ram

Hi,
System Center 2012 – Operations Manager is supported by Service Manager and Service Manager SP1 for connectors and agents. However, only corresponding System Center versions are supported when you register a data source in the Data Warehouse
workspace.
System Center 2012 – Operations Manager agents were not supported with System Center 2012 – Service Manager. However, the agent that is automatically installed by System Center 2012 – Service Manager
SP1 is compatible with System Center 2012 – Operations Manager and System Center 2012 – Operations Manager SP1.
More details:
Operations Manager Considerations in System Center 2012 - Service Manager
http://technet.microsoft.com/en-us/library/hh524312.aspx
Regards,
Yan Li
Regards, Yan Li

SCOM Alert connector fighting with AD connector?

I am experiencing some conflicts between the Operations Manager Alert connector and the Active Directory connector. They are both updating the same property values, but the values are not the same.
Example:
A User changes Department, and the Department property in Active Directory are modified with the name of the new Department
The Active Directory connector modifies the value of the User Objects Department property in the Service Manager Configuration Management Database
Then the Operations Manager Alert connector modifies the same property on the User Object with the old value.
Have someone seen the same behavior?

Perhaps correct the bad data in the Ops Manager system?
In all seriousness, the problem with this behavior is that you have two systems that disagree on the value of a property of an object. the behavior you are seeing is them disagreeing. to quote microsoft, "This behavior is by design"

Error importing DA from SCOM through connector

Hi,
After the System Center 2012 R2 upgrade we are seeing event log (operations manager log) errors when the SCOM CI Connector runs.
It states that not everything is synced and it complains about the MP Microsoft.Windows.Peripheral.Networkadapter class, that seems to be included in the SCOM Microsoft.WIndows.Library MP but not in the Microsoft.Windows.Library for SCSM.
Instead it is a separate MP that has not changed version.
I´m investigating if it in fact is not syncing all items, maybe it just warns, but either way this seems strange, and I wonder if anyone else has seen this and if so, what have you done?
ERRORS in operations manager log during SCOM CI Connector sync (there are a lot of these errors for different objets).
log error: 34096
Skipping import of instances of class Microsoft.Windows.Peripheral.NetworkAdapter. The management pack Microsoft.Windows.Library that defines this class has version 7.5.8501.0 in Operations Manager that is higher than its version 7.5.3079.0 in Service Manager.
The following steps will resume import of instances of this class:
1) Import management pack Microsoft.Windows.Library with version 7.5.8501.0 into Service Manager.
2) Edit the connector configuration and ensure that this management pack is selected for synchronization.
And also
log error: 34094
Connector Name=Operations Manager CI Connector, Id=rxc51f96-3434-071c-6b93-34ad39962620
Cannot create part of service map [servicename].
Skipped component: resourcename.domain.net.
Class of skipped component: Health Service.
The component resourcename.domain.net is defined in management pack System Center Core Library. Check for prior errors that indicate if importing a missing management pack can help resolve this issue.
E.O

We are finding something similar when syncing OpsMgr DA's with Service Manager.
Cannot create part of service map [xxxx-xxxxxxx].
Skipped component: Local Area Connection 3.
Class of skipped component: Computer Network Adapter.
The component Local Area Connection 3 is defined in management pack Windows Core Library. Check for prior errors that indicate if importing a missing management pack can help resolve this issue.
Skipping import of instances of class Microsoft.Windows.Peripheral.NetworkAdapter. The management pack Microsoft.Windows.Library that defines this class has version 7.5.8501.0 in Operations Manager that is higher than its version 7.5.3079.0 in Service Manager.
The following steps will resume import of instances of this class:
1) Import management pack Microsoft.Windows.Library with version 7.5.8501.0 into Service Manager.
2) Edit the connector configuration and ensure that this management pack is selected for synchronization.
Well, that's not true, I verified the version is 7.5.8501.0 in the ManagementPacks table.
Service Manager 2012 R2 has the Windows Peripheral Library MP that defines a handful of classes derived from classes in the Windows Library MP.
<ClassType ID="Microsoft.Windows.Peripheral.NetworkAdapter" Accessibility="Public" Abstract="false" Base="Windows!Microsoft.Windows.NetworkAdapter" Hosted="true" Singleton="false" Extension="false">
OpsMgr 2012 R2 does not have this MP, it's not in the Management Packs folder in the bits, and I can't find it in the Service Manager bits. There are no discoveries in it, so this is a fun mystery. Anyone else run into this?

Mapping information to SCOM Alert "Path" field through the connector

Hello,
We are using the Oracle Enterprise Manager connector (link to the guide: http://docs.oracle.com/cd/E11857_01/install.111/e14736/toc.htm) to send events from OEM to SCOM.
According to the Oracle connector documentation, the Target host parameter from OEM can be mapped with one of the SCOM Alert custom fields paramaters.
The issue is that we need to have this parameter mapped with the SCOM Alert Path field instead of Custom field.
Is it possible from the SCOM side to accept custom values and assign them to Alert Path field through the connectors?
Thank you a lot in advance!

Hi
Alert path is read only property for alert, you can not change this parameter. you can use custom field(1 to 9) or Ticket Id for alert.
Regards
sridhar v

Recovery from a SCOM alert - ORCH or task - best practice?

Hi - wonder if anybody in the "real world" can give me any guidance on this?
I look after SCOM and have traditionally been tasked with creating recovery scripts for certain custom alerts. I am also involved in the ORCH sphere but not totally responsible. We seem to be creating recovery in SCOM still but not ORCH.
I would have thought that the idea would be best to monitor for the SCOM alert in ORCH and use the flexibility of the latter to do checks and do a fix.
Are you limited in ORCH to how many alerts you can monitor or is there reasons to still do in SCOM? Just wondering which way we should really be heading?
thanks

I would suggest you keep using both. Recovery scripts in scom work just fine for basic recovery procedures that are performed locally on the monitored node. It is a simple, thus quite reliable framework for responding to incidents. However,
if your recovery procedure is complex and involves coordination of multiple activities running on different systems, then Orchestrator will be the right tool to handle it.
Gleb.

SCOM 2012 R2 Data Warehouse failed to request a list of management packs from SQL RS server

Hello, I get this alert can someone help me out ?
I did check the Proxy and is configured on all the MS and DW server.
Alert Description
Data Warehouse failed to request a list of management packs which contain
reports deployed to SQL Reporting Services Server. Report deployment process
failed to request management pack list from SQL RS Server. The operation will be
retried.
Exception 'WebException': The request failed with HTTP status 407:
Proxy Authentication Required ( Forefront TMG requires authorization to fulfill
the request. Access to the Web Proxy filter is denied. ).
One or more
workflows were affected by this.
Workflow name:
Microsoft.SystemCenter.DataWarehouse.Deployment.Report
Instance name:
Data Warehouse Synchronization Service
Instance ID:
{FDC7C774-397C-3660-9D57-EFBED3B60329}

Every call to the SRS generates a call to the OpsMgr SDK on Root Management
Server to check permissions (security integration). It apepars the account
the call is made under does not have access.
To figure out which account is used follow this process:
1) Run console and click on "Run As Profiles" in the Administration space;
2) Double-click "Data Warehouse Report Deployment Account";
3) Click on "Run As Accounts" tab;
4) If you have a line in the accounts which lists your Root Management
Server in the "Target Computer" column, note the account name in the "Run As
Account" column. If you do not have such a line, follow steps 2-4 for the
"Default Action Account" profile and note the account name;
5) Click on "Run-As Accounts" in the Administration space and double click
the account name which you got on step 4)
6) Switch to the "Account" tab and note domain name and user name;
Once you found the account (say, DOMAIN\user) check that it is a member of
the User Role "Operations manager Report Security Administrators". If not -
add it and the process will recover automatically.
Also You can refer below links
http://blogs.technet.com/b/smsandmom/archive/2007/09/06/system-center-operations-manager-doesn-t-show-any-reports.aspx
http://www.networksteve.com/enterprise/topic.php/Data_Warehouse_failed_to_request_a_list_of_management_packs..._E/?TopicId=16627&Posts=2
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

SCSM's Allowed List for SCOM CI Connector not working as expected

Hi Everyone,
We're running into some unexpected behavior with the SCOM CI Connector, wondering if anyone can shed some light on it. Our requirement is to ensure Distributed Applications are not sync'd from SCOM to SCSM (hence, they don't show up in the "All
Business Services" view). We have only two MPs in SCOM/SCSM that sync Distributed Applications, both of which are for SharePoint monitoring.
We have the 2 SharePoint MP's in both SCSM and SCOM. We've configured the SCOM CI Connector to select the 2 SharePoint MP's for synchronization.
Now, we thought all we'd need to do to ensure the SharePoint Distributed Applications no longer sync from SCOM to SCSM is remove the "System.Service" class from the Allowed List of classes for SCOM CI -- which we did, however, they continue to
sync.
After a fair amount of back and forth trying to figure out how we need to configure the Allowed List of classes for the SCOM CI Connector to ensure the DA's aren't sync'd any more, we finally removed ALL classes from the Allowed List. Surely, this
will stop the sync we thought -- however, after having deleted the SharePoint Business Service CI's, removing ALL classes from the Allowed List, and then rerunning the SCOM CI Connector, the Distributed Applications associated with the SharePoint MP's STILL
come over.
Is there something I'm missing here?
Thanks!

Hi -- can anyone provide any feedback for me on this one?
Thanks!

SCOM CI Connector is stuck in runnig state

Hello,
I have problem with SCOM CI Connector in SCSM. It is stuck in running and 5%. I have tried to disable and re-enable but without success. I can't see any workflow related to this connector in workflow status. Is there any possibility how to stop this or diagnose
what is wrong?
Thanks

I'm assuming you've tried refreshing the connector view. Have you tried reconnecting the console to ensure that you're looking at fresh data?
You can try this:
Get-SCSMConnector "Name" |Set-SCSMConnector -state:disabled
And then try restarting it.
- Get on the floor, do that dinosaur

Multiple SCOM Alerts for the same unique Windows Event

Multiple SCOM Alerts are being raised for a single Windows event.
For e.g., below is the event :
Date and Time: Description:
12/15/2014 5:15:36 PM Initiating move for database 'xxxdb02' (FromServer=xxxdagnode1.dt.inc, ToServer=, MoveComment=<Null>)
Log Name:
Microsoft-Exchange-HighAvailability/Operational
Source:
Microsoft-Exchange-HighAvailability
Event Number:
306
Level:
4
Logging Computer:
xxxdagnode1.dt.inc
User:
NT AUTHORITY\SYSTEM
Event Data:
< DataItem type =" System.XmlData " time =" 2014-12-15T17:15:37.9848250-05:00 " sourceHealthServiceId =" 261D34BA-3596-ABCF-3728-B5A0AC035D90 " >
< UserData >
< EventXML >
< UniqueId > 2014.12.15.05.15.35.285#9#xxxdagnode2#4d0ce477-5f5c-4304-8c59-292a4a8ca809 </ UniqueId >
< DatabaseName > xxxdb02 </ DatabaseName >
< DatabaseGuid > 4d0ce477-5f5c-4304-8b59-292a4a8ca809 </ DatabaseGuid >
< ActiveServer > XXXDAGNODE1.dt.inc </ ActiveServer >
< ActionCategory > Move </ ActionCategory >
< ActionInitiator > Automatic </ ActionInitiator >
< ActionReason > StoreStopped </ ActionReason >
< AmRole > PAM </ AmRole >
< PAMServer > xxxdagnode2.dt.inc </ PAMServer >
< MountFlags > None </ MountFlags >
< DismountFlags > SkipCacheFlush </ DismountFlags >
< MountdialOverride > None </ MountdialOverride >
< FromServer > xxxdagnode1.dt.inc </ FromServer >
< TargetServer />
< TryOtherHealthyServers > True </ TryOtherHealthyServers >
< SkipValidationChecks > None </ SkipValidationChecks >
< MoveComment > <Null> </ MoveComment >
</ EventXML >
</ UserData >
</ DataItem >
But three alerts were raised for this event.
I double checked with the Unique ID for the Windows Event.
Also the Duplicate alerts show the Same event in the 'Alert Context' field.
My environment:
3 SCOM 2012 R2 UR3 Management Servers.
1 SQL DB Server
Service Manager Connector is configured for Alert Sync. However this issue also affect the alerts that are not synced.
Anybody else faced this issue?

Hi,
It seems like that you are using rule to monitor this event, unlike monitors, rules can continue to send alerts as long as the condition that caused the alert persists or repeats. Depending on what the rule is checking for, a single issue could possibly
generate a huge number of alerts. To prevent the noise of too many alerts, alert suppression can be enabled for a rule.
More details, please check article below:
http://technet.microsoft.com/en-us/library/hh212847.aspx
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

XCmd Service - SCOM alert - Unpredictable state

Hey folks,
I keep get a SCOM alert for an unpredictable state for the xcmd service.
It says:
The xCmd Service service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.
This is only happening on our Server 2008 and 2008 R2 machines.
Been googling around and cant find a fix. Anyone have an idea?

Have you checked the product knowledge of the alert? It gives you the answer you are looking for:
Summary
This rule generates an alert when the Service Control Manager detects that a service has started with an invalid configuration. It is important to note that even though the Service Control Manager detected an invalid configuration, the service still started
successfully.
The service may not be running as expected and may behave in an unpredictable manner. Additionally, the service may not be able to be restarted until the issue is resolved.
Sample Event:
This rule generates an alert whenever any of the following events occur and are recorded in the System Event Log:
The %1 service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.
The Service Control Manager encountered an error that has undone a configuration change to the %1 service. The service's %2 is currently in an unpredictable state. If you do not correct this configuration, you may not be able to restart the %1 service or
you may encounter other errors. To ensure that the service is configured properly, use the Services snap-in in MMC.
â€¢
Source: Service Control Manager; Event ID: 7030The %1 service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.
â€¢
Source: Service Control Manager; Event ID: 7037The Service Control Manager encountered an error that has undone a configuration change to the %1 service. The service's %2 is currently in an unpredictable state. If you do not correct this configuration, you
may not be able to restart the %1 service or you may encounter other errors. To ensure that the service is configured properly, use the Services snap-in in MMC.
Causes
This alert is generated whenever any of the following conditions occur:
â€¢
The service is configured to run interactively but system policy is configured to prevent services from running in this mode.
â€¢
An error occurred while attempting to configure the service.
Resolutions
There are two possible resolutions for this alert. Refer to the event that generated the alert and select the appropriate set of resolution steps.
Event ID: 7030
To resolve this alert, consult with a subject matter expert or the vendor to determine if the service must run interactively on the desktop. If not, follow these steps:
â€¢
Open the Services MMC snap-in.
â€¢
Double-click the appropriate Service and open that serviceâ€™s property sheet.
â€¢
Click the Log On tab.
â€¢
Clear the Allow service to interact with desktop check box.
If the service must run interactively, you will need to change the â€œAllow service to interact with desktopâ€ system policy. To do this, perform the following steps:
HKLM\System\CCC\Control\Windows
0 - Enabled
1 - Disabled
â€¢
Open the Registry Editor.
â€¢
Navigate to the registry value â€œNoInteractiveServicesâ€ at:HKLM\System\CCC\Control\Windows
â€¢
Set the value from â€œ0â€ to â€œ1â€ 0 - Enabled1 - Disabled
â€¢
Open the Services MMC snap-in.
â€¢
Select the appropriate Service and restart it.
Event ID: 7037
Resolve this alert by doing the following:
â€¢
Open the Services MMC snap-in.
â€¢
Double-click the appropriate service and open that serviceâ€™s property sheet.
â€¢
Click each of the tabs and verify that the configuration information is appropriate. Update any configuration fields that have incorrect or corrupted data in them.
â€¢
Restart the service and check the event log to determine whether another instance of event 7037 has occurred. If not, the issue has been resolved.
â€¢
If a new instance of event 7037 occurs, use Sc.exe to examine the serviceâ€™s advanced configuration settings and then update them as appropriate. Use the
qc and config commands within Sc.exe to view and configure the service.
Regards,
Marc Klaver
http://jama00.wordpress.com/

SCOM Alerts Connector run as failed

Similar Messages

Maybe you are looking for