CMC - set QaaWS security....grayed out

other Xcelsius - Crystal Dashboard Design
1

XI3.1 SP3 FP3.3
In CMC, under QaaWS.
After I go into QaaWS area, to create folders to store queries, or manage user security to grant rights, I can’t becase that toolbar is grayed out. I am using “Administrator” account, which has Full Control against QaaWS.

This is weird because it’s only happening in my Prod environment.
Works fine in my Dev and QA environments, which are all at the same version / patch level.

Any ideas?

ccermak :us: (BOB member since 2007-11-13)

2

I have a similar issue on BOE XI 3.1 SP4 on the CMC. When I click “User Security” on either the Qaaws root folder or a Qaaws folder, I get “The webpage cannot be displayed” page.

This is only happening on one of two SIAs that are running on the same Business Objects server.

I am able to create Qaaws folders, though.

I submitted a support case with SAP. I’ll post back with their solution (I’m trying to be positive :slight_smile: )

amedinak (BOB member since 2007-09-05)

3

I got my issue resolved, by redeploying the dswsbobje war file. Seems that somehow it was ok on some servers in the cluster but not all. I have a large environment, with 4 tomcat servers, and it was working ok on 2 servers and not on the other 2. I redeployed on the 2 failing servers and issue is now resolved. Found this by trying the CMC from each individual Tomcat server and noticed it all of a sudden worked ok when I switched to certain server. Not sure why this happened since my install routine was the same on all, and they’re all similar Windows servers, but redploying seemed to fix. It was actually SAP support that helped me on this one…first time for everything!!! :rotf:

ccermak :us: (BOB member since 2007-11-13)

4

I worked with SAP support to fix my issue. The cause of my issue was a corrupt database as it relates to qaaws. According to SAP, this is a known issue that has been around for a while, since BOE XI 3 sp1. I’ll leave it up to the forum administrators to determine if the steps below can be shared with the forum or not:

  1. Make a backup of the CMS database.
  2. Get the from CMC.
    **** Do this by hovering over the Qaaws folder in the CMC and capturing the uniqueID.
  3. Get the name and port of the CMS (from CMC or CCM) and the name of
    the node (i.e. the SIA name).
  4. Stop the SIA.
  5. Open a command-prompt window (Start->Run->cmd)
  6. Change directory to the win32_x86 directory.
  7. Run the following command-line: CMS.exe -serverconsole -name
    -port -dbinfo boe.dbinfo
    To view the acl of the object (QaaWS folder), type:
    acl .

One of the entries there has a principal that’s not a user or group #
it is a MetaData.DataDBField called “Customer ID”.

*** As I understand it, for qaaws, the User/Group numbers should be less than 100. So, in the example below, the one with the problem is the last row: user/group 397

User/Group 1 Right 1555 0 for any object type for this object
User/Group 1 Right 1555 0 for any object type for descendant object
User/Group 2 Role 20416
User/Group 397 Role 20416

The command to remove the offending entry is:
removerole <user/group ID> (Ex. removerole 399
71880 23724708)
**** In my example, the command would be: removerole 397 115 20416

  1. Enter quit. This will exit the cms command session.
  2. Start SIA and verify the problem is resolved.

Alba

amedinak (BOB member since 2007-09-05)

5

Always a fun one getting deep into the weeds of the cms db. You must’ve finally found the support guy with the thick glasses who they keep locked up in the basement with a case of red bulls. :shock:

ccermak :us: (BOB member since 2007-11-13)