NicolBlog : Connected Services Framework

Message Visualizer HOWTO

NicolD — Mon, 24 Sep 2007 12:44:00 GMT

Senthil in his post describes how to use CSF3's message visualizer tool to track/debug sessions. Check it out!

InChannelResponse parameter and Session interaction with CSF SDK based services

NicolD — Fri, 31 Aug 2007 16:09:00 GMT

When you define a CSF session, InChannelResponse partecipant's parameter allows to define how CSF session server communicate with the selected endpoint. In particular it allows to specify whether it should hold open the channel that the session server uses to communicate with the service when it routes a message, or whether it should close the channel. In the following example, CSF can recognize successfully the "OneWayFalseMethod" response only if the partecipant have InChannelResponse=true

    public class GenericSoapService : SoapService
    {
        public GenericSoapService()
        {

        }

        [SoapMethod(ServiceActions.OneWayFalseMethodRequest, ResponseAction = ServiceActions.OneWayFalseMethodResponse)]
        public String OneWayFalseMethod()
        {
            return "GenericSoapService OneWayFalseMethodResponse: OK";
        }
    }

If you use CsfService instead of SoapService to derive your service class, It have enough logic inside to undestand how CSF is calling him and decide how to deliver the answer in the correct way.

Infact the following example works with both InChannelResponse=true and InChannelResponse=false

    [CsfService(Name = "TestCSFService", Namespace = "http://TestCSFService")]
    public class Service : CsfService
    {
        [Operation(Name = "OneWayFalseMethod",
                   Action = ServiceActions.OneWayFalseMethodRequest,
                  ResponseAction = ServiceActions.OneWayFalseMethodResponse,
                   Oneway = false)]
        public String OneWayFalseMethod(String OneWayFalseMethodRequest)
        {
            return "OneWayFalseMethodResponse: OK";
        } 
    }

More information:

How the InChannelResponse Property Affects Messaging
Download Microsoft Connected Services Framework 3.0 Developer Lite Edition, Microsoft.ConnectedServices.Sdk.* libraries included

WSE message body encryption on CSF for dummies:-)

NicolD — Thu, 18 May 2006 20:15:00 GMT

In this post I'm showing how to enable WSE policy and body message encryption for CSF using one of the standard CSF examples: the Counting Scenario.

Prerequisites

In order to be sure that CSF installation is correct, the counting scenario have to work fine before to do any of the following actions.

Background
Counting scenario start through "CountingScenarioApp.exe" application. When you press "createSession" button follow messages will be routed:

CountingApp --> ServiceCatalog (ServiceCatalogGetUris)
ServiceCatalog -->CountingApp (ServiceCatalogGetUrisResponse)
CountingApp --> Session (CreateSession)
Session -->CountingApp (CreateSessionResponse)

our objective is to have ServiceCatalogGetUris message encrypted.

Step1: enable policy config

open c:\program files\microsoft csf\configuration\policycache.config
add as endpoint your CountingScenarioApp.exe application: you'll have to add something like:

Verify that enpoint of session and servicecatalog components have as URI the same name used by CountingScenarioApp.exe: usually in the file you find http://localhost/servicecatalog/... while the application call http://MYMACHINE/servicecatalog/...

Step2: configure applications
configure session web.config, servicecatalog web.config and countingscenarioapp.exe.config files to use the correct policycache.config file, adding following code under <microsoft.web.services2> node:

you can also add <policyTrace> to have policy logs

Step3: iisreset

Now CreateSession and TerminateSession form countingscenarioapp.exe should work fine. Please check also on event viewer to verify that no error appairs.

Step4: load a certificate to encrypt the message body
Follow instruction you find in "C:\Program Files\Microsoft WSE\v2.0\Samples\Sample Test Certificates\read.htm" to install "Server Private.pfx" certificate. You can also generate a brend new certificate as well.

Step5: configure servicecatalog to accept messages with encrypted body
Open policycache.config file and under <policies> ---> <Policy> ---> "EncryptMessage" set: <wssp:SubjectName>CN=WSE2QuickStartServer</wssp:SubjectName>.

Please use subject name of your certificate here!

Step6: modify servicecatalog endpoint as follows

Step 5: IISRESET

Now run CountingScenarioApp.exe and select CreateSession button. If everything still works, you'll obtain services URIs from the SC, with service catalog request "ServiceCatalogGetUris" body encrypted (look at WSE trace).

TIP: in case of error, check the event viewer. If you find as error "System.InvalidOperationException: Private Key is not available..." this suggests that the certificate was found but there was not enought permission given to access the private key file of the certificate. You can give these permission to any account using WSE certificate tool, clicking on the private key properties and then adding the selected user to the ACL's of the file.

Good luck!

CSF Session doesn't propagate credential from source to destination VAS

NicolD — Mon, 27 Mar 2006 19:18:00 GMT

If you don't include a "Persona Partecipant" in your session manifest, credentials aren't propagated from one VAS to another one.

Have a loook to the counting scenario you can find in sample CSF directory. The example call in sequence 2 VASes, each on these increment a value by 1, so if you submit 100, you receive 102 as result.

This is the template manifest for the example:

<csfse:Session xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" timestamp="2006-03-27T18:42:09.9344400+02:00" timeout="15" serialize="None" state="Active" routeAnyAction="true" ackOnRouteMsgToParticipants="false" xmlns:csfse="http://www.microsoft.com/csf/20/Session/">
<csfse:SessionName>CountingSample</csfse:SessionName>
<csfse:Participants>
  <csfse:Participant timeout="30" role="Service" mode="OneWay" type="WebService">
   <csfse:ParticipantName>ServiceParticipant1</csfse:ParticipantName>
   <csfse:ParticipantID>ServiceParticipant1</csfse:ParticipantID>
   <csfse:ParticipantUrl>http://CSF01/CountingService2/Service2.ashx</csfse:ParticipantUrl>
   <csfse:ParticipantWsdlUrl>http://CSF01/CountingService2/Service2.ashx</csfse:ParticipantWsdlUrl>
  </csfse:Participant>
  <csfse:Participant timeout="30" role="Service" mode="OneWay" type="WebService">
   <csfse:ParticipantName>ServiceParticipant2</csfse:ParticipantName>
   <csfse:ParticipantID>ServiceParticipant2</csfse:ParticipantID>
   <csfse:ParticipantUrl>http://CSF01/CountingService1/Service1.ashx</csfse:ParticipantUrl>
   <csfse:ParticipantWsdlUrl>http://CSF01/CountingService1/Service1.ashx</csfse:ParticipantWsdlUrl>
  </csfse:Participant>
  <csfse:Participant timeout="30" role="Service" mode="OneWay" type="WebService">
   <csfse:ParticipantName>UIParticipant</csfse:ParticipantName>
   <csfse:ParticipantID>UIParticipant</csfse:ParticipantID>
   <csfse:ParticipantUrl>soap.tcp://localhost:9111/UiFormService</csfse:ParticipantUrl>
   <csfse:ParticipantWsdlUrl>soap.tcp://localhost:9111/UiFormService</csfse:ParticipantWsdlUrl>
  </csfse:Participant>
</csfse:Participants>
<csfse:RoutingTable version="1" timestamp="2006-03-27T18:42:13.9603020+02:00">
  <csfse:Routes>
   <csfse:Route>
    <csfse:Criteria>(ACTION EQ 'Add')</csfse:Criteria>
    <csfse:Destination>ServiceParticipant1[Add]</csfse:Destination>
    <csfse:Intercept/>
   </csfse:Route>
   <csfse:Route>
    <csfse:Criteria>((ACTION EQ 'AddResponse') AND (SOURCE EQ 'ServiceParticipant2'))</csfse:Criteria>
    <csfse:Destination>UIParticipant[RouteResponse]</csfse:Destination>
    <csfse:Intercept/>
   </csfse:Route>
   <csfse:Route>
    <csfse:Criteria>((ACTION EQ 'AddResponse') AND (SOURCE EQ 'ServiceParticipant1'))</csfse:Criteria>
    <csfse:Destination>ServiceParticipant2[Add]</csfse:Destination>
    <csfse:Intercept/>
   </csfse:Route>
  </csfse:Routes>
</csfse:RoutingTable>
</csfse:Session>

Everything starts with a message with an "Add" action from UI partecipant.
The SOAP header is something like (some header removed to simplify the reading):

<soap:Envelope>
    <soap:Header>
      <csfse:SessionID>urn:...</csfse:SessionID>
      <wsa:Action>Add</wsa:Action>
