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 - blaisephilip

Pages: 1 [2]
Windows Server 2019 Standard
Prolaborate Version
PCS 5.0.104

Dear all,
during the deployment of Prolaborate, I'm facing an authentication issue:
Our model has enabled model security, with active Windows and OpenID users. Additionally I've added an EA Worker and a Prolaborate Worker user - the first for automated diagram image generation (this works well), the second for repository-related Prolaborate connection. Prolaborate and PCS are working in the same domain.

Prolaborate lets me store the user+pass for the repository connection successfully, still, after refreshing the tab in Google Chrome, the warning from above is shown. No further content configuration for the repository is possible. In the logs I see the following not too informative authentication issue error:

2022-06-07T17:07:44.0856418+02:00 [ERR] () Internal Error occurred : {"ReferenceLink":null,"Code":"011501","Information":"Invalid Authentication"}

Any input would be appreciated. Thanks in advance.

Bugs and Issues / Re: HTML Publishing in EA v 16 RC 64bit
« on: April 08, 2022, 12:49:00 am »
You're right, the Default Diagram (Current / Other / None) is practically ignored, and a simple welcome section is added in index.htm.
Code: [Select]
<td class="contentcell">
<div class="welcome_message">
<h2>Welcome to your model</h2>
<p>To get started navigate through the model via the index on the left</p>

I've updated my script so I get to the proper default page (EA1.htm) instead of index.htm.
$filename = $filename + "/EARoot/EA1.htm"

I don't think that EA development should change the Default Diagram feature for the official release, content integration is already used to Default Diagram.

Bugs and Issues / Failed OpenID test @ EA V16 RC 1603
« on: April 07, 2022, 06:14:39 pm »
Dear all,
I've a certain model with configured Windows and OpenID authentication.
All internal corporate users who can use Windows SSO can log in successfully to the model. However, OpenID fails even in test. OpenID is only needed for to the management of external users with Azure AD groups, not Windows.

After clicking Test:

After clicking Login with OpenID:

There is no indication that EA would start a browser. Our IT is triggered to investigate any security-related blocked event, but still, this is a very minimal feedback from the application about what goes wrong.

The information under the links below is already known.

Thank you for any constructive input in advance.

Bugs and Issues / Re: HTML Publishing in EA v 16 RC 64bit
« on: April 07, 2022, 01:08:36 am »
Opening the exported HTML can be quite problematic.
I've written a small powershell script to enable this for non-technical stakeholders that need to access content after architecture workshops. Keeping the exported content in sync with OneDrive is easy & primitive, but it works. The script is dropped next to the index.html and shall be called by the users to start a browser session that is capable to display all content. This works well with EA 15.2 and 16 RC so far.

Code: [Select]
$cmd_arg = "start shell:AppsFolder\Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge --allow-file-access-from-files --profile-directory=Default "
$scriptPath = split-path -parent $MyInvocation.MyCommand.Definition
cd $scriptpath
$filename = (Convert-Path -path $scriptpath).Replace('\','/')
$filename = $filename + "/index.htm"
echo $filename
$uri = [uri]::EscapeDataString($filename)
$cmd_arg = $cmd_arg + $uri
& cmd.exe /c  $cmd_arg

(Some hints on the web tell that a user only needs to pass the following arguments to the start of the browser: "--allow-file-access-from-files --profile-directory=Default"
... however, in some user environments the args alone fail to work, that's the reason of scripting ...)

Bugs and Issues / Re: Element status colors not displayed in EA V16 RC
« on: March 15, 2022, 07:07:24 pm »
Yes, this was the issue. Thanks for the help!

Dear Geert, Eve,
thank you for your responses. We will regulate in our organization to use Javascript in the future.

Bugs and Issues / Element status colors not displayed in EA V16 RC
« on: March 12, 2022, 01:25:17 am »
Hello everyone,

I have another small issue to report:

Test Setup:
EA Version: V16.0.1603
An .EAPX project exists (created with V15.2) that includes application of model types (Settings-> Model Types-> General Types) and has configured colors to Status values.

After opening the project ...
- in EA V15.2, all colors are displayed correctly in the diagrams. (e.g. Requirement Diagram in SysML)

 - in EA V16.0.1603, no colors are displayed on diagrams, but under Settings -> Model Types -> General Types -> Status the values are present and so are the colors. So just the color style on placed elements in the diagrams is ignored.

Is there any workaround for this?

Hello everyone,
the current beta EA V16 Build 1603 throws the following error when debugging of scripts is attempted:

[24297919]      Stack recording threshold set to 3 frames
[24297989]      Default Directory is C:\Program Files\Sparx Systems\EA
[24297989]      Agent dll found: C:\Program Files\Sparx Systems\EA\SScript.dll
[24297989]      Default Directory is C:\Program Files\Sparx Systems\EA
[24297990]      Agent: Started
[24298036]      Microsoft Process Debug Manager creation Failed: 0x80040154
[24298036]      This is included as part of various Microsoft products.
[24298036]      Download the Microsoft Script Debugger to install it.
[24298036]      Failed to initialize VBScript engine
[24298037]      Debug Session Ended

Background might be the same as a couple of years before:,11131.msg149386.html#msg149386

Still, it would be good to provide an official backup resource from where the Microsoft Script Debugger can be installed on the website of Sparx Systems, or in a more optimal way, just include it to the deployed files of the EA installer, if the licensing of the component allows it.

Please note that this is quite an important feature and attempting post-install steps on the side of end-users shall not be seen as mature deployment solution.
Any response with a working official resource would be appreciated. Notes about package references found on the web are not valid anymore for Visual Studio 2019 Professional 16.11.11.

Bugs and Issues / Re: Project transfer crashes EA V16 RC
« on: March 09, 2022, 10:41:44 pm »
Hello Henrik,
you were right about the 64bit version. After I've converted EAPX to QEA first, transfer to MySQL worked with EA Build 1601. Thanks!

Bugs and Issues / Project transfer crashes EA V16 RC
« on: March 09, 2022, 07:22:01 am »
Hello everyone,
I'm having an issue just after initiating project transfer in the following setup:
Client: EA V16.0.1601
Server: Windows Server 2019 with XAMPP v3.3.0 and MySQL. The latest Pro Cloud Server is already installed but not configured yet. (shall not be an issue in my scenario)
DB Connection between client and server is working correctly. Editing other test repositories created in MySQL works without issues.

The local .EAPX file in question: ca 50 MB, content distributed in 2 root nodes, without active security features.

After start of project transfer (local->DBMS), EA crashes in 2 seconds. The log is empty. I cannot verify from the recorded network traffic the exact background of error.

If you could recommend a hint about the possible reason of such an issue, it would be appreciated.
Thanks in advance

Pages: 1 [2]