Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

After Upgrade CRM 6.0 to 7.02 CRM url is not wokring

Hi All,

After upgrade of CRM 6.0 to 7.02 the url is not working. Please help to resolve ASAP.

http://sapcrmdev.XXX.com:8000/sap/bc/bsp/sap/crm_ui_frame/default.htm

  Error while processing your query

What has happened?

The URL call http://sapcrmdev.xxx.com:8000/sap/bc/bsp/sap/crm_ui_frame/default.htm was terminated because of an error.

Note

The following error occurred in system CRD : Could not set enqueue lock

The error occurred on application server SAPCRMDEV_CRD_00 and in work process. 4

The termination type was: ERROR_MESSAGE_STATE

The ABAP call stack was:

Method: PREPARE_OTR_DOCUMENT of program CL_HTTP_SERVER_NET============CP

Method: AUTHENTICATION of program CL_HTTP_SERVER_NET============CP

Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME

Module: %_HTTP_START of program SAPMHTTP

What can I do?

If the termination type was RABAX_STATE, you will find more information on the cause of termination in system CRD in transaction ST22.

If the termination type was ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server SAPCRMDEV_CRD_00 in transaction SM21.

If the termination type was ERROR_MESSAGE_STATE, you can search for further information in the trace file for the work process 4 in transaction ST11 on the application server SAPCRMDEV_CRD_00 . You may also need to analyze the trace files of other work processes.

If you do not yet have a user ID, contact your system adminmistrator.

Error Code: ICF-IE-http -c: 000 -u: SAPSYS -l: E -s: CRD -i: SAPCRMDEV_CRD_00 -w: 4 -d: 20150109 -t: 095832 -v: ERROR_MESSAGE_STATE -e: Could not set enqueue lock -X: 00505682314E1ED4A681FF4068762936_00505682314E1ED4A681FF4063942936_1 -x: FA0F98E44303F1B6893600505682314E

HTTP 500 - Internal Server Error

Your SAP Internet Communication Framework Team

Thanks,

Kavitha Rajan.

Tags:
Former Member
Former Member replied

Hemanth,

I manually performed the same kernel again that SUM updated. All are fine now.

Thanks,

Kavitha Rajan.

1 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question