<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Resolution to some problems you might encounter when upgrading to the Commerce Server Feature Pack</title><link>http://blogs.msdn.com/vinayakt/archive/2004/06/11/153358.aspx</link><description>This post contains resolution for a list of problems you might face when upgrading to the Feature Pack. I have compiled this list based on the Newsgroup questions and I will keep updating this post with any new issues. 1. Unable to access the catalog</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Resolution to some problems you might encounter when upgrading to the Commerce Server Feature Pack</title><link>http://blogs.msdn.com/vinayakt/archive/2004/06/11/153358.aspx#164440</link><pubDate>Thu, 24 Jun 2004 09:55:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:164440</guid><dc:creator>Daniel Tsadok</dc:creator><description>I have a problem - the Web Service fails with &amp;quot;The request failed with HTTP status 400: Bad Request.&amp;quot;&lt;br&gt;&lt;br&gt;&lt;br&gt;The full event log text is:&lt;br&gt;Microsoft.CommerceServer.UI.ServiceConnectionException: The Catalog Web Service &amp;quot;&lt;a target="_new" href="http://localhost/CatalogWebService/CatalogWebService.asmx&amp;quot;"&gt;http://localhost/CatalogWebService/CatalogWebService.asmx&amp;quot;&lt;/a&gt; is currently unavailable. The Web Service might be experiencing technical difficulties, or you may need to adjust your connection settings. ---&amp;gt; System.Net.WebException: The request failed with HTTP status 400: Bad Request.&lt;br&gt;   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)&lt;br&gt;   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)&lt;br&gt;   at Microsoft.CatalogServer.WebService.Proxies.CatalogWebService.AuthorizedInvoke(String methodName, Object[] parameters)&lt;br&gt;   at Microsoft.CatalogServer.WebService.Proxies.CatalogWebService.GetServiceVersion()&lt;br&gt;   at Microsoft.CatalogServer.Agent.CatalogContext.ValidateWebServiceVersion()&lt;br&gt;   at Microsoft.CatalogServer.Agent.CatalogContext.Create(ServiceAgent serviceAgent, DebugContext debugContext)&lt;br&gt;   at Microsoft.CatalogServer.CatalogContext.Create(CatalogServiceAgent catalogServiceAgent, DebugContext debugContext)&lt;br&gt;   at Microsoft.CommerceServer.UI.ConnectionCheck.ConnectToCatalogService(String catalogServiceUrl, String[] authMethods, IPromptForCredentials credentialPrompter, IWebProxy proxy)&lt;br&gt;   --- End of inner exception stack trace ---&lt;br&gt;   at Microsoft.CommerceServer.UI.ConnectionCheck.ConnectToCatalogService(String catalogServiceUrl, String[] authMethods, IPromptForCredentials credentialPrompter, IWebProxy proxy)&lt;br&gt;   at Microsoft.CommerceServer.UI.CatalogManager.LaunchPad.LoadDefaultSiteUrlConnection()</description></item></channel></rss>