Screen Layout Designer Error - Object reference not set to an instance of an object.

(0) Share

Report

Posted on by Community Member

Wondering if any has seen this or has any ideas for me. Thank you in advance for your assistance.

I receive the following error when launching the Designer for a screen layout:

"Method 'Start' in COM object of class '_TillLayoutDesigner' returned error code 0x80004003 (<unknown>) which means: Object reference not set to an instance of an object."

The Retail POS receives this error when launching:

"Object reference not set to an instance of an object."

Retail POS posts this in the Windows application event log:

Object reference not set to an instance of an object.: System.NullReferenceException: Object reference not set to an instance of an object.
at LSRetailPosis.POSProcesses.WinControls.GridViewColumnCustomizer.RefreshColumns(ColumnView gridView)
at LSRetailPosis.POSProcesses.WinControls.ReceiptPayments.TranslateLabels()
at LSRetailPosis.POSProcesses.WinControls.ReceiptPayments.InitCustomFields()
at LSRetailPosis.POSProcesses.WinControls.Receipt.InitCustomFields()
at LSRetailPosis.POS.frmMain.frmMain_Load(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at DevExpress.XtraEditors.XtraForm.OnLoad(EventArgs e)
at LSRetailPosis.POS.frmMain.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at DevExpress.XtraEditors.XtraForm.WndProc(Message& msg)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam).

Details:

-Using AX VM Demo

-This only occurs on Screen Layouts that have Application Type = Retail POS. Modern POS application type does not have this issue.

-This occurs when creating a new screen layout or using an existing layout.

-Re-registered TillLayoutDesigner.DLL and all .ocx files.

-POS does launch but screen layout is distorted.

-Compared "RetailTill*" tables between working and non-working AX instances. They appear to be exact.

-Rebooted AX server several times.

*This post is locked for comments

I have the same question (0)

All responses (12)

Answers (0)

echo 595 on at

Like (0)

Report

Hi,

I am facing exactly the same issue? What was the resolution to this?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Sorry, I wish I had a better answer for you... I had to restore the test VM back to it's original version in order to get around this. This was all done in a test environment so I was not worried about losing settings and data. Since the update to CU11 I have not been able to recreate this problem. I hope that helps a little.

Was this reply helpful? Yes No
Suggested answer

Mauro Pedro da Silva 552 on at

Like (0)

Report

Hi Ryan, in case you bump again on this issue.... this blog has the fix: daxdude.blogspot.com/.../ax-issue-method-start-in-com-object-of.html

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thank you Mauro. I tried this blog as well and was not able to get past the error. However, just last week I found a fix. I had to add my Windows user in SQL to the database as dbowner. Once I did this I was able to launch screen layout successfully.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi,

I am facing same problem and user is already added as a dbowner in Dyanamics AX database and channel database also.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Harpal Gohil , Did u resolve this issue please send me the solution?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

When running into this issue in recent CU updates, I have been able to add the SQL user as SYSADMIN to the AX database to fix this issue. I understand that this is not best practice so I can only advise this for non-production environments and testing purposes only. Perhaps it will provide a stating point for troubleshooting the issue.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi

Ryan, I am facing this issue while open screen layout, above suggestion I tried still no luck.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Ankur, I wish I had more to help you. It seems that you need the "Retail Headquarters" option installed from the AX installer (on your SQL server), SQL admin rights to the database and properly registered DLLs with correct security as Mauro mentioned previously in the link he provided.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (1)

Report

Hi Ankur,

I faced the same issue earlier and resolved it through restored the till layout designer data.

However, XML layout data has been corrupted at the time of screen level changes and try to restore the backdated data in which screen level changes has not been performed or modified it. Moreover ,this issue is not related to SQL admin rights. Kindly verified it if you are able to resolve it.

Was this reply helpful? Yes No