Log Entries Are Not Imported When LogOverlap Is Set to Discard and ContinueID: Q234775
|
Log entries may not be imported when you import log files from different log data sources if there are overlapping dates and if LogOverlap is set to discard and continue.
Setting LogOverlap to discard and continue does not take into account that log files may be from different data sources. Any overlapping entries are discarded.
A supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next Site Server service pack
that contains this fix.
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 on support costs, please go to the following
address on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later:
Date Time Size File name Platform
-------------------------------------------------------------
07/02/98 03:27p 913 Eula.txt Alpha
05/12/99 08:17p 1,303,824 Uas.exe Alpha
01/27/99 02:56p 80,144 Update.exe Alpha
04/16/99 01:29p 1,607 Update.inf Alpha
07/02/98 03:27p 913 Eula.txt x86
05/12/99 08:17p 675,872 Uas.exe x86
01/27/99 02:02p 62,544 Update.exe x86
04/16/99 01:29p 1,607 Update.inf x86
Q154871 Determining If You Are Eligible for No-Charge Technical Support
Microsoft has confirmed this to be a problem in Site Server 3.0.
A problem remains when you import to a single LDS in an unordered sequence. The schema does not support this functionality. A fix for this is being considered for a future version.
Additional query words:
Keywords :
Version : winnt:3.0
Platform : winnt
Issue type : kbbug
Last Reviewed: July 2, 1999