Author Topic: Wow!  (Read 4854 times)

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Wow!
« on: June 13, 2013, 04:26:14 am »
Instead of "Error - Missing" I now get "Error - Missing (0x80040154)"!

Which incredible step forward! An error code!

Would someone from Sparx be so kind to explain what this error code means? I mean, I'm no wizard nor a clairvoyant.

Honestly, I'm quite pissed off by the level of debug info we get from EA when it comes to automation or MDG deveolpment >:( >:( >:(

q.
« Last Edit: June 13, 2013, 04:26:39 am by qwerty »

philchudley

  • EA User
  • **
  • Posts: 740
  • Karma: +20/-0
  • UML/EA Principal Consultant / Trainer
    • View Profile
Re: Wow!
« Reply #1 on: June 13, 2013, 04:57:18 am »
May not help much, but this is what I got from a Google search

[highlight]'0x80040154' errors and other critical malfunctions can arise when the Windows operating system becomes overloaded with invalid system references, as well as corrupted and deleted registry files.[/highlight]

Also this

[highlight]ERROR 0X80040154: REGDB_E_CLASSNOTREG.This error is due to Class not registered[/highlight]


The cause is most likely that the extension entry in the windows registry does not match the location of the extension dll

I have also had this error when my extension used another dll which was not installed on the client machine

I found this out using a tool called [highlight]procman[/highlight] a Process Manager from Microsoft, this will help identify which dll is actually missing, but won't tell you why  :'(

Cheers

Phil
follow me on Twitter

@SparxEAGuru

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8063
  • Karma: +118/-20
    • View Profile
Re: Wow!
« Reply #2 on: June 13, 2013, 08:47:57 am »
You're angry because you're getting the same information that Windows gives us?

While it may or may not be possible to programmatically retrieve a textual description of the error code, the information wouldn't be any more useful than what you can find from googling.

The most useful page that I found with a quick search was http://stackoverflow.com/questions/6711571/techniques-for-resolving-com-related-error-0x80040154. It's for C#, if you're using a different platform to write your code you may need to substitute regsvr32 for regasm, but most of the advice should still be somewhat applicable.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Re: Wow!
« Reply #3 on: June 13, 2013, 09:45:44 am »
Simon, where from should I know that this code originates from Windoze?

However, here's still my plea: give us better error messages! For sure this  error message can be improved.

q.

P.S. And yes, the cryptic message simply told me where my error is (since I set up new things and did not register my add-in). 0x4711 is not so informative in contrast to that.
« Last Edit: June 13, 2013, 09:47:59 am by qwerty »

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13274
  • Karma: +556/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Wow!
« Reply #4 on: June 13, 2013, 03:35:24 pm »
I'm happy already with the error code. At least Google usually knows what might be the cause, and how to fix it.

It's still way better then before.

Geert

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Re: Wow!
« Reply #5 on: June 13, 2013, 05:37:27 pm »
Just because it's "better" than before does not its good. And it really does not make me happy.

Errors in MDG still are silently swallowed and you just see that it does not work.

What is the difficulty of giving reasonable error messages?

q.