SAS Enterprise Guide Error The remote server returned an error: (401) Unauthorized.

[satish504]

Hi All,

I am getting below error when ever I open the SAS Enterprise Guide session of QA/UAT environment.

Configuration Details
----------------------------

SAS Enterprise Guide version: 7.100.0.2002
Platform version: 9.4 M2

Can you please suggest me what can be done to resolve this?

Problem report created: Wednesday, January 16, 2019 10:42:04 AM UTC

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

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

The remote server returned an error: (401) Unauthorized.

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

Exception Details:
----------------------------------------
Exception type: System.Net.WebException
Message: The remote server returned an error: (401) Unauthorized.
Source: System
Target Site: GetResponse

Stack Trace:
at System.Net.HttpWebRequest.GetResponse()
at SAS.EC.SASWebExtensions.VisualAnalyticsTransport.TransportServiceAPI.MakeHttpWebRequest(Uri requestUri, WebRequestMethod requestMethod, String requestPayload, WebHeaderCollection headers, String acceptHeaderType, CookieContainer sessionCookieContainer, Boolean allowRedirect)
at SAS.EC.SASWebExtensions.VisualAnalyticsTransport.TransportServiceProxy.MakeHttpWebRequest(Uri requestUri, WebRequestMethod requestMethod, String requestPayload, Boolean allowRedirect, String acceptHeaderType, WebHeaderCollection headers)
at SAS.EC.SASWebExtensions.VisualAnalyticsTransport.TransportServiceProxy.GetFavorites(String folderGroupSBIP)
at SAS.EC.Favorites.Favorites.LoadServerFavorites(TransportServiceProxy transportServiceProxy)
at SAS.EG.Favorites.FavoritesManager.CheckForServerFavorites()
at SAS.EG.Favorites.FavoritesManager.CreateFavoritesMenu(ToolStripMenuItem favoritesMenu)
at SAS.EG.MainForm.UpdateTasksAndFavorites()
at SAS.EG.MainForm.HandleProviderChange(Boolean fOMRConnection)
at SAS.EG.MainForm.OnProviderConnected(Provider provider)
at SAS.EG.MainForm.ConnectToRepository(Provider provider)
at SAS.EG.MainForm.OnAppLoaded()

[VDD]

If you have just entered these and then immediately see a 401 error, it means that one or both of your user ID and password were invalid for whatever reason (entered incorrectly, user ID suspended etc.).

[satish504]

I have entered the valid credentials and tried connecting, but still getting the same message.

And In addition getting another message every few minutes

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.EG.Application
Target Site: SaveForProjectRecovery

Stack Trace:
at SAS.EG.MainForm.SaveForProjectRecovery(Boolean applicationExiting)
at SAS.EG.MainForm.projectRecoveryTimer_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

When exploring SASApp, getting below message

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.EG.SDS.Model
Target Site: SASWorkspace

Stack Trace:
at SAS.EG.SDS.Model.Server.SASWorkspace()
at SAS.EG.SDS.Views.View.DoPopulate(DisplayOperation& op)

Some times it allowing to run the code.

[satish504]

Even I tried with sas installation id, which is never expired but still same message

[satish504]

Issue has been resolved after restarting all the SAS Services in the correct order.

[VDD]

@satish504 wrote restarting all the SAS Services in the correct order.  Yes the order of execution could result in the 404 error.