Project not in database

A project in my folder was copied for someone else to work on and somehow they remained linked meaning that when he deleted his copy it also deleted the original. Within project manager it now says the project is not found in the database. The pages are still there via windows explorer and can still be opened but not via project manager. Our IT system does have a back up but rather than restoring the whole database I was wondering if anyone can tell me which part of the database is causing this problem so we can just restore the relevant parts?

Parents
  • I'd just like to add to what Tani wrote and say that you could restore the database backup to a new name to avoid disrupting work on other projects. After connecting to this temporary database on promis.e Setup you should then be able to access the problem project and back it up using Project Manager. Then connect to the production database on proms.e Setup and restore the project backup.



  • @Matt / Tani,
    If I've understood the SS8 changelog correctly, I believe Promise SS8 can import 'orphaned' promise files and rebuild the intelligence. I don't know to what limits but in theory could this user import the latest copy of their files for it to rebuild intelligently?

    SS8 Notes:

    • The Import Drawings command in the Project Manager is now able to import an orphaned Promis.e DGN file and rebuild the intelligence of the drawing upon import. You can now import DWG files as well. Some additional UI enhancements were also done to improve the usability of the tool.
  • Using Import Drawings would be a last resort. Rebuilding intelligence from only drawings means pending changes (changes due to occur on pages when they are next opened based on new information in the database) are lost. This in turn can result in discrepancies between pages. Ideally the solution is to restore a database backup and project folder backup that were made at roughly the same time. But yes, in SS8 pages that result from Import Drawings have some recovered intelligence, at least if they originated in promis.e/Bentley Substation in the first place.



Reply
  • Using Import Drawings would be a last resort. Rebuilding intelligence from only drawings means pending changes (changes due to occur on pages when they are next opened based on new information in the database) are lost. This in turn can result in discrepancies between pages. Ideally the solution is to restore a database backup and project folder backup that were made at roughly the same time. But yes, in SS8 pages that result from Import Drawings have some recovered intelligence, at least if they originated in promis.e/Bentley Substation in the first place.



Children
  • I think a database restore is potentially quite dangerous, depending on the number of other users and/or number of other projects that's been worked on since the restore.

    If the database is restored, I assume you'd either have to restore all files (from all projects) that have been worked on since the restore date or run a manual backup within promise on those projects and restore through promise after the database has been restored?

    p.s is there any news on the SS8 date? :)

  • Luckily for me at the moment there is only me and an apprentice working on it so we have done a full database restore but yes it would potentially cause a major headache if the whole department were using it.
  • Please see my May 6 response in this thread. I suggested restoring the database to a different name. This way it would not affect other projects because you would not be overwriting the production database. Hopefully you would have a backup of the project folder made at the same time as the database backup so that they are as in sync as possible. Once connected to the restored database in promis.e, you should be able to browse to the restored project folder in Project Manager (or the production project folder if that is all you have) and backup the project. Connect to the product database in promis.e, restore the project backup, and you can delete the temporary, restored project database. Going forward, all project and page operations should be done using Project Manager to avoid this situation, and periodically making your own project backups using Project Manager.



  • Matt, we would have done this if there were multiple users but as I knew nothing else would be affected we just decided to use the quickest route of a normal restore but it is useful to know for future if it was to happen again for any reason (hopefully it won't)

    Thanks
  • Today we had same issue as described above "Project not found in database". Im not entirely sure how it came around, I suspect something was accidently deleted/moved either via windows explorer or the project manager.

    For us the files were there, but we had the red warning symbol over the project stating "Project not found in database".

    Rather than restoring a backup of the SQL database, I created a new clean project, copied the existing pages from the broken project to a new folder on my desktop (only the pages, not the other files).
    Then within the new project (via project manager), selected File -> Import. After setting the page numbers and diagram type (schematic), the pages successfully imported are working fully, including all the cross referencing.

    This may not be the preferred method of restoring, but atleast it works (and works well!).

    Adam