AD-Exchange Connector versions Incompatibility Issues : Extremely URGENT

Hi,
We have tested our code in dev environment (AD, Exchange versions 2003). But in production env, the root context for the two are different from those of dev environment.
In dev env: root context are: DC=company,DC=devxyz for ADITResource,Exchange
In prod env: root context are: DC=company,DC=devxyz for ADITResource ; DC=devxyz for Exchange.
Exchange being dependent on AD, when AD is provisioned, Exchange fetches the ObjectGUID of AD User, and searches in parent root context (DC=devxyz) which return some garbage value -50 corresponding to null value. SInce ObjectGUID is not fetched, Exchange cannot be provisioned.
Please give some pointers for this issue. It is very critical at this stage as we cannot do any changes in the existing configurations.
Regards,
Deepika

Exchange fetches the ObjectGUID of AD User, and searches in parent root context (DC=devxyz) which return some garbage value -50 corresponding to null value. SInce ObjectGUID is not fetched, Exchange cannot be provisioned.If it is facing issue only with objecrGUID then You can write your custom JNDI code to fetch this value and update in some field.
Just make a task in Exchange Process Definition which will do this thing.

Similar Messages

Version incompatibility issue with Interop.SAPbobsCOM.dll in SBO 2004

Hi,
I have encountered an incompatibility issue in DI API 2004 across different patch level-versions. Originally, I developed an application in SBO 2004 pl4 environment. Now, some of the customers who were installing the application, notified me that the application has a login problem. It turned out that the CompanyClass.connect() method returns an error message "object reference not set to an instance of an object", when the DI API version installed in the production environment is higher (in this case, pl7) than the DI API version which was used in the development environment.
I figured out that the problem can be fixed by replacing the Interop.SAPbobsCOM.dll file in the application directory by a newer version that reflects the DI API that is installed in the system. However, it seems a rather lousy workaround, if the customer needs to manually replace the dll. Maybe the installer could be customized to "sniff" the correct DI API level, but this too would be a pretty kludgy solution.
Does anyone know a better solution to this problem ?
Regards,
Henry

normally this is not a problem as long as they don't change the signatures on the DI-API (which they said they wouldn't) but it appears in P5 they changed that signature... we noticed some enums that got added and a few minor changes.

Exchange Connector 3.0 status Never Run

