• Replies 3 replies
  • Subscribers 338 subscribers
  • Views 48 views
  • Users 0 members are here
Related

infomaker pbl migration error

Dale Aucoin
$organization

I just installed Infomaker 12.1 and migrated a copy of our custom reports pbl.  All was fine except for 3 objects that gave me an error like this one:

C0159: Conversion of T:\User Reports\ud_roundabout_custom_reports-V11.pbl(ud_gl_summary_report.dwo) failed. Probable library file I/O error

Has anyone else encountered this.  I'm having no luck finding anything on the Sybase forums or the web in general.


Thanks,
Dale 

Parents
  • $organization

    I’ve seen datawindows become corrupted in the past.  This can be through a variety of reasons, but most often due to an interruption during the save process.  Unfortunately, using Infomaker, you can’t see the underlying source of the object (nor do you probably want to).

     

    Using the previous Infomaker version on the un-migrated library, there are a few things you can try.  From the Library painter, you can right click on a library and select “Optimize” as a menu option.  For each datawindow, you can highlight (multi-select as well), right click and select Regenerate.  This might clean up a few issues prior to doing the migration.

     

    Probably by saving the report to the new PBL, the regenerate process happened in the middle of that.

     

    +Ryan Creps

    +Tessitura Network

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Dale Aucoin
    Sent: Thursday, August 02, 2012 11:02 AM
    To: Ryan Creps
    Subject: RE: [Tessitura Technical Forum] infomaker pbl migration error

     

    Thanks Ryan, I tried that as well but no luck.

    The good news is only one of the three reports that didn't migrate was actually in use (thank you Migration-Custom Report Run Frequency report) and we figured out two work arounds:

    1. I created a brand new infomaker report using the same stored procedure as the original object then copied the fields and formatting from the original report to the new report.  This only took a couple of minutes.  I then saved the report in the same PBL and re-migrated.  The new report migrated fine and works fine.

    2. We saved the original report that didn't migrate to its own PBL then migrated and it works fine.


    Dale

    From: Ryan Creps <bounce-ryancreps9649@tessituranetwork.com>
    Sent: 8/1/2012 7:17:02 PM

    Sounds like a network timing issue.  You might try redoing this migration using a copy of the library file local to the workstation running Infomaker.

     

    +Ryan Creps

    +Tessitura Network

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Dale Aucoin
    Sent: Wednesday, August 01, 2012 3:50 PM
    To: Ryan Creps
    Subject: [Tessitura Technical Forum] infomaker pbl migration error

     

    I just installed Infomaker 12.1 and migrated a copy of our custom reports pbl.  All was fine except for 3 objects that gave me an error like this one:

    C0159: Conversion of T:\User Reports\ud_roundabout_custom_reports-V11.pbl(ud_gl_summary_report.dwo) failed. Probable library file I/O error

    Has anyone else encountered this.  I'm having no luck finding anything on the Sybase forums or the web in general.


    Thanks,
    Dale 




    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!




    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!

Reply
  • $organization

    I’ve seen datawindows become corrupted in the past.  This can be through a variety of reasons, but most often due to an interruption during the save process.  Unfortunately, using Infomaker, you can’t see the underlying source of the object (nor do you probably want to).

     

    Using the previous Infomaker version on the un-migrated library, there are a few things you can try.  From the Library painter, you can right click on a library and select “Optimize” as a menu option.  For each datawindow, you can highlight (multi-select as well), right click and select Regenerate.  This might clean up a few issues prior to doing the migration.

     

    Probably by saving the report to the new PBL, the regenerate process happened in the middle of that.

     

    +Ryan Creps

    +Tessitura Network

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Dale Aucoin
    Sent: Thursday, August 02, 2012 11:02 AM
    To: Ryan Creps
    Subject: RE: [Tessitura Technical Forum] infomaker pbl migration error

     

    Thanks Ryan, I tried that as well but no luck.

    The good news is only one of the three reports that didn't migrate was actually in use (thank you Migration-Custom Report Run Frequency report) and we figured out two work arounds:

    1. I created a brand new infomaker report using the same stored procedure as the original object then copied the fields and formatting from the original report to the new report.  This only took a couple of minutes.  I then saved the report in the same PBL and re-migrated.  The new report migrated fine and works fine.

    2. We saved the original report that didn't migrate to its own PBL then migrated and it works fine.


    Dale

    From: Ryan Creps <bounce-ryancreps9649@tessituranetwork.com>
    Sent: 8/1/2012 7:17:02 PM

    Sounds like a network timing issue.  You might try redoing this migration using a copy of the library file local to the workstation running Infomaker.

     

    +Ryan Creps

    +Tessitura Network

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Dale Aucoin
    Sent: Wednesday, August 01, 2012 3:50 PM
    To: Ryan Creps
    Subject: [Tessitura Technical Forum] infomaker pbl migration error

     

    I just installed Infomaker 12.1 and migrated a copy of our custom reports pbl.  All was fine except for 3 objects that gave me an error like this one:

    C0159: Conversion of T:\User Reports\ud_roundabout_custom_reports-V11.pbl(ud_gl_summary_report.dwo) failed. Probable library file I/O error

    Has anyone else encountered this.  I'm having no luck finding anything on the Sybase forums or the web in general.


    Thanks,
    Dale 




    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!




    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!

Children
No Data