...
      <wsse:Security soap:mustUnderstand="1">
        <wsu:Timestamp wsu:Id="Timestamp-9f6829b8-d2d3-49c5-9c7c-60c026998a57">
          <wsu:Created>2006-03-27T16:51:38Z</wsu:Created>
          <wsu:Expires>2006-03-27T16:56:38Z</wsu:Expires>
        </wsu:Timestamp>
        <wsse:UsernameToken wsu:Id="SecurityToken-...">
          <wsse:Username>administrator@fabrikam.com</wsse:Username>
          <wsse:Password>password</wsse:Password>
          <wsse:Nonce>VOlNA2DOTUoFuWOjfW8lvg==</wsse:Nonce>
          <wsu:Created>2006-03-27T16:51:38Z</wsu:Created>
        </wsse:UsernameToken>
      </wsse:Security>
    </soap:Header>
    <soap:Body>
...
    </soap:Body>
</soap:Envelope>

When session routes this message to ServicePartecipant1 the header becomes:

<soap:Envelope>
    <soap:Header>
     <csfse:SessionID>urn:...</csfse:SessionID>
      <wsa:Action>Add</wsa:Action>
...
      <wsse:Security>
        <wsu:Timestamp wsu:Id="Timestamp-f97709ea-9a36-4a3c-9c27-301e655c404a">
          <wsu:Created>2006-03-27T16:51:38Z</wsu:Created>
          <wsu:Expires>2006-03-27T16:56:38Z</wsu:Expires>
        </wsu:Timestamp>
      </wsse:Security>
    </soap:Header>
    <soap:Body>
      ...
    </soap:Body>
</soap:Envelope>

as you can see the username token is gone. If you want to keep it, modify template manifest as follows:

(1) add persona partecipant

<csfse:Participant timeout="30" role="Persona" mode="OneWay" type="WebService">
<csfse:ParticipantName>PersonaParticipant</csfse:ParticipantName>
<csfse:ParticipantID>PersonaParticipant</csfse:ParticipantID>
<csfse:ParticipantUrl>...</csfse:ParticipantUrl>
<csfse:ParticipantWsdlUrl>...</csfse:ParticipantWsdlUrl>
<csfse:SecurityToken>
  <wsse:UsernameToken wsu:Id="SecurityToken-055ed3fb-b592-49c7-b2b7-6f18a1ff7a86">
   <wsse:Username>administrator@fabrikam.com</wsse:Username>
   <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">...</wsse:Password>
   <wsse:Nonce>wPasvF7+DZ2DTcuWfEKVsg==</wsse:Nonce>
   <wsu:Created>2006-03-24T17:07:19Z</wsu:Created>
  </wsse:UsernameToken>
</csfse:SecurityToken>
</csfse:Participant>

(2) For any participant except for the Persona participant, the <policyDocument> tag indicates that secondary credentials are required for the participant. If a <policyDocument> tag is specified for a participant, then a Session Persona <Participant> should also be defined. Warning: If you specify the <policyDocument> without a persona partecipant, the message is simply not ruoted!!!

Service Logic: RuleEngineDeploymentNotDeployedException

NicolD — Tue, 14 Feb 2006 18:49:00 GMT

in this case "TestProduct3_Policy" is published and not deployed or it is not present at all. Use business rules composer interface to publish and deploy the rule.

-----------------------------------------------

