Connect Edition - Error issues

Hi All,

I am using GC CE (update 3) and keep getting errors occurring:

I have an existing file with a transaction script that works well. I copied this dgn and loaded a script from a saved GCT file, then modified my inputs to suit the new file. Everything works well and processes correctly until I close the file and reopen - then I get an error saying "Internal error - resource file not found" when the baseCS node is placed. What could cause this to happen? I am working on Projectwise, but loading the local workspace instead of using the PW managed workspace. I wasn't having this issue prior to updating to CE update 3, however that might be a coincidence.

Also, on another note I have had files crash on me previously, and throw an error "The given key was not present in the dictionary". No matter what I tried I could not repair the problem, as GC interface was not allowing any editing so I had to rebuild that file to get it working again.

If someone could please shed some light on what might cause these errors that would be great, as it gets pretty tiring having to rebuild files over and over again!

Thanks,


Edward

  • Hi Edward,

    It would be great to get the file that exhibits the first problem you describe causing the "Internal error - resource file not found" error.

    This error message is known to us from one case where it was being posted when a GC script was run placing ABD/BIM nodes with CatalogItems that are not defined in the currently active dataset.  This could happen for example when a GC script was developed in a US dataset and later is opened in the UK dataset.  However, this should be fixed in Update 3.  I tested that known case again and did not receive that error; however, the respective node showed an error that its CatalogItem input is invalid which is an accurate and helpful error message.  All the other nodes are generated as they should.  This would be the expected behavior.  There may be an indication of this when opening the file.  ABD posts a message when files come from a different WorkSet, which may mean that they are also based on a different dataset. 

    Another question I have is how you installed Update 3: was it a new install (after uninstalling the previous version), or was it executed as an update to Update 2?

    The second message "The given key was not present in the dictionary" occurs after a file has suffered from corruption.  It is a message from deep down in the dotNet Framework.  It is an indication that it may be too late for a remedy.  Submitting the file with a service request may still have a small chance of recovering its contents; however, it is a very small chance.  It would help us to know, if there are any patterns when this type of corruption occurs. 

    Regards,

         Volker

       

  • Hi Volker,
    I installed the update as an upgrade. I may need to completely uninstall by the sounds of it? 

    Good news is the file wasn't corrupt this morning when I opened it. I have an old copy though that still results in the error so I'll send you the download link through private message.

    I had a feeling that the second message meant it was beyond repair... fortunately that one hasn't came up too often! 

    Whilst on that subject of corrupt files; I have been making a conscious effort to constantly back up transactions scripts as a GCT file, however it would be a great feature to have this as an option to load/save a gct file associated with the dgn automatically on dgn file open/close. That way you would have the ability to check-in the transaction file separately on Projectwise, to maintain a full separate version history of the script (which is lightweight in size). You could store every session that way if it was deemed necessary. I was thinking of using the 'include-file' transaction type to achieve this, however that seemed to crash my system on initial testing, resulting in a corrupt file as described above.

    Thanks for the help,

    Ed

  • Hi Ed,

    This is a good suggestion. 

    Part of such mechanism has already been implemented: when a DGN containing GC script is opened, GC generates a *.~gt file that contains that script. This is a GCT file. If GC crashes, that *.~gt file hangs around and could be copied as a backup. Currently, GC will override it the next time the DGN is opened. Because that's when a user would notice any file corruption, more than one version of the *.~gt file would be needed to secure users against loss of work. We are considering an enhancement which would keep several copies around.

    Also, fortunately relatively often, GC transactions may appear to have vanished when opening files in succession in the same session. The occurrence of this seems to have increased with the update from CONNECT Edition Update 2 to Update 3. Exiting the application and starting it again, then opening the file very often will then show the "missing" transactions again. On my machine, after uninstalling the updated version 3 and clean new installation of ABD CONNECT Edition Update 3 with GC, this problem vanished. 

    Regards,

        Volker

       

  • Thanks Volker, I'll try uninstalling and reinstalling a fresh version of update 3 then; hopefully that fixes the issue.

    Cheers,


    Ed

  • Hi Volker,
    Just letting you know that I uninstalled then reinstalled GC & ABD (update 3); however I am still getting the 'resource file not found' error when copying an existing file and then opening it