"Not allowed" message in NovaView web applications

Contents
"Not allowed" message in NovaView web applications
Scenario

There are many reasons that may cause this message, therefore the reason for it should be first identified before the solution applied.

Common scenarios:

 

  1. Client side error - this user should not see this data (happens within single user or group of users)
  2. Client side error - the users roles or permissions were changed on server side (happens within single user or group of users)
  3. Client side issue - the credentials are not passed by the browser (happens within single user or group of users)
  4. Server side issue -  the credentials are not approved by IIS (the error will appear for all users)
  5. Server side - data source is down or not availible (the error will appear for all users)
  6. Server side issue - there's an error in this view (the error will appear for all users)
  7. Inconsistent "Not allowed" error

 

Steps

A. Client side error - this user should not see this data

  1. Log on to client machine with different user, which verified as able to see the information (Administrator for example)
  2. Open NovaView Administrator on Panorama server and user "Run Web Access as.." on same book
  3. Use the Event Log to see the background message of "Not allowed" for this user.

B. Client side error - the users roles or permissions were changed on server side

  1. Run test .. from previous step. With a result of "now allowed" proceed to next step.
  2. Open SQL Management Studio on Panorama server and browse the cube
  3. Use the "Impersonate" button to see if the Role hat the tested user belongs too, can see the data
  4. Synchronize the roles using NovaView Administrator using the book

C. Client side issue - the credentials are not passed by the browser

  1. Make sure you have all client pre-requisites set correclty
  2. Add Panorama server name under "Trusted sites" on every client machine
  3. When using Windows Integrated Authentication, you need to make sure the option "Automatic Logon with Current Username and Password" is checked.

D. Server side issue -  the credentials are not approved by IIS

  1. Access Web Access by the address http:///panorama.welcome.htm instead of standard server name.
  2. Access Web Access by the address http://panorama.welcome.htm instead of standard server name or vise versa
  3. If one of them works, this should be IIS issue, and the solution is here.

E. Server side - data source is down or not availible

  1. Perform a UDL test to selected data source from Panorama server. If the test unsuccessful, means the cube currently being processed or not deployed. If the test shows "connection succeded" go to next step.
  2. Use the Event Log to see the background message of "Not allowed"

F. Server side issue - there's an error in this view

  1. Open the view using "Run Desktop as Administrator" from NovaView administrator. The view opens correctly, go over other scenarious, use the Event Log to see the real message. If the view would not open, or open with error, proceed to step 2.
  2. Recreate the view from scratch, save in the book and preview within Desktop client.
  3. Whether step 2 is unsuccessful, browse the cube with the same dimensions as used in a view. There's a possibility that something is wrong with cube structure.
  4. If view or book name contain special ASCII characters, this can result in "Not allowed" error for the user. Follow this article to resolve.

Inconsistent "Not allowed" error

This one is most difficult to track and resolve. It might be related to: special characters in cube entities, inconsistent drivers version of OLAP connectivity an many more. To resolve this, support will request the Application Event log, IIS log for the correct and incorrect behviour under same circumstances, in working and non-working state, your server configuration, registry keys export and in some very particular cases, your cube and view example.

Version
  • All versions
 
Free business joomla templates