A Tale of Third Party Application Errors

Feb 13th, 2009 | Posted by | Filed under Uncategorized

Scene 1: 

A dark and smoky conference room (not really, but a fluorescent-lit and lung-friendly conference room is less dramatic).  Randy Miller, Alex Ruppe and Allan Lamar gather to prioritize new documentation.

 

Allan:  “A definite priority is a document that walks you through resolving third party application errors.  The error log shows what is wrong, but not how to fix the problem.”

Alex:  “Cool.”

Randy:  “There are a number of error codes we can generate for third party integrations, many of which would rarely be seen.  This may be overwhelming and could be hard to use.”

Alex:  “It’s all good. Why don’t we just handle the errors user will most likely get?”

Randy:  “That makes sense.  Allan, do you know what those are?”

Allan:  “Hmm… Let me research that and get back to you.”

Alex:  “Cool.”

End scene 1

 

Scene 2: 

Allan’s office.  Allan sits at his computer wondering how he can find out what are the most common third party application errors customers receive.

 

Allan (talking to himself): There must be a way to do this.  Maybe I can log onto every customer’s server and see what errors they have and write them down.  No, that won’t work.  Our customers diligently maintain those errors.  They are cleared out too quickly for this to work.

 

A unicorn enters Allan’s office and invites him for coffee. (If we are going to push the boundaries of reality with every customer’s error log being empty, let’s take it all the way.)

 

Returning to his office stimulated from the caffeine enriched coffee and his conversation with the unicorn, Allan realizes that he has no idea how to quickly and accurately gather this information.  In a flash of laziness – err, umm –  management delegation excellence, Allan tells Matt Luckhaupt he needs a list of the top third party errors our customers receive.  A short time later Matt returns carrying an Alex inspired suggestion:  “Why not write a blog and ask our customers?”

End scene 2

 

Scene 3: 

Allan is in his office writing a blog…                           

 

Help write the ending for this inspiring story of one man’s epic struggle by sending Allan your top ten third party errors.  The unicorn anxiously awaits your responses.

Tags:
  1. Aaron@a-mrazek.com
    Feb 13th, 2009 at 12:53
    Reply | Quote | #1

    Here is a picture what’s sitting in my error log right now. I know how to fix most of them.

    http://img300.imageshack.us/img300/113/thirdpartyerrorsfj3.jpg

    My question would be not just how to fix them, but why we get so many “the order number does not exist in movers suite” ones.
    Why’s isn’t it downloading them in the first place?
    I would also say if I process those errors by putting them in movers suite the very next error is on that order will be about no booking agent, even if one was entered, so then I’ll manually put that in movers suite and reprocess it again.
    This error log is typical and has been this way since before the any to any conversion.

  2. Penelope
    Feb 13th, 2009 at 13:09
    Reply | Quote | #2

    When I was trying to pull up an attached document to a certain order…I received the following error:

    {unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

    Unable to cast object of type ‘System.DBNull’ to type ‘System String’.

    When trying to CONTINUE, it does not.

    Thank you.

  3. CorriganCIO
    Feb 15th, 2009 at 18:37
    Reply | Quote | #3

    Never thought I would appear in a caffeine-induced blog post as a unicorn. But hey, anything is possible in Colorado.

    I recall recently sending over a pile of errors (of course, they were cleared out immediately) not too long ago. I believe Anita has our list.

    I’ll take a cheat sheet for the time being. What errors can be deleted, which ones REQUIRE some attention, etc.

    Thanks!

  4. Allan
    Feb 16th, 2009 at 08:46
    Reply | Quote | #4


    Penelope :
    When I was trying to pull up an attached document to a certain order…I received the following error:
    {unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.
    Unable to cast object of type ‘System.DBNull’ to type ‘System String’.
    When trying to CONTINUE, it does not.
    Thank you.

    Penelope – this sounds like it may have to do with the application Planes created to link documents to orders. I would recommend contacting your internal IT team and if it turns out to be something related to MoversSuite, they can submit an incident ticket.

  5. Allan
    Feb 16th, 2009 at 08:47
    Reply | Quote | #5

    @Aaron@a-mrazek.com
    Great suggestion, I will have that included in the document.

  6. lleblanc
    Mar 5th, 2009 at 10:39
    Reply | Quote | #6

    Hello Allan,

    The following are frequent errors that we run into

    2041-2044-Unable to process registration,no order found
    2040- Unable to process the memo pad from the van line
    2006-2007 OA/DA agent was not found, unable to add/update

    Thanks!
    Lynn -Capitol

  7. Jackieb
    Apr 17th, 2009 at 14:26
    Reply | Quote | #7

    It would be really nice not to have all these erros! We have Error Codes 2001, 2010, 2017, 2020, 2021, 2022, 2029, 2030, 2039, 2040, 2041, 2042, and 2044!

    I can not keep up with them!

  8. Jackieb
    May 13th, 2009 at 08:50
    Reply | Quote | #8

    It would also be nice to know the original date of the download error. This list gets too overwhelming and it would nice to just delete everything that has been out there more than a month.

  9. Allan
    May 13th, 2009 at 09:31
    Reply | Quote | #9

    @Jackieb
    This is a good idea and would be a great enhancement submission. I would suggest posting this on the new enhancement voting site. Thanks for the suggestion!

You must be logged in to post a comment.

Fatal error: Call to undefined method s2class_upgrade::get_usermeta_keyname() in /home/mover2/public_html/ewsgroup/blog/wp-content/plugins/subscribe2/classes/class-s2-upgrade.php on line 292