Mike Lucas

[Mike Lucas]

Ok, we’ll try that. Thanks.

[Mike Lucas]

Update to this: the error is incorrectly reported as ‘no more licences’. In fact, it’s a communication error between client and the LSA, usually caused by network changes.
Best solution is to create a new LSA for the SAME machine as where eaDocX is installed. Remember, each LSA is IP-address specific, so you will need to go to the eaDocX website and create new LSAs.
Once this works OK, then create a new LSA on a network machine, is possible, one where you have Admin rights, and can control network and firewall settings.
Once this works, carry on looking at your network settings.

We have also seen many problems where the LSA is running on a Virtual Server: it’s a high-security application, designed to prevent fraud, and we think that the application doesn’t really understand VSs and throws strange errors. Sorry about this, but it’s out of our control. So, we recommend LSAs run on real servers.

We’re experiencing similar problems at the moment, getting an error message saying that there are no licences available even though none are checked out. Is the advice to recreate a new LSA still the right thing to do?

Thanks

[Mike Lucas]

Thanks for the quick reply. Looks like Sparx ought to be providing more information to extensions. I’m guessing that this isn’t the only issue caused by the API. 🙁

[Mike Lucas]

Thanks for looking into this, much appreciated.

All may not be lost. Setting the eaDocX table “vertical alignment” property to top, in conjunction with the table style alignment, appears to give us what we need in this instance. This may cause other issues in the future but it solves my current problem. 🙂

Thanks

Mike

[Mike Lucas]

I’ve now been able to try this with v3.9.2.4 of eaDocX and I can confirm that the problem still exists.

[Mike Lucas]

That’s great, I’d completely forgotten about being able to assign types to TVs, that will solve our immediate problem.

Also, thanks for your thoughts on how to handle stakeholders, that’s a really good point you make. Lot’s to think about there 🙂

Thanks

Mike

[Mike Lucas]

Thanks, that has helped. The starting point was the following output:

1 My use case

1.1 Scenarios
1.2 Basic Path : Basic Path
1.3 Alternate : Something went wrong

When I edited the use case profile to remove the Scenarios title and regenerated the document the Scenarios heading was removed, just as you said.

1 My use case

1.1 Basic Path : Basic Path
1.2 Alternate : Something went wrong

When I then added the Scenarios title back into the Use Case profile and regenerated the document the Scenarios heading was added back in and the heading level for each of the scenarios is now at the correct level.

1 My use case

1.1 Scenarios
1.1.1 Basic Path : Basic Path
1.1.2 Alternate : Something went wrong

Thanks

Mike

[Mike Lucas]

Thanks for the prompt response. I’ll see if I can get it updated and try again.

[Mike Lucas]

Just confirming that we have updated our version of eaDocX to 3.9.1.2 and the problem still exists. From what I can see from the release notes this hasn’t been addressed in any of the releases since 3.9.1.2.

Are there any plans to fix this? This is causing us real problems.

Thanks

Mike

[Mike Lucas]

Thanks for your help yesterday. I have attached some more files to hopefully explain the situation better.

When the attached Word document is loaded into eaDocX and regenerated, the output I get is as shown in “Document after eaDocX generation.PNG”. If I then select the table containing the requirements and reapply the eaDocXRequirementsTable table style manually, the format changes as shown in “Document after reapplying the eaDocXRequirementsTable style manually.PNG”. The differences are that the vertical text alignment is top rather than center and there’s a bottom margin on each row to space out the requirement text.

Hope that makes more sense. I’d be interested to know if you can reproduced that behaviour.

Thanks

Mike

[Mike Lucas]

Here’s the model.

• This reply was modified 8 years, 1 month ago by Mike Lucas.

[Mike Lucas]

Yes, I created my own table style based on Table Normal.

I have attached a simple model and word document showing the issue.

You can reproduce the problem by:

1. Regenerate the doc from the model
2. With the table selected in the Word doc, click on the Design tab
3. Right click on the currently selected style (eaDocXRequirementsTable) and select Apply (and clear formatting). (

The format now changes to match the table style.

• This reply was modified 8 years, 1 month ago by Mike Lucas. Reason: Typo

[Mike Lucas]

Thanks for the prompt response.

Changing the licence model to check out licences when EA starts up doesn’t sound so good. Looks like sparx needs to give some thought to improving the support for extensions in their licence server API.

[Mike Lucas]

eaDocX has stopped working in our corporate network environment as of yesterday with the same kind of error. Are there any updates on solutions or is it still a case of moving from virtual to physical for licence server hosting to see if that works?

[Mike Lucas]

Ok, just realised what is going on here. Because eaDocX believes that the repository has changed it can’t resolve the hyper links in the model. New links that I have added are being generated correctly, so I guess the only real issue is why eaDocX thinks that the project id has changed. Has anyone seen this behaviour before?

[Author]

Posts