Hi, I'm trying to open up a Power Inroads file. It was working fine before. I've been getting this same message.
When I try to click continue, Power Inroads shuts down. I've rebooted my computer and even ran the Microsoft.Net Framework repair kit. Still no luck. How can I resolve this?
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************Bentley.ECObjects.ECObjectsException+ECXMLFormatError: Error while reading ECSchema 'Bentley_Civil__Model_Geometry.04.08' ---> Bentley.ECObjects.ECObjectsException+SchemaNotFound: The schema 'Bentley_Civil__Model_Geometry.04.08' references schema 'Bentley_Civil__Model_DTMFilterGroups.04.08', but that schema cannot be located. ---> Bentley.ECObjects.ECObjectsException+ECXMLFormatError: Error while reading ECSchema 'Bentley_Civil__Model_DTMFilterGroups.04.08' ---> Bentley.ECObjects.ECObjectsException+SchemaNotFound: The schema 'Bentley_Civil__Model_DTMFilterGroups.04.08' references schema 'Bentley_Civil__Model_FilterGroups.04.08', but that schema cannot be located. at Bentley.ECObjects.XML.ECSchemaXmlReader.DeserializeSchemaReference(XmlTextReader reader, IECSchema parentSchema) at Bentley.ECObjects.XML.ECSchemaXmlReader.DeserializeSecondPass(XmlTextReader reader) at Bentley.ECObjects.XML.ECSchemaXmlStringReader.Deserialize(IECSchema schema) --- End of inner exception stack trace --- at Bentley.ECObjects.XML.ECSchemaXmlStringReader.Deserialize(IECSchema schema) at Bentley.ECObjects.XML.ECSchemaXmlStringReader.Deserialize() at Bentley.ECXAttributes.ECXAttributes.LoadSchema(IElementRef* schemaElementRef, ECXADgnFileLocateContext locateContext) at Bentley.ECXAttributes.ECXADgnFileSchemaLocater.LocateSchema(String schemaName, Int32 versionMajor, Int32 versionMinor, SchemaMatchType matchType, IECSchema parentSchema, Object context) at Bentley.ECObjects.ECObjects.LocateSchema(String schemaName, Int32 versionMajor, Int32 versionMinor, SchemaMatchType matchType, IECSchema parentSchema, Object context) at Bentley.ECObjects.XML.ECSchemaXmlReader.DeserializeSchemaReference(XmlTextReader reader, IECSchema parentSchema) --- End of inner exception stack trace --- at Bentley.ECObjects.XML.ECSchemaXmlReader.DeserializeSchemaReference(XmlTextReader reader, IECSchema parentSchema) at Bentley.ECObjects.XML.ECSchemaXmlReader.DeserializeSecondPass(XmlTextReader reader) at Bentley.ECObjects.XML.ECSchemaXmlStringReader.Deserialize(IECSchema schema) --- End of inner exception stack trace --- at Bentley.ECObjects.XML.ECSchemaXmlStringReader.Deserialize(IECSchema schema) at Bentley.ECObjects.XML.ECSchemaXmlStringReader.Deserialize() at Bentley.ECXAttributes.ECXAttributes.LoadSchema(IElementRef* schemaElementRef, ECXADgnFileLocateContext locateContext) at Bentley.ECXAttributes.StoredSchemaInfo.LoadSchema() at Bentley.ECXAttributes.ECXAttributes.DiscoverStoredSchemas(DgnModelRef* rootModel, Int32 modelIterationMask, Int32 modelIterationDepth, IList`1& outWarnings) at Bentley.ECXAttributes.ECXAttributes.EnsureThatSchemaDiscoveryHasBeenCalled(DgnCache* dgnCache) at Bentley.ECXAttributes.ECXADgnFileSchemaLocater.LocateSchema(String schemaName, Int32 versionMajor, Int32 versionMinor, SchemaMatchType matchType, IECSchema parentSchema, Object context) at Bentley.ECObjects.ECObjects.LocateSchema(String schemaName, Int32 versionMajor, Int32 versionMinor, SchemaMatchType matchType, IECSchema parentSchema, Object context) at Bentley.ECXAttributes.ECXAttributes.LocateSchema(IntPtr dgnCacheP_as_IntPtr, Boolean useSharedSchemaCache, String schemaName, Int32 majorVersion, Int32 minorVersion, SchemaMatchType matchType) at Bentley.DGNECPlugin.ECRelationshipBlockXAttributeHandler.GetOneBlock(ElemHandle* elemHandle, XAttributeHandle* curr, Dictionary`2 dictionaryOfCaches) at Bentley.DGNECPlugin.ECRelationshipBlockXAttributeHandler.GetAll(Dictionary`2 dictionaryOfCaches, ElemHandle* elemHandle, XAttributeIter* curr) at Bentley.DGNECPlugin.ECRelationshipBlockXAttributeHandler.GetAll(IElementRef* elRef) at Bentley.DGNECPlugin.RelationBlockSetCacheRegistry..ctor(IElementRef* elRef) at Bentley.DGNECPlugin.RelationshipData.GetRelationBlockSetCacheRegistry(IElementRef* elRef) at Bentley.DGNECPlugin.ECXRelationshipsManager.TryGetRelationsEnumerables(IEnumerable`1* relationEnumerator, IElementRef* elRef) at Bentley.DGNECPlugin.ECXRelationshipsManager.TryGetAllRelationAccessors(IEnumerable`1* relationEnumerator, IElementRef* elRef) at Bentley.Civil.Model.MSPlugIn.?A0xbd7f1969.hasRelationshipsBackPointers(EditElemHandle* eh) at Bentley.Civil.Model.MSPlugIn.ElementsToProcess.FillFromCache(ElementsToProcess* , DgnCache* dgnCache) at Bentley.Civil.Model.MSPlugIn.ElementsToProcess.Process(ElementsToProcess* ) at Bentley.Civil.Model.MSPlugIn.ModelManager.ProcessAffected() at Bentley.Civil.Model.MSPlugIn.AddIn.ProcessAffected(String unparsed) at Bentley.Internal.MicroStation.CoreHook.DispatchNoHandler(UInt32* argStack, UInt32 mysp, IntPtr pFunc) at Bentley.Internal.MicroStation.CoreHook.Dispatch(UInt32* argStack, UInt32 mysp, IntPtr pFunc)************** Loaded Assemblies **************
The unfortunate truth is that these .NET Framework errors in the SS10 generation products and older have seldom proven useful to actually troubleshoot file corruption. This is likely something else entirely that is causing your troubles. What changed recently with your file? Was a reference attachment added? Was an existing reference attachment deleted? Most likely what you’re seeing is a broken relationship within the file that cannot be resolved due to missing or damaged data.
If you can sleuth this out and restore the missing data, you might be in luck. However, it might be that your best course of action is to recover a backup copy of all data and resume from that point.
HTH
-John
OpenRoads Designer 2021 Release 2 | ProjectWise CONNECT 3.453
A few things to test:
However, I have also had files that became corrupted and had to manually rebuild them. These files were corrupted to the point that opening them crashed the system. All I could do was reference them into a new file and use them as a guide while I rebuilt the files.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
If you do not receive a "Newer Civil Data Found" message when attempting to open this file, it is possible that one of attached References is of the CONNECT Platform format (ex. Civil Data has been upgraded to OpenRoads Designer CE 2022 Release 1 schema). You could run the Civil File Manager tool from OpenRoads Designer to check these Files (to identify Civil Schema Version), without opening them to check.
Matthew Kovach
Design Systems Administrator
ProjectWise Explorer CONNECT Edition, Version 10.00.03.453
ProjectWise Drive 2022.1, Version 2022.1.638.0
OpenRoads Designer CE 2021 Release 2, Version 10.10.21.04
OpenRoads Designer CONNECT Edition, Version 10.09.00.91