Could not connect to deployment dervice. TCP Error Code 10060.

John Hartley
John Hartley
in AppWorks #1

Hi All,

 

Requesting a little help... Its been a little while since I've done any metastorm development. However, in the last few weeks I was trying a few things out and I now have problems deploying (any) solution to our build server (which previously worked fine for us).

 

If I try to deploy to my local machine it works fine.

 

When I attempt to deploy to build however I get the attached "Could not connect to deployment service / TCP 10060" error.

 

I've tried: stopping and starting the Deployment service on my machine (client) and this doesn't fix it. I've also tried changing the service account log on detail to 'local' from the custom ad login which from memory occasionally worked when I had deployment service problems previously but this does nothing. Both accounts however deploy fine to my local machine. I've proxied onto the build server and can find no sign of any error in the windows event log that anything has failed or even that I've managed to connect to the machine.

 

A colleague has had similar problems (and I think the same error) so that to me would suggest there is a problem with the server rather than the service account or client.

 

Any ideas/thoughts ? I've seen a slightly similar posting regarding a TCP Error Code 10061, but the advice on that was to change the deployment service to a local account which I've tried...

 

I am running Metastorm 9.1.0.2 on Windows 2008 R2.

 

Thanks John

Tagged:

Comments

  • achopra
    achopra
    #2

    Have you checked the deployment service on the server to make sure it is running properly?

  • John Hartley
    John Hartley
    #3

    Unsure Ari. Its weird, our Data Centre team maintain that server and its architecture so I must admit I am not intimate with it (have passed it over to them also for the moment), but when I proxy on there are no metastorm services I can see. Neither a process engine or a deployment service. 

     

    Yet in the browser, all the pages and administration are served up correctly.

     

    It may be that it is a split architecture over 2 machines and I'm logged onto the wrong one, as I know that is the case for staging and live. Although build I thought was the same as our local environment.

     

    I'll try to get some of there time and get back to you.

  • Jacob_Eastman
    Jacob_Eastman
    #4

    The error is due to your Designer machine not being able to connect to the deployment service running on the server on port 808.

     

    First, make sure that the Deployment Service is actually running on port 808. It should throw an error when starting the service if the port is already taken, but I've seen strange things happen. To do this, run the following in a command prompt:

     

    netstat -nao | find ":808"

     

    This will give you a list of any processes connecting or listening on that port. Take the PID and check that it is the DeploymentService.exe via Task Manager.
     

    If it is correctly listening on port 808, then the issue is due to networking, likely a firewall. As a test, you can try telnetting to the BPM server on port 808 to see if you can connect.

     

    If the service is NOT running on 808, or another service is, then I'd recommend opening a support ticket so we can help you with this nonstandard configuration or error.

  • Jerome_Pearce
    Jerome_Pearce
    #5

    So you have a deployment service on your local machine, and one on the server? Then restarting the deployment service on the local machine (as you tried) will have no effect at all on deploying to the remote server.

     

    The first question I would ask is if the designer on your machine is the exact same version as the deployment service and engine on the remote server. This is one of the three major issues encountered when using multiple deployment services from one Designer instance.

  • John Hartley
    John Hartley
    #6

    This was in fact a basic deployment service issue, in that had simply stopped running. It was split architecture also so I was proxied onto the wrong machine.

Categories

image
OpenText CE Products
AppWorks
Gateway & Platform