One of the powerful features in erwin is its ability to export/import to and from an External file using the embedded MetaIntegration Mapping Bridge (MIMB). This document is to cover the steps to troubleshoot the basic problems and should help in understanding and resolving them.
First, how MIMB uses this bridge? MIMB basically does mapping between erwin and an external file format. It does so by converting the file in XML format. During export, it converts an erwin file to a XML file and then maps it an XML file compatible with the external file format selected in the Destination tab. During import also, it does the same by converting the external file format to XML, mapping it to the XML format that erwin will accept and then importing that XML file to create an erwin model. This conversion from/to an erwin model to erwin supported XML uses two DLLs that are provided with erwin install. These are:
These DLLs are registered during the install but in some cases (generally privileges related) they may not be. So, if MIMB is not responding as expected, the first part is to make sure that these two aforementioned DLLs are registered. Both these DLL files are in the folder where erwin is installed. You can register these by highlighting the file, Right Mouse Click and open it using REGSVR32.EXE in C:\Windows\SysWOW64 (for Windows 7, Windows 10 – it may be in some different location for other OS). You can also register them using DOS prompt - make sure that the DOS (or Command) prompt is launched as an Administrator. You will need to register them one at a time. Once these two DLLs are registered MIMB should be available to work.
Once that is set up, the following are some other factors to consider:
Exporting from erwin to an External File:
The following will need to be checked to diagnose the problem during export of a model:
- Make sure the model is exported, is saved. It will prompt one to save the file before the wizard even launches.
- If it is a model specific issue -- To verify if it is file related, simply create a new model with just one or two Tables and a few Columns, save it and try exporting that. If that works then it is model related and the problematic model will need to be looked into.
- If even a new file does not work, it may be a problem with the Export parameters, check those to make sure that all required parameters are entered as required. The resultant log file may also be helpful in determining the problem.
Importing from an External File into erwin:
- It is not related to the file being imported. To verify this, simply export a simple model to that format and then try importing that file to see if it works. Also, make sure that the file being imported was created using the supported version of the application selected as Source.
- If importing from a Repository, please make sure that the required parameters are entered correctly. This may include the database, connection login, instances, directories or other similar application specific parameters.
What if it still does not work?
In some extreme cases, the bridge parameter may become compromised (too many failed attempts or something similar). To remedy that, delete the folders containing those parameters in Registry as follows:
The Registry entry mentioned above is located at:
You can also delete the ERwinMetaIntegration folder which has both, Import Destination and Import Source as well as Export Destination and Export Source parameters. In the screenshot above you do not see any Export related folder because no Export has yet been attempted from this install of the application. These folders are created when the Export and/or Import is used. So, when you delete the folder, it will be recreated the next time you use this functionality.
Import worked without any errors but no objects are displayed:
This is as expected. After a successful import, the objects are brought in the model but are not associated with any Diagram or Subject Area (SA). To check this, go to Model Explorer and see if there is (+) sign before the Class of Objects (e.g. Tables). Expand that to see if you see the tables in Model Explorer. If so, then simply add them to any Diagram as needed or create a new Diagram and select the ‘Auto Populate’ checkbox to bring in the objects into that Diagram. You may also select all and then use one of the options for available layouts as an import from MIMB does not manage the display. It will need to be done using the functionality in erwin.
This should resolve most basic issues regarding using MIMB but if the problem still persists, please contact Technical Support.