This error may occur post client copy if somehow BDLS was not run properly. If you see an entry in CRMPRLS in ECC and CRMMLSGUID in CRM/SRM and they're same, the issue might still be there. So delete CRMPRLS on ECC, reset the queue and execute.
A new entry in CRMPRLS would be populated automatically. If the CRMPRLS table now has a new entry with blank logsys it can be due to the old logsys name.If the logsys name has to be changed then run the BDLS report.
Hi Rohit,
I have asked Basis to do the Settings as told by you.Now the Queue is moving to Inbound Queue of CRM.
Now they are getting stuck in CRM with the error coming as
Exception condition "GUID_FOR_LOGSYS_CHANGED" raised.
I checked CRMPRLS in R/3 and the logical client of R/3 is having a GUID say 'x'
I checked CRMMLSGUID in CRM and R/3 Logical Client is having a GUID say 'y'.
Should these GUID's not be same?? If Yes,What can be done to make them equal in both the systems.Please reply ASAP as the whole integration is getting stuck.
Puneet
Yes, these GUIDS have to be the same. CRMMLSGUID table entry should be deleted and you need to re-execute the queue in CRM Inbound so that it gets processed successfuly.
Hi Rohit,
After deleting the entry in CRMMLSGUID,I Deleted all the queues and again started the Initial Load.The same error is coming.What to do now.
Now,there is no entry in CRMMLSGUID.Its again stuck.Kindly guide.Its urgent
Regards
Puneet
