Messages

1

Automation Interface, Add-Ins and Tools / MDG Link Doors fails with error ExportDoorsData.xml not found

« on: March 01, 2023, 06:32:45 pm »

Hello everyone,

we are trying to use the MDGLink to update doors objects to our Enterprise Architect model. The import fails all the time with the message mentioned below, which I got from the log file.

EA15.2, 1560
MDGLink 3.0.301
DOORS 9.7

Does anyone know the root cause of this issue or can support me in analyzing it?
Thank you very much

Code: [Select]

2023-02-28 16:51:02
Message:
The file "C:\Users\...\AppData\Roaming\Sparx Systems\EADoors\ExportDoorsData.xml" was not found
Source:
mscorlib
InnerException:

StackTrace:
   bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   bei System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   bei System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   bei System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)
   bei System.IO.File.InternalReadAllText(String path, Encoding encoding, Boolean checkHost)
   bei System.IO.File.ReadAllText(String path)
   bei DoorsEASync.DoorsEAClass.readDoorDataXml(DataTable ObjDetailsInDoors, DataTable ObjLinksasEAConnectors, DataTable DTObjectExternalReference)

2

Automation Interface, Add-Ins and Tools / Re: Error "Import Objects failed due to invalid Properties in the profile" Doors imp

« on: February 27, 2023, 07:37:09 pm »

Hello,

we are facing the same issue. Not only for "/" character, but also for "@". The interface does not escape it and will fail with the same error message. We see it as a bug and opened a bug report.

Thanks AFernandez for pointing out the error log file path.