Frame 7 to Frame 10 occasionally crashes
Mon, 07/30/2012 - 11:28am — randallgaz
Hello,
We are doing an automation project with frame 7 sources, but using frame 10. We occasionally get frame crashes with a DCLError popup, but then it often then continues to work. That error can't be trapped, so an admin needs to remote into the server to clear the popup.
I have seen a few messages on the adobe forums about this. Is this common, and is the solution to get the sources upgraded/washed_via_mif up to the frame 10 format?
Thanks
FM 7 in FM 10
We need a bit more info. Just what does the error say? What does _m2g_log.txt show? Any messages in the Frame console window? There are many possible issues.
If you are planning on using the Frame 7 files in Frame 10, it makes sense to convert them to Frame 10 first. You do that just by opening them in Frame 10, then saving them again. Mif2Go isn't involved. If you have any problem then, you know it is with Frame. Remember, you can open and save all files in a book in one shot from the Shift-File menu.
If you want to try Wash via MIF, do it on the new Frame 10 files.
If that works, then do your Mif2Go conversion, whatever it is to, using your new Frame 10 files. If you have a problem then, we'll need a test case to diagnose it; see the User's guide appendix on tech support for exactly what we need. Basically, it's the Frame files, the .mif (VERY important!), the .inis, the .prj, and all outputs including the log, all in one .zip. We need to be able to reproduce the problem here to fix it.
If you are running a book, and one file causes a crash, you can tell Mif2Go to proceed; it will continue with the next file. In that case, the failed file may not have a MIF file, or may not have the expected output, and may have a .dcb file left behind. For that, we'd want the .fm, .mif, and definitely the .dcb (along with the .inis and .prj).
HTH!