Desktop productivity for business analysts and programmers

SAS EG 7.1 Options Menu Crash

Reply
New Contributor
Posts: 3

SAS EG 7.1 Options Menu Crash

Hello,

I am having a strange issue in my environment which I am hoping someone can help with.

This is the steps to reproduce the error.

Open SAS EG 7.1 > Tools > Options > Results General > don't change any settings and click OK > SAS Produces the error below.

Results General is not the only menu item that will crash SAS, interesting things is that if I go to Application Logging and turn it on, SAS will no longer crash on any menu item and work as you would expect.

We deploy SAS 7.1 with AppV 5 SP3... I have been able to reproduce this with a normal install  also.

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.SharedUI.WPF

Target Site:     CommitChanges

Stack Trace:

   at SAS.SharedUI.WPF.LoggingController.LoggingConfiguration.CommitChanges()

   at SAS.EG.Options.Forms.OptionsLoggingPanel.OnOK(Object sender, EventArgs e)

   at SAS.SharedUI.Panels.SASPanelStack2.OnOK(Object sender, EventArgs e)

   at SAS.SharedUI.Panels.SASPanelStack2._OK_Click(Object sender, EventArgs e)

   at System.Windows.Forms.Control.OnClick(EventArgs e)

   at System.Windows.Forms.Button.OnClick(EventArgs e)

   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

   at SAS.SharedUI.Controls.OpenButton.OnMouseUp(MouseEventArgs mea)

   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.ButtonBase.WndProc(Message& m)

   at System.Windows.Forms.Button.WndProc(Message& m)

   at SAS.SharedUI.Controls.OpenButton.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)

Respected Advisor
Posts: 3,065

Re: SAS EG 7.1 Options Menu Crash

What version of Microsoft .NET Framework are you running? I believe you should have 4.5.1.


What version of Windows are you installing on and is EG 32-bit or 64-bit?

New Contributor
Posts: 3

Re: SAS EG 7.1 Options Menu Crash

the OS has 4.5.2 installed.

In SAS if I go to Help > About SAS Enterprise Guide > Configuration Details > it tells me it has .NET 4.0.30319.34209

Windows 7 x86

Does SAS have its own private .NET ?

Cheers.

Respected Advisor
Posts: 3,065

Re: SAS EG 7.1 Options Menu Crash

That's what I see in my EG, so you are probably OK with .NET.

Do you have another PC with the same install and does it give the same problem?

I would also open a track with SAS Tech Support.

Community Manager
Posts: 2,697

Re: SAS EG 7.1 Options Menu Crash

I agree with SASKiwi that you should track this with tech support.  The AppV deployment might be a factor -- perhaps there is a missing component or the app is trying to access a folder that doesn't exist in the AppV environment as it's configured.

Chris

SAS Super FREQ
Posts: 272

Re: SAS EG 7.1 Options Menu Crash

This is an issue (in EG 7.1) that we are aware of and fixed in EG 7.11.

As originally noted, you can workaround the issue in EG 7.1 with the one-time step of selecting "Enable Logging" or "Reset to Defaults" in Tools->Options->Application Logging. After doing that, the exception does not happen anymore, even when you turn off logging (uncheck "Enable Logging") to get back to the original state.

New Contributor
Posts: 3

Re: SAS EG 7.1 Options Menu Crash

thanks everyone for your help,

seems like I have a work around for now with the one-time option, ill look to upgrade to 7.11 when possible for my environment.

thanks again for you help.

Cheers.

Ask a Question
Discussion stats
  • 6 replies
  • 628 views
  • 0 likes
  • 4 in conversation