« previous next »
Pages: [1]

Author Topic: XMI import problem  (Read 8935 times)

kayani

  • EA Novice
  • *
  • Posts: 10
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
XMI import problem
« on: July 18, 2007, 05:24:18 pm »
I'm trying to load a package from a large XMI file in EA but it inconsistently generates various error messages i.e. "DAO.Database[3035] System resource exceeded", "DAO.Database[3052] File Sharing lock count exceeded, Increase ...". When i load the package from several small XMI files (exported for sub-packages) it works fine but for complete package with a big XMI file it just crashes every time. Is there any maximum model or file size limit known in this scenario?
The problem persists in both 6.5 and 7 versions.
Logged

VK

  • EA Administrator
  • EA User
  • *****
  • Posts: 50
  • Karma: +0/-0
    • View Profile
Re: XMI import problem
« Reply #1 on: July 18, 2007, 07:35:59 pm »
Hi kayani,

Check if this solves your issue : http://support.microsoft.com/kb/q198633/

Cheers.
Logged

Giu Platania

  • EA User
  • **
  • Posts: 88
  • Karma: +4/-0
  • As Above so Below
    • View Profile
    • Linkedin
Re: XMI import problem
« Reply #2 on: February 23, 2018, 04:03:14 am »
hi,
I'm working a windows 10 machine with EA 13 installed and I have the issue of the XMI import of a 150 MB file.
I tried to modify the registry but the key
SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 4.0
described here
https://support.microsoft.com/en-ca/help/198633/you-receive-an-file-sharing-lock-count-exceeded-error-message-when-you

is not present on my system

idea?
thanks
Logged
Giuseppe Platania
Enterprise Architect
Door Business Consulting
+++
"As above so below, to accomplish the miracles of the One Thing" - Trismegistus
===
The above content reflects my own opinion and is not endorsed by Monthy Python
***
The above is NOT a reference to Monty Python

Giu Platania

  • EA User
  • **
  • Posts: 88
  • Karma: +4/-0
  • As Above so Below
    • View Profile
    • Linkedin
Re: XMI import problem
« Reply #3 on: February 23, 2018, 04:06:25 am »
BTW, the original model is on a SQL server, what I'm looking for is to have a "portable version" of it, this is why I need an EAP file.
Logged
Giuseppe Platania
Enterprise Architect
Door Business Consulting
+++
"As above so below, to accomplish the miracles of the One Thing" - Trismegistus
===
The above content reflects my own opinion and is not endorsed by Monthy Python
***
The above is NOT a reference to Monty Python

VKN

  • EA User
  • **
  • Posts: 187
  • Karma: +9/-1
    • View Profile
Re: XMI import problem
« Reply #4 on: February 23, 2018, 10:21:37 am »
If you don't have that key present in the registry then create it and try the import again.
Logged

hd

  • EA Administrator
  • EA User
  • *****
  • Posts: 312
  • Karma: +0/-0
    • View Profile
Re: XMI import problem
« Reply #5 on: February 23, 2018, 02:51:55 pm »
I think you'll find the key in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\...
Logged

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13404
  • Karma: +567/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: XMI import problem
« Reply #6 on: February 23, 2018, 03:33:13 pm »
Quote from: pgiuseppe on February 23, 2018, 04:06:25 am
BTW, the original model is on a SQL server, what I'm looking for is to have a "portable version" of it, this is why I need an EAP file.
In that case you are better off using model transfer.
Much faster and less error prone then xmi import/export.

Geert
Logged

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8607
  • Karma: +257/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: XMI import problem
« Reply #7 on: February 23, 2018, 05:25:09 pm »
Quote from: Geert Bellekens on February 23, 2018, 03:33:13 pm
Quote from: pgiuseppe on February 23, 2018, 04:06:25 am
BTW, the original model is on a SQL server, what I'm looking for is to have a "portable version" of it, this is why I need an EAP file.
In that case you are better off using model transfer.
Much faster and less error prone then xmi import/export.

Geert
+10  We snapshot our corporate repository using project transfer every night.  A 600Mb output file takes about 10 mins.

Paolo
Logged
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

eberline

  • EA User
  • **
  • Posts: 40
  • Karma: +1/-0
    • View Profile
Re: XMI import problem
« Reply #8 on: October 23, 2018, 09:11:45 am »
Although the Microsoft support article doesn't mention it, I needed to restart Windows before the larger MaxLocksPerFile value seemed to take effect. Once I'd done that, all good. FWIW.

(I was getting those pesky DAO errors pasting a diagram.)
Logged
Pages: [1]
« previous next »