Troubleshooting the Connected Services Framework usually involves three areas: Environment and Configuration, Message Delivery, and Security Settings.
Summary of Common mistakes:
Not using the Connected Services Framework API method, Session.RouteMsgToParticipants to route messages.
Forgetting that only Session participants can route messages.
Mistyping action names - remember that Session criteria are case sensitive.
Incorrect use of parenthesis when specifying Session Route criteria.
Not clearing the Session cache (specified in the Session.config file) when adding or removing methods from participant services.
Not correlating on SessionID or application-specific identifiers sent in the message headers.
Environment and Configuration: These are the issues relating to the configuration and setup of the components that are used by Microsoft® Connected Services Framework or are running Connected Services Framework components. A successful environment setup allows the component to be up and running under Microsoft Internet Information Services (IIS), and its Web Services Description Language (WSDL) may be queried successfully. Also, each component has specific requirements above and beyond those needed to simply receive a request. Configuration errors will show up in errors written out to the Microsoft Windows® event log or in error messages returned to the user of the component.
Message Delivery: Message routing is controlled through the building of the manifests sent to Session. Later requests to route those messages will succeed or fail based on the criteria. These generally result in errors to the event log.
Security Settings: There are several levels of security checking:
- The basic is what is required by the hosting environment—IIS, for example.
- The next level of security is what is configured into the Web Services Enhancements (WSE) 2.0 environment for the validation of messages sent to components. This is set through the WSE policy files.
- The final level of security is that imposed upon the requests by individual components. This is set in the configuration of a component at installation time. These errors generally show up in the Windows event log or are returned in response to requests.
Microsoft Operations Manager (MOM) 2005: The Connected Services Framework also ships with a MOM 2005 pack that allows aggregation and management of logging errors across the servers running the Connected Services Framework components.