Problem CRM System - Component provider_dl failed opend.

[Former Member]

Hi, i have problem open component provider_dl (CRM_UI)

Error when processing your request

What has happened?

The URL http://ctsx64ntcrm.ctsnx.com:8000/sap/bc/bsp/sap/provdlframe/BSPWDApplication.do was not called due to an error.

Note

The following error text was processed in the system CRX : Exception condition "COMMUNICATION_FAILURE" raised.

The error occurred on the application server ctsx64ntcrm_CRX_00 and in the work process 0 .

The termination type was: RABAX_STATE

The ABAP call stack was:

Method: LOAD_FROM_BSP_PAGE of program CL_BSP_WD_STREAM_LOADER=======CP

Method: GET_REPOSITORY_XML of program CL_BSP_WD_COMPONENT_FACTORY===CP

Method: GET_COMPONENT_TYPE of program CL_BSP_WD_COMPONENT_FACTORY===CP

Method: GET_COMPONENT_REPOSITORY of program CL_BSP_WD_COMPONENT_FACTORY===CP

Method: CONSTRUCTOR of program CL_BSP_WD_COMPONENT_USAGE=====CP

Method: GET_COMPONENT_USAGE of program CL_BSP_WD_COMPONENT_CONTROLLERCP

What can I do?

If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system CRX in transaction ST22.

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

If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server ctsx64ntcrm_CRX_00 . In some situations, 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 administrator.

Error code: ICF-IE-http -c: 810 -u: PRUEBA -l: E -s: CRX -i: ctsx64ntcrm_CRX_00 -w: 0 -d: 20110518 -t: 123632 -v: RABAX_STATE -e: RAISE_EXCEPTION

HTTP 500 - Internal Server Error

Your SAP Internet Communication Framework Team

*****************************************************************************************************************************

Int Tx ST11 show messages:

****************************************************************************************************************************

N RSEC: The entry with identifier /HMAC_INDEP/RFC_EXTERNAL_TICKET_4_TRUSTED_SYSTEM

N was encrypted by a system

N with different installation number and cannot be read.

M *** ERROR => LocFunc_ReadKeyFromDB(): Error in function: 'RSecDReadItem()' (errorcode=-2) [sntxxhmac.c 1298]

A *** ERROR => RFC Signon> Failure in ab_MakeTicketSndExternal calling SntHMAC_SetHMACKey (rc: 53) [abrfcsgn.c 1019]

A TH VERBOSE LEVEL FULL

A ** RABAX: end RX_GET_MESSAGE

A TH VERBOSE LEVEL FULL

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

A ** RABAX: level LEV_RX_SAVE_SHMLOCKS entered.

A ** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.

A ** RABAX: level LEV_RX_ROLLBACK entered.

A ** RABAX: level LEV_RX_ROLLBACK completed.

A ** RABAX: level LEV_RX_DB_ALIVE entered.

A ** RABAX: level LEV_RX_DB_ALIVE completed.

A ** RABAX: level LEV_RX_HOOKS entered.

A ** RABAX: level LEV_RX_HOOKS completed.

A ** RABAX: level LEV_RX_STANDARD entered.

A ** RABAX: level LEV_RX_STANDARD completed.

[Former Member · Accepted solution]

N RSEC: The entry with identifier /HMAC_INDEP/RFC_EXTERNAL_TICKET_4_TRUSTED_SYSTEM
N was encrypted by a system
N with different installation number and cannot be read.

Probably the Issuing System information was changed, probably you have to Re-Exchange the certificates.

Thanks

SM

[Former Member · Accepted solution]

Hi, SM, the certificate in the TX strustsso2??

[Former Member · Accepted solution]

Is this a system copy of Production?

Refer to this below Answered threads:

Thanks

SM

[Former Member · Accepted solution]

No, system is DEV.

[Former Member · Accepted solution]

Sm, logon in the TX strustsso2, show messages

Cannot create RFC connection.

The system PSE show yellow.

[Former Member · Accepted solution]

Hello Eli,

What about your SYSTEM PSE, is that showing green, right click on SYstem PSE ---> Check, if there is an error,

do DELETE and RECREATE PSE.

If this error is about a CERTIFICATE from different system then delete it and re-import the new certificate of that issuing system.

Thanks

SM

[Former Member · Accepted solution]

The error certificate is same system.

the system: CRX

The error certificate with CRX.

[Former Member · Accepted solution]

So you have to recreate the SYSTEM PSE as the current PSE is not valid.

DELETE: STRUSTSSO2---> right click on SYTEM PSE --> Delete

CREATE: STRUSTSSO2---> right click on SYTEM PSE --> CREATE.

It will turn Green once you have created it else post the error.

Regards

SM

[Former Member · Accepted solution]

SM, in TX sm59 failed all connections.

Show messages in test connection:

- Error connection

- RFC error when sending logon data

[Former Member · Accepted solution]

Hi, I solved problem apply note: 1532825 - Deleting SECSTORE entries during system export/system copy

[symon_braunbaer · Accepted solution]

This is the REAL solution which helped me!! Please note, that if the secure store is messed up, you can't import the profiles !!

[Former Member]

Hi,

If you are getting this error while performing any operation on CRM Web UI, then check if the crrect RFC destination pointing to ISU or other system is assigned in transaction BD97.

Regards,

Vamshi.

[Former Member]

Hello Eli

Kindly check the ST22 Dump against this user and can you provide that information.

Regards

Vivek

[Former Member]

show messages in the TX st22

A RAISE statement in the program "CL_BSP_WD_STREAM_LOADER=======CP" raised the

exception

condition "COMMUNICATION_FAILURE".

Since the exception was not intercepted by a superior

program, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

-