Project Corruption?

Hi,

I have an issue where navigating to an older project (~1 year old), is currently showing pages of a recently completed project. 

A couple of key points to note / things ive spotted;

  • All pages are correct and present within the old project (viewable in explorer).
  • The ect.fid file for the older project is showing the quid as "dc4e6bcb-edd5-4654-9f6a-002b132db044". This is the SAME quid as listed in the ect.fid file for the newer project.
  • Looking in SQL management studio, the quid for the older project is listed as "dc4e6bcb-edd5-4654-9f6a-002b132db044"
  • Looking in SQL management studio, the quid for the new project is listed as "98e3cc77-4be2-4327-8bba-a52a529ee2d6"
  • If I update the quid in the ect.fid file of the newer project to match "98e3cc77-4be2-4327-8bba-a52a529ee2d6", the project has a red warning symbol over it within project manager and is not viewable.

Can anyone offer any help on what might the issue be?

Kind Regards

Parents
  • Hi Adam,

    Were both the projects, the old one as well as the new, created by restoring from a same project backup .prj file? Or was the new project created by copying pages from the old project into the new one?

    Regards,
    Sarvesh Kulkarni
    Product Engineer - Bentley Systems

  • I believe there is a high possibility that the user may have copied the older project to use as the newer project, however the user cannot recall exactly.

    There has been some confusion around the correct projectproperties file to use, so my suspicion is that the projectproperties file was copied from older project to newer project. At the same time, I think the user may have copied the ctd.fid file?

    This isnt confirmed, but it sounds likely to me?

  • Hi Adam,

    As you have mentioned that it might be due to the reason that user might have copied the ECT.fid file. But if the user is trying to Copy the Old Project Pages to New Project Page then they can copy the pages in Promis.e Project Manager which will make sure that the user doesn't copy ECT.fid file by mistake, the steps for the same can be followed in the below Wiki Link.



    Also you can select the required Project Option for a Project while creating and then copy Project pages in Project Manager which will be the correct work flow. Below is Wiki Link for Project Option.



    Regards,
    Satish Saptasagar

  • Hi,

    I have re-iterated the above to the engineer thank you.

    But do you have any suggestions for linking our older project back to the original project?

    Regards

  • Hi Adam,

    I was able to recreate your scenario by copying the ect.fid file from one project folder into another. I resolved the issue by changing the guid back to its original value in the ect.fid file of the affected project and also by matching the Project Id in ect.fid file with the one in the database.

    To elaborate on the solution, I had a project named GUID_COPIED in which I had copied the ect.fid file from another project. I changed the guid for this project in the ect.fid file as what was present in the database. Then I checked the Project Id in the database for this project and then changed the value in ect.fid file with the one in the database.



    In the database the Project Id was 1023. So, in the ect.fid file change the first line to have the Project Id as 1023.



    Regards,
    Sarvesh Kulkarni
    Product Engineer - Bentley Systems

Reply
  • Hi Adam,

    I was able to recreate your scenario by copying the ect.fid file from one project folder into another. I resolved the issue by changing the guid back to its original value in the ect.fid file of the affected project and also by matching the Project Id in ect.fid file with the one in the database.

    To elaborate on the solution, I had a project named GUID_COPIED in which I had copied the ect.fid file from another project. I changed the guid for this project in the ect.fid file as what was present in the database. Then I checked the Project Id in the database for this project and then changed the value in ect.fid file with the one in the database.



    In the database the Project Id was 1023. So, in the ect.fid file change the first line to have the Project Id as 1023.



    Regards,
    Sarvesh Kulkarni
    Product Engineer - Bentley Systems

Children
  • Hi Sarvesh,

    I have updated the ect.id file, so in both projects, the ID and the GUID matches.

    However, both projects are incorrectly displaying the wrong pages in project manager, i.e

    Old Project is showing 5 pages which is from new project and new project is showing 30+ pages which should be in the old project (note previews are not available, I think its just confused somewhere).

    Is there somewhere else in the database the ID or GUIDs are being used?

  • Adam,

    Project Id is used in other tables besides dbo.Project such as in dbo.Page table. I believe we can expedite the process to resolve this issue by having a screen sharing session. Let me know your thoughts on the same.

    Also, please provide your direct contact details so that we can get in touch with you.

    Regards,
    Sarvesh Kulkarni
    Product Engineer - Bentley Systems

  • Hi Adam,

    Thank you for the live meeting. We were able to resolve your issue by exchanging the values of guid in the dbo.Project table and project_id in the dbo.Page table.

    We will create a Wiki Article that can be referred by anyone facing this scenario.

    Regards,
    Sarvesh Kulkarni
    Product Engineer - Bentley Systems

  • Many thanks again for your help Sarvesh.

    For anyone else we appeared to have some discrepancies around the project id, located within the dbo.project and dbo.page.

    To confirm;

    • The first line on the ect.fid located within the project is the "Project id". This needs to match the "project id" listed within the database within the table "dbo.project".
    • The 7th line is the guid, which also needs to match the "guid" listed within the database within the table dbo.project
    • The project id also needs to be correct within the database table "dbo.page". For some reason, our pages had crossed over and had an incorrect project id assigned to them. Once we updated to the correct project id, this resolved the issues.