Job server doesn't work

[Bubble]

Dear guys
We use Cognos planning 8.4 When I want use Job Server Cluster in Planning - Contributor Administrator i have Error:
HTTP/1.1 407 Proxy Authentication Required~~Proxy-Authenticate: NTLM~~Cache-Control: no-cache~~Pragma: no-cache~~Content-Type: text/html; charset=utf-8~~Proxy-Connection: close~~Set-Cookie: ; Path=/~~Connection: close~~Content-Length: 1934~~~~URL: http://--:9300/p2pd/servlet/dispatch~~Failed to send the SOAP message~~


Please help. Thank you.

[ericlfg]

Looks like there is a proxy in use, but it can't negotiate through it due to authentication issues.

Try taking the dispatcher URI (Http://servername:9300/p2pd/servlet/dispatch) and plug that into a browser on the job server and then do the same from the machine running the CAC service.  This will just help you identify where the problem may be.  You may have to input proxy settings into the browser of the job server to get this to work.

[Bubble]

Where will we look what proxy is used?  If we put URI in browser and log in  we can see web portal Cognos in server and machine with CAC service. If we put proxy settings into the browser - we had the same problem

[ericlfg]

Where will we look what proxy is used?  If we put URI in browser and log in  we can see web portal Cognos in server and machine with CAC service. If we put proxy settings into the browser - we had the same problem

Which server?  On the job server?

Can you please briefly describe your environment -- how many servers you have and their basic function.

Do you have an IT department you can involve?  The error you're experiencing is not a cognos error, but rather an http error I believe to be caused by not having the proxy settings configured correctly in the browser.  You'd find the proxy configuration in IE -> Tools -> Internet Options -> Connections -> Lan Settings.  You will want to compare the settings here with all of the other machines.

[Rutulian]

Hi Bubble,

Eric's absolutely right that you need to be involving your network team here.  If you've got an intercepting proxy that picks up all traffic on port 80, they may need to make changes to the proxy config.  One way to avoid this would be to disable proxy routing for all addresses starting with SERVERNAME (you'll need to make sure all dispatchers are excluded, not just the web server).  If it's a non-intercepting proxy, you should be able to set it as Eric outlines in the last post.

From the proxy logs a network tech should be able to tell you why authentication is failing - sometimes this can be fairly easily remedied without having to set up new exclusions, I've seen instances in the past with SQUID-using-NTLM-auth where the Cognos service account just needed to be added to the proxy's list of permitted users.

Kind Regards,
Alexis Lawrence

[Bubble]

Thank you for all. Please tell, why cognos adm. contributor use proxy(internet) for his work, why he does't use internal network

[Rutulian]

Hi Bubble,

You'd have to ask IBM for a definitive answer, but I'd imagine that it's because we're a service oriented architecture with all traffic over port 80.  I don't know if windows forces you to pick up IE settings for HTTP communications or if this was a choice the dev teams made.  Either way, it should be possible to put a proxy exception in once you find the right network guys... Alternatively I'm sure there are plenty of Tech consultants out there who'd be glad to pick up a couple of days' install & config work, if you've got a complicated environment it will be well worth having experienced eyes over the system at an early stage so any changes recommended can be costed and considered before you hit production.

Cheers,
Alexis

[Bubble]

Thank you for you replay. I value your help.