Sunday, January 20, 2013 6:13 PM
Hi - Hope someone can help me with this issue.
We had a change implemented to upgrade an existing tax application and after the change we started seeing the following error message when trying to access the application client.
Setup: Windows 2008 Application and SQL server windows 2008 with SQL Server 2008 SP2 enterprise edt.
Load balanced application : HTTPS 443
Service broker at https//***.com failed to retrieve the service information for Https://****.com (same address as 1st).
The underlying connection was closed. The connection was closed unexpectedly.
<action d1p1: mustunderstand="1" xmlns:d1p1="http://www.w3.org/2003/05/soap-envelope"
<ServiceClaimsClient xmlns="http://services.corptax.com"><serviceClaimsClient sessiondID=""
client id="000000-00000-0000-00000000" environment="environmentID= "000000-00000-0000-00000000" enterprise key="0" eneterprise id="000000-00000-0000-00000000" system year "0" username="" userID="000000-00000-0000-00000000" windowsidentityName= domain\userID" /></ServiceClaimsClient>
<rEPLY TO XMLNS="http://www.w3.org/2005/08/addressing">
<To d1p1:mustUnderstand="1" xmlnsd1p1="http://www.w3.org/2003/05/soap-envelope"
Monday, January 21, 2013 4:28 PM
could you please run SSBDiagnose utility on the service broker setup in question and share the output ? run the utility first in CONFIGURATION mode to make sure there are no configuration errors, before you run it for RUNTIME mode to track a particular conversation.
Please follow this link for more information on how to use the ssbdiagnose utility - http://msdn.microsoft.com/en-us/library/bb934450.aspx
Sanil Mhatre | Database Developer | MCTS | If you find my reply useful in any way, please vote it as helpful. If it has helped answer your question, please mark it as Answer. http://sqlwithsanil.com
Monday, January 21, 2013 4:34 PM
This error appears to be in a Web Service call to a web service endpoint at https://***.com/servicebroker.svc
The SQL Server Service Broker feature does not create any such web services, and nothing in the error message indicates any connection to SQL Server Service Broker.
This web service appears to be part of the "existing tax application", and so you need to address this with whoever supports that application.
- Marked As Answer by Iric WenModerator Monday, January 28, 2013 6:06 AM