The Default SAS Server appears blank or only lists 'Local' instead of SASMain in SAS Server Connections in the SAS Add-In for Microsoft Office (AMO).

From the SAS menu, select Tools, Server Connections and the Default SAS Server is either empty or only has a selection for Local. If you select Connect and then login, it will still be empty or only lists Local. If you select Change and enter credentials, the Default SAS Server will still be empty or only lists Local.

This behavior has been noted under the following two conditions. Both conditions must exist:

1. The AMO 2.1 installation has hotfix 21AMO03 or 21AMO04 applied
2. There is a blank password in the user's login in SAS Management Console, specifically it's the outbound login associated with the Workspace server (the outbound password is blank)

The workaround is to supply a password for the login per the user. If the user has more than one login, then supply a password for the outbound login that is associated with the Workspace server.

Steps for workaround:

1. Open SAS Management Console and select User Manager
2. Double click the user to see the User's Properties
3. Select the Logins tab and select the entry that is associated with the Workspace server - the login that has the same AuthDomain as the Workspace server
4. Add the user's password in both the password prompt and the confirm password prompt
5. Select OK, then OK again to exit the user's properties window

The login that needs the password added is not the login used for initial authentication, but the login that has the same AuthDomain as the workspace server. If the user only has one login being used for both authentication and the Workspace server, then enter a password for that login.

Note: To verify if hotfix 21AMO03 or 21AMO04 has been applied, select the SAS menu, Help, About SAS Add-In for Microsoft Office. If 21AMO03 is applied it will be 2.1.0.265. For 21AMO04, it will be 2.1.0.270.

Select the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for Add-In for Microsoft Office 2.1 is available at: