EA 13 - Input string was not in correct format

[vroomado]

Hi Everyone,

My thanks and apologies in advance as this is for Sparx EA 13 Beta.

I've been using EA 9, 11, and 12, 12.1 and just recently installed 13 beta.

The installation went smoothly.  In exploring 13 beta (user acceptance, perhaps), I revisited models I had previously been developing and encountered a problem which prevents me from creating elements.

Essentially, when I click OK after creating an element, either from the project browser or the toolbox, I get the message "Input string was not in correct format", and the element is not created.  In addition, some elements when dragged from the toolbox to a diagram generate an extra error message.  When I drag Signal from the Class toolbox to a class diagram I get the second error message "Unknown / illegal base type 'Signal' Command: UML::Signal".

So, I can create packages and drawings.  I can add exiting elements to drawings.  I can rename existing elements.  I can connect elements on diagrams.  I cannot create elements.   

I've repaired the 13 beta install, I've removed and reinstalled 13 beta to no avail.  Following sharing this situation with some colleagues, I was advised that they witnessed this happen with 12.1.

A google of the error message suggests this is DLL or OS related.  I'm wondering if a company security policy or recent change prevented a DLL from being installed or registered.

Thanks kindly for your attention,

vroomado

EDIT

Problem occurs with both a local EAP file (and no network connection) or remote SQL Server DB.

[Glassboy]

What is the underlying repository? 

[vroomado]

Thanks for responding so quickly!  I forgot that bit.

Problem occurs with both a local EAP file (and no network connection) or remote SQL Server DB.

regards, vroomado

[Glassboy]

I'd actually suspect a MDAC problem.  If someone has fubared your patching you could have dlls from multiple versions.  Hard to say what you can do about it.  I generally like a new clean O/S install at that point.

[qwerty]

I'd suggest to contact Sparx support with that issue.

q.