Activation (Communications Industry) (MOSC)

MOSC Banner

Order Stops in 103 Status in SARM

edited Aug 21, 2013 11:45AM in Activation (Communications Industry) (MOSC) 1 commentAnswered
All orders got stuck in SARM in 103 status with following messages in SARM diagnostic file:
>> 192917.011:24:SANE:ASDL Dispatch            :4017:sarm/sarm/sarm/nep_driver.c
'T_TIKONA-LDAP_V3_HOST': State: 2 Pending 21 In Proc 0 Connect 1 Prime 1
>> 192917.011:24:SANE:ASDL Dispatch            :4069:sarm/sarm/sarm/nep_driver.c
'T_TIKONA-LDAP_V3_HOST': Not Dispatching ASDL yet because of NE busy state.

And message in NEP diagnostic file:

>> 173613.050:23:PROG:System Event             :163 :sys_if/libasccomm/socket_if.c
ASAP System Event: SYS_ERR
Error: Jinterp connection for host (T_TIKONA-LDAP_V3_HOST) failed. Check if Jinterpreter is up and running

What could be the problem?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center