Error message after importing project

Hi,

I got following error message when retrieving project #1 from backup:

Import completed successfully, I can see the project but some unexperienced behavior occurs while trying to access some pages (promis.e exiting without error messages). But most of the pages looks OK.

Project #2 imported without errors.

Both projects was created on other computer with 12.137 version. On the target computer also 12.137 is installed.

Regards
Wojtek

Parents
  • Please find the related wiki article from the given link to solve the error. Please let us know whether it helped you or not. communities.bentley.com/.../20890.exception-thrown-when-opening-a-page-transaction-log-is-full


    This is a test

  • No, it did not. I have created database backup, but I couldn't precisely follow that instruction: https://msdn.microsoft.com/en-us/library/ms179478(v=sql.120).aspx . I am not able to change recovery mode to FULL or BULK_LOGGED. I have only SIMPLE and it's greyed out. Also I can't find any things related to Transaction log at that point.

    I have tried creating new database (promise3) using a script provided, connect it to Promis.e (succeed) and import that project to new database, but the same error occurs.

    Also I have noticed that on source computer different languages were set: Polish_CI_AS and Danish_Norwegian_CI_AS on a target. When creating new database promise3 I have added 

    ALTER DATABASE promise3 COLLATE Polish_CI_AS
    GO

    to have the same collate on both computers, but it also didn't help.

    When I try to rebuild database on that project, I can see some errors but the process is going on, and suddenly on one page promis.e exits without error message.

    The other project recovers successfully.

     Regards
    Wojtek


  • From the Compatibility Chart: "promis.e is currently only certified on English SQL Server versions, even for versions of promis.e localized for other languages. The SQL_Latin1_General_CP1_CI_AS collation is recommended."  But I don't know that your problem is related to collation or SQL Server at all. It seems like it is not related if one project from the same SQL Server restores fine.

    Unknown said:
    When I try to rebuild database on that project, I can see some errors but the process is going on, and suddenly on one page promis.e exits without error message.

    I'm not sure if you are rebuilding the source project or the restored project. I would try rebuilding the source project. If that fails on a certain page, then focus on that page, perhaps try Update Page and Validate Page on it to fix or reveal the problem, although I expect those tools might fail with the same error message too.

    Another approach would be to copy the source project and make a backup of the copy. If the copy is successful and the backup restores without issue, great. If the same error message occurs, then you can delete a suspect page from the copy and make a new backup. If that eliminates the error message on restore you could start with a fresh copy of the project and then start deleting items off the problem page until the problem item is found. Or you could choose to redraw the page.



Reply
  • From the Compatibility Chart: "promis.e is currently only certified on English SQL Server versions, even for versions of promis.e localized for other languages. The SQL_Latin1_General_CP1_CI_AS collation is recommended."  But I don't know that your problem is related to collation or SQL Server at all. It seems like it is not related if one project from the same SQL Server restores fine.

    Unknown said:
    When I try to rebuild database on that project, I can see some errors but the process is going on, and suddenly on one page promis.e exits without error message.

    I'm not sure if you are rebuilding the source project or the restored project. I would try rebuilding the source project. If that fails on a certain page, then focus on that page, perhaps try Update Page and Validate Page on it to fix or reveal the problem, although I expect those tools might fail with the same error message too.

    Another approach would be to copy the source project and make a backup of the copy. If the copy is successful and the backup restores without issue, great. If the same error message occurs, then you can delete a suspect page from the copy and make a new backup. If that eliminates the error message on restore you could start with a fresh copy of the project and then start deleting items off the problem page until the problem item is found. Or you could choose to redraw the page.



Children
No Data