Book a Demo

Author Topic: EA Crash by SystemAccessViolation by runReport  (Read 7011 times)

Stefan Bolleininger

  • EA User
  • **
  • Posts: 308
  • Karma: +0/-0
    • View Profile
EA Crash by SystemAccessViolation by runReport
« on: May 15, 2014, 04:44:47 pm »
Hi Guys,

Since my try to rollout EA11 i got a problem with some user installations. (It forced me to stop the EA11 deployment)

We are using a little Add-in to enhance the users komfort and decrease the Settings.
Within the Add-in the Command
Project.runReport(Packageguid, template, filename)
is commanded to run the report.

Now, everything wents fine until it comes up to this line.

The runreport ist startet, you will see the full Report-form.
After a short time(report is not started yet) the filename within the form vanishes and the EA crashes.

The problem within the WIN8-failurebox: "SystemAccessViolationException"

Happens with EA1105 and EA1106

The normal Report by using the "Generate Documentation" works fine.

What i currently found out: it is depended on the Windows-User. Some users didn't had that problems (unfortunately noone within my validation team had that problem) and others have if.

For example: My normal windows-user doesn't have if, but my second windows-login on the same Computer has this issue.

Any ideas?

Regards

Stefan
Enterprise Architect in "safetycritical development" like medical device industry. My free Add-in at my Website

Aaron B

  • EA Administrator
  • EA User
  • *****
  • Posts: 941
  • Karma: +18/-0
    • View Profile
Re: EA Crash by SystemAccessViolation by runReport
« Reply #1 on: May 15, 2014, 04:55:19 pm »
What parameters are you passing to RunReport()?  What are the template and filename values that you are passing in?  Does the user have permission to write to the location specified in the filename?

Stefan Bolleininger

  • EA User
  • **
  • Posts: 308
  • Karma: +0/-0
    • View Profile
Re: EA Crash by SystemAccessViolation by runReport
« Reply #2 on: May 16, 2014, 07:58:11 am »
The use has the write-permission. (e.g. it is his desktop.)

aproject.RunReport(packageguid,template,filename)

packageguid is a string
Template might be e.g. "System" or "Design"
filename might be any file on the desktop

Best regards

Stefan
Enterprise Architect in "safetycritical development" like medical device industry. My free Add-in at my Website

Stefan Bolleininger

  • EA User
  • **
  • Posts: 308
  • Karma: +0/-0
    • View Profile
Re: EA Crash by runReport
« Reply #3 on: May 21, 2014, 07:48:50 pm »
Within the problems investigation i didn't found any newer informations.

Even with the normal Documentation, which also drives the RTF-generator, this issue appears.

Any ideas?

Enterprise Architect in "safetycritical development" like medical device industry. My free Add-in at my Website

Stefan Bolleininger

  • EA User
  • **
  • Posts: 308
  • Karma: +0/-0
    • View Profile
Re: EA Crash by SystemAccessViolation by runReport
« Reply #4 on: June 07, 2014, 04:39:47 am »
This issue (for my case) is fixed in EA 1107.

Regards

Stefan
Enterprise Architect in "safetycritical development" like medical device industry. My free Add-in at my Website

MarcioMonego

  • EA Novice
  • *
  • Posts: 10
  • Karma: +1/-0
    • View Profile
Re: EA Crash by SystemAccessViolation by runReport
« Reply #5 on: June 12, 2014, 05:07:45 am »
Quote
This issue (for my case) is fixed in EA 1107.

Regards

Stefan

Unlike Stefan it brakes even in 11.1107 (Trial)
In my case I was generating a RTF or PDF report from a versioned package in TFS.

I tried to checkout the package or generate from a non versioned one but EA still crashes.

I used the Use Case Summary and Use Case Details system templates.

UPDATE: On EA full 11.1107 the problem has gone away.

Regards,
Marcio Monego
« Last Edit: July 30, 2014, 06:36:56 am by marciomonego »

skelly

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
Re: EA Crash by SystemAccessViolation by runReport
« Reply #6 on: July 09, 2014, 02:22:24 am »
I'm using 11.1107 and it crashes frequently.  I just ran a report on one package and it was fine; ran it on a second package and it gave me a memory alloc error, tried again and it dies now with an AppCrash.

This happens every few weeks and when I try to reduce it to a simpler model to reproduce the problem, it starts working again.  It almost seems like something in the environment, not the repository contents.  Very frustrating and a huge time waster