Determining the root cause of errors in the Dynamics AX 2009 for Retail POS

NOTE: This is an old post I'm just now getting around to posting 3 years later...  It was helpful back then so maybe some of the people on AX 2009 for Retail can still use it.
 
On occasions, a user will see an error within the POS and something unusual will happen like clear out all of the items selected in the POS or crash the POS.  While this is rare, it can happen.

So the end user (or help desk person) now needs to report the error to the appropriate people within the organization to make sure that it can be investigated since it will more than likely be one of three things: a user error, a bug in the system, or a situational thing like a network or service issue.

Since the person investigating the error cannot step into the code in the POS like you can in  Dynamics AX 2009 or AX 2012 product, it is harder to find out why the code is failing. There is a table in the POS DB that stores all of the actions and errors.

[NOTE: this article was written for when multiple POS DBs per store were supported]

To give some background info, the AX system has a master database and each POS has a database of its own which, in generalities, is a mini-AX database that mirrors tables in AX.  Note that the POS headquarters concept for AX for Retail is different than that of the Dynamics Retail Management Solution (RMS) solution.  The headquarters for AX for Retail is actually a module in AX and not a separate program.  The 'Worksheets' concepts in RMS are called 'Scheduler jobs' in AX but are roughly the same idea.

In AX 2009, the log table is in the [POS DB with the error].[dbo].[POSISLOG].  In here, you should be able to see a line in the table that shows the error stack.
In AX 2012, I don't know the log table but I am guessing it is different since it will mimic the AX DB and the AX table structure is significantly different in the new version.

I won't go into all of the errors but I will let you post yours below if you want.

Hope that helps!