Hi,
I've setup lab enviroment of SCSM 2012 SP1 following the instructions:
http://technet.microsoft.com/en-us/library/hh914226.aspx
Everything works fine with an exception of Exchange Connector. It is stuck in status: Never Run
I was able to configure the connector with out error. I checked the event logs and it showed success
of all the config items and even showed it connected to an email that I sent to the workflow mailbox:
Logs:
Log Name: Operations Manager
Source: Exchange Connector
Date: 7/28/2014 11:52:00 AM
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: GENINGSCSMT01.CORP.IGES.SI
Description:
Exchange Connector: Attempting to connect to Exchange with the settings: login email address="contoso@CORP", impersonation email address="none", server URL="https://geningcas.corp.iges.si/EWS/Exchange.asmx"
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Exchange Connector" />
<EventID Qualifiers="0">0</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-07-28T09:52:00.000000000Z" />
<EventRecordID>152481</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>CONTOSO.COM</Computer>
<Security />
</System>
<EventData>
<Data>Exchange Connector: Attempting to connect to Exchange with the settings: login email address="testscsm@CORP", impersonation email address="none", server URL="...................................................................."
</Data>
</EventData>
</Event>
- Exchange Connector: Exchange web service tracing enabled.
- Exchange Connector: Using Exchange Web Service URL:.....................
EwsRequestHttpHeaders: <Trace Tag="EwsRequestHttpHeaders" Tid="1" Time="2014-07-28 09:52:00Z">
POST /EWS/Exchange.asmx HTTP/1.1
Content-Type: text/xml; charset=utf-8
Accept: text/xml
User-Agent: ExchangeServicesClient/14.03.0032.000
Accept-Encoding: gzip,deflate
</Trace>
EwsRequest: <Trace Tag="EwsRequest" Tid="1" Time="2014-07-28 09:52:00Z" Version="14.03.0032.000">
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<t:RequestServerVersion Version="Exchange2007_SP1" />
<t:TimeZoneContext>
<t:TimeZoneDefinition Id="Central Europe Standard Time" />
</t:TimeZoneContext>
</soap:Header>
<soap:Body>
<m:FindItem Traversal="Shallow">
<m:ItemShape>
<t:BaseShape>AllProperties</t:BaseShape>
</m:ItemShape>
<m:IndexedPageItemView MaxEntriesReturned="1" Offset="0" BasePoint="Beginning" />
<m:Restriction>
<t:And>
<t:IsEqualTo>
<t:FieldURI FieldURI="message:IsRead" />
<t:FieldURIOrConstant>
<t:Constant Value="false" />
</t:FieldURIOrConstant>
</t:IsEqualTo>
<t:IsEqualTo>
<t:FieldURI FieldURI="item:ItemClass" />
<t:FieldURIOrConstant>
<t:Constant Value="IPM.Note" />
</t:FieldURIOrConstant>
</t:IsEqualTo>
</t:And>
</m:Restriction>
<m:ParentFolderIds>
<t:DistinguishedFolderId Id="inbox" />
</m:ParentFolderIds>
</m:FindItem>
</soap:Body>
</soap:Envelope>
</Trace>
EwsResponseHttpHeaders: <Trace Tag="EwsResponseHttpHeaders" Tid="1" Time="2014-07-28 09:52:00Z">
200 OK
Transfer-Encoding: chunked
Content-Encoding: gzip
Vary: Accept-Encoding
Persistent-Auth: true
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Date: Mon, 28 Jul 2014 09:52:00 GMT
Server: Microsoft-IIS/7.5
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
</Trace>
EwsResponse: <Trace Tag="EwsResponse" Tid="1" Time="2014-07-28 09:52:00Z" Version="14.03.0032.000">
<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header>
<h:ServerVersionInfo MajorVersion="14" MinorVersion="2" MajorBuildNumber="347" MinorBuildNumber="0" Version="Exchange2010_SP2" xmlns:h="http://schemas.microsoft.com/exchange/services/2006/types"
xmlns="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<m:FindItemResponse xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types">
<m:ResponseMessages>
<m:FindItemResponseMessage ResponseClass="Success">
<m:ResponseCode>NoError</m:ResponseCode>
<m:RootFolder IndexedPagingOffset="1" TotalItemsInView="2" IncludesLastItemInRange="false">
<t:Items>
<t:Message>
<t:ItemId Id="AAMkAGY0NWM1MDJlLWNlYzctNDUwMy04NjUyLWZmNmJhODZmZWFjNwBGAAAAAABEWg/FMFIlQ6snViUYxTCgBwCX9G6oX6gvSK4RK8YlCtwaAAAApoPnAACX9G6oX6gvSK4RK8YlCtwaAAAApqtHAAA=" ChangeKey="CQAAABYAAACX9G6oX6gvSK4RK8YlCtwaAAAApwJt"
/>
<t:ParentFolderId Id="AAMkAGY0NWM1MDJlLWNlYzctNDUwMy04NjUyLWZmNmJhODZmZWFjNwAuAAAAAABEWg/FMFIlQ6snViUYxTCgAQCX9G6oX6gvSK4RK8YlCtwaAAAApoPnAAA=" ChangeKey="AQAAAA==" />
<t:ItemClass>IPM.Note</t:ItemClass>
<t:Subject>FW:
Test 2</t:Subject>
<t:Sensitivity>Normal</t:Sensitivity>
<t:DateTimeReceived>2014-06-13T05:41:55Z</t:DateTimeReceived>
<t:Size>9889</t:Size>
<t:Importance>Normal</t:Importance>
<t:IsSubmitted>false</t:IsSubmitted>
<t:IsDraft>false</t:IsDraft>
<t:IsFromMe>false</t:IsFromMe>
<t:IsResend>false</t:IsResend>
<t:IsUnmodified>true</t:IsUnmodified>
<t:DateTimeSent>2014-06-13T05:41:53Z</t:DateTimeSent>
<t:DateTimeCreated>2014-06-13T05:41:55Z</t:DateTimeCreated>
<t:ReminderIsSet>false</t:ReminderIsSet>
<t:ReminderMinutesBeforeStart>0</t:ReminderMinutesBeforeStart>
<t:DisplayCc />
<t:DisplayTo>Test Scsm</t:DisplayTo>
<t:HasAttachments>false</t:HasAttachments>
<t:Culture>en-US</t:Culture>
<t:EffectiveRights>
<t:CreateAssociated>false</t:CreateAssociated>
<t:CreateContents>false</t:CreateContents>
<t:CreateHierarchy>false</t:CreateHierarchy>
<t:Delete>true</t:Delete>
<t:Modify>true</t:Modify>
<t:Read>true</t:Read>
</t:EffectiveRights>
<t:LastModifiedName>Gorazd Lenko</t:LastModifiedName>
<t:LastModifiedTime>2014-06-13T05:41:55Z</t:LastModifiedTime>
<t:Sender>
<t:Mailbox>
<t:Name>Gorazd Lenko</t:Name>
</t:Mailbox>
</t:Sender>
<t:IsReadReceiptRequested>false</t:IsReadReceiptRequested>
<t:IsDeliveryReceiptRequested>false</t:IsDeliveryReceiptRequested>
<t:ConversationIndex>Ac+Gyiy/zkDKDTIqSzSWEj8rvPTxVQ==</t:ConversationIndex>
<t:ConversationTopic>test2</t:ConversationTopic>
<t:From>
<t:Mailbox>
<t:Name>Gorazd Lenko</t:Name>
</t:Mailbox>
</t:From>
<t:InternetMessageId><CC14C50767AF3448BEC68A24DC76AC439F00CDE0@></t:InternetMessageId>
<t:IsRead>false</t:IsRead>
<t:IsResponseRequested>false</t:IsResponseRequested>
<t:ReceivedBy>
<t:Mailbox>
<t:Name>Test Scsm</t:Name>
</t:Mailbox>
</t:ReceivedBy>
<t:ReceivedRepresenting>
<t:Mailbox>
<t:Name>Test Scsm</t:Name>
</t:Mailbox>
</t:ReceivedRepresenting>
</t:Message>
</t:Items>
</m:RootFolder>
</m:FindItemResponseMessage>
</m:ResponseMessages>
</m:FindItemResponse>
</s:Body>
</s:Envelope>
</Trace>
As you can see from the last event (bold letters) the Workflow account manages to get to the Exchange account, reads the inbox, but it isn't able to poll the message to SM.
Any ideas guys?

