Exchange Connector -  Exchange-11.1.1.5.0

hi all,
I want to use Exchange Connector for Exchange 2010 - "Exchange-11.1.1.5.0".
In certification matrix it states that it is certified with 'Exchange 2010 SP1' I have SP2 can i use this connector with Exchange 2010 SP2 as well?
is it a stable connector with good performance? do you recommend it to be used or the previous versions of AD and Exchange connectors 9.1.x are better? pleas share your experience.....
Thanks....

Hi ,
Please note that 9.x Exchange connector is not certified on Exchange 2010 SP2 (i have confirmed this with oracle and they have raised an enhancement request on this too). So if your env is 2010 sp2 , then 11.1.1.5.0 Exchange connector is the only option .
Best Regards
Suren

Similar Messages

  • Send connector from exchange 2007

    Currently since I have both environments up, I see that Exchange 2013 is using the send connector that was created in my exchange 2007 environment.  Will this send connector go away once I bring down my exchange 2007 environment? Shoould I create
    a new one for Exchange 2013?

    Hi
    From what i have seen running ex2010 and upgrading to 2013 it stayed (exchange 2013 is clever :-)). you can just modify your send connector and make sure that the settings are for your exchange 2013 server.

  • How to send email to a SMTP server over a secure channel using STARTTLS setting of a send connector (Exchange and SMTP server are in the same domain)

    I’m trying to send email using exchange send connector STARTTLS setting to the SMTP server. I have read multiple documents on configuring TLS for send connector, but they talks about outbound connections to internet facing servers. My Exchange 2013 and SMTP
    server is in the same domain (let’s say A.com) and I’m creating dummy domains on my SMTP server (e.g.
    [email protected],
    [email protected] ) and their respective send connectors on the exchange server end. In the smart host section added the IP address of the SMTP server and in the scoping section added the SMTP domain address (e.g. dummy1.local ). In the FQDN field, added
    the FQDN of the exchange server 2013 which certificate is enabled with SMTP service.
    Could you tell me a step by step procedure, where I’m going wrong or any extra settings needs to added?
    Presently, it is giving me an error that 530 5.5.1 TLS encrypted connection is required.
    Note: I’ve created the Microsoft CA certificates for the SMTP and exchange servers and imported them in the personal certificate container. In which, the exchange certificate is created with FQDN name of the server and enabled for the SMTP service.
    I’m using OPENSSL certificate for making the SMTP server TLS enabled. (let me know, if I need to import the OPENSSL certificate anywhere on the exchange end)?
    Thanks!

    -IgnoreSTARTTLS is set to false on the send connector properties.
    I'm trying to established a HTTP over TLS connection. I'm not using mutual TLS between these two server.
    The send connector protocol logging is attached as below,
    2014-09-22T20:09:45.468Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,2,10.219.3.74:24939,10.219.3.73:25,<,220 SMTP.A.local Welcome (MTA version),
    2014-09-22T20:09:45.546Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,3,10.219.3.74:24939,10.219.3.73:25,>,EHLO Exchange.A.local,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,4,10.219.3.74:24939,10.219.3.73:25,<,250-SMTP.A.local Exchange.A.local OK,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,5,10.219.3.74:24939,10.219.3.73:25,<,250-SIZE,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,6,10.219.3.74:24939,10.219.3.73:25,<,250-8BITMIME,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,7,10.219.3.74:24939,10.219.3.73:25,<,250-BINARYMIME,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,8,10.219.3.74:24939,10.219.3.73:25,<,250-PIPELINING,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,9,10.219.3.74:24939,10.219.3.73:25,<,250-HELP,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,10,10.219.3.74:24939,10.219.3.73:25,<,250-DSN,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,11,10.219.3.74:24939,10.219.3.73:25,<,250-CHUNKING,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,12,10.219.3.74:24939,10.219.3.73:25,<,250-AUTH SCRAM-SHA-1 GSS-SPNEGO DIGEST-MD5 CRAM-MD5 NTLM,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,13,10.219.3.74:24939,10.219.3.73:25,<,250-AUTH=SCRAM-SHA-1 GSS-SPNEGO DIGEST-MD5 CRAM-MD5 NTLM,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,14,10.219.3.74:24939,10.219.3.73:25,<,250-STARTTLS,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,15,10.219.3.74:24939,10.219.3.73:25,<,250-DELIVERBY,
    2014-09-22T20:09:45.624Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,16,10.219.3.74:24939,10.219.3.73:25,<,250-MT-PRIORITY,
    2014-09-22T20:09:45.640Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,17,10.219.3.74:24939,10.219.3.73:25,<,250 ENHANCEDSTATUSCODES,
    2014-09-22T20:09:45.655Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,18,10.219.3.74:24939,10.219.3.73:25,>,STARTTLS,
    2014-09-22T20:09:45.671Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,19,10.219.3.74:24939,10.219.3.73:25,<,220 2.7.0 Ready to start TLS,
    2014-09-22T20:09:45.687Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,20,10.219.3.74:24939,10.219.3.73:25,*,,Sending certificate
    2014-09-22T20:09:45.687Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,21,10.219.3.74:24939,10.219.3.73:25,*,CN=Exchange.A.local,Certificate subject
    2014-09-22T20:09:45.687Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,22,10.219.3.74:24939,10.219.3.73:25,*,"CN=DC-CA, DC=A, DC=local",Certificate issuer name
    2014-09-22T20:09:45.687Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,23,10.219.3.74:24939,10.219.3.73:25,*,63E7E70100000000000B,Certificate serial number
    2014-09-22T20:09:45.687Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,24,10.219.3.74:24939,10.219.3.73:25,*,CAEB1200CDF49715E5F2E4B8315EFDDC01F8F945,Certificate thumbprint
    2014-09-22T20:09:45.780Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,25,10.219.3.74:24939,10.219.3.73:25,*,Exchange.A.local,Certificate alternate names
    2014-09-22T20:09:46.654Z,Exchange-SMTP send connector,08D1A4A14C7EDED5,26,10.219.3.74:24939,10.219.3.73:25,-,,Local
    2014-09-22T20:09:46.669Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,0,,10.219.3.73:25,*,,attempting to connect
    2014-09-22T20:09:46.685Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,1,10.219.3.74:24940,10.219.3.73:25,+,,
    2014-09-22T20:09:46.701Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,2,10.219.3.74:24940,10.219.3.73:25,<,220 SMTP.A.local Welcome (MTA version),
    2014-09-22T20:09:46.701Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,3,10.219.3.74:24940,10.219.3.73:25,>,EHLO Exchange.A.local,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,4,10.219.3.74:24940,10.219.3.73:25,<,250-SMTP.A.local Exchange.A.local OK,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,5,10.219.3.74:24940,10.219.3.73:25,<,250-SIZE,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,6,10.219.3.74:24940,10.219.3.73:25,<,250-8BITMIME,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,7,10.219.3.74:24940,10.219.3.73:25,<,250-BINARYMIME,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,8,10.219.3.74:24940,10.219.3.73:25,<,250-PIPELINING,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,9,10.219.3.74:24940,10.219.3.73:25,<,250-HELP,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,10,10.219.3.74:24940,10.219.3.73:25,<,250-DSN,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,11,10.219.3.74:24940,10.219.3.73:25,<,250-CHUNKING,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,12,10.219.3.74:24940,10.219.3.73:25,<,250-AUTH SCRAM-SHA-1 GSS-SPNEGO DIGEST-MD5 CRAM-MD5 NTLM,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,13,10.219.3.74:24940,10.219.3.73:25,<,250-AUTH=SCRAM-SHA-1 GSS-SPNEGO DIGEST-MD5 CRAM-MD5 NTLM,
    2014-09-22T20:09:46.716Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,14,10.219.3.74:24940,10.219.3.73:25,<,250-STARTTLS,
    2014-09-22T20:09:46.732Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,15,10.219.3.74:24940,10.219.3.73:25,<,250-DELIVERBY,
    2014-09-22T20:09:46.732Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,16,10.219.3.74:24940,10.219.3.73:25,<,250-MT-PRIORITY,
    2014-09-22T20:09:46.732Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,17,10.219.3.74:24940,10.219.3.73:25,<,250 ENHANCEDSTATUSCODES,
    2014-09-22T20:09:46.810Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,18,10.219.3.74:24940,10.219.3.73:25,*,,sending message with RecordId 52652004081667 and InternetMessageId <[email protected]>
    2014-09-22T20:09:46.810Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,19,10.219.3.74:24940,10.219.3.73:25,>,MAIL FROM:<> SIZE=7653 BODY=BINARYMIME,
    2014-09-22T20:09:46.810Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,20,10.219.3.74:24940,10.219.3.73:25,>,RCPT TO:<[email protected]>,
    2014-09-22T20:09:46.825Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,21,10.219.3.74:24940,10.219.3.73:25,<,530 5.5.1 A TLS-encrypted connection is required,
    2014-09-22T20:09:46.950Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,22,10.219.3.74:24940,10.219.3.73:25,<,503 5.5.1 unexpected RCPT command,
    2014-09-22T20:09:46.981Z,Exchange-SMTP send connector,08D1A4A14C7EDED6,23,10.219.3.74:24940,10.219.3.73:25,>,RSET,

  • What are the correct Send Connectors settings in Exchange 2013

    Hi
    I'm new to exchange, successfully setup a lab with 2 cashub roles and 2 mailbox roles. I am trying to set the send connectors settings, because I've not been able to send nor receive external email via owa. Since I'm separating the exchange roles, my mailbox
    servers only use internal IP settings and cannot resolve external DNS. I'm thinking I need to tick, proxy through CAS for it to work? any suggestions?

    Hi 
    Can you please let us know what version of Exchange that you are using 
    "I'm new to exchange, successfully setup a lab with 2 cashub roles and 2 mailbox roles"
    - Because Exchange 2013 does not hold hub role.
    " I am trying to set the send connectors settings, because I've not been able to send
    nor receive external email via owa."
    It would be great if you could answer few questions so that people can help you out here
    Are you able to send emails internally without any issues with Outlook ? If not can you paste the errors.
    What error you are getting while trying to send emails through owa . Can you paste the errors.
    If you are looking for steps to create new send connector please follow below technet article
    http://technet.microsoft.com/en-us/library/aa998936(v=exchg.150).aspxFeel free to post your comments/errors you received  to proceed
    further
    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 Thanks Sathish
    (MVP)

  • 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$">&lt;?xml version="1.0" encoding="utf-16"?&gt;
    &lt;ParameterMapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt;
    &lt;ParameterList&gt;
    &lt;RunbookParameterItem&gt;
    &lt;Name&gt;Get RA Guid&lt;/Name&gt;
    &lt;Id&gt;344b15effc1a44528e517c5b4227179c&lt;/Id&gt;
    &lt;Type&gt;String&lt;/Type&gt;
    &lt;Value&gt;Generic::Id&lt;/Value&gt;
    &lt;Direction&gt;In&lt;/Direction&gt;
    &lt;ContextInfo /&gt;
    &lt;/RunbookParameterItem&gt;
    &lt;/ParameterList&gt;
    &lt;RunbookId&gt;4085f0da-ab83-48e5-bbe3-1f3b5fa2dc4a&lt;/RunbookId&gt;
    &lt;/ParameterMapping&gt;</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$">&lt;?xml version="1.0" encoding="utf-16"?&gt;
    &lt;ParameterMapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt;
    &lt;ParameterList&gt;
    &lt;RunbookParameterItem&gt;
    &lt;Name&gt;RA Activity GUID&lt;/Name&gt;
    &lt;Id&gt;5677d117a0294a2c898a695032f26c72&lt;/Id&gt;
    &lt;Type&gt;String&lt;/Type&gt;
    &lt;Value&gt;Generic::Id&lt;/Value&gt;
    &lt;Direction&gt;In&lt;/Direction&gt;
    &lt;ContextInfo /&gt;
    &lt;/RunbookParameterItem&gt;
    &lt;/ParameterList&gt;
    &lt;RunbookId&gt;ca88b13b-861a-4d39-a3cb-fd912d951e35&lt;/RunbookId&gt;
    &lt;/ParameterMapping&gt;</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>

  • 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

  • Exchange Receive Connector Temporary Server Error. Please Try again later. PRX4

    Hi , 
    I installated Exchange server 2013 on Windows 2012 R2 Servers.. 
    Topology ; 
    1 Active Directory Server : Windows 2012 r2 all updates installed. 
    1 Exchange 2013 Server : Windows 2012 r2 all updates installed.
    I configured send Connector settings and I checked Receive connectors Default Frontend Exchange settings. Anonymous users is ok and don't have any problem.
    When I send mail Exchange -> Internet  mail goes. this is ok. 
    But when I send mail Internet -> Exchange I am getting this error ; 
    Message or connection acked with status Retry and response 451 4.4.0 Primary target IP address responded with: ""501 5.5.4 Required arguments not present."" Attempted failover to alternate host, but that did not succeed. Either there
    are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was xxx.xxx.xxx.xxx:2525
    telnet results are below ; 
    220 exchange.bulut.email Microsoft ESMTP MAIL Service ready at Tue, 30 Dec 2014
    14:12:19 +0200
    EHLO bulut.email                      250-exchange.bulut.email Hello [xxxxxxxxxxxxxxxxx]
    250-SIZE 37748736
    250-PIPELINING
    250-DSN
    250-ENHANCEDSTATUSCODES
    250-STARTTLS
    250-X-ANONYMOUSTLS
    250-AUTH NTLM
    250-X-EXPS GSSAPI NTLM
    250-8BITMIME
    250-BINARYMIME
    250-CHUNKING
    250 XRDST
    MAIL FROM:[email protected]                     250 2.1.0 Sender OK
    RCPT TO:[email protected] NOTIFY=success,failure                 250 2.1.5 Recipient OK
    DATA354 Start mail input; end with <CRLF>.<CRLF>
    Subject: Test from Contosoa
    This is a test message
    451 4.7.0 Temporary server error. Please try again later. PRX4
    QUIT                                221 2.0.0 Service closing transmission channel
    Thanks. Regards.

    Hi,
    If the CAS and MBX servers are collocated on the same server the SMTP Receive connection for the Transport service will listen on 2525 instead of 25. This is because two services (FET and Transport Service) can’t listen on the same port.
    Refer from this article:
    http://blogs.technet.com/b/rischwen/archive/2013/03/13/exchange-2013-mail-flow-demystified-hopefully.aspx
    Please try to create an endpoint for 2525 on default receive connector to test mail flow by the following steps:
    EAC -> mail flow -> receive connectors -> Default EXCHANGE
    Click Edit then click scoping tab.
    Under Network adapter bindings, click
    add button to create port 2525 for all available Ipv4/Ipv6 addresses.
    Best Regards.

  • Exchange 11g connector : error with 2003 mailbox databases

    Hi,
    I have installed the Exchange 11g connector in a OIM 11g R2 server. I successfully ran the "Exchange User Mailbox Database Group Lookup Reconciliation" job and recon-ed a mailbox for a specific user (Exchange 2010 mailbox) account using the "Exchange Target Resource User Reconciliation".
    But the fun stops there, when I try the execute the "Exchange Target Resource Delete User Reconciliation" job, I get the following error (see #1) in the result. I don't have any new event in the Event viewer. When I check the connector server I see a similar error (see #2). I tried to manually run the powershell command with the connector server user and it works properly (see #3).
    The problem seems to be related the Exchange 2003 mailboxes, since when I try to recon a mailbox for a user with a 2003 mailbox, I get a similar "database not found" error. There again, if I check the same user using the service account, I can get it's mailbox.
    Any idea what might be the problem ? Any more debugging I can try ?
    Thanks
    h4. #1 - In the scheduled task result :
    org.identityconnectors.framework.common.exceptions.ConnectorException: Problem while PowerShell execution Org.IdentityConnectors.Framework.Common.Exceptions.ConnectorException: Couldn't find database "ORME-DE-COUR\Premier groupe de stockage\Banque de boîtes aux lettres (ORME-DE-COUR)". Make sure you have typed it correctly.
    at Org.IdentityConnectors.Exchange.RunSpaceInstance.CheckErrors(IList errors)
    at Org.IdentityConnectors.Exchange.RunSpaceInstance.InvokePipeline(Collection`1 commands)
    at Org.IdentityConnectors.Exchange.RunSpaceInstance.InvokePipeline(Command item)
    at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.InvokePipeline(Command cmd)
    h4. #2 - In the connector server log :
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> ExchangeConnector, Method -> CreateFilterTranslator, Message -> Method Entered
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> CreateFilterTranslator, Message -> Method Entered
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> ExchangeConnector, Method -> ExecuteQuery, Message -> Method Entered
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> ExecuteQuery, Message -> Method Entered
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> ExchangeUtility, Method -> GetCommand, Message -> Method entered
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> ExchangeUtility, Method -> GetCommand, Message -> Returning cmd Get-Mailbox
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> ExchangeUtility, Method -> GetCommand, Message -> Exiting the method
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> InvokePipeline, Message -> Method Entered
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> InvokePipeline, Message -> PowerShell Command: Get-Mailbox
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> InvokePipeline, Message -> Parameter: IgnoreDefaultScope Value:
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> InvokePipeline, Message -> Parameter: ReadFromDomainController Value:
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> InvokePipeline, Message -> Parameter: ResultSize Value:Unlimited
    ConnectorServer.exe Error: 0 : Org.IdentityConnectors.Framework.Common.Exceptions.ConnectorException: Problem while PowerShell execution Org.IdentityConnectors.Framework.Common.Exceptions.ConnectorException: Couldn't find database "ORME-DE-COUR\Premier groupe de stockage\Banque de boîtes aux lettres (ORME-DE-COUR)". Make sure you have typed it correctly.
    at Org.IdentityConnectors.Exchange.RunSpaceInstance.CheckErrors(IList errors)
    at Org.IdentityConnectors.Exchange.RunSpaceInstance.InvokePipeline(Collection`1 commands)
    at Org.IdentityConnectors.Exchange.RunSpaceInstance.InvokePipeline(Command item)
    at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.InvokePipeline(Command cmd)
    at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.InvokePipeline(Command cmd)
    at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.SearchUser(ObjectClass oclass, String query, ResultsHandler handler, OperationOptions options, ObjectClassInfo ocInfo)
    at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.ExecuteQuery(ObjectClass oclass, String query, ResultsHandler handler, OperationOptions options)
    at Org.IdentityConnectors.Exchange.ExchangeConnector.ExecuteQuery(ObjectClass oclass, String query, ResultsHandler handler, OperationOptions options)
    at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.RawSearcherImpl`1.RawSearch(SearchOp`1 search, ObjectClass oclass, Filter filter, ResultsHandler handler, OperationOptions options)
    at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.RawSearcherImpl`1.RawSearch(Object search, ObjectClass oclass, Filter filter, ResultsHandler handler, OperationOptions options)
    at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.SearchImpl.Search(ObjectClass oclass, Filter originalFilter, ResultsHandler handler, OperationOptions options)
    at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.ConnectorAPIOperationRunnerProxy.Invoke(Object proxy, MethodInfo method, Object[] args)
    at ___proxy1.Search(ObjectClass , Filter , ResultsHandler , OperationOptions )
    at Org.IdentityConnectors.Framework.Impl.Server.ConnectionProcessor.ProcessOperationRequest(OperationRequest request)
    DateTime=2013-05-30T14:49:37.1880494Z
    h4. #3 - Powershell using the service account
    Get a 2003 database
    [PS] C:\Windows\system32>Get-MailboxDatabase "ORME-DE-COUR\Premier groupe de stockage\Banque de boîtes aux lettres (ORME-DE-COUR)"
    Name Server Recovery ReplicationType
    Banque de boîtes aux lettre... ORME-DE-COUR False None
    Get a 2003 mailbox
    [PS] C:\Windows\system32>Get-Mailbox -Filter "DisplayName -eq 'Marchand Robert 0'"
    Name Alias ServerName ProhibitSendQuota
    marchanr marchanr orme-de-cour unlimited
    Edited by: SG on May 30, 2013 11:57 AM
    Edited by: SG on May 30, 2013 1:41 PM

    Any update on this? I have the exact same problem...
    Thanks,
    --jtellier                                                                                                                                                                                       

  • Exchange 2010 Receive Connector intermittently getting an SMTP RSET from sending SMTP servers causing missing user email

    Users are receiving about 95% of their messages from sending SMTP servers. Intermittently, sending SMTP servers send the Exchange 2010 Server a SMTP RSET command for no apparent reason. The RSET Command (by SMTP specification) causes the Exchange 2010 Server
    to drop the message. The sending SMTP servers then do not resend the message after asking the Exchange server to drop the message. This means the message is marked as Sent by the sending servers but the dropped messages never show up in the users' Outlook
    inbox.
    Exchange 2010 Version 14.3 (Build 123.4)
    Roles: Hub Transport, Client Access, Mailbox
    What is going on?
    Exchange Receive Connector log showing a RSET example:
    2014-07-17T12:47:07.370Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,1,10.80.120.15:25,65.99.255.73:53479,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
    2014-07-17T12:47:07.370Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,2,10.80.120.15:25,65.99.255.73:53479,>,"220 vpn.a1expediting.com Microsoft ESMTP MAIL Service ready at Thu, 17 Jul 2014 08:47:06 -0400",
    2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,3,10.80.120.15:25,65.99.255.73:53479,<,EHLO inbound37.exchangedefender.com,
    2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,4,10.80.120.15:25,65.99.255.73:53479,>,250-vpn.a1expediting.com Hello [65.99.255.73],
    2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,5,10.80.120.15:25,65.99.255.73:53479,>,250-SIZE 52428800,
    2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,6,10.80.120.15:25,65.99.255.73:53479,>,250-PIPELINING,
    2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,7,10.80.120.15:25,65.99.255.73:53479,>,250-DSN,
    2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,8,10.80.120.15:25,65.99.255.73:53479,>,250-ENHANCEDSTATUSCODES,
    2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,9,10.80.120.15:25,65.99.255.73:53479,>,250-AUTH,
    2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,10,10.80.120.15:25,65.99.255.73:53479,>,250-8BITMIME,
    2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,11,10.80.120.15:25,65.99.255.73:53479,>,250-BINARYMIME,
    2014-07-17T12:47:07.480Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,12,10.80.120.15:25,65.99.255.73:53479,>,250 CHUNKING,
    2014-07-17T12:47:07.511Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,13,10.80.120.15:25,65.99.255.73:53479,<,MAIL FROM:<[email protected]> SIZE=165270,
    2014-07-17T12:47:07.511Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,14,10.80.120.15:25,65.99.255.73:53479,*,08D16FD38F3D3355;2014-07-17T12:47:07.370Z;1,receiving message
    2014-07-17T12:47:07.511Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,15,10.80.120.15:25,65.99.255.73:53479,>,250 2.1.0 Sender OK,
    2014-07-17T12:47:07.558Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,16,10.80.120.15:25,65.99.255.73:53479,<,RCPT TO:<[email protected]> ORCPT=rfc822;[email protected],
    2014-07-17T12:47:07.558Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,17,10.80.120.15:25,65.99.255.73:53479,>,250 2.1.5 Recipient OK,
    2014-07-17T12:47:10.496Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,18,10.80.120.15:25,65.99.255.73:53479,<,RSET,
    2014-07-17T12:47:10.496Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,19,10.80.120.15:25,65.99.255.73:53479,>,250 2.0.0 Resetting,
    2014-07-17T12:47:10.559Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,20,10.80.120.15:25,65.99.255.73:53479,<,QUIT ,
    2014-07-17T12:47:10.559Z,A1-S1\Windows SBS Internet Receive A1-S1,08D16FD38F3D3355,21,10.80.120.15:25,65.99.255.73:53479,>,221 2.0.0 Service closing transmission channel,
    Daniel

    Hi,
    According to the receive connector log, your emails were failed to be deliverd with DNR. If I misudnerstand the meaning, please feel free to let me know.  If yes, I'd like to confirm the detail information in the DNR to narrow down the
    cause.
    Additionally, based on my research, the RSET command performs an SMTP reset, and then aborts the message that is currently being sent. Thus, the log didn't provide more information for troubleshooting. Is there any other error in your event log? please check
    the event log when the issue happens again.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange Server 2010 - Receive Connector for Client Computers

    I have one customer with a SBS 2011 with Exchange Server 2010 - a pretty standard setup except for some customisation with Receive Connectors in order to cater for an application which is installed on a number of computers that requires to use an SMTP Server
    to send notifications. In order to accomplish this (allow to be sent using Exchange Server) we added the IP Address of client computer (which we also set as a DHCP reservation) to a pre-configured Receive Connector (Anonymous setup for Printer/Scanner).
    This worked fine, but we now find that there are other applications that require the same function to use SMTP to send.
    How should/could this be better configured so an application can send if they authenticate?

    Hi 
    For this  you need to create a seperate receive connector to be used for Relay in your organizations.
    Follow the below steps
    1) Create a dedicated Relay Receive Connector
    2) Add only the Ip addresses of the applications which needs to relay on Exchange servers 
    3) You can use either anonymous or authenticated relay according to your relay config
    You can follow the below link as well
    http://exchangequery.com/2013/12/02/steps-to-configure-anonymous-and-authenticated-relay-in-exchange-2013/
    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 Thanks Sathish
    (MVP)

  • Receive Connector stopped working after Update Rollout 2 for Exchange 2007 SP2

    One of the Exchange 2007 servers receive connector has stopped working since installing the latest rollout update for Exchange 2007 SP2 - for some reason the following error is received (when troubleshooting on the adjacent server) :
    "Remote server server.domain.co.uk failed the mail acceptance test. MAIL FROM command: Respond = 530 5.7.1 Client was not authenticated."
    Most admins will know you usually get this when first setting up Exchange and the receive connector not allowing anonymous connections. But our setup has been working for well over a year with no problems. Even enabling anonymous connections still doesn't fix the problem.
    Our setup is 2 exchange servers across 2 sites, with the problematic server never receiving email from the internet, only from the other Exchange server (which is internet facing). The above error is received when the internet facing server is relaying email over to the problematic server. Though in the message queue the following error is received:
    "SMTPSEND.DNS.NonExistantDomain; nonecistant domain"
    After testing DNS that all seems fine, so I don't believe it's a DNS problem.
    Any ideas why this would happen?
    Thanks,
    Matt

    Hi Matt....
    To receive e-mails from the external servers or domains or clients, you can setup a new receive connector on Hub Transport Server. To do this task, you can go through the steps mentioned in this blog....
    https://mailsolutions.wordpress.com/2015/02/06/resolving-error-530-5-7-1-client-was-not-authenticated-with-receiver-connector/
    Hope this will work
    Thanks

  • How to correctly configure send and receive connectors for SBS2011 exchange to connect to EOP

    Hello SBS fans,
    we have a customer with SBS2011 and exchange.  The server email is setup for Exchange Online Protection.
    It passes the Remote Connectivity Analyzer for inbound and outbound email.  It shows a warning for the spf, saying it cannot find the spf record, BUT MXtool box passes everything associated with their domain name, including the spf record.
    They are now getting some bounced email from yahoo servers, referencing this ip
    65.55.169.249, which is a valid Microsoft ip.
    I checked the bounce back email header carefully, and found a reference to an internal ip, 192.168.11.14, which just happens to be the ip of the user's desk PC!! - NOT the local addr of the sbs2011 server (which should not be there anyway)
    I will guess that there is an incorrect setting in one or both of the hub transports?  There is a correct smart host connector.
    I am no longer sure about the other connectors!
    Any ideas on this?
    ewholz
    Network and Server Installs

    Hi,
    à
    It shows a warning for the spf, saying it cannot find the spf record
    Would you please let me know the complete warning message that you can get? Meanwhile, would you please let
    me know how long ago you add the SPF record? Be
    more than 72 hours?
    Please also refer to following article and check if can help you.
    Configuring
    Exchange 2007 Hub Transport role to receive Internet mail
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • Using the Same Profile for Outlook Connector and Exchange

    Is anyone using the same profile in Outlook for both the Oracle Connector for Outlook and Exchange server? Only Exchange would have an IMAP mail service defined.
    Oracle tech support kindly provided me with the following information but I would really appreciate hearing about customer experiences:
    "In theory this should work without causing any problem if only one service within the same Profile is configured for mail. However, before configuring a large amount of users with such a configuration, please start with 1 user and perform some tests, as I am not aware of anyone using such a configuration. The fact that you want your Oracle calendar users to invite Exchange users, will be like inviting External users, the Free/Busy information for these users will not be available etc. Also inviting external user is an already existing feature of the Oracle Calendar."
    Thanks very much.
    Brenda

    We are doing it currently as we are switching over from Exchange 5.5 to OCS. We set up a profile using the Oracle connector and then go into properties and add the Exchange account. We used this method to move files from the Exchange server to the Oracle server by having both profiles running.

  • Configure send connector for exchange online protection

    Hello Forum members,
    I am trying to configure send and receive connectors for Exchange 2010 to route
    on-premises mailboxes to Exchange OnLine Protection.  The "help" info MS provides
    is for Ex 2013 - and the EAC GUI and config does not lend a close fit to using the 2010
    Exch Management Console.  How can I configure connectors to properly connect to the Exchange Online Protection?
    I have seen where the ip addresses are posted, etc.  I am unclear how to configure the properties on the SBS 2011/EX 2010 server.
    Any tips will help,
    Thanks,
    Eric H.
    Network and Server Installs

    Hello Wesleyhe,
    You cannot use AD anything with EOP - if you mean exchange on-line protection.
    you have to set a smart host on the SBS server to connect to EOP, you may need to add the EOP server ips to your network config
    on the SBS server.  the smart host line (for the send connector on SBS server) is something like: yourdomainname-com.mail.protection.outlook.com.
    Then you need to configure the outside ip for your SBS server access in the EOP admin area.
    Hope this helps.
    eholz
    Network and Server Installs

  • 11004 error SBS Exchange 2003 SP2 with POP connector. Exchange version 6.5 7638.1

    Hello
    I am getting loads of errors displayed in Event Viewer Application log like:-
    Event ID 1035
     A error occurred in connecting to the <xxx.xxxxxx.co.uk> POP3 server for user <[email protected]>. The error is 11004. The server may be down for maintenance
    or your server is not connected to the Internet.
    Event ID 1023
    The downloading process for mailbox <[email protected] [mail.XXXXXXXXXXXXX.co.uk]> was ended with one or more errors.
    The Server has 3GB memory and 64GB free disk space on the parttiion supporting Exchange
    Can anyone suggest a troubleshooting scheme?

    Is this machine running SBS? Is this an error that's logged by the kludgy POP3 connector? If so, that connector isn't part of Exchange -- it's something the SBS folks added. You'll have to ask our question in a SBS forum.
    Keep in mind that a POP3 server will lock the mailbox if the messages are being checked by another client (unlike Exchange which allows multiple POP3 sessions). That would cause those 1035 errors to be logged by Exchange.
    When you combine the 1035 with the 1023 events it looks more like connectivity problems than an Exchange problem. You might want to use a network monitor and see if the connection's being dropped.
    In any case, good luck with Exchange 2003. It's no longer supported -- but I don't think your problem is related to Exchange but to the SBS add-on software.
    --- Rich Matheisen MCSE&I, Exchange MVP

  • Error in creating exchange mailbox via Exchange Connector 91000 (or 91010)

    Hi,
    i have been trying to create a mailbox on an Exchange 2000 server via MSFT_Exchange 91000 and 91010.
    i have imported the connector(s) successfully.
    i have set path to the script comes with the connector.
    . my AD connector can create users in AD
    . but when i tried to create a mailbox, it is rejected at "Create Mailbox" step.
    error message iincludes ""com.thortech.xl.integration.ActiveDirectory.tcADUtilLDAPController.cleanHierarchyString(Ljava/lang/"" and say "an unknown responce returned"
    AD and Exchange have been installed on different servers
    honestly, i am stuck and need a fool-proof guide to make the connector work.
    any help/idea are very much welcome and appreciated.
    kind regards
    hakan

    hi,
    i reinstalled to connector (91010) from the scratch and re-ran the scheduled task to populate mailbax store lookup. then it worked. :-)
    hakan

Maybe you are looking for