DPR-ERR-2080 : Firewall problem

[Nosnos]

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

 

[JGirl]

I would check in your config that all your references to gateways etc are the same (eg. you arent using MACHINENAME in one instance, and localhost for another reference to the same machine)

A bit more info about what you were doing when you got the error would also help

J

 

[christenhusz]

i have seen this once on a unix box.

solved this with a umask 022 on the cerx directory. if it is a windows machine verify if the user has suffient rights

christenhusz

 

[vzak]

I would check if there is no problem with Content Store.

Vlad

 

[MeatballB]

I'm getting the exact same error message. I had run a sysprep on the machine and then run an image of it. When I brought it back up and reconfigured it I started getting that error on attempting to connect to RN on the machine.

Previously a programmer had upgraded to MR2 as well, so I'm not sure which is the specific cause.

I've checked that the CAF is disabled, have also replaced some Java files as suggested in their KB article # 1013662 to no avail.

Anyone else get this figured out?

 

[Nosnos]

Hi ,

- All my references to gateways are same
- I am on a windows machin with no rights consideration
- I haven't yet deal with Content store, because I suppose that if ReportNet couldn't start, the database is useless.
- 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 ?

 

[vzak]

Check your configuration. Your Content Store is located in your DB. ReportNet will nor start if you don't specify proper connection to CS or DB is down.

Vlad

 

[cindyw]

You need to first identify where the problem is.

First, check to see if you content manager is running. Use this URL in 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!