Event Type: Error
Event Source: ServiceLogic
Event Category: None
Event ID: 0
Date:  2/2/2006
Time:  3:25:42 PM
User:  N/A
Computer: CSF01
Description:
Microsoft.EnterpriseInstrumentation.Schema.ErrorMessageEvent
{
   String Message = "Microsoft.RuleEngine.RuleEnginePolicyRetrievalException: Error retrieving the latest information for ruleset "TestProduct3_Policy" from the Update Service. ---> Microsoft.RuleEngine.RuleEngineDeploymentNotDeployedException: No versions of ruleset "TestProduct3_Policy" are deployed.

Server stack trace:
   at Microsoft.RuleEngine.RemoteUpdateService.RemoteUpdateService.GetLatest(String ruleSetName)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(MethodBase mb, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.RuleEngine.IRuleEngineUpdateServiceInterface.GetLatest(String ruleSetName)
   at Microsoft.RuleEngine.RemoteUpdateService.RemoteUpdateServiceProxy.GetLatest(String ruleSetName)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(MethodBase mb, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [1]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.RuleEngine.RemoteUpdateService.RemoteUpdateServiceProxy.GetLatest(String ruleSetName)
   at Microsoft.RuleEngine.RuleEngineCache.Allocate(String rulesetName, TrackingConfiguration& trackingConfig)
   --- End of inner exception stack trace ---
   at Microsoft.RuleEngine.RuleEngineCache.Allocate(String rulesetName, TrackingConfiguration& trackingConfig)
   at Microsoft.RuleEngine.Policy..ctor(String policyName)
   at Microsoft.Csf.Sbe.OrderHandling.ServiceLogic.BizTalkHelper.RulePolicyManager.ExecuteRulePolicy(XmlNode mid, String policyName)"
   String ErrorCode = "90000"
   Int32 Severity = 1
   Int32 ProcessID = 908
   String ProcessName = "C:\PROGRA~1\MICROS~4\BTSNTSvc.exe"
   String ThreadName = ""
   ComPlusInfo ComPlus = {
      String ActivityID = ""
      String ApplicationID = ""
      String TransactionID = ""
      String DirectCaller = ""
      String OriginalCaller = ""
   }
   WindowsSecurityInfo WindowsSecurity = {
      String CurrentAccountName = "FABRIKAM\Administrator"
      String ProcessAccountName = "BUILTIN\Administrators"
   }
   ManagedSecurityInfo ManagedSecurity = {
      String IdentityName = ""
      String AuthenticationType = ""
      Boolean IsAuthenticated = False
   }
   String StackTrace = " at Microsoft.EnterpriseInstrumentation.Schema.ErrorMessageEvent.Raise(EventSource eventSource, String message, Int32 severity, String errorCode)
at Microsoft.Csf.Utilities.Logger.LogException(Exception theException)
at Microsoft.Csf.Sbe.OrderHandling.ServiceLogic.BizTalkHelper.Logger2.LogException(CsfException theException)
at Microsoft.Csf.Sbe.OrderHandling.ServiceLogic.BizTalkHelper.Utility.ProcessException(Exception exception, MessageType messageType)
at Microsoft.Csf.Sbe.OrderHandling.ServiceLogic.BizTalkHelper.Utility.ProcessGenericOrchestrationException(Exception exception)
at Microsoft.Csf.Sbe.OrderHandling.ServiceLogic.Orchestration.GenericOrchestration.segment26(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
at Microsoft.XLANGs.Core.SegmentScheduler._RunSomeSegments(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunSomeSegments(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunMore(Object t)
at Microsoft.XLANGs.BizTalk.CrossProcess.WorkItem.Execute()
at Microsoft.XLANGs.BizTalk.CrossProcess.GlobalThreadPool._workerWithContext(Object workItemObj)"
   String EventSourceInstance = "03526852-a2d5-4458-a2c9-56d617134ab3"
   String EventSourceName = "ServiceLogic"
   Int64 EventSequenceNumber = 6
   String EventSchemaVersion = "7.0.5000.0"
   DateTime TimeStamp = 2/2/2006 3:25:41 PM
   String AppDomainName = "__XDomain_3.0.1.0_0"
   String MachineName = "CSF01"
   String RootRequestName = ""
   String RootRequestInstance = ""
   String RequestInstance = ""
   String RequestName = ""
   Int64 RequestSequenceNumber = 0
   Int32 EventLogEntryTypeID = 1
}

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

Session - The security token could not be authenticated or authorized

NicolD — Thu, 26 Jan 2006 13:38:00 GMT

Event Type: Error
Event Source: Microsoft WSE 2.0
Event Category: None
Event ID: 0
Date:  26/01/2006
Time:  10.21.49
User:  N/A
Computer: PSSCSM2
Description:
Message Dispatch Failure: <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Header><wsa:Action>http://schemas.xmlsoap.org/ws/2004/03/addressing/fault</wsa:Action>

<wsa:MessageID>uuid:f72d4193-5884-42d3-92f6-3612b2494b0c</wsa:MessageID><wsa:RelatesTo>uuid:d60016fb-ca69-4b03-87bc-ffea68069b7b</wsa:RelatesTo><wsa:To>soap.tcp://client:9823/SessionSnapIn</wsa:To>

<wsse:Security><wsu:Timestamp wsu:Id="Timestamp-6b703080-475e-435c-ad6a-f1faacb01acb"><wsu:Created>2006-01-26T09:21:49Z</wsu:Created><wsu:Expires>2006-01-26T09:26:49Z</wsu:Expires></wsu:Timestamp></wsse:Security></soap:Header><soap:Body><soap:Fault><faultcode xmlns:code="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">code:FailedAuthentication</faultcode><faultstring>Microsoft.Web.Services2.Security.SecurityFault: The security token could not be authenticated or authorized
   at Microsoft.Web.Services2.Security.Tokens.UsernameTokenManager.OnLogonUserFailed(UsernameToken token)
   at Microsoft.Web.Services2.Security.Tokens.UsernameTokenManager.LogonUser(UsernameToken token)
   at Microsoft.Web.Services2.Security.Tokens.UsernameTokenManager.AuthenticateToken(UsernameToken token)
   at Microsoft.Web.Services2.Security.Tokens.UsernameTokenManager.VerifyToken(SecurityToken securityToken)
   at Microsoft.Web.Services2.Security.Tokens.SecurityTokenManager.LoadXmlSecurityToken(XmlElement element)
   at Microsoft.Web.Services2.Security.Tokens.SecurityTokenManager.GetTokenFromXml(XmlElement element)
   at Microsoft.Web.Services2.Security.Security.LoadToken(XmlElement element, SecurityConfiguration configuration, Int32& tokenCount)
   at Microsoft.Web.Services2.Security.Security.LoadXml(XmlElement element)
   at Microsoft.Web.Services2.Security.SecurityInputFilter.ProcessMessage(SoapEnvelope envelope)
   at Microsoft.Web.Services2.Pipeline.ProcessInputMessage(SoapEnvelope envelope)
   at Microsoft.Web.Services2.Messaging.SoapReceiver.FilterMessage(SoapEnvelope envelope)
   at Microsoft.Web.Services2.Messaging.SoapReceiver.ProcessMessage(SoapEnvelope message)</faultstring><faultactor>http://session.csf.local/Session/SessionManagerAdmin.ashx</faultactor>

</soap:Fault></soap:Body></soap:Envelope>

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

Event Type: Error
Event Source: SessionManagement
Event Category: None
Event ID: 0
Date:  26/01/2006
Time:  10.21.49
User:  N/A
Computer: PSSCSM2
Description:
SessionManagement http transport adaptor
"Session application recieved invalid soap envelope - The security token could not be authenticated or authorized"

For more information, see Help and Support Center at

These errors regards communication between Session component and session administrator snap-in.

Assuming that user present in soap header message exists, is active and authorized, one reason of this error can be that session answer came after that message or user token is expired.

Why? Server load, some kind of deadlock or contention on CSF session DB.

For this reason I kindly disregard it.

CSF Session component Session doesn't route back the message to the sender

NicolD — Tue, 24 Jan 2006 02:10:00 GMT

This is by desing.

ps_x_TemplateManifestGivenRequestUUID error

NicolD — Mon, 23 Jan 2006 20:14:00 GMT

40004: OHSBE Error in: SbeMasterController.GetServiceUrisResponse(), Description: SbeMasterController.ProcessGetServiceUrisResponse(): Database error. Procedure: GetTemplateSessionManifest() Error was: Error in ps_x_TemplateManifestGivenRequestUUID - Unable to locate record for passed PK - - RequestUUID, CSFErrorCodes: 40004

You need to have proper records in the two tables in the SBE database.

The tables in consideration are: ProductActionTemplateManifest and TemplateManifest.

The Template Manifests are stored in the Template Manifest table. The TemplateManifestID is referenced in the ProductActionTemplateManifest table.

The ProductOfferID column in the ProductActionTemplateManifest contains the name of the product you are passing in the in the Order Request. Once a request is received it is first searched in the ProductActionTemplateManifest table based in the Product Offering ID and the TemplateManifestID is read. Then from the TemplateManifest table the Template Manifest is read and returned. Check the records in the two tables and the values passed in the order request.

(thanks to Kapil note!)

OHSBE ThrottleInterval must be > 0

NicolD — Mon, 16 Jan 2006 14:42:00 GMT

In production environment never set ThrottleInterval=0 because may cause a condition called thread exhaustion.

Follow a list of error you can encourr:

Event Type: Error Event Source: SbeMasterController Description: Microsoft.EnterpriseInstrumentation.Schema.ErrorMessageEvent { String Message = "Microsoft.Csf.Sbe.OrderHandling.SbeMasterControllerException: SbeMasterController.ProcessCreateSessionResponse(): Database error. Procedure: GetQueryServiceForProductResponse() Error was: Error in ps_x_ProductServiceMappingDataGivenRequestUUID - Unable to find valid binary pointer - ProductServiceMappingData at Microsoft.Csf.Sbe.OrderHandling.MasterController.SbeMasterController.ProcessCreateSessionResponse(SoapEnvelopeHolder holder)" String ErrorCode = "40004"

Microsoft.EnterpriseInstrumentation.Schema.ErrorMessageEvent { String Message = "Microsoft.Csf.Sbe.OrderHandling.SbeMasterControllerException: SbeMasterController.ServiceLogicStatus(): Database error. Procedure: GetRequestUUIDGivenSessionID() Error was: Error in ps_s_GetRequestUUIDGivenSessionID - Lookup value not found. - SessionID at Microsoft.Csf.Sbe.OrderHandling.MasterController.SbeMasterController.ProcessServiceLogicStatus(ServiceLogicCompletionStatus status, SoapEnvelopeHolder holder)" String ErrorCode = "90000"

Microsoft.EnterpriseInstrumentation.Schema.ErrorMessageEvent { String Message = "ServiceLogicStateManager.ChangeStateToCompleted:: Database error in service logic. Procedure: dbo.ps_x_ChangeServiceLogicStateTo_Completed Error message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding." String ErrorCode = "50009"

Multiple SBE Monitor issue

NicolD — Wed, 28 Dec 2005 00:07:00 GMT

Do not run more than one SBE Monitor for a set of load-balanced OHSBEs. One of the error you can encounter is the following:

<SubmitOrderComplete xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns="http://www.microsoft.com/csf/20/Sbe">
<InteractionID>...</InteractionID>
<RequestUUID>...</RequestUUID>
<ResultCode>40005</ResultCode>
<ErrorMessage>OHSBE Error in: SbeMasterController.MonitorUpdate(), 
Description: SbeMasterController.CheckIfRequestWasBlocking(): 
Database error. Procedure: CheckIfRequestShouldStillBeStaged() 
Error was: Error in ps_x_CheckIfRequestShouldStillBeStaged - 
Order Response initial State not correct to update to  - 
Staged, CSFErrorCodes: 40005</ErrorMessage>
</SubmitOrderComplete>

Master controller can not communicate with Service Catalog

NicolD — Tue, 20 Dec 2005 12:32:00 GMT

Master controller can not communicate with Service Catalog (that is on the same machine) when it is balanced with external hardware.

This kind of error can happen in the scenario bellow

CLIENT: order requester

VCSF: load balancer hardware

CSF01: Master controller + service catalog

CSF02: Master controller + service catalog

PSM: product service mapping web service

This is the sequence:

Client call master controller in order to send a order request:

TO: http://VCSF/MasterController/SbeMasterController.ashx

REPLYTO: http://CLIENT/responsemanager.ashx

Master controller call product service mapping

TO: http://PSM/psm.ashx

REPLYTO: http://VCSF/MasterController/SbeMasterController.ashx

Master controller call service catalog

TO: http://VCSF/ServiceCatalog/ServiceCatalogConnector.ashx

REPLYTO: http://VCSF/MasterController/SbeMasterController.ashx (***)

(***) Here there is the error because it can happen that from a balanced node (CSF01) isn't reachable the virtual IP VCSF because hardware balancer limit.

In order to fix this issue: Open /Microsoft CSF/configuration/SBE master controller.config and:

(1) Set MultipleOHSBEs=true

(2.1) on CSF01: Set ServiceCatalogResponseReplyTo=http://CSF01/MasterController/SbeMasterController.ashx

(2.2) on CSF02: Set ServiceCatalogResponseReplyTo=http://CSF02/MasterController/SbeMasterController.ashx

(3) iisreset

SBE Error 40006 "failed role check validation"

NicolD — Tue, 22 Nov 2005 20:22:00 GMT

The SBE checks that the user in the SumbitOrderRequest header belongs to the role defined in "SBEMasterController.config" file under "OHSBERole" config value.
This means that usually user must be into YOURDOMAIN\Requestors@CSF_SBE group.
One typical configuration mystake is to have in SBEMasterController.config file following content:

Obviously change "CSF" with your domain name and try again :)
N