I am doing some work around worksharing and I am being proactive about detecting that state of the workset and the local file. There is one situation that I have not been able to nail down. I am using the ModelUpdatesStatus, but is does not include a status for 'Central File Missing'. It reports 'Current with Central' when disconnected from the Central File, which is misleading.
We are catching the Exceptions caused by checking out worksets when there are issues with the central file (e.g. CentralModelException, CentralFileCommunicationException), but we want to know before we try.
Is there a way to get the status of the central model or the connection to the central model, or to infer it from other data (like the model path), so that we can know when the central model is inaccessible?
Dear Jesika,
Thank you for your query.
I submitted the wish list item CF-2161 [API: ModelUpdatesStatus Enumeration lacks 'Central File Missing'] on your behalf for the functionality you suggest, as this issue requires exploration and possibly a modification to our software. Please make a note of this number for future reference.
Cheers,
Jeremy
FYI - This also throws the CentralFileCommunicationException exception:
Dim workSetInfo As IList(Of WorksetPreview) = WorksharingUtils.GetUserWorksetInfo(modelPath)
Each of these can be (minimally) checked for by searching for the file returned by BasicFileInfo.CentralPath
Dear Matthew,
Thank you for the info.
I added it to the wish list item CF-2161 [API: ModelUpdatesStatus Enumeration lacks 'Central File Missing'].
I have not heard anything from the development team on it yet, though.
Cheers,
Jeremy