![]() |
Telelogic System Architect (steve huntington) | ![]() |
Topic Title: Running reports in multi-user environment Topic Summary: Recently, we've been getting db error dialog boxes when running a report and other users are editting Created On: 17-May-2007 22:42 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Since 2003, we've been running reports mostly at night, but many times during the day while others are editting. It wasn't til recently that while running reports that we began to encounter:
message box: database error: 7100, codes: 4, 1206, 137 message box: database error: 7101, codes: 4, 4407, 137 - [ happens 8 times] then repeats for each row it doesn't like when writing the report temp NDX files. (((On 6/2006, we moved to SA 10.3 and have been on since then (looking to go to SA 10.7 soon) - it wasn't til recently this started happening. We've always been on SQL Server 2k and on windows OS) Thoughts? (We have a ticket in, but we're struggling together trying to figure it out) |
|
![]() |
|
![]() |
|
Worth adding, the old documentation on reporting engine for SA 8.x is the following, but we don't know how that is related to SA 10.3 and up on SQL Server 2000. We supposedly have plenty of free space in our MDF and LDF : Errors in the 7000 range occur during reporting. Reporting goes through two |
|
![]() |
|
![]() |
|
looks likely to be disk space as our c drive was dangerously low (our data drive had plenty of room which was confusing). Reports write temporary NDX/etc. files to the C drive based on the SA v8 architecture, and it couldn't write its NDXs so, for each remaining row it was attempting to write, it created the 9 errors.
|
|
![]() |
|
![]() |
|
Did freeing some space up fix the problem?
Thanks Ian ------------------------- Senior Software Developer Telelogic UK Ltd. |
|
![]() |
|
![]() |
|
Hi Ian Yeah, this was part of it. There were several other issues that this caused and we created a checklist of things to check now on crashes. Turns out anti virus and backup jobs were causing a dump at night eating up the Hard drive space. |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.