COGNOiSe.com - The IBM Cognos Community

Legacy Business Intelligence => COGNOS ReportNet => Topic started by: nosnos on 23 Nov 2005 04:24:39 PM

Title: Firewall problem
Post by: nosnos on 23 Nov 2005 04:24:39 PM
Hi,

I have a DPR-ERR-2080 error message : a firewall error prevent me from continuing. States of the error :  "412, 401, 442, 404"

I have already diseable CAF.

Any Idea ?
Thx
Title: Re: Firewall problem
Post by: admin1234 on 26 Nov 2005 04:38:59 AM
Is this intermittent or does it happen all the time?  Have you ever been able to get ReportNet working?

Assuming you have installed the software correctly, and if you have a multi-server installation ensure you have either configured each server's Cognos Application Firewall correctly (in Cognos Configuration) or turned it off on each server machine.

Check your %CRN_INSTALL_DIR%\Cognos\Crn\logs\crnserver.log file for more information about the error, and log a case with Cognos Support.

Cheers,
admin1234


Title: Re: Firewall problem
Post by: nosnos on 01 Dec 2005 11:47:07 AM
Hi ,

It appen all time and I 've never been able to get ReportNet working.

It is a stand alone installation, just for test and Cognos application firewall is turn off.

logs give this :
192.168.0.1 - - [01/Dec/2005:18:43:50 +0100] "GET /p2pd/servlet/dispatch?b_action=xts.run&m=portal/main.xts HTTP/1.1" 200 4242
192.168.0.1 - - [01/Dec/2005:18:43:53 +0100] "GET /p2pd/servlet/gc HTTP/1.1" 503 137.

Any ideas ? Can the problem come from tomcat ?
Title: Re: Firewall problem
Post by: cindyw on 01 Dec 2005 11:36:39 PM
You need to first identify where the problem is.

First, check to see if you content manager is running. Use this URL customized for you environment
http://machinename:port/p2pd/servlet
If thru your browser you get a message that Content Manger is running, you can rule that out. If it says its not running, you have to work thru this to get anywhere. You will not pass "go" without having a running content manager. I'd recommend first logging directly into that db. If you can't log in to that, get ahold of your DBA.

Next, try your dispatchers manually. Use this URL, customized for your environment
http://machinename.com:port/p2pd/servlet/dispatch

If you get a login page, and you can log in, now you know your dispatchers are ok, and the issue is definately on your gateway.

Good Luck!