Author Topic: BUG - Vista does not start .NET processes  (Read 1375 times)

7Alpha7

  • EA Novice
  • *
  • Posts: 18
  • Karma: +0/-0
    • View Profile
BUG - Vista does not start .NET processes
« on: January 24, 2008, 03:32:33 am »
Hi,

the purpose is to generate sequence diagrams.
with Vista the "Debug Workbench" does not start a .NET .exe as specified in the build/run scripts dialog. With the same .NET C# project reversed in EA and the appropriate path specified, the .exe process starts under XP but fails to start under Vista.

have you experienced this ?

thanks.


mrf

  • EA User
  • **
  • Posts: 312
  • Karma: +0/-0
    • View Profile
Re: BUG - Vista does not start .NET processes
« Reply #1 on: January 24, 2008, 07:22:42 pm »
Hello,

I've just tried to reproduce the behaviour your reported on my own Vista installation. The project was a Windows Forms application (.exe) and was started by the EA debugger without any problems.

If the issue still persists, the best avenue of action would be to mail a formal support request through to support@sparxsystems.com.au, and provide some further details such as Vista/.NET versions and perhaps a sample .NET application that reproduces the issue.
Best Regards,

Michael

support@sparxsystems.com
"It is more complicated than you think." - RFC 1925, Section 2.8

7Alpha7

  • EA Novice
  • *
  • Posts: 18
  • Karma: +0/-0
    • View Profile
Re: BUG - Vista does not start .NET processes
« Reply #2 on: January 25, 2008, 12:14:03 am »
Hello,

I have already mailed a formal request to the support some days ago. I started this topic because I had not received any reply to it.

mrf

  • EA User
  • **
  • Posts: 312
  • Karma: +0/-0
    • View Profile
Re: BUG - Vista does not start .NET processes
« Reply #3 on: January 29, 2008, 08:31:43 pm »
No problems, I've just managed to track down your support request. I'll continue correspondance through email.
Best Regards,

Michael

support@sparxsystems.com
"It is more complicated than you think." - RFC 1925, Section 2.8

mrf

  • EA User
  • **
  • Posts: 312
  • Karma: +0/-0
    • View Profile
Re: BUG - Vista does not start .NET processes
« Reply #4 on: January 31, 2008, 06:10:23 pm »
Hi Everyone,

We've tracked down the cause of the issue and are currently investigating. It seems that if Vista's User Access Control is on, then EA is being denied permission to create certain child processes.

If UAC is turned off then .NET exes can be started from the workbench without a problem.
Best Regards,

Michael

support@sparxsystems.com
"It is more complicated than you think." - RFC 1925, Section 2.8

7Alpha7

  • EA Novice
  • *
  • Posts: 18
  • Karma: +0/-0
    • View Profile
Re: BUG - Vista does not start .NET processes
« Reply #5 on: February 02, 2008, 01:06:26 am »
UAC seems not to be the only problem if it is. One of the engineer working with me tried turning UAC off but the process didn't start either.

mrf

  • EA User
  • **
  • Posts: 312
  • Karma: +0/-0
    • View Profile
Re: BUG - Vista does not start .NET processes
« Reply #6 on: February 03, 2008, 02:19:06 pm »
Thanks for the update Alpha7. We're still investigating the problem, but it seems that the most likely cause is the way permissions are set on shared objects between EA and the debugger process (eg named pipes, mutexes etc).

While the existing methodology worked in XP, it seems that Vista behaves differently/more restrictivley. We're currently looking at a few different ways of addressing the problem, but I'll make sure to test it on both UAC and non UAC environments.
Best Regards,

Michael

support@sparxsystems.com
"It is more complicated than you think." - RFC 1925, Section 2.8

mrf

  • EA User
  • **
  • Posts: 312
  • Karma: +0/-0
    • View Profile
Re: BUG - Vista does not start .NET processes
« Reply #7 on: February 07, 2008, 04:03:02 pm »
Hello again,

Just a quick note to advise that the issue has been resolved, the fix should appear in the next build of Enterprise Architect.
Best Regards,

Michael

support@sparxsystems.com
"It is more complicated than you think." - RFC 1925, Section 2.8