Showing results for 
Search instead for 
Do you mean 
Community Home Request Access Read Blogs Share Your Ideas Search Community View My Settings
Reply
New Member
Posts: 8
Registered: ‎06-01-2010

What does this error message mean?

Hello,

 

We have a customer running Exchange Link. Two weeks ago the exchange link error logs begun to register this error en each sincronization

 

TExchangeRecipients - could not retrieve PR_ENTRYID or PR_OBJECT_TYPE property

 

When I run manually the integrations it seems that this error happens in one specific sincronization, but I have no idea why does this error happens and what I can to to solve it.

 

Any ideas?

 

This is a part of the manual log sincronization where this specifi error happens.

 

13:35:51:494  Processing attendee:
13:35:51:510  Modifying SalesLogix activity, ACTIVITYID = V6UJ9A00026Z
13:35:51:510  Successfully called ExchangeToSLX - GetRecipientTable
13:35:51:510  Successfully called ExchangeUserToSlxUser - IAddrBook.OpenEntry
13:35:51:510  Could not find SLX user for SID = S-1-5-21-4057588611-516736325-3382091719-2663
13:35:51:525  Will now update the alarm time. Alarm: 0
13:35:51:525  Update USER_ACTIVITY.ALARM (SLX version 7.x)
13:35:51:525  Updated USER_ACTIVITY.ALARM
13:35:51:572  Modified SalesLogix activity Actualizada: Foto de grup Abertis Logística-Salvador Alemany
13:35:51:572  in TSyncRun.MsgSourceKeyToEntryID
13:35:51:572  in TSyncRun.GetExchnageManageStore
13:35:51:572  out of TSyncRun.GetExchnageManageStore
13:35:51:572  Successfully called IExchangeManageStore::EntryIDFromSourceKey
13:35:51:572  out of TSyncRun.MsgSourceKeyToEntryID
13:35:51:588  Successfully called TActivitySyncRun.ExchangeToSLX IMsgStore:Smiley SurprisedpenEntry
13:35:51:588  Successfully called TExchangeRecipients - GetRecipientTable
13:35:51:588  Successfully called TExchangeRecipients - HrQueryAllRows
13:35:51:588  TExchangeRecipients - could not retrieve PR_ENTRYID or PR_OBJECT_TYPE property
13:35:51:588  Successfully called ExpandDL - IAddrBook.OpenEntry
13:35:51:713  Successfully called ExpandDL - IDistList.GetContentsTable
13:35:51:713  Successfully called ExpandDL - HrQueryAllRows
13:35:51:791  Successfully called ExchangeUserToSlxUser - IAddrBook.OpenEntry
13:35:51:791  Could not find SLX user for SID = S-1-5-21-4057588611-516736325-3382091719-2663
13:35:51:791  Successfully called ExchangeUserToSlxUser - IAddrBook.OpenEntry
13:35:51:791  ExchangeToSLX - could not retrieve PR_EMS_AB_ASSOC_NT_ACCOUNT. Does the Windows user still exist? - /o=Abertis/ou=First Administrative Group/cn=Recipients/cn=ToniGarcia
13:35:51:8

 

 

Highlighted
Gold Super Contributor
Posts: 3,087
Registered: ‎03-19-2009

Re: What does this error message mean?

You don't say what version/SP of EL.

   A - you should be running the latest.

 

    B - Try resetting the "link" for that user by:

              1 - Stop the EL service

              2 - Delete BOTH the .sdf and .mdf file for THAT contact link.

              3 - Start EL back up

   C - Wait and see if the problem comes back.

 

   D - Make sure AV software is NOT scanning the folder w/the EL logging and config files.

--
RJ Ledger - rjledger@rjlSystems.net +1 603.369.3047 x101

".. Innovators in Mobility - Experts in Workflow Automation..."
http://www.rjlSystems.net - blog: www.rjlSystems.net/blog.html
New Member
Posts: 8
Registered: ‎06-01-2010

Re: What does this error message mean?

Thanks for the answer.

 

Already done B & C but the problem is still there. Saleslogix is 7.2.2 and exchangelink 8.0.0.1040 (Hotfix 3)

 

Sorry for my English, I think I did not explain correctly the problem.

 

This integration was running ok about two weeks ago. When I said it happened only whith one integration I meant it happend obnly with one activity (I do not konw which one).

When I perform one integration manually there are several calls (I can count more than 20)  to  HrQueryAllRows that reports that lines in the log. It seems that perform this sequence for each of the exchange activities that should be sincronized:

 

out of TSyncRun.MsgSourceKeyToEntryID
Successfully called TActivitySyncRun.ExchangeToSLX IMsgStore:Smiley SurprisedpenEntry
Successfully called TExchangeRecipients - GetRecipientTable
Successfully called TExchangeRecipients - HrQueryAllRows

 

But ONLY ONE of these calls report the error

 

TExchangeRecipients - could not retrieve PR_ENTRYID or PR_OBJECT_TYPE property

 

I think this error is originated in some wrong data in one of the exchange activities, but since I do not know which activity is or what does this error mean I do not know how to locate it.

 

 

 

 

 

Employee
Posts: 165
Registered: ‎03-03-2009

Re: What does this error message mean?

From what it looks like, the information you sent originally has an ActivityID and a subject.  You may want to start with that particular activity.

 

Also, you may want to consider enabling the logging in the registry (check under hkey_local_machine\software\salesLogix\Exchange Link).  Enabling additional logging will help provide more details about the activity you are trying to track down.

 

As RJ suggested, I would recommend looking at upgrading to Exchange Link 8.0 HF5.  This version provides even more detailed logging that may help you track down the particular activity that could be causing the problem.

Loretta Carroll
QA Engineer
New Member
Posts: 8
Registered: ‎06-01-2010

Re: What does this error message mean?

Thank you again,

 

I'll try to update to hotfix5, Unfortunatelly the IT department of this specific customer requires a delay of 15 days and a lot of documentation to each change made in the production servers Smiley Sad

 

One more question the activity implied is the one shown after that problem lines is it? I mean the lines:

 

Update USER_ACTIVITY.ALARM (SLX version 7.x)
Updated USER_ACTIVITY.ALARM
Modified SalesLogix activity (activity name here)

 

Are the last lines of each sincronized activity are they?

 

If this is true I think that maybe there is something in common in all the activities with that error, but I should ask to the affected users to check if my theory is correct, and if the hotfix 5 solves the problem.