Arp V2 and XP

[apettinotti_(Guest)]

i realize that we are using a very out-dated version of apreggio, but we^re stuck with it for at least another 6-10 months, and thus i^m hoping that someone out there might have some insight into our latest issue...____the reports reside on a Win 2k server__workstations are XP professional (some with sp 1, some w/out)____starting approx 3 weeks ago, we started having issues of arpeggio reports becoming corrupted. the scenario seems to be when one has opened and closed the same report more than about 5 times (but up to as many as 16x) on a given day, the report suddenly becomes corrupted and the user recieves the highly informative error, "ARpeggio report designer has encountered a problem and needs to close. We are sorry for the inconvience" then arpeggio closes and one gets a "memory could not be read" error.____after that point, when ANYONE from ANY workstation tries to open that report, arpeggio crashes before one is even prompted to logon to the database, UNLESS you change the ODBC datasource from what is saved with the report, then you DO get to log in, it hangs for more than usual and then prompts you AGAIN to log in only this time to the datasource that was saved with the report and THEN it gets the very informative error followed by the memory error again.____the only solution is to restore the report from tape. which we keep doing. but we^re pretty dynamic about changes to our reports and so we^ve lost more than several hours of work because of this problem...____anecdotally, it seems to be happening more and more frequently as time goes by (ie - once three weeks ago, twice last week, 3 times TODAY)____my network admin guys tell me that they haven^t made any changes to the environment for at least a few weeks before this started happening.____any clues? suggestions?____thanks,__ariel

[kfleming]

[updated:LAST EDITED ON Apr-01-03 AT 10:27 PM (EST)]It may not help at all but try adding a section called Database to your RSW.INI file and in that section add a line that says:__UseQEConnect=1____Also-have you looked at the thread "File Already in Use" on opening reports on 2000 servers using an XP workstation. Several people are seeing locked reports and I wonder if your problem is at all related?____Kathleen__R&R Support

[apettinotti_(Guest)]

thanks, kathleen,__i^ll try adding that setting and see if it helps. i did scrutinize the file locking threads you mention and checked on our server to see if the files having the problems are locked and they are not so i think the issue isn^t related.____one interesting additional fact that i just discovered this morning in a flailing attempt to find a solution (since our backups have failed, it turns out, the last 4 nights and i^m loosing over 8 hours of work that i had done on the latest corrupted report) is that even tho^ the report continues over and over to cause the same error on ANY xp workstation (even after reboot), if i mosey on over to an NT workstation, i can open and print it FINE.____what does THAT mean?????____that solves MY problem since i just happen to have an NT workstaion in the cubicle behind me, but the 50 other people in my office who dependend on these reports for their daily job functions aren^t so lucky... *sigh*

[apettinotti_(Guest)]

while i^m not 100% that there was cause and effect since this problem is so strange, i must report apparent success. unfortunately, i broke the rule of trouble shooting and did two things at once so i don^t know which (if any) actually fixed the issue.____as i posted above, i opened and printed the report from an NT machine. then i saved and closed it. next i added the section [database] and the line UseQEConnect=1 to my rsw.ini on my xp machine and i am now able to open & print the "corrupted" report with no problem.____i then ran over to another xp workstation (the one which has "corrupted" the most reports, btw, and where i have NOT made the rsw.ini change) and tried to open & print the report in question: worked fine. THEN, i tried to open my other - untouched by NT and presumably still corrupted - copy of this same report from her machine and IT opened fine too...____mystery continues, but at least the view brightens for the moment. ;)