Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - skiwi

Pages: [1] 2 3 ... 139
1
We use corporate floating licenses, our license key server is PCS, access to the models is via PCS, we apply security at the model and project level.
We like to encourage and make it easy for people to use the tool.


But most importantly (and this is our use case) this allows us to use "auto update" from the Store, so when SparxSystems update the release it gets deployed to all users.


The current approach of having to download (then package), then install is not optimal.

2
This is a suggestion for SparxSystems to provide the latest stable (non-beta) version of EA in the Microsoft store.


This would make it very easy, in our enterprise environment, to install and keep up to date our version of EA in a modern way.

3
Bugs and Issues / Re: EA stability
« on: July 12, 2024, 06:40:38 am »
Geert is correct
these come from the Windows Event viewer

I used the following Windows Application Event Log query

Use the XML tab on the Folder Current Log dialogue
Code: [Select]
‚Äč<QueryList>
<Query Id="0" Path="Application">
<Select Path="Application">*[EventData[Data[@Name='AppName'] and (Data='EA.exe')]]</Select>
</Query>
</QueryList>

4
Bugs and Issues / Re: EA stability
« on: July 11, 2024, 07:08:48 am »
Just to stress that we use a "vanilla" install of EA. We are not developing scripts or SQL queries.


Here is an example from the error log. [reported]
I don't see as many error log entries as I observe crashes.


Log Name:      Application
Source:        Application Error
Date:          4/07/2024 4:26:24 pm
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Keywords:     
User:          xxxxxx\xxxxxx
Computer:      xxxxxx
Description:
Faulting application name: EA.exe, version: 16.1.0.1627, time stamp: 0x64acb5ed
Faulting module name: EA.exe, version: 16.1.0.1627, time stamp: 0x64acb5ed
Exception code: 0xc0000005
Fault offset: 0x000000000273d061
Faulting process id: 0x0x3A54
Faulting application start time: 0x0x1DACCBA72174820
Faulting application path: C:\Program Files\Sparx Systems\EA\EA.exe
Faulting module path: C:\Program Files\Sparx Systems\EA\EA.exe
Report Id: 8047b6c2-fa58-4ca6-87e4-a51139911199
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
    <EventID>1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2024-07-04T04:26:24.9858071Z" />
    <EventRecordID>128634</EventRecordID>
    <Correlation />
    <Execution ProcessID="23568" ThreadID="36480" />
    <Channel>Application</Channel>
    <Computer>xxxxxxx</Computer>
    <Security UserID="xxxxxxx" />
  </System>
  <EventData>
    <Data Name="AppName">EA.exe</Data>
    <Data Name="AppVersion">16.1.0.1627</Data>
    <Data Name="AppTimeStamp">64acb5ed</Data>
    <Data Name="ModuleName">EA.exe</Data>
    <Data Name="ModuleVersion">16.1.0.1627</Data>
    <Data Name="ModuleTimeStamp">64acb5ed</Data>
    <Data Name="ExceptionCode">c0000005</Data>
    <Data Name="FaultingOffset">000000000273d061</Data>
    <Data Name="ProcessId">0x3a54</Data>
    <Data Name="ProcessCreationTime">0x1daccba72174820</Data>
    <Data Name="AppPath">C:\Program Files\Sparx Systems\EA\EA.exe</Data>
    <Data Name="ModulePath">C:\Program Files\Sparx Systems\EA\EA.exe</Data>
    <Data Name="IntegratorReportId">8047b6c2-fa58-4ca6-87e4-a51139911199</Data>
    <Data Name="PackageFullName">
    </Data>
    <Data Name="PackageRelativeAppId">
    </Data>
  </EventData>
</Event>


We also observe other errors
  • The program EA.exe version 16.1.0.1627 stopped interacting with Windows and was closed.
  • <Data Name="ExceptionCode">c0000409</Data>
  • <Data Name="ExceptionCode">c000041d</Data>

5
Yes, we see this a lot (we use SQL Server). (as I referred to in may post about instability).
It basically makes direct DB access unusable, because you have to click through so many messages each time you change something (although to its credit EA does keep working)


I wonder if it is related to a DB connection being dropped and then reinstated.

6
Bugs and Issues / Re: EA stability
« on: July 08, 2024, 02:28:27 pm »
We don't normally use the direct DB connection
(as PCS is recommended, and because we frequently get "Operation is not allowed when object is closed" errors when using direct DB)


