If you are unable to create a new account, please email support@bspsoftware.com

 

When Open Workspace Advance the endless pop-up looping

Started by chipslam, 10 Oct 2014 03:30:23 AM

Previous topic - Next topic

chipslam

Hi Everyone,

does anyone has an experience, when open the Workspace, after i click "Blank" or "List", the workspace will keep popup and close the popup itself. It will keep on popup and close, until i close the whole IE.

When i view the log, it show
********************************************************************
RSV-SRV-0030 The user does not have the assigned capability to use HTMLItem.   
********************************************************************
I have check this error, and follow ibm example to add capability (Execute & Traverse )in
IBM Cognos Adminstration -> Security -> Cability -> Report Studio
IBM Cognos Adminstration -> Security -> Cability -> Report Studio -> HTML Item in Report

My Cognos Server Config
Window 2008 r2,

My Client Machine
Window 7, I have try IE 10, IE 9 , Chrome, Firefox, also has this issue.

And, now i have a new founding, there an error message in the workspace, and an url "Open design view" inside open in Workspace,
during the pop up looping, if i click url "Open design view" many time, the design view will show the empty list, the popup will stop show.
But, if i delete the empty list again, the pop up will show again!

Thanks everyone first!!

tinocash

Hello,

Did you find a fix to this problem? I am currently having the same issue in Workspace Advanced Cognos 10.2.

I also followed ibm fix to add capabilities (Execute & Traverse ) to
IBM Cognos Adminstration -> Security -> Cability -> Report Studio
IBM Cognos Adminstration -> Security -> Cability -> Report Studio -> HTML Item in Report

Jlloyd666

Hi,

Has any progress been made with this, I have a similar sollution, someone is suggesting this is something to do with the IIS setup and duplicate hander mapping settings.

Jlloyd666

Hello,

I thought id add my sollution to this so it might benefit thr forum. THis looking issue seemed to be caused by multiple handler ISAPI files created during the IIS 7 setup. We recreated the default website from scratch making sure that the ISAPI handler mapping only existed at the CGI-BIN Application level. I hope this helps someone in the future.

Regards