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

 

Packages won't load in Report Studio of Cognos 10.1.1 using MS IE11- new issue

Started by RicardoBach, 05 Jul 2016 02:45:10 PM

Previous topic - Next topic

RicardoBach

We recently began getting tis error, " "Web browser default behaviors are disabled. Some settings will not be preserved[/b]." This happens when we try to launch Report Studio. we can login to Cognos (10.1) fine, but when We try to choose a package the error occurs. (Similarly, if we click on the blue triangle for Report Studio on an existing report, it also occurs. ) we can click on OK on the error, but then the spinning icon never stops spinning, never goes to the page and we need to X out.  We can run existing report just fine. We found an IBM Support article which suggests enabling "Userdata Persistence" in IE11 (which we use exclusively), but the error popup persists. We thought it might have been caused by the recent monthly Microsoft monthly patches, but we cannot determine or isolate which one.  ( We fell back to IE10 on one PC; problem followed it there.) We use Deltek products,  and have a technical support case open with them, but no solution yet, so I thought I'd put it here to seek help from a wider audience. We ARE able to run Report Studio successfully ON the application server using IE11 there. Also, I have a newly installed TEST instance of Cognos 10.2 on a separate server,  and I can run Report Studio without the error there.  on the production We are using MS SQL Server 2008 on Windows Server 2008 R2. (I had posted this in the "Report Studio" group and saw 112 reads and one with a suggestion (welcomed but did not fix our issues) ; I'm just trying to get a wider audience by posting here,  and perhaps one of you has experienced this as well recently,  and have a solution you would share.) Gracias.

sdf

had this before with one of our testing instance.
didn't succeeded in finding out the cause or solution for this.
But, what worked for me before (sometime at least) is cleaning the browser cache.
Also, did killing bibus service and it will work when i relaunch cognos connection.
But this is not recommended specially in a production env. I just did it cos im the only one using it.

anyway, just sharing.. would love to know other inputs regarding this from other users.
But i can say that the issue is with the machine browser coz when i try using other clients i dont face that issue.

sunosoft

QuoteWe recently began getting tis error, " "Web browser default behaviors are disabled. Some settings will not be preserved[/b]." This happens when we try to launch Report Studio. we can login to Cognos (10.1) fine, but when We try to choose a package the error occurs. (Similarly, if we click on the blue triangle for Report Studio on an existing report, it also occurs. ) we can click on OK on the error, but then the spinning icon never stops spinning, never goes to the page and we need to X out.  We can run existing report just fine. We found an IBM Support article which suggests enabling "Userdata Persistence" in IE11 (which we use exclusively), but the error popup persists. We thought it might have been caused by the recent monthly Microsoft monthly patches, but we cannot determine or isolate which one.  ( We fell back to IE10 on one PC; problem followed it there.) We use Deltek products,  and have a technical support case open with them, but no solution yet, so I thought I'd put it here to seek help from a wider audience. We ARE able to run Report Studio successfully ON the application server using IE11 there. Also, I have a newly installed TEST instance of Cognos 10.2 on a separate server,  and I can run Report Studio without the error there.  on the production We are using MS SQL Server 2008 on Windows Server 2008 R2. (I had posted this in the "Report Studio" group and saw 112 reads and one with a suggestion (welcomed but did not fix our issues) ; I'm just trying to get a wider audience by posting here,  and perhaps one of you has experienced this as well recently,  and have a solution you would share.) Gracias.


Did you check this behaviour directly with dispatcher URL ? This will help to isolate the issue from IIS/webserver so that you can investigate in precise direction.

Thanks
SK