FIX: A Web Log Import Is Unsuccessful While Processing Hits from Multiple Logs (813728)



The information in this article applies to:

  • Microsoft Commerce Server 2000
  • Microsoft Commerce Server 2000 SP3

SYMPTOMS

Occasionally, a Web log import is unsuccessful while it stitches hits from multiple logs. A hit that has a long referrer in place will result in a lost hit count.

Note If you import the Web logs individually, you do not experience any lost hits.

RESOLUTION

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 Commerce Server 2000 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: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. The English version of this fix has the file attributes (or later) 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 tool in Control Panel.
   Date         Time   Version      Size    File name
   --------------------------------------------------------
   12-Feb-2003  22:36  4.0.3861.0  536,848  Cdtstasks.dll 
				

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:10/11/2005
Keywords:kbHotfixServer kbQFE kbfix kbbug KB813728 kbAudDeveloper