Ayende @ Rahien

It's a girl

Microsoft CRM: Error reporting from the stone age

image

I have said, more than once, that the #1 reason that I like .NET is that I get good error handling.

Here is the current error that I have to deal with from the CRM.

I had to dig into the three separate log files, the event log, restart services and howl at the moon to figure out what is wrong.

 

 

 

BLAH!

Comments

Avish
08/27/2007 05:01 PM by
Avish

I don't see what's so hard to understand. You're experiencing a simple Invalid Argument error, which means your argument is not valid. Normally this would be ok, but you're having the platform type, which makes things a little more dangerous, since that means the error is of type platform. Of course, you could have understood all that from the error code (the 40203 suffix is a sure sign!), but if you happen to forget the table of error codes (bad practice in itself), it's right there in bold letters for your convenience. What more could you ask for?

Nate Kohari
08/27/2007 08:48 PM by
Nate Kohari

It seems like most Microsoft tools still rely too much on COM to provide useful error messages. We just ran into a similar problem the other day with SSIS. If I ever have to look up the meaning of the HRESULT from a COMException again, it'll be too soon. :)

Comments have been closed on this topic.