Message Visualizer HOWTO

Senthil in his post describes how to use CSF3’s message visualizer tool to track/debug sessions. Check it out! http://blogs.msdn.com/csf/archive/2006/11/02/csf-3-0-message-visualizer-tip.aspx

0

InChannelResponse parameter and Session interaction with CSF SDK based services

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…

0

WSE message body encryption on CSF for dummies:-)

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.   BackgroundCounting scenario…

0

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

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…

0

Service Logic: RuleEngineDeploymentNotDeployedException

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: ErrorEvent Source: ServiceLogicEvent Category: NoneEvent ID: 0Date:  2/2/2006Time:  3:25:42 PMUser:  N/AComputer: CSF01Description: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…

0

Session – The security token could not be authenticated or authorized

Event Type: ErrorEvent Source: Microsoft WSE 2.0Event Category: NoneEvent ID: 0Date:  26/01/2006Time:  10.21.49User:  N/AComputer: PSSCSM2Description: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&amp; tokenCount)  …

2

ps_x_TemplateManifestGivenRequestUUID error

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…

0

OHSBE ThrottleInterval must be > 0

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…

1

Multiple SBE Monitor issue

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>

3