Hi,
It was set to Default Incident Template. I have created a new Incident template and recreated Exchange Connector, but the issue is still present. Workflow account is a member of SCSM Admin role, Workflow role and a local admin on the server. It is also Sysadmin
on the database.
On the Exchange server I have also ran Get_MailboxStatistics command and the output:
[PS] C:\Windows\system32>Get-MailboxStatistics | select lastlog* | fl
cmdlet Get-MailboxStatistics at command pipeline position 1
Supply values for the following parameters:
Identity: testscsm
LastLoggedOnUserAccount : CORP\testscsm
LastLogoffTime : 31.7.2014 7:45:14
LastLogonTime : 31.7.2014 7:39:58
So that means that the a
ccount logs in to mailbox but is unable to process emails.
Also I have found the difference in the EWSLogEntry on the test and production server:
The production log says:
<m:IndexedPageItemView MaxEntriesReturned="2147483647" Offset="0" BasePoint="Beginning" />
and the test log:
<m:IndexedPageItemView MaxEntriesReturned="1"
Offset="0" BasePoint="Beginning" />
Is there any way I can edit those settings?

SAP Exchange Connector

Which SAP Exchange connector version can I use with Exchange 2003

Hi
Pls find some useful links on the same
http://www.erpgenie.com/interfaces/exchange.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVCOMMSX/BCSRVCOMMSX.pdf
If it helps you pls give some points

Exchange Connector - iOS Version Reporting

We run reports on the different versions of iOS that connect to Exchange in SCCM using the exchange connector. We have found that when a device is updated to a newer version of iOS the Operating System version information is not updated in SCCM. I checked
through the information in Exchange and it does have the correct version of iOS on the object it just doesn't appear to be updating in SCCM.

Can't say I have any insight into this but it sounds like it may be a bug or a scenario not accounted for. You may want to open a CSS case.
How long are you waiting after the update occurred to check the console? Have you checked the data directly in the DB? This could simply be a timing issue.
Jason | http://blog.configmgrftw.com

