Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

When logging into SAS Web Report Studio you might see this error message:

The authentication system is not responding. Please contact your system administrator.

The SAS Web Report Studio log contains the following error message:

Personal Folders created, new logon needed(Reason : User repository cache is stale, a new logon is recommended.)

Additional attempts to log in to SAS Web Report Studio result in unexpected application behavior such as view-only access or errors that the user name and password do not match the current session.

In nearly all cases, this problem is caused by incorrect permissions on critical user folders in the BIP Tree structure.

Note: Depending on why this problem occurs in your environment, this error might start appearing after a hot fix installation. The hot fix itself does not cause the problem. Instead, the newer release of SAS Web Report Studio is more explicitly identifying a problem with incorrectly defined folder permissions.

Resolving the Error for Individual Users

To resolve the issue when it occurs for an individual user, perform these steps:

1. Log into SAS Management Console with the sasadm account.
2. Select Environment Management ► User Manager.
3. In the right pane, right-click on the user's name and select Properties.
4. Click the Logins tab and examine the user's credentials. Here are some items to look for:
   • If the log mentions an authentication domain associated with the user, then make sure that same authentication domain is displayed in the Authentication Domain field.
   • If the user ID must be fully qualified with a host name, make sure that you are using the correct slash (forward or backward).
   • If there are multiple logins shown, delete any logins that are not needed.
5. Save any corrections that you make to the login.
6. Expand BI Manager ► BIP Tree ► ReportStudio ► Users.
7. Delete the folder that corresponds with the user who is having the problem. For example, if the user is sasdemo, then delete the folder named "sasdemo."
8. Restart your servlet container (Tomcat, WebSphere, or WebLogic).

The next attempt to log into SAS Web Report Studio should be successful, and a new personal folder should be created for the user. However, if the user is still getting the authentication error, then perform these additional steps:

9. Log back into SAS Management Console with the sasadm account.
10. Open the properties for the user's new folder and click the Authorization tab. It is likely that the user is not listed on this tab. Add the user and explicitly grant at least ReadMetadata (RM) and WriteMetadata (WM) on the folder.

Note: For an explicit permission, the check box has a white background . For an inherited permission, the check box has a gray background  .

11. Restart your servlet container (Tomcat, WebSphere, or WebLogic).

Resolving the Error for All Users

Have passwords recently changed?

If you are encountering this problem after a password change, then it is possible that the password in the metadata login for the SAS Web Administrator no longer matches the password currently valid for the type of authentication mechanism that you are using (for example, you might be using host authentication).

As a test, attempt to log into SAS Management Console with the SAS Web Administrator credentials. If he logs in successfully, look on the status bar at the bottom right corner of the application. If the SAS Web Administrator is logged in as PUBLIC, then log out of SAS Management Console and log back in as an unrestricted user (typically, sasadm).

Under the User Manager plug-in, open the properties for the SAS Web Administrator, click the Logins tab, and re-enter the password, making sure to use the password that is currently valid for the type of authentication that you are using.

Restart your servlet container (Tomcat, WebSphere, or WebLogic).

Check to see if the problem is now resolved in SAS Web Report Studio. If the problem is not resolved, then continue with the next section.

Note: For more information about the importance of the SAS Web Administrator account, see SAS Note 35115 .

Verify permissions on critical folders

If you verified that the login for the SAS Web Administrator account is correct, then check folder permissions on the folder structure in Figure 1, as described next.

Figure 1. This is the folder structure referred to in the following instructions.

1. Navigate to Environment Management ► BI Manager ► BIP Tree.
2. Right-click on BIP Tree, select Properties, and then click the Authorization tab.
3. Select SAS System Services and view the permissions. This group must have an effective grant of RM on the folder.

Note: Effective permissions are a calculation of the net impact of all applicable permission settings in the metadata layer. If you see a gray background for the permission in the Grant column, then select the box once. If the check mark is removed, then the user does not have effective permissions. Click the box again to make the permission explicit.

4. With SAS System Services still selected, click the Properties button and view the Members tab. Make sure that the SAS Web Administrator account is a member of this group. This is a read-only display. So, if SAS Web Administrator is not a member of this group, then, when you are done checking permissions, use the User Manager plug-in to add him as a member.
5. Beneath BIP Tree, right-click on the ReportStudio folder, select Properties, and then click the Authorization tab.
6. Select SAS System Services and view the permissions. This group must have an effective grant of RM on the folder.
7. Beneath ReportStudio, right-click on the Users folder, and then click the Authorization tab.
8. Check permissions for the following users:
• Select SAS System Services and view the permissions. This group must have an effective grant of RM and WM on the folder.
• Select SASUSERS and view the permissions. This group must have an effective grant of RM on the folder.
9. Beneath Users, right-click on each user's personal folder, click the Authorization tab, and view the permissions for SAS System Services and for the user who owns the folder. Both the group and the user must have RM and WM effectively granted. The user's permissions should be explicit (white background).
10. Restart your servlet container (Tomcat, WebSphere, or WebLogic).

Next Steps

If the above suggestions do not resolve your problem, then refer to SAS Note 32616 and SAS Note 33273 . These notes discuss authentication issues that are related to an incorrectly defined SAS Profile.

Operating System and Release Information