Exchange connector failed

Hi,
Does anyone have a method of monitoring the Exchange connector in SCSM. Apparently ours had a problem processing a message, which I fixed, but we didn't know abou the error until several hours after it happened.
Thanks

i have two the same incidents wich differ only with the Event Description how can i monitor the only one event with the SCOM
The 1 Event apear only when MailFlow is Stopped, and the second i have every minute,
i ask microsoft about the 2 event but i was told to vait for connector update
1 Event Description
Log Name:      Operations Manager
Source:        Health Service Modules
Date:          04.07.2011 14:02:17
Event ID:      33880
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SCSM.mb.local
Description:
A Windows Workflow Foundation workflow failed during execution.
Workflow Type: Microsoft.SystemCenter.ExchangeConnector.ProcessEmailsWorkflow
Workflow Identifier: 5f39606b-eaaa-28a8-c8d1-5713551b73f7
Exception Type: System.NullReferenceException
Exception Message: Object reference not set to an instance of an object.
Exception Stack:    at Microsoft.SystemCenter.ExchangeConnector.ExchangeInbox.ProcessMail()
   at Microsoft.SystemCenter.ExchangeConnector.ProcessEmailsWorkflow.Execute(ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.CompositeActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(Activity activity, ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
   at System.Workflow.Runtime.Scheduler.Run()
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Health Service Modules" />
    <EventID Qualifiers="49152">33880</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-07-04T11:02:17.000000000Z" />
    <EventRecordID>2684963</EventRecordID>
    <Channel>Operations Manager</Channel>
    <Computer>SCSM.mb.local</Computer>
    <Security />
</System>
<EventData>
    <Data>Microsoft.SystemCenter.ExchangeConnector.ProcessEmailsWorkflow</Data>
    <Data>5f39606b-eaaa-28a8-c8d1-5713551b73f7</Data>
    <Data>System.NullReferenceException</Data>
    <Data>Object reference not set to an instance of an object.</Data>
    <Data>   at Microsoft.SystemCenter.ExchangeConnector.ExchangeInbox.ProcessMail()
   at Microsoft.SystemCenter.ExchangeConnector.ProcessEmailsWorkflow.Execute(ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.CompositeActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(Activity activity, ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
   at System.Workflow.Runtime.Scheduler.Run()</Data>
</EventData>
</Event>
2 Event Description
Log Name:      Operations Manager
Source:        Health Service Modules
Date:          04.07.2011 14:02:13
Event ID:      33880
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SCSM.mb.local
Description:
A Windows Workflow Foundation workflow failed during execution.
Workflow Type: Microsoft.SystemCenter.ExchangeConnector.ProcessEmailsWorkflow
Workflow Identifier: d90a1166-01fb-c687-0c9b-1883794d8adc
Exception Type: System.ArgumentNullException
Exception Message: Value cannot be null.
Parameter name: Cannot find Exchange connector status instance: InboxConnector.928babe243f6416284ca3f4af4154a9f
Exception Stack:    at Microsoft.SystemCenter.ExchangeConnector.ExchangeInbox.initializeConnectorObjects()
   at Microsoft.SystemCenter.ExchangeConnector.ExchangeInbox.ProcessMail()
   at Microsoft.SystemCenter.ExchangeConnector.ProcessEmailsWorkflow.Execute(ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.CompositeActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(Activity activity, ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
   at System.Workflow.Runtime.Scheduler.Run()
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Health Service Modules" />
    <EventID Qualifiers="49152">33880</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-07-04T11:02:13.000000000Z" />
    <EventRecordID>2684936</EventRecordID>
    <Channel>Operations Manager</Channel>
    <Computer>SCSM.mb.local</Computer>
    <Security />
</System>
<EventData>
    <Data>Microsoft.SystemCenter.ExchangeConnector.ProcessEmailsWorkflow</Data>
    <Data>d90a1166-01fb-c687-0c9b-1883794d8adc</Data>
    <Data>System.ArgumentNullException</Data>
    <Data>Value cannot be null.
Parameter name: Cannot find Exchange connector status instance: InboxConnector.928babe243f6416284ca3f4af4154a9f</Data>
    <Data>   at Microsoft.SystemCenter.ExchangeConnector.ExchangeInbox.initializeConnectorObjects()
   at Microsoft.SystemCenter.ExchangeConnector.ExchangeInbox.ProcessMail()
   at Microsoft.SystemCenter.ExchangeConnector.ProcessEmailsWorkflow.Execute(ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.CompositeActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(Activity activity, ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
   at System.Workflow.Runtime.Scheduler.Run()</Data>
</EventData>
</Event>

Similar Messages

Exchange Connector 3.1 Fails on Test of "Run as Account" -EventViewer has "Unmarshalling Policy check" error

When Testing the Exchange Connector 3.1 during Create Connector, it gives the following Error when Testing the Connection:
"The connection to the server was unsuccessful. Please check the server name and/or credentials entered.
Additional Information: Unable to validate credentials, please refer the the event logs for more information (Err Type: AutoDiscoverRemoteException, Message=The Autodiscover service returned an error.)"
Event Viewer shows the following each time I Try:
Event 10031 COMRunTime
An unmarshaling policy check was performed when unmarshaling a custom marshaled object and the class {45FB4600-E6E8-4928-B25E-50476FF79425} was rejected.
Other Info:
Service Manager Workflow Account is a Local Admin
Service Manager Worfklow Account is a Service Manager Full Admin
Email Account is Create in Exchange 2010 Sp1
Service Manager 2012 R2 +CU5 +CU% Hotfix are installed. (Same error when running +CU4 though.
UAC is Turned Off.
Exchange Web Services Managed API Client DLL (x64) (Microsoft.Exchange.WebServices.dll is installed and copied into Service Manager Directory.)
Both Microsoft.SystemCenter.ExchangeConnector.dll and Microsoft.SystemCenter.ExchangeConnector.resources.dll are copied into Service Manager Directory.
Exchange connector MP has been imported.
David Baur

Partly resolved...
What I did to resolve this was to go into ADSIEdit.msc and go to the path of AdminImpersonateAll.In ADSI Edit, open 'Configuration'. Inside Configuration go to Services->Microsoft Exchange->then CN=YourOrgName->RBAC->Role Assignments-> and
Deleted the CN=AdminImpersonateAll.
Then I re-ran the Powershell script on the Exchange Server:
New-ManagementRoleAssignment -Name:AdminImpersonateAll
-Role:ApplicationImpersonation -User SCSMWorkflow<o:p></o:p>
After doing this, the Connector for Exchange 3.1 worked.
BUT...the event error is still occurring and it repeats?
David Baur

Getting error when trying to create Exchange Connector in System Center Service Manager 2012

Getting error when trying to create Exchange Connector in System Center Service Manager 2012
The connection to the server was unsuccessful. Please check the server name and/or credentials entered.
Additional Information: The server URL is not accessible or the user does not have permission to access it (message: The request failed. The remote server returned an error: (401) Unauthorized.
Warm Regards, Pramod Kumar Singh Manager-IT

Someone sorted out this issue by installing API 1.2 and copying the dll files to the service manager server ,service folder and replacing it with API 2.0 dll files.
Also, your question is related to SCSM, please post at SCSM forum if you have further question.
Juke Chou
TechNet Community Support

SCSM 2012 Exchange connector 3.0 Status Never Run.

HI ,
SCSM exchange connector was Running for almost 8 months . all of sudden it stopped pulling email from Exchange Server.
I looked in to the issue and did not found any major error in the Event log “Operation Manager”
Only event were warning, “OpsMgr Config Service failed to send the dirty state notifications to the dirty OpsMgr Health Services. This may be happening because the Root OpsMgr Health Service is not running.” I did not installed SCOM at
all. This server is not connected to any SCOM server.
I have reinstalled the Exchange web Service API (copied file to SCSM folder)
I have reinstalled exchange connector 3.0 (copied files to SCSM folder and imported management packs)
Created new Exchange connector and all test passed.
But the connector status stays “Never Run”
In my regedit ,I also made the following changes
KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Service Manager Exchange Connector
EnableEWSTracing = 7
LoggingLevel= 7
I have also looked and tried every option with “Run as Account” and also making admin Role.
I am not getting any error in the log apart from following warning .
I did not found any major error in the Event log “Operation Manager
Only event were warning, “OpsMgr Config Service failed to send the dirty state notifications to the dirty OpsMgr Health Services. This may be happening because the Root OpsMgr Health Service is not running.
Can someone help me , what should be the next step.

the reason you are seeing operations manager errors is because Service manager uses the operations manager SDK to do all of it's work. the error that you are seeing "OpsMgr Config Service failed to send the dirty state notifications to the dirty OpsMgr
Health Services. This may be happening because the Root OpsMgr Health Service is not running." means that the service manager configuration service can't notify the data access service that there are changes to it's MP base, for whatever reason.
i would stop all the system center services on this server, go into the service manager folder, find the "Health state" and "Config State" folders, and move them somewhere else on the system, then restart both services. assuming your
system isn't otherwise damaged, this will force both the config and data access services to rebuild their cache from the database, and should unstick your workflows.

Error while installing AD exchange connector

Hi All,
When I m trying to install exchange connector 9.1.1.7.0 in OIM 11.1.1.3.0 I m getting the following error
the error occurred while importing connector xml files
please help me in this regards
DOBJ.XML_IMPORT_ERROR
oracle.iam.reconciliation.exception.ConfigException: oracle.iam.platform.entitymgr.SchemaUpdateException: CREATE TABLE RA_EXCHANGE12 (RECON_TABLE_KEY NUMBER(19,0) PRIMARY KEY NOT NULL,re_key NUMBER(19,0) REFERENCES RECON_EVENTS(re_key) NOT NULL,RECON_CHGLOGATTR_IDXLST VARCHAR2(256),RECON_DBOVERQUOTALIMIT18282E09 VARCHAR2(10),RECON_OTHERTELEPHONENU8FAAE255 VARCHAR2(20),RECON_ADSERVER6D5E9E00 VARCHAR2(19),RECON_DBUSERDEFAULTS311616E5 VARCHAR2(5),RECON_MAILNICKNAMEC69E0A1F VARCHAR2(50),RECON_DELETEDITEMFLAGS4B8499C1 VARCHAR2(2),RECON_MAILSTORENAMEF58A4893 VARCHAR2(300),RECON_SUBMISSIONCONTLED9766CE0 VARCHAR2(10),RECON_DELIVERYCONTLENG317E1988 VARCHAR2(10),RECON_PAGERNUMBER582E286 VARCHAR2(32),RECON_MAIL VARCHAR2(80),RECON_MOBILENUMBERF6563487 VARCHAR2(20),RECON_DBOVERHARDQUOTALE34CA3C8 VARCHAR2(10),RECON_LOGONNAMED4149F30 VARCHAR2(150),RECON_OBJECTGUID VARCHAR2(32),RECON_GARBAGECOLLECTIO4F439638 VARCHAR2(10),RECON_EXCHANGERECIPIENTB8EAAD7 VARCHAR2(10),RECON_DBSTORAGEQUOTA8D855431 VARCHAR2(10),RECON_DISPLAYNAME66894369 VARCHAR2(100),RECON_TELEPHONENUMBER7AECF325 VARCHAR2(20),RECON_EXCHANGEHIDEFROM83F62EF4 VARCHAR2(5),RECON_SAMACCOUNTNAME VARCHAR2(256))
Regards
Sri

Did you tried and failed in importing the AD connector in OIM?
Login to the OIM database and check if that table already exists. Do you get any other errors before or after this one in the diagnostic logs.

Creating multiple mailboxes on Exchange 2007 fails

Hi All,
We have a problem to create multiple mailboxes simultaneously on Exchange 2007 using the OIM Exchange connector. Only one of the mailboxes is created when multiple powershell scripts are launched at the same time. This problem only occurs in the production environment and not on the Exchange 2007 test server. Therefore it's likely to be an Exchange 2007 server setting causing the other powershell processes and mailboxes to fail. Has anyone else experienced this problem?
Thanks,
Albin

hi.
have you managed to solve this issue? we have a similar problem when updating some exchange mailbox variables through powershell cmds via OIM. if we run several cmds simultaneously, or right after each other, only the first one is run. tried googling it, but no luck so far.
thanks,
tinba

Exchange connector to hosted Exchange Server gives Connection errors in log.

I have setup the exchange connector within SCCM 2012 R2 CU3. Everything seems to work. I get the EAS connected devices discovered in the SCCM console.
The Hosted Exchange server I used is https://ps.outlook.com/PowerShell-Live-ID
Although everything seems to work i frequently get the following errors in the EASdisc.log:
ERROR: [MANAGED] Failed to open Runspace. Exception: System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server failed with the following error message : The SSL connection cannot be established. Verify that the service
on the remote host is properly configured to listen for HTTPS requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command
on the destination to analyze and configure the WinRM service: "winrm quickconfig -transport:https". For more information, see the about_Remote_Troubleshooting Help topic.~~   at System.Management.Automation.Runspaces.AsyncResult.EndInvoke()~~
  at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResult asyncResult)~~   at System.Management.Automation.Runspaces.RunspacePool.Open()~~   at System.Management.Automation.RemoteRunspace.Open()~~
  at Microsoft.ConfigurationManager.ExchangeConnector.ExchangeRunspace.InitRunspace()
ERROR: Failed to call Initialize of managed COM. error = Unknown error 0x80131501
ERROR: Failed to initialize managed com instance. Error = Unknown error 0x80131501, -2146233087
There is no fixed interval in which these errors are reported.
Can i neglect these errors, or am I missing something?
I found the following thread without a solution:
http://community.office365.com/en-us/f/156/t/265109.aspx

Try to use FQDN of Cas server in URL and Add CASADMIN into all the three Exchage Roles: Recipient Management; View Only Organization Management; and Server
Management. Enabled the Windows Authentication on Exchange CAS Server for /powershell in IIS.
Also You can check below link
https://social.technet.microsoft.com/Forums/en-US/e7ca3f0c-a793-4437-8050-2de4c9d9253c/exchange-connector?forum=configmanagergeneral
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"Mai Ali | My blog:
Technical | Twitter:
Mai Ali

Exchange Connector to O365 is dropping

Hello, we have configured Exchange Connector in SCSM 2012 R2 with Office 365.
Connector fails few times per week and usually restart of the workflow server works. When I look on connectors, finished time on connector is up to date but work items are not created. I've tried to completely recreate the connector and also delete Health
Service Cache without any success. Event log is clear (logging level is maximal)
Is there any way how to troubleshoot this?
Thanks

I checked that. No workflow requires attention but any of them wasn't running for few days. Also I have message in event log about Health Service:
OpsMgr Config Service failed to send the dirty state notifications to the dirty OpsMgr Health Services. This may be happening because the Root OpsMgr Health Service is not running.
But this service is running and I also tried to restart it but it doesn't change this state. I've also tried to run AD connector and I can see it as running and finished in log but not in the console. Also This connector runs only for one second, so
I guess it's not syncing. What can I do with workflows stuck like this?
Thanks

SCCM 2012 SP1 CU1 Exchange connector error

Hi, I have configured the Exchange connector on SCCM 2012 SP1 CU1 towards an Exchange 2013. I get this error in easdisk.log:
ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed. Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The
value "$true" could not be converted to type System.Boolean."~~ at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)~~ at System.Management.Automation.PowerShell.Invoke(IEnumerable
input, PSInvocationSettings settings)~~ at System.Management.Automation.PowerShell.Invoke()~~ at Microsoft.ConfigurationManager.ExchangeConnector.Connector.Invoke(PSCommand cmd)
If I launch the same command (Get-recipient), using the same account SCCM uses, directly in PSRemote on the Exchange server, it works correctly. I tried also to make the account Organization Manager, but same result.
Any hints?
thanks,
David Papini
MCSA, MCT

I made a thread about unmanageable devices. I had this error too after updating my environement. In my scenario this particular error only occured after I updated to Exchange 2013 CU1. Therefore I believe this error is an Exchange related bug.
SCCM 2012 with Exchange 2013 gave me this error:
ERROR: [MANAGED] Invoking cmdlet Set-ActiveSyncMailboxPolicy failed. Exception: System.Management.Automation.RemoteException: A parameter cannot be found that matches parameter name 'IsDefaultPolicy'.
SCCM 2012 CU1 with Exchange 2013 gave me the same error:
ERROR: [MANAGED] Invoking cmdlet Set-ActiveSyncMailboxPolicy failed. Exception: System.Management.Automation.RemoteException: A parameter cannot be found that matches parameter name 'IsDefaultPolicy'.
SCCM 2012 CU1 with Exchange 2013 CU1 gave me your error:
ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed.
Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."

Exchange Connector 3.0 (Hotfix Release) Error - Error Message=The key value of an object cannot be changed.

Hello,
I am running Service Manager 2012 with the Exchange Connector 3.0 RTM (Re-release Version). The issue I have is that when an e-mail is processed that is trying to update the status or event log of an incident, the Exchange Connector encounters an error
and will not update the object. The Operations Manager log denotes:
Exchange Connector: Unable to process mail item. Subject="Close Ticket: [IRXXXXX]", Error Message=The key value of an object cannot be changed.
This will happen on a seemingly random selection of Incident work items. I cannot correlate them with a specific template, exchange connector, or incident tier queue that could be causing the issue. I can recreate the way a specific ticket
was created and update it through e-mail without issue, and the next ticket can cause the error to trigger.
I have already opened a Microsoft Support Case using our Software Assurance agreement. After a few months of troubleshooting the issue and trying different fixes, Microsoft support said they were unable to fix the problem and that we would need to
purchase Premier support to go further. At this point I thought I would reach out to the community for ideas.
The setup I have for the Exchange connectors is as follows.
I have three separate Exchange connectors set up to three different mailboxes. One Exchange connector processes external support tickets and applies a specific template. Another processes client support tickets and applies a different template.
And the last Exchange connector processes internal tickets and also processes the updates of tickets created by the other two exchange connectors.
Here are the fixes I've attempted so far:
1. Changed the templates that each Exchange connector applies.
2. Changed the management pack that each template is stored in.
3. Checked my management pack(s) for extended classes by searching for Extension="true" (This was also checked by Microsoft support)
4. Deleted each Exchange connector and recreated each connector
5. Deleted each Exchange connector, deleted the management pack, and reinstalled the management pack and connectors
6. Repeated Step 5, deleted Microsoft.SystemCenter.ExchangeConnector.dll and Microsoft.SystemCenter.ExchangeConnector.resources.dll and then installed the Exchange connector Re-release version 3.0 Published 10/7/2013 (which is supposed to address this
issue)
7. Deleted the HealthServiceState folder and restarted the Management Service
I'm not really sure what to do at this point. I've put many hours into customizing my installation to get it working for my organization so reformatting and starting from scratch would be a nightmare scenario. This environment is in production.
I do have a band-aid in place using Orchestrator. Basically I have a monitor task searching for the error message and when it finds one it searches the mailbox for the offending e-mail and applies either the Resolve or Close status change that is requested
from the user. However, I do not have it working to update the ticket if a comment is applied to the incident. If anyone is in this position and needs to know how to apply this Orchestrator task I am willing to provide my workflow.
I am new to the community and am already impressed with the amount of help and effort there is in this forum. I appreciate in advance any help that is provided and am open to any ideas at this point. I can post more information as needed.
Thank you,
John

Yes that is the whole template. However, I did confirm that this is only happening to incidents where either of two situations triggers a runbook to fire and modify the incident. When I remove the activity from the incident it does clear the
issue. For some background the first Runbook Activity set's the first response date when an incident is resolved if the first response value is null. The second assigns the incident to a user upon creation if the title contains assignto:username;
1.)
<ObjectTemplate ID="Template.d33b5bbcaf3c49b18d8b72bc1e5e1ee4" TypeID="IncidentManagement!System.WorkItem.Incident.ProjectionType">
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/Escalated$">False</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/NeedsKnowledgeArticle$">False</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/HasCreatedKnowledgeArticle$">False</Property>
<Object Path="$Context/Path[Relationship='CustomSystem_WorkItem_Activity_Library!System.WorkItemContainsActivity' TypeConstraint='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity']$">
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/RunbookId$">4085f0da-ab83-48e5-bbe3-1f3b5fa2dc4a</Property>
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/TemplateId$">Template.d33b5bbcaf3c49b18d8b72bc1e5e1ee4</Property>
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/IsReadyForAutomation$">True</Property>
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/PropertyMapping$"><?xml version="1.0" encoding="utf-16"?>
<ParameterMapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<ParameterList>
<RunbookParameterItem>
<Name>Get RA Guid</Name>
<Id>344b15effc1a44528e517c5b4227179c</Id>
<Type>String</Type>
<Value>Generic::Id</Value>
<Direction>In</Direction>
<ContextInfo />
</RunbookParameterItem>
</ParameterList>
<RunbookId>4085f0da-ab83-48e5-bbe3-1f3b5fa2dc4a</RunbookId>
</ParameterMapping></Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Activity_Library!System.WorkItem.Activity']/ChildId$">1906</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Activity_Library!System.WorkItem.Activity']/Status$">$MPElement[Name='CustomSystem_WorkItem_Activity_Library!ActivityStatusEnum.Active']$</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Activity_Library!System.WorkItem.Activity']/Skip$">False</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Library!System.WorkItem']/Title$">Set First Response on Resolve</Property>
</Object>
</ObjectTemplate>
2.)
<ObjectTemplate ID="Template.b311e1f9126e4e19bbbbeb65ddb220ba" TypeID="IncidentManagement!System.WorkItem.Incident.ProjectionType">
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/Escalated$">False</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/Status$">$MPElement[Name='CustomSystem_WorkItem_Incident_Library!IncidentStatusEnum.Active']$</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/NeedsKnowledgeArticle$">False</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Incident_Library!System.WorkItem.Incident']/HasCreatedKnowledgeArticle$">False</Property>
<Object Path="$Context/Path[Relationship='CustomSystem_WorkItem_Activity_Library!System.WorkItemContainsActivity' TypeConstraint='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity']$">
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/RunbookId$">ca88b13b-861a-4d39-a3cb-fd912d951e35</Property>
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/TemplateId$">Template.b311e1f9126e4e19bbbbeb65ddb220ba</Property>
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/IsReadyForAutomation$">True</Property>
<Property Path="$Context/Property[Type='CustomMicrosoft_SystemCenter_Orchestrator!Microsoft.SystemCenter.Orchestrator.RunbookAutomationActivity.Base']/PropertyMapping$"><?xml version="1.0" encoding="utf-16"?>
<ParameterMapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<ParameterList>
<RunbookParameterItem>
<Name>RA Activity GUID</Name>
<Id>5677d117a0294a2c898a695032f26c72</Id>
<Type>String</Type>
<Value>Generic::Id</Value>
<Direction>In</Direction>
<ContextInfo />
</RunbookParameterItem>
</ParameterList>
<RunbookId>ca88b13b-861a-4d39-a3cb-fd912d951e35</RunbookId>
</ParameterMapping></Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Activity_Library!System.WorkItem.Activity']/ChildId$">1120</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Activity_Library!System.WorkItem.Activity']/Status$">$MPElement[Name='CustomSystem_WorkItem_Activity_Library!ActivityStatusEnum.Active']$</Property>
<Property Path="$Context/Property[Type='CustomSystem_WorkItem_Activity_Library!System.WorkItem.Activity']/Skip$">False</Property>
<Property Path="$Context/Property[Type='WorkItem!System.WorkItem']/Title$">Execute Orchestrator IR - Autoassign</Property>
</Object>
</ObjectTemplate>

PeopleSoft connector failing after upgrade

Has anyone heard of the Peoplesoft connector failing to connect after a PeopleTools upgrade? We have 9.1.1.5 of the Peoplesoft User Management Connector installed. Prior to the upgrade of PeopleTools, it was on version 8.50.09 and we were able to connector and provision users. After the upgrade to PeopleTools 8.50.16, we cannot connect. Below is a piece of the log file where we are getting this error:
DEBUG,18 Apr 2011 11:03:33,015,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader:findClass - Data: loading class - Value: oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager
DEBUG,18 Apr 2011 11:03:33,026,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader/findClass entered.
DEBUG,18 Apr 2011 11:03:33,026,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader:findClass - Data: loading class - Value: psft.pt8.joa.API
DEBUG,18 Apr 2011 11:03:33,027,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : getConnectionWithTimeout:: STARTED
DEBUG,18 Apr 2011 11:03:33,027,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader/findClass entered.
DEBUG,18 Apr 2011 11:16:09,519,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader/findClass entered.
DEBUG,18 Apr 2011 11:16:09,519,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader:findClass - Data: loading class - Value: bea.jolt.JoltVersionException
DEBUG,18 Apr 2011 11:16:09,522,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader/findClass entered.
DEBUG,18 Apr 2011 11:16:09,523,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader:findClass - Data: loading class - Value: psft.pt8.joa.PSMessage
ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],====================================================
ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : getConnectionWithTimeout : Unable to connect to Application Server. Try :: 1
ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],====================================================
ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],====================================================
ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : getConnectionWithTimeout : Previously created Session Destroyed : 1
ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],====================================================
DEBUG,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : getConnectionWithTimeout:: FINISHED
INFO,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : connect : Connect = false
ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],====================================================
ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : connect : Maximum Retries Reached. exiting........
ERROR,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],====================================================
DEBUG,18 Apr 2011 11:16:09,524,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : closeSession:: STARTED
DEBUG,18 Apr 2011 11:16:09,525,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : closeSession : Session Closed : true
DEBUG,18 Apr 2011 11:16:09,525,[OIMCP.PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager : closeSession:: FINISHED
ERROR,18 Apr 2011 11:16:09,530,[PSFTUM],====================================================
ERROR,18 Apr 2011 11:16:09,530,[PSFTUM],oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProvisionManager : createUser : Connection Failed
ERROR,18 Apr 2011 11:16:09,530,[PSFTUM],====================================================
DEBUG,18 Apr 2011 11:16:09,530,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/setAdpRetVal entered.
DEBUG,18 Apr 2011 11:16:09,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getRetValString entered.
DEBUG,18 Apr 2011 11:16:09,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getRetValString - Data: class - Value: java.lang.String
DEBUG,18 Apr 2011 11:16:09,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getRetValString - Data: poRetVal.toString() - Value: PSFT.CONNECTION_ERROR
DEBUG,18 Apr 2011 11:16:09,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getRetValString - Data: Returning:sRetVal - Value: PSFT.CONNECTION_ERROR
DEBUG,18 Apr 2011 11:16:09,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/getRetValString left.
DEBUG,18 Apr 2011 11:16:09,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/setAdpRetVal - Data: Setting Adapter Return Value to PSFT.CONNECTION_ERROR - Value:
DEBUG,18 Apr 2011 11:16:09,531,[XELLERATE.ADAPTERS],Class/Method: tcAdpEvent/setAdpRetVal left.
OIM: 9.1.0.2
Any ideas?

You will have to use the new psjoa jar. See the connector documentation for compatible psjoa jar.

Custom Script Execution with 11.1.1.5.0 Exchange Connector

Folks ,
We would be cloning the 11.1.1.5.0 Exchange connector to support 2 different kind of mailboxes in Exchange server 2010 SP2.
The 2 kinds of mailboxes are Personal mailbox and a reference mailbox (similar like a personal mailbox , the only difference is that Auto-reply will be set on this mailbox).
OOTB Exchange connector will be used to create both of these mailboxes . However we want to set auto-reply only on reference mailbox using a powershell cmdlet
http://technet.microsoft.com/en-us/library/dd638217.aspx
So i would like to understand , does the connector provide such a capability to execute a cmdlet from a provisioning process via a process task or some other mechanism .
Thanks
Sid

Thanks Rahul , I have gone through the documentation .
But i dont understand , when doc mentiona you can execute a script before/after a user is created , so is this based on the event on the target after/before a mailbox is created or its triggerd from the create user task in OIM .
As i have 2 clones of exchange connector and both create mailboxes, i want invoke the script in 1 scenario and dont want to execute the script in other scenario .
thanks
Sid

Exchange Connector Setup: Could not establish trust relationship for the SSL/TLS secure channel

This may be more of a cert issue than an issue with SCSM, but here goes.
I am running into something new when creating an Exchange Connector (I swear its always something with this thing. Check the screen shot:
I can get to the service in IE, however there is a cert issue. Again, see the screen shot:
So it appears that the management server does not trust my Exchange cert, nor does it trust my root cert. I added the root CA cert to the management server snapin but still nothing.
If the root cert is under Trusted Root Certification Authorities, shouldn't it trust it? I'm not sure where to go from here?
- Get on the floor, do that dinosaur

Looking at that certificate path tab, it looks like this certificate is a self-signed certificate issued by the exchange server to the exchange server. is it safe to assume this is a lab environment? it's kinda rare for that to be left as-is in a production
exchange architecture.
If it is a self signed certificate (the Issuer and subject fields on the first page will be the same), then the only wat to trust it is to add that certificate to the trusted root certificate authorities under the system certificate store.
Here is an excellent tutorial on how to add certificates to the local machine trusted root store.
If this is a production environment, get with your exchange administrator, because you might be hitting the wrong CAS server, and getting the wrong certificate as a result.m

Exchange Connector 3.0 RTM - Wrong action log type (user comments are sometimes analyst comments)

Hi,
We started using Service Manager a few days ago and I'm noticing some strange behavior from the Exchange connector. Sometimes when a user replies to an e-mail, it get's added as an "Analyst comment", also the private checkbox has a dot in it (not
blank or checked, but a dot..)
In this screenshot user "Marwan" is a regular user, replying to us via email...
Any ideas?

Today there already is intelligence that checks if the recipient == affected user. I am merely suggesting to rewise and/or extend this logic
As I wrote, I see two possible ways here. The easy and the hard (optimal) way. The easy way would be to turn it around, meaning all comments = End-User comments unless it's coming from the Assigned User. So the check would be on the Assigned User instead
of the Affected User as it is today. I understand that some people might complain about this, and might have adapted to the current solution, so it should be optional. In my experience I just see this as more suitable for the customers needs. Well if the source
code could be released it would make it easier to make custom adjustments, e.g. change the Private boolean value to false etc. ;)
The hard optimal way would be to add more options for deciding when it's an Analyst and when it's an End-User. Of course the Exchange connector can't figure that out, but if it did comparison to preselected groups or perhaps User Roles (e.g. if recipient
is Incident Resolver and not affected user => analyst comment).
In any case it's an interesting discussion with many aspects, but one thing is for certain: the exchange connector is unfinished. Not broken, just lacking options. Today people are making alot of custom workflows and even their own connectors to accommodate
for these issues.

How to create a Service request using Exchange connector in SCSM 2012

HI ,
I am able to create Incident request using exchange connector.Could you please let me know that how can i create Service request using Exchange connector 3.0.
Thanks in advance.

Hi,
Select a service request's template for new work items on the last wizard's page.
Cheers,
Marat
Site: www.scutils.com Twitter:
LinkedIn:
Graveyard:

Exchange connector failed

Similar Messages

Maybe you are looking for