Incompatibility issues when saving BW workbook in early excel versions

When saving a BW workbooks to my desktop for example so that I can then send it to a user to view the report I get incompatibility issues when saving workbook to earlier excel versions. I am currently using 2007 and when I save the workbook to Excel 97 - 2003 then I get incompatibility messages. If I ignore these and just save then no one is able to open the workbook. This means that I cannot also save workbooks on the reporting system as those users not using 2007 cannot view them. The message that I get is that 'the features of this workbook are not supported by the earlier features of Excel.'

Hi,
Please refer to this note,
Note 1152092 - Error opening MS Excel 2007 workbook in MS Excel 2003
Usually when you do any formatting feature available in Excel 2007 to the workbook it would throw you the error, not sure if you are formatting the workbook.
Regards,
Mani

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 not get Active Directory Object_GUID

Hi all.
I've upgraded the Exchange Connector to version 11.1.1.5.0 and I have a issue.
The connector is unable to get Active Directory Obejct_GUID and populate the ReturnValue field in UD_MSEXCHG and the provisioning user in Microsoft Exchange is not completed.
Anyone can help me ?
Thks,
Joel

Hi all.
I've upgraded the Exchange Connector to version 11.1.1.5.0 and I have a issue.
The connector is unable to get Active Directory Obejct_GUID and populate the ReturnValue field in UD_MSEXCHG and the provisioning user in Microsoft Exchange is not completed.
Anyone can help me ?
Thks,
Joel

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

Windows Server 2012 Essentials Connector version is more current than server

In trying to connect a new laptop to domain/server, it kept failing with a message indicating that other software was in the process of installing or that a reboot was pending. Since neither was the case, I downloaded the current version of the Connector
software from the Microsoft website to try. That didn't work either. It turns out that a pre-installed software component called Intel Smart Connect Tech was keeping the laptop from connecting. I uninstalled this software and installed the
connector software and it appeared to connect to the server. However, it is displayed in the Essentials Dashboard as Offline. The client (Laptop) displays a message saying "The Windows Server 2012 Essentials Connector version that is installed
on this computer is more recent that the sever. Contact the administrator to ensure the server is up to date". I tried uninstalling the Connector software from Control Panel, but I get a message "Could not delete key \software\microsoft\windows
server. Verify that you have sufficient access to that key, or contact your support personnel". I've tried both with domain admin and local admin credentials. So, I ignored the message and continued the connector install. It finished
and appeared to connect successfully. The connector version displayed in Control Panel\Programs and Features is correct. However, the registry entry is not updated and the version error pops up with each login and the Dashboard shows the client
as offline.

Hi C.R.Lowe,
Based on your description, I’m a little confused with this issue. Before going further, would you please let
me confirm something more? Thanks for your understanding.
When connect the client to Windows Server 2012 Essentials, did you mean that use
http://<servername>/Connect
and then select Download software for Windows option? More descriptions, please refer to the following article.
To connect a client computer to the
server
If I misunderstand, please don’t hesitate to let me know.
On current situation, please navigate to the registry path as the error message shows. And check
Version value and let me know. Meanwhile, please right click
Windows Server folder in Registry Editor and select “Permissions…”, then check if the account was assigned the correct permission to delete key.
In addition, please check if you have installed the
Update Rollup 1 for Windows Server 2012 Essentials
By the way, please check Event Viewer and some related logs if can find some more clues. If any update, please
feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

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.

Problem handling SMTP address with OIM 11gR2 Exchange connector

Hello,
I have a problem in regarding the primary SMTP address with the Exchange connector. The connector doesn't seem to be able to update it. Changing a user's primary SMTP address from its account details in OIM creates a new secondary address in Exchange. It does not change the current primary SMTP address. This does not look like a normal behavior... Any ideas on how to fix this?
I'm using OIM 11gR2 with BP10 with AD 11.1.1.5.0A and Exchange 11.1.1.5.0.
Thanks,
--jtellier

Yes, you can try out few things suggested in below thread
Re: Exchange Provisioning
The error looks like form exchange server side but still not sure about it.
Meantime open Service Request with oracle about the same as I can see other developers are also facing same issue.

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.

Scsm 2012 r2 (ur 3) with exchange connector 3 - state never run but reveices mail in opm log?!

