locked
Getting an error from Session Component RRS feed

  • Question

  •  

    We are getting an error from the CSF Session component when we want to integrate our front end web application with the Service Logic component using OHSBE. When we observe the event log under the "OHSBE" section we got the following error:

     

    "Participant name must be specified and can not be 'SESSION'."

     

    Complete event log trace information:

     

    Timestamp: 3/28/2007 1:45:04 PM

    Message:

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

    Exception Messages:

    Type: Microsoft.ConnectedServices.Sbe.OrderHandling.Exceptions.SbeException

    Name: soapException

    Nature: System.Web.Services.Protocols.SoapException: Participant name must be specified and can not be 'SESSION'.

    Type: Microsoft.ConnectedServices.Sbe.OrderHandling.Exceptions.SbeException

    Name: soapException.Code

    Nature: http://www.w3.org/2003/05/soap-envelope: Sender

    Type: Microsoft.ConnectedServices.Sbe.OrderHandling.Exceptions.SbeException

    Name: soapException.Detail

    Nature: IsEmptyOrNull

    Type: Microsoft.ConnectedServices.Sbe.OrderHandling.Exceptions.SbeException

    Name: soapException.Message

    Nature: Participant name must be specified and can not be 'SESSION'.

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

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

    Detail Message Info:

    Type: Microsoft.ConnectedServices.Sbe.OrderHandling.Exceptions.SbeException

    Name: soapException

    Nature: System.Web.Services.Protocols.SoapException: Participant name must be specified and can not be 'SESSION'.

    Type: Microsoft.ConnectedServices.Sbe.OrderHandling.Exceptions.SbeException

    Name: soapException.Code

    Nature: http://www.w3.org/2003/05/soap-envelope: Sender

    Type: Microsoft.ConnectedServices.Sbe.OrderHandling.Exceptions.SbeException

    Name: soapException.Detail

    Nature: IsEmptyOrNull

    Type: Microsoft.ConnectedServices.Sbe.OrderHandling.Exceptions.SbeException

    Name: soapException.Message

    Nature: Participant name must be specified and can not be 'SESSION'.

    Stack:

    at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)

    at System.Environment.get_StackTrace()

    at Microsoft.ConnectedServices.Sbe.OrderHandling.Exceptions.SbeException.GetMesageInfo(StringBuilder& sbMessageParameters, StringBuilder& sbCompleteMessageInfo)

    at Microsoft.ConnectedServices.Sbe.OrderHandling.Exceptions.SbeException.get_Message()

    at Microsoft.ConnectedServices.Sbe.OrderHandling.Exceptions.SbeException..ctor(ExceptionParameter[] parameterList)

    at Microsoft.ConnectedServices.Sbe.OrderHandling.SbeMasterController.ThreadProcessFaultResponse(Object data)

    at Microsoft.ConnectedServices.Sbe.OrderHandling.Threading.CallbackThreadPool.ThreadPoolFunc()

    at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

    at System.Threading.ExecutionContext.runTryCode(Object userData)

    at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)

    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

    at System.Threading.ThreadHelper.ThreadStart()

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

    Category: General

    Priority: 4

    EventId: 10201

    Severity: Error

    Title:Exception

    Machine: CSFDOMAIN-103

    Application Domain: /LM/W3SVC/1/Root/OHSBE30-1-128195630910330807

    Process Id: 4176

    Process Name: c:\windows\system32\inetsrv\w3wp.exe

    Win32 Thread Id: 4392

    Thread Name:

    Extended Properties:

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

    Timestamp: 3/28/2007 1:45:04 PM
    Message: Microsoft.ConnectedServices.Sdk.Messaging.SoapFaultException: Participant name must be specified and can not be 'SESSION'.
       at Microsoft.ConnectedServices.Connector.Session.SessionManager.ValidateAndNormalizeParticipants(ParticipantManifest[] participants, String faultAction)
       at Microsoft.ConnectedServices.Connector.Session.SessionManager.CreateSession(CreateSessionRequest createRequest)
       at Microsoft.ConnectedServices.Connector.Session.SessionManagerAdminWS.CreateSession(CreateSessionRequest create)
    Category: Session OperationalEvent
    Priority: 1
    EventId: 20112
    Severity: Error
    Title: Session
    Machine: CSFDOMAIN-103
    Application Domain: /LM/W3SVC/1/Root/Session30-1-128195631009080807
    Process Id: 2812
    Process Name: c:\windows\system32\inetsrv\w3wp.exe
    Win32 Thread Id: 5336
    Thread Name:
    Extended Properties:

     

    Please help us in resolving this issue, we searched UDDI store and also the t-Model files which are used to configure the services but they are all fine.

     

    Regards,

     

    Wednesday, March 28, 2007 2:23 PM

Answers

  •  

    We could able to solve this error. There was a mistake in the UDDI server for one of the tModel information related to the VAS service which we are consuming in our application. By changing the tModel details to this service we could able to solve this error..... Now are facing one more error from Session component.

     

    After we processed the request using Service Logic, when it returns the Submit Order Complete response to OHSBE through CSF Session component we are receiving following error “Secondary credentials do not exist for either message security or transport security for Participant OHSBE.” 

     

    This issue was solved by changing the ESSO entries for the Session and OHSBE components.

     

    Regards,

    Friday, March 30, 2007 5:13 AM