From time to time an InfoMaker report will crash Tessitura with the attached message. Opening it in InfoMaker itself will cause a similar crash. A regenerate within IM fixes this.
These used to come up once or twice a year, but for some reason these "corruptions" are popping up more often recently, and I am wondering if anyone knows what exactly is happening here, and if there is anything that can be done to prevent it?
Thanks.
Tessitura 10.0 and 10.0.0.1 use Infomaker 10.5.1 (build 6021 I think). You might look into finding the 10.5.1 maintenance release, if you are just running Infomaker 10.5.
-Ryan
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Chris JensenSent: Thursday, January 13, 2011 12:37 PMTo: Ryan CrepsSubject: [Tessitura Technical Forum] Corrupt InfoMaker reports?
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Thanks for your reply, Ryan. We are running 10.5.1 Build 6021 here, though.
One thing I've found helpful is to create a new blank .pbl and copy your existing datawindows into the new library (just drag and drop via the Library Painter). Then switch the names so the corrupted one is your production library.
Thanks for your reply, Brian. My usual practice has been to drag the offending report into a special "fix_reports" pbl, do the regen there, then drag it back to the production pbl, overwriting the corrupt original. Do you think renaming the original rather than overwriting would be better?
Sometimes it's the library itself that's the problem, so copying the reports back into it won't necessarily solve the issue, no matter what the name. That's why I recommend creating a fresh library and moving all the objects over as an initial step. If you want to continue your current practice, though, I can't see what difference it would make to bring the report back in under a new name vs. overwriting it.
Thanks for the suggestion. A few days ago I Optimized the Live pbl, and haven't had a crashy report crop up in the short time since (knock wood). Next time this occurs, I'll try your method first.