FIX: Error messages are logged in the Application log when you unpack a Commerce Server 2007 site to the root folder of the IIS Web site and then you try to access the SiteCacheRefresh.axd URL (922068)

SYMPTOMS

Consider the following scenario. You unpack a Microsoft Commerce Server 2007 site to the root folder of the Microsoft Internet Information Services (IIS) Web site. You try to access the SiteCacheRefresh.axd URL from any of the user interfaces. In this scenario, the following error messages are logged in the Application log:

System.InvalidOperationException: There was an error generating the XML document. ---> System.InvalidOperationException: Instance validation error: '0' is not a valid value for System.Net.HttpStatusCode.
 at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterList1.Write1_HttpStatusCode(HttpStatusCode
 v)
 at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterList1.Write3_CacheRefreshFailureInformation(String
 n, String ns, CacheRefreshFailureInformation o, Boolean isNullable, Boolean needType)
 at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterList1.Write4_Item(Object o)
 --- End of inner exception stack trace ---
 at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)
 at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o)
 at Microsoft.CommerceServer.Internal.SerializableExceptionSignature.ReflectProperty(XmlWriter xmlWriter, Object obj, SerializableProperty propertyInfo)
 at Microsoft.CommerceServer.Internal.SerializableExceptionSignature.BuildDetailXml(Boolean useCustomErrors, SerializableExceptionInfo exceptionInfo, Exception exceptionToSerialize)
 at Microsoft.CommerceServer.Internal.ExceptionSerializer.TrySerializeToSoapException(Boolean useCustomErrors, SerializableExceptionInfo exceptionInfo, Exception exceptionToSerialize, Boolean& shouldLogException)
 at Microsoft.CommerceServer.Internal.ExceptionSerializer.TrySerializeToSoapException(SerializableExceptionInfo[]
 exceptionInfoList, Exception exceptionToSerialize, Boolean& shouldLogException)
 at Microsoft.CommerceServer.Marketing.WebService.MarketingWebService.PropagateOrLogExceptionInternal(Exception
 except)
 at Microsoft.CommerceServer.Marketing.WebService.MarketingWebService.PropagateOrLogException(Exception except)
 at Microsoft.CommerceServer.Marketing.WebService.MarketingWebService.RefreshCache(String cacheName)

Additionally, you receive error messages that resemble the following when you use Commerce Server Staging (CSS) to access the SiteCacheRefresh.axd URL:

Failed to import business data for 'Marketing' resource for project 'MarketingFull' : Microsoft.CommerceServer.CacheRefreshFailedException: One or more errors occurred while refreshing the cache 'Advertising' of the site 'SiteName': The server 'ServerName' of the application 'ApplicationName' returned HTTP status code 502 (Proxy Error ( The host was not found. )). The cache refresh URL used was 'http://sitecacherefresh.axd/?CacheToRefresh=Advertising'.The <http://sitecacherefresh.axd/?CacheToRefresh=Advertising'.The> server 'ServerName' of the application 'Services' returned HTTP status code 502 (Proxy Error ( The host was not found. )). The cache refresh URL used was 'http://sitecacherefresh.axd/?CacheToRefresh=Advertising'.The <http://sitecacherefresh.axd/?CacheToRefresh=Advertising'.The> server 'ServerName' of the application 'LearningPlatform' returned HTTP status code 502 (Proxy Error ( The host was not found. )). The cache refresh URL used was 'http://sitecacherefresh.axd/?CacheToRefresh=Advertising <http://sitecacherefresh.axd/?CacheToRefresh=Advertising> '

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Commerce Server 2007 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Commerce Server 2007 installed before you apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you must restart IIS after you apply this hotfix. To do this, click Start, click Run, type iisreset, and then click OK.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File name	File version	File size	Date	Time
Microsoft.commerceserver.shared.dll	6.0.3757.0	219,968	27-Jun-2006	04:00