Microsoft KB Archive/250829

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


Usage Import Reports Ad Log Placement Incorrectly

Article ID: 250829

Article Last Modified on 10/6/2005



APPLIES TO

  • Microsoft Site Server 3.0 Standard Edition



This article was previously published under Q250829

SYMPTOMS

Usage Import reports Ad Placement incorrectly. Ad Placements are reported, but some Ad Placement Request counts are inaccurate because a small number of ads are appearing incorrectly as Unknown Placement Titles.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Site Server 3.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical 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 should have the following file attributes or later:

   Date      Time    Version       Size       File name    Platform
   ----------------------------------------------------------------
   2/3/2000  8:00    7.0.1294.0    676,366     Uas.exe        x86
   2/3/2000  7:59    7.0.1294.0  1,308,432     Uas.exe       ALPHA
                



STATUS

Microsoft has confirmed that this is a problem in Site Server 3.0.

Keywords: kbbug kbfix kbqfe kbhotfixserver KB250829