Hello everybody,
we have installed scsm 2012 r2 (UR 3) with exchange connector 3. We have connected the connector by the workflow Account (domain user "servicedesk" is in local admin group of the sm server and in the sm Administrators group) and have access
to the mailbox on exchange (2010; autodiscovery is working correct). We receive all mails in the servicedesk mailbox on restarting the sm services and see the mails in the opm logs. But no incidents are created and the connector stays in "never
tun" state and does not receive mails any More after the first start. What do we have missed to check? Beste regards Thomas

i have added the registry keys.
the last log says:
EwsResponse: <Trace Tag="EwsResponse" Tid="1" Time="2014-08-10 18:38:52Z" Version="14.03.0067.001">
<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
    <s:Header>
      <h:ServerVersionInfo MajorVersion="14" MinorVersion="3" MajorBuildNumber="174" MinorBuildNumber="1" Version="Exchange2010_SP2" xmlns:h="http://schemas.microsoft.com/exchange/services/2006/types"
xmlns="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
    </s:Header>
    <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <m:FindItemResponse xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types">
        <m:ResponseMessages>
          <m:FindItemResponseMessage ResponseClass="Success">
            <m:ResponseCode>NoError</m:ResponseCode>
            <m:RootFolder IndexedPagingOffset="1" TotalItemsInView="1" IncludesLastItemInRange="true">
              <t:Items>
                <t:Message>
                  <t:ItemId Id="AAMkAGM0NzI4Nzc5LWM0NWMtNDBiZC1iMjIyLWU5YTZlNGM0YjVjZgBGAAAAAADPPKNYSCzLRLMWL/UoJg1CBwAVmecTYATlQovl76GEizxlAAAAoyGrAAAVmecTYATlQovl76GEizxlAAAAo0kZAAA="
ChangeKey="CQAAABYAAAAVmecTYATlQovl76GEizxlAAAAo4Fd" />
                  <t:ParentFolderId Id="AAMkAGM0NzI4Nzc5LWM0NWMtNDBiZC1iMjIyLWU5YTZlNGM0YjVjZgAuAAAAAADPPKNYSCzLRLMWL/UoJg1CAQAVmecTYATlQovl76GEizxlAAAAoyGrAAA="
ChangeKey="AQAAAA==" />
                  <t:ItemClass>IPM.Note</t:ItemClass>
                  <t:Subject>Test 1</t:Subject>
                  <t:Sensitivity>Normal</t:Sensitivity>
                  <t:DateTimeReceived>2014-08-10T18:35:12Z</t:DateTimeReceived>
                  <t:Size>2858</t:Size>
                  <t:Importance>Normal</t:Importance>
                  <t:IsSubmitted>false</t:IsSubmitted>
                  <t:IsDraft>false</t:IsDraft>
                  <t:IsFromMe>false</t:IsFromMe>
                  <t:IsResend>false</t:IsResend>
                  <t:IsUnmodified>true</t:IsUnmodified>
                  <t:DateTimeSent>2014-08-10T18:34:56Z</t:DateTimeSent>
                  <t:DateTimeCreated>2014-08-10T18:35:12Z</t:DateTimeCreated>
                  <t:DisplayCc />
                  <t:DisplayTo>Service Desk</t:DisplayTo>
                  <t:HasAttachments>false</t:HasAttachments>
                  <t:Culture>de</t:Culture>
                  <t:EffectiveRights>
                    <t:CreateAssociated>false</t:CreateAssociated>
                    <t:CreateContents>false</t:CreateContents>
                    <t:CreateHierarchy>false</t:CreateHierarchy>
                    <t:Delete>true</t:Delete>
                    <t:Modify>true</t:Modify>
                    <t:Read>true</t:Read>
                  </t:EffectiveRights>
                  <t:LastModifiedName>Thomas Göttl</t:LastModifiedName>
                  <t:LastModifiedTime>2014-08-10T18:35:12Z</t:LastModifiedTime>
                  <t:Sender>
                    <t:Mailbox>
                      <t:Name>Thomas Göttl</t:Name>
                    </t:Mailbox>
                  </t:Sender>
                  <t:IsReadReceiptRequested>false</t:IsReadReceiptRequested>
                  <t:ConversationIndex>Ac+0ycOTmfHK8XrvSM2ftu9rcjREeg==</t:ConversationIndex>
                  <t:ConversationTopic>Test 1</t:ConversationTopic>
                  <t:From>
                    <t:Mailbox>
                      <t:Name>Thomas Göttl</t:Name>
                    </t:Mailbox>
                  </t:From>
                  <t:InternetMessageId><[email protected]></t:InternetMessageId>
                  <t:IsRead>false</t:IsRead>
                  <t:ReceivedBy>
                    <t:Mailbox>
                      <t:Name>Service Desk</t:Name>
                    </t:Mailbox>
                  </t:ReceivedBy>
                  <t:ReceivedRepresenting>
                    <t:Mailbox>
                      <t:Name>Service Desk</t:Name>
                    </t:Mailbox>
                  </t:ReceivedRepresenting>
                </t:Message>
              </t:Items>
            </m:RootFolder>
          </m:FindItemResponseMessage>
        </m:ResponseMessages>
      </m:FindItemResponse>
    </s:Body>
</s:Envelope>
</Trace>
and the one before:
EwsResponseHttpHeaders: <Trace Tag="EwsResponseHttpHeaders" Tid="1" Time="2014-08-10 18:38:52Z">
200 OK
Transfer-Encoding: chunked
Content-Encoding: gzip
Vary: Accept-Encoding
Persistent-Auth: false
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Date: Sun, 10 Aug 2014 18:38:51 GMT
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate oYGyMIGvoAMKAQChCwYJKoZIgvcSAQICooGaBIGXYIGUBgkqhkiG9xIBAgICAG+BhDCBgaADAgEFoQMCAQ+idTBzoAMCAReibARqZCLk7OlBLjMLGg8XtQO+mutKfYPyK2jeJ2B+wq9raDj1chIZkQT0/72YftQJfdtu1DwfzmlEz8kDSD7ElFT2nF/T5LMDIMT4EpLJALsGQPTec86ubSbl1dKsIZn09qdoGDg5tGxV0bwOSg==
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
</Trace>
the one before:
EwsRequest: <Trace Tag="EwsRequest" Tid="1" Time="2014-08-10 18:38:51Z" Version="14.03.0067.001">
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
      <t:RequestServerVersion Version="Exchange2007_SP1" />
      <t:TimeZoneContext>
        <t:TimeZoneDefinition Id="W. Europe Standard Time" />
      </t:TimeZoneContext>
    </soap:Header>
    <soap:Body>
      <m:FindItem Traversal="Shallow">
        <m:ItemShape>
          <t:BaseShape>AllProperties</t:BaseShape>
        </m:ItemShape>
        <m:IndexedPageItemView MaxEntriesReturned="1" Offset="0" BasePoint="Beginning" />
        <m:Restriction>
          <t:And>
            <t:IsEqualTo>
              <t:FieldURI FieldURI="message:IsRead" />
              <t:FieldURIOrConstant>
                <t:Constant Value="false" />
              </t:FieldURIOrConstant>
            </t:IsEqualTo>
            <t:IsEqualTo>
              <t:FieldURI FieldURI="item:ItemClass" />
              <t:FieldURIOrConstant>
                <t:Constant Value="IPM.Note" />
              </t:FieldURIOrConstant>
            </t:IsEqualTo>
          </t:And>
        </m:Restriction>
        <m:ParentFolderIds>
          <t:DistinguishedFolderId Id="inbox" />
        </m:ParentFolderIds>
      </m:FindItem>
    </soap:Body>
</soap:Envelope>
</Trace>
the one before:
EwsRequestHttpHeaders: <Trace Tag="EwsRequestHttpHeaders" Tid="1" Time="2014-08-10 18:38:51Z">
POST /EWS/Exchange.asmx HTTP/1.1
Content-Type: text/xml; charset=utf-8
Accept: text/xml
User-Agent: ExchangeServicesClient/14.03.0067.001
Accept-Encoding: gzip,deflate
</Trace>
the one before (xxx for our Domain):
Exchange Connector: Autodiscovered URL: https://sv-exchange01.xxx.intra/EWS/Exchange.asmx
Is there something we missed?

AD-Exchange Connector versions Incompatibility Issues : Extremely URGENT

Similar Messages

Maybe you are looking for