Usage Note 59996: A 401 unauthorized error might appear when selecting SAS® Central
 |  |  |  |  |
In Microsoft Excel, when you attempt to open SAS Central within the SAS® Add-In for Microsoft Office, you might see the following error:
SAS Add-in for Microsoft Office has encountered a problem
We recommend that you save your work and restart SAS Add-in for Microsoft Office.
The remote server returned an error: (401) Unauthorized
---------------------------Technical Information Follows ----------------------------------
Exception Details:
Exception type: System.Net.WebException
Message: The remote server return an error: (401) unauthorized
Source: System
Target Site: Get Response
Stack Trace:
at System.Net.Http.WebRequest.GetResponse()
at SAS.EC.SASWebExtensions.VisualAnalytic.Transport.TransportServiceAPI. <>c__DisplayClass1.<MakeHttpWebRequest>b__0()
at SAS.EX.SASWebExtensions.X509 CertificateHelper.SetupCertificates(Object service, Action workMethod)
at SAS.EC.SASWebExtensions.X509CertificateHelper.SetupCertificates(Object service, Action workMethod)
Typically, this error can occur if the connection information specified for SAS® Visual Analytics Transport Service is incorrect.
How can you tell where your SAS Visual Analytics Transport Service is connecting
You can check the internal and external connections for all of your services by running the code listed on the Full Code tab. Before submitting the code, modify the Options statement at the top of the code for your site-specific information. The results list out the port, host, and service name. Use this information to verify that the protocol, host name, and port are specified correctly for SAS Visual Analytics Transport Service.
You can also use SAS® Management Console to verify your SAS Visual Analytics Transport Service connection information.
- On the Plug-ins tab, select Application Management ► Configuration Manager ► SAS Application Infrastructure ► Visual Analytics 7.3 ► Visual Analytics Services 7.3.
- Right-click Visual Analytics Transport Service 7.3 and select Properties.
- Verify the information on both the Internal Connection and the External Connection tabs. In particular, verify the Host Name and Port Number. You can compare these properties in the Visual Analytics Transport Service with other services to see whether the Host Name and Port Number are different.
How to fix your SAS Visual Analytics Transport Service connection
If the Visual Analytics Transport Service is pointing to an incorrect host, you need to correct that information in order for the SAS add-in to work correctly. You can modify the information in SAS Management Console.
- On the Plug-ins tab, select Application Management ► Configuration Manager ► SAS Application Infrastructure ► Visual Analytics 7.3 ► Visual Analytics Services 7.3.
- Right-click Visual Analytics Transport Service 7.3 and select Properties.
- Make the necessary changes on both the Internal Connection and the External Connection tabs. This includes the communication protocol, host name, and port number. The Service should be set to /SASVisualAnalyticsTransport.
- Click OK to save your changes and close the dialog box.
- To enforce the changes, restart the SAS® Web Application server and the Microsoft Office application.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Add-in for Microsoft Office | Microsoft® Windows® for x64 | 7.13 | 9.4 TS1M4 | ||
| Microsoft Windows 8 Enterprise 32-bit | 7.13 | 9.4 TS1M4 | ||||
| Microsoft Windows 8 Enterprise x64 | 7.13 | 9.4 TS1M4 | ||||
| Microsoft Windows 8 Pro 32-bit | 7.13 | 9.4 TS1M4 | ||||
| Microsoft Windows 8 Pro x64 | 7.13 | 9.4 TS1M4 | ||||
| Microsoft Windows 8.1 Enterprise 32-bit | 7.13 | 9.4 TS1M4 | ||||
| Microsoft Windows 8.1 Enterprise x64 | 7.13 | 9.4 TS1M4 | ||||
| Microsoft Windows 8.1 Pro 32-bit | 7.13 | 9.4 TS1M4 | ||||
| Microsoft Windows 8.1 Pro x64 | 7.13 | 9.4 TS1M4 | ||||
| Microsoft Windows 10 | 7.13 | 9.4 TS1M4 | ||||
| Microsoft Windows Server 2008 | 7.13 | 9.4 TS1M4 | ||||
| Microsoft Windows Server 2008 R2 | 7.13 | 9.4 TS1M4 | ||||
| Microsoft Windows Server 2008 for x64 | 7.13 | 9.4 TS1M4 | ||||
| Microsoft Windows Server 2012 Datacenter | 7.13 | 9.4 TS1M4 | ||||
| Microsoft Windows Server 2012 R2 Datacenter | 7.13 | 9.4 TS1M4 | ||||
| Microsoft Windows Server 2012 R2 Std | 7.13 | 9.4 TS1M4 | ||||
| Microsoft Windows Server 2012 Std | 7.13 | 9.4 TS1M4 | ||||
| Windows 7 Enterprise 32 bit | 7.13 | 9.4 TS1M4 | ||||
| Windows 7 Enterprise x64 | 7.13 | 9.4 TS1M4 | ||||
| Windows 7 Home Premium 32 bit | 7.13 | 9.4 TS1M4 | ||||
| Windows 7 Home Premium x64 | 7.13 | 9.4 TS1M4 | ||||
| Windows 7 Professional 32 bit | 7.13 | 9.4 TS1M4 | ||||
| Windows 7 Professional x64 | 7.13 | 9.4 TS1M4 | ||||
| Windows 7 Ultimate 32 bit | 7.13 | 9.4 TS1M4 | ||||
| Windows 7 Ultimate x64 | 7.13 | 9.4 TS1M4 | ||||
options
metaserver="localhost"
metaport=8561
metauser="sasadm@saspw"
metapass="xxxxxx";
data tcpip;
keep name port host protocol service;
length port host protocol objid service uri name $255;
nobj=0;
n=1;
do while (nobj >= 0);
nobj=metadata_getnobj("omsobj:TCPIPConnection?@Name='Connection URI' or @Name='External URI'",n,uri);
if (nobj >= 0) then do;
rc=metadata_getattr(uri,"Name",name);
if trim(name)='Connection URI' then name="Internal URI";
rc=metadata_getattr(uri,"CommunicationProtocol",protocol);
rc=metadata_getattr(uri,"HostName",host);
rc=metadata_getattr(uri,"Port",port);
rc=metadata_getattr(uri,"Service",service);
concat=strip(name) || ' ' || strip(protocol) || '://' || strip(host) || ':' || strip(port) || strip(service);
put concat;
output;
end ;
n = n + 1;
end;
run;
proc sort data=tcpip out=sorted;
by service;
run;
proc print data=sorted;
var name protocol port host service;
title 'Internal and External Connections (except SASThemes)';
title2 'Listed by Service';
run;
| Type: | Usage Note |
| Priority: | medium |
| Date Modified: | 2017-02-28 15:02:48 |
| Date Created: | 2017-02-17 13:24:06 |