Service Manager Exchange Connector error

We have a noticed a few of these errors show up for the exchange connector.
Exchange Connector: Unable to process mail item. Subject="[SR15902] this is another test", Error Message=The key value of an object cannot be changed.
We are using the latest version of the exchange connector (7.5.2017.6). We recently added a second management server on another machine and it also has the exchange connector there.
Any ideas why we would get this error? Thanks in advance.
Thanks Lance

Hi,
I would like to confirm did you use Exchange connector 3.0, if that is the case, please try the newest connector published recently.
Exchange connector 3.1 is published, would you please try it:
System Center Service Manager Connector 3.1 for Exchange
http://www.microsoft.com/en-us/download/details.aspx?id=45291
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Similar Messages

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."

Operations Manager OpsMgr Connector error [event ID21006

Hello,
Our office is currently successfully running SCE 2007 SP1 on one system (NEWSCE) however it had been installed previously on a different server (OLDSCE). It would appear that the previous admin had successfully uninstalled the old server and had it successfully removed from the AD however on all of our servers (and some clients) I am seeing the following OpsMgr Connector error.
Event Type: Error
Event Source: OpsMgr Connector
Event Category: None
Event ID: 21006
Date:  2/17/2009
Time:  1:21:36 PM
User:  N/A
Computer: CRITICAL_SERVER
Description:
The OpsMgr Connector could not connect to OLDSCE.domain.com:5723. The error code is 10061L(No connection could be made because the target machine actively refused it.
). Please verify there is network connectivity, the server is running and has registered it's listening port, and there are no firewalls blocking traffic to the destination.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
This error seems to relate to the fact that I have two copies of MonitoringHost.exe resident in memory and when I look in the registry for OLDSCE I find there are two registry key entires for management groups for OLDSCE_MG and NEWSCE_MG
HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Agent Management Groups\
My question is this:
Can I simply delete the registy key for the OLDSCE_MG managment group and be done with this issue or is there more to it?
Thanks,

Hi , how to delete in registers readily . What is the result ?
the result ?

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.

Exchange connector stops working after patching?

our service manager exchange connector stopped working after patching that we performed on wed.
When starting or stopping the exchange connector we get this info in the Operations manager log file.
Error importing solutions. Error message:Management Pack [Microsoft.EnterpriseManagement.ServiceManager.Connector.AD,d43c3091-62c2-6404-607d-4376e592a89b] already imported.
Management Pack [Microsoft.EnterpriseManagement.ServiceManager.Connector.Sms,f772aa89-b934-2fac-4f37-5e0165d390ec] already imported.
Management Pack [Microsoft.SystemCenter.ConfigurationManager.Connector.PowerManagement,a070249c-6b56-37b8-d52c-a2906a63f9fc] already imported.
Management Pack [Microsoft.EnterpriseManagement.ServiceManager.Connector.Sms2011,fbea6f5a-838d-25a2-20af-fc21eb0b6706] already imported.
Management Pack [Microsoft.SystemCenter.ConfigurationManager2011.Connector.PowerManagement,bc23ed54-a33a-f608-05a9-c1f292140d2e] already imported.
Has anybody else seen this? Any suggestions?
Thanks Lance

Hi,
Did you try to restart SCSM's services?
If this doesn't help, I would try to delete and recreate the connectors.
More info:
System Center Service Manager Connector 3.0 for Exchange
http://www.microsoft.com/en-us/download/details.aspx?id=38791
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

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

Service Manager 2012 R2 - Exchange connector - Resolve an incident

I am trying to resolve an incident by adding [Resolved] to the subject of an email. The email already has [IR###] in it.
Responding to the email does update the incident so the Exchange connector is working. However adding the additional [Resolved] does not actually Resolve the ticket.
I verified the parsing keyboard was indeed [Resolved]
Ideas? I had trouble finding any detailed documentation on this feature.

The [IRxyz] needs to be in the
subject of the email, the [Resolved] must be in the
body of the email.
Than it should work with resolving the incident via email ;-)
Hope this helps.
Andreas Baumgarten | H&D International Group

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>

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

Error With Exchange Connector

Hi,
I installed the Exchange Connector (SCSM 2012 SP1), but
does not work and displays the following error:
Application: System Center Service Manager
Application Version: 7.5.2905.0
Severity: Error
Message: Microsoft.EnterpriseManagement.ServiceManager.UI.Administration.Connectors.Common.ConnectorTaskHandler..ctor()
System.MethodAccessException: Microsoft.EnterpriseManagement.ServiceManager.UI.Administration.Connectors.Common.ConnectorTaskHandler..ctor()
   at Microsoft.EnterpriseManagement.UI.SdkDataAccess.ConsoleTaskHandler.DoTask(IList`1 navigationNodes, NavigationModelNodeTask task, List`1 parameterList)
   at Microsoft.EnterpriseManagement.UI.SdkDataAccess.ConsoleTaskHandler.DoTask(IList`1 navigationNodes, NavigationModelNodeTask task)
   at Microsoft.EnterpriseManagement.ConsoleFramework.WindowJobRecord.ExecuteBackgroundJob(Object sender, ConsoleJobEventArgs eventargs)
   at Microsoft.EnterpriseManagement.ServiceManager.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)

I had copied the files:
Microsoft.SystemCenter.ExchangeConnector.resources.dll,
Microsoft.SystemCenter.ExchangeConnector.dll and
Microsoft.Exchange.WebServices.dll
to the directory:
C: \ Program Files \ Microsoft
System Center 2012 \ Service Manager
but it still did not work.

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

Need to stop the pop and Imap receive connectors to be able to start the pop and Imap services in Service Manager

Hello All,
I am hoping that someone else has run across this issue (may have started after CU5 was installed).
Upon every reboot I have found that the "Microsoft Exchange IMAP4" and "Microsoft Exchange POP3" services in the service manager will not start... basic reason in the event viewer is that the ports are already in use.
If I go into the ECP and disable my POP and Imap receive connectors I am able to then start the services.
After the services are started I can then go back to ECP and enable the receive connectors again and everything is fine .
Can anyone shed any light on this?
Thanks in advance ;)
Chris

Hello Winnie,
I bounced the Transport service tonight (adjusting spam filter levels)... so I was able to issue a stop and re-start of the IMAP4 and POP3 services in the service manager.
I stopped both the IMAP4 and POP3 services in service manager.
I issued the start of the services with PowerShell as requested:
PS C:\Users\administrator.XXXXXXXX> Start-service MSExchangePOP3
WARNING: Waiting for service 'Microsoft Exchange POP3 (MSExchangePOP3)' to start...
WARNING: Waiting for service 'Microsoft Exchange POP3 (MSExchangePOP3)' to start...
WARNING: Waiting for service 'Microsoft Exchange POP3 (MSExchangePOP3)' to start...
Start-service : Failed to start service 'Microsoft Exchange POP3 (MSExchangePOP3)'.
At line:1 char:1
+ Start-service MSExchangePOP3
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service],
   ServiceCommandException
    + FullyQualifiedErrorId : StartServiceFailed,Microsoft.PowerShell.Commands.StartServiceCommand
Then I first stopped the receive connector in ECP and issued the command:
PS C:\Users\administrator.XXXXXXXX> Start-service MSExchangePOP3
WARNING: Waiting for service 'Microsoft Exchange POP3 (MSExchangePOP3)' to start...
WARNING: Waiting for service 'Microsoft Exchange POP3 (MSExchangePOP3
With the receive connector disabled in ECP it was successfully started.... then I enabled the receive connector in ECP and all is fine now
repeated the same with IMAP4
to recap....
If I stop the IMAP4 and/or POP3 service in service manager, I must first disable the IMAP and/or POP receive connector in the ECP, then start the service in service manage.. and then finally go into ECP and enable the receive connector.
Thanks,
Chris
Chris

Manages Exchange server health Service is NOT starting after installing EDGE role using Exchange2013 SP1+CU5 setup

I used Exchange 2013 SP1+CU5 to install Edge role on Windows server 2012 R2 workgroup machine
then after installation the service "Exchange server health Service" was not starting automatically or manually with the following error "Error 1075: The dependency service does not exist or has been marked for deletion"
and in the Event Viewer I have this error:
Event Id: 7003
The Microsoft Exchange Health Manager service depends on the following service: MSExchangeADTopology. This service might not be installed.
please advice

The Exchange 2013 Edge Role has a reduced set of services compare to a CAS or MBX server role:
Active Directory Web Services
Microsoft Exchange ADAM
Microsoft Exchange Anti-spam Update
Microsoft Exchange Diagnostics
Microsoft Exchange Credential Service
Microsoft Exchange Health Manager
Microsoft Exchange Service Host
Microsoft Exchange Transport
Microsoft Exchange Transport Log Search
The above one was from Exchange 2013 Sp1. Not sure whether Microsoft Exchange Health Manager service has been replaced from CU5.
Just restart the edge server once again and ensure that you are able to see this service again in services console.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

Exchange Installation Error on Mailbox role: Transport Service Step

The error I receive occurs at 47% of the Mailbox Role: Transport Service installation. The details of the error are as follows:
    Mailbox role: Transport service
FAILED
     The following error was generated when "$error.Clear();
          if ($server -eq $null)
            set-ExchangeServerRole -Identity $RoleNetBIOSName -IsProvisionedServer:$true -DomainController $RoleDomainController
        " was run: "Active Directory operation failed on DC1.xxxxxx.xxxxxx.com. This error is not retriable. Additional information: The object cannot be added because the parent is not on the list of possible superiors.
Active directory response: 00002099: NameErr: DSID-0305109C, problem 2005 (NAMING_VIOLATION), data 0, best match of:
        'CN=EXCH-MBOX1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=AZGT,CN=
Microsoft Exchange,CN=Services,CN=Configuration,DC=xxxxxx,DC=xxxxxx,DC=com'
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
Also, when opening the setup log I have this:
[12/26/2012 17:51:25.0809] [1] [ERROR] A naming violation occurred.
[12/26/2012 17:51:25.0809] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___a16cb82f909348d3a32b9046f3bfb9ba Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[12/26/2012 17:51:25.0809] [1] Setup is stopping now because of one or more critical errors.
[12/26/2012 17:51:25.0809] [1] Finished executing component tasks.
[12/26/2012 17:51:25.0809] [1] Ending processing Install-BridgeheadRole
[12/26/2012 17:51:25.0825] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[12/26/2012 17:51:25.0825] [0] End of Setup
[12/26/2012 17:51:25.0825] [0] **********************************************
I have done a ton of searches trying to find a resolution to this error and there are two pages with a similar issue for Exchange 2007 but after trying the solutions suggested, the installation still fails with the same error.
http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploylegacy/thread/dfa9961a-9b20-4c17-ae4d-ebf44c66c18f/
http://exchangetroubleshooting.blogspot.com/2011/05/unable-to-run-preparead-command.html/
Some additional information:
This is a clean installation of Exchange 2013 in a forest that has never had exchange.
The domain and forest preparations run without errors and are at functional level of 2003.
The Exchange server has all prerequisites installed for a Mailbox server role and is running on a VM with Server 2012 as the OS.
This error occurs on other VMs as well that we are trying to implement as mailbox servers in the same forest.
I am running the installation as an enterprise, schema, domain admin.
Thanks for your help in advance.

Yes. I cleaned out Exchange with ADSIEdit so I could re-run the Prepare Schema, domain and all domains and then re-ran setup to show the output here. But the install still failed.
PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareSchema
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis
COMPLETED
Configuring Microsoft Exchange Server
    Extending Active Directory schema
COMPLETED
The Exchange Server setup operation completed successfully.
PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareAD /OrganizationName:AZGT
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis
COMPLETED
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have b
een detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.
aspx
Configuring Microsoft Exchange Server
    Organization Preparation
COMPLETED
The Exchange Server setup operation completed successfully.
PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareAllDomains
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis
COMPLETED
Configuring Microsoft Exchange Server
    Prepare Domain Progress
COMPLETED
The Exchange Server setup operation completed successfully.
PS F:\>
PS F:\> .\setup /IAcceptExchangeServerLicenseTerms /mode:install /roles:Mailbox /TargetDir:"C:\Program Files\Microsoft\Exchange Server\V15"
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Languages
Management tools
Mailbox role: Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Performing Microsoft Exchange Server Prerequisite Check
    Configuring Prerequisites
COMPLETED
    Prerequisite Analysis
COMPLETED
Configuring Microsoft Exchange Server
    Preparing Setup
COMPLETED
    Stopping Services
COMPLETED
    Copying Exchange Files
COMPLETED
    Language Files
COMPLETED
    Restoring Services
COMPLETED
    Language Configuration
COMPLETED
    Exchange Management Tools
COMPLETED
    Mailbox role: Transport service
FAILED
     The following error was generated when "$error.Clear();
          if ($server -eq $null)
            set-ExchangeServerRole -Identity $RoleNetBIOSName -IsProvisionedServer:$true -DomainController $RoleDomainCo
ntroller
        " was run: "Active Directory operation failed on DC1.XXXX.XXXX.com. This error is not retriable. Addi
tional information: The object cannot be added because the parent is not on the list of possible superiors.
Active directory response: 00002099: NameErr: DSID-0305109C, problem 2005 (NAMING_VIOLATION), data 0, best match of:
        'CN=EXCHMBOX1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=AZGT,CN=
Microsoft Exchange,CN=Services,CN=Configuration,DC=XXXX,DC=XXXX,DC=com'
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
PS F:\>

SCSM Exchange Connector not recognizing custom Service Request prefix

Hello,
We have an Orchestrator runbook that brings over "Projects" from our Financial system into Service Manager as Service Request. As a way to distinguish these as projects we changed the prefix from the default "SR" to "PT".
In all out testing everything worked fine until we installed the Exchange connector. It won't recognize any Service Request that starts with a different prefix than "SR" (defined in the system settings). Does anyone know of
a way to get the Exchange connector to recognize other prefixes?
Thanks

Hi,
The system uses the only prefix that defined in the settings. There's no way to add support for the second prefix in Microsoft Exchange Connector. But you can create your own custom connector with the required behavior.
Cheers,
Marat
Site: www.scutils.com Twitter:
LinkedIn:
Graveyard:

Service Manager Exchange Connector error

Similar Messages

Maybe you are looking for