Eg with error "System.NullReferenceExceptionObject reference not set to an instance of an object"

[Anusha26]

Cannot connect to the SAS server to run queries.

machine - HP ELITEBOOK REVOLVE 810 G2 I7.

Restarted SAS Eg and updated SAS credentials and still not working.

SAS Eg was working well before.

[andreas_lds]

Contacting the responsible server-admin seems to be the most efficient way to solve the issue.

[ChrisHemedinger]

That message is not one that should ever happen -- so, either something is wrong with your EG install/setup, or you've found a way to trigger a bug.

I recommend tracking with SAS tech support.  You can help expedite the case by enabling the Application Log (Tools->Options), follow the steps to trigger the problem, and send the resulting log file to tech support as well.

Chris

[Kurt_Bremser]

If there is additional information ("Details") in the message, please post it.

[Technolero]

I had a user report the same error at the end of last week (EG 7.15HF2). The application log was not on, so we turned it on, and she has not replicated the error yet. We will definitely work with Tech Support and follow up here if we see the issue again.

The user did provide some exception details:

Application Error
SAS Enterprise Guide has encountered a problem
We recommend that you save your work and restart SAS Enterprise Guide.

-------------------------------------------------------------------------------------------------------
Exception information
-------------------------------------------------------------------------------------------------------

Object reference not set to an instance of an object.

-------------------------- Technical Information Follows --------------------------

Exception Details:
----------------------------------------
Exception type: System.NullReferenceException
Message: Object reference not set to an instance of an object.
Source: SAS.Tasks.ImportData
Target Site: SelectDataExcel_Load

Stack Trace:
at SAS.Tasks.ImportData.SelectDataExcel.SelectDataExcel_Load(Object sender, EventArgs e)
at System.Windows.Forms.UserControl.OnLoad(EventArgs e)
at System.Windows.Forms.UserControl.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.SetVisibleCore(Boolean value)
at System.Windows.Forms.Control.set_Visible(Boolean value)
at SAS.SharedUI.Wizard2.set_ActivePageIndex(Int32 value)
at SAS.Tasks.ImportData.ImportDataView.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.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
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)

[Kurt_Bremser · Accepted solution]

My current version of EG is 7.15 HF7, and we needed to update to that hotfix level so we can deal with certain problems caused by Office 2016.

Consider installing hotfix B4N007.

[Technolero]

Yes, that will be my first course of action if we see that error again. Being an admin, I'm running HF7, but in my company getting the Windows admins to deploy patches to applications is a slow and painful process...that's why the end users are still on HF2!