Err Msg: Runtime Error '6': Overflow

Izjava o odricanju odgovornosti za sadržaj o otpisanom proizvodu u bazi znanja

Ovaj je članak napisan o proizvodu za koji Microsoft više ne pruža podršku. Članak će stoga ostati nepromijenjen i više se neće ažurirati.


When you use the Import History Manager in Usage Import and there are more than 2,519 rows in the TBLInterseHistory table, the following error message occurs:
Run-Time error '6': Overflow
After you click OK, Usage Import shuts down.


During this process, there is a signed integer variable used for indexing. When the number of rows in the TBLInterseHistory table exceeds 2,519, the index exceeds the maximum allowable value for a signed integer (32767 or 7FFF Hex).


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 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 Size File name Platform
08/24/1999 8:17PM 2,259,968 UImport.exe (Access) x86
08/24/1999 8:17PM 2,442,240 UImport.exe (SQL Server)

08/24/1999 8:17PM 2,822,656 UImport.exe (Access) Alpha
08/24/1999 8:17PM 3,019,264 UImport.exe (SQL Server)


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

ID članka: 239933 - posljednja izmjena: 19. lip 2014. - verzija: 1

Povratne informacije