I have run using a direct DB connection and I am still encountering crashes.


It would be very useful if there was some logging I could turn on.

7
Bugs and Issues / Re: EA stability
« on: June 27, 2024, 01:53:18 pm »
I do know however that, when writing addins or scripts, you have to be very careful. It only takes one uncaught exception to make EA crash completely.
I had to build in a type of "catch-all" mechanism to make sure no exceptions would ever escape to EA.
So the crashes you are experiencing might be caused by whatever add-ins or scripts you are running.

There are a few instances where I can pretty reliably make EA crash. This is when using the schema composer with my add-in the Message Composer.

In my tests EA v15.2 has proven to be more stable than v16, and the 32 bit edition is more stable than the 64 bit edition.

Geert
We are not using any add-ins (other than the OOTB ones). And not using schema composer.
With no phone home, or exception reporting capability it is difficult to demonstrate to SparxSystems that we have stability issues.
If I had to guess I'd some some are related to network issues (we use Pro Cloud Server).
At a minimum EA should not just 'disappear', it should provide an error message.

8
Bugs and Issues / EA stability
« on: June 26, 2024, 06:02:06 am »
With EA 17 in the pipeline my wish is for more stability, and optional phone home error reporting
(those long in the tooth will recall this from some time back).


My experience is that EA disappears (crashes) without any warning (i.e. crashes are not caught and no error message or log file is created) at least weekly and generally several times a week (EA 16.1.1627).


The purpose of this post is is ask if you observe crashes and at what frequency.


Simon

9
PCS Bugs and Issues / Re: PHP security
« on: June 24, 2024, 08:09:19 am »
Sparx Systems provides virtually no documentation on how to install and configure WebEA on a Windows Server OS running IIS, including how to configure WebEA, without using XAMPP. This is, in my opinion, an issue.
Agreed, I made the mistake of pointing our ITMS partner at the SparxSystems Pro Cloud server installation documentation in the belief that it was intended and suitable for 'Production Use'.

10
PCS Bugs and Issues / Re: PHP security
« on: June 20, 2024, 07:45:18 am »
Thanks Eve,
could I possibly suggest then that the SparxSystems advice on the website should be clearer about this - specifically XAMPP is (according to the vendor) insecure.
Also that XAMPP NOT to be used in production, and possibly change the advice to simply specify apache server and PHP.




11
PCS Bugs and Issues / Re: PHP security
« on: June 19, 2024, 09:55:33 am »
Doing a little more research (WebEA Quick Start Guide | Enterprise Architect User Guide (sparxsystems.com))
WebEA Installation and Configuration | Enterprise Architect User Guide (sparxsystems.com) XAMPP is suggested.


However XAMPP themselves state "XAMPP is not meant for production use but only for developers in a development environment"

In the readme.txt it states
Quote
A matter of security (A MUST READ!)

As mentioned before, XAMPP is not meant for production use but only for developers in a development environment. The way XAMPP is configured is to be open as possible and allowing the developer anything he/she wants. For development environments this is great but in a production environment it could be fatal. Here a list of missing security
in XAMPP:

- The MySQL administrator (root) has no password.
- The MySQL daemon is accessible via network.
- phpMyAdmin is accessible via network.
- Examples are accessible via network.

12
PCS Bugs and Issues / PHP security
« on: June 19, 2024, 09:10:57 am »
Recent PHP security issues (CVE-2024-4577) mean we need to urgently update to PHP 8.3.8.
Is anyone running PCS on this version of PHP and is it working OK?

(and its a nuisance that XAMPP releases seen to be running so far behind)

13
I have heard from support:
Quote
Thank you for the enquiry.
 Our developers have confirmed that this is a bug and it is logged to be fixed. We cannot yet say when (in which build) the fix will be implemented.
 The issue id is : 24057410

14
Suggestions and Requests / Re: UAF MDG Request
« on: May 29, 2024, 06:23:12 am »
Can I add that some of the analysis patterns, e.g.  Azure (Nov 2022), AWS etc. need to be frequently updated,
and must be able to be updated on the fly, rather than waiting for new releases.
(BTW could we please have consistent naming standards for these patterns. e.g. Nov 2022, Rel 1, Rel 5, v1.5 are not helpful when attempting to understand what the most recent version is (tip: date works well))

15
Suggestions and Requests / Re: Improved support for View columns
« on: May 17, 2024, 06:05:14 am »
I support this

Pages: [1] 2 3 ... 139