Time out while deploying..

Hi,

We are using Open Deployment and facing deployment failure....

We are deploying similar files to two different servers and it also involves lots of comarison of file which is very time taking...

We just wanted to know whether time consuming process can be one of the reason for deployment failure.. I mean it's getting times out and so the deployment is getting failed...

Let me know if you need any other information on this...

Thanks & Regards,
Nitesh Ambuj

Find more posts tagged with

Comments

kshitiz

Have you checked the deployment logs? It must show the reason for the deployment failure?

Ambuj

thank you for your reply...

It has some reason but I am not sure that this is the only problem... also I would like to know what is the procedure to change a transactional open deply to filelist based open deploy.. and is there anything we should take care before changing this..

Cheers,
Ambuj Smiley Happy

Ambuj

I'm getting below error..

ERROR: Could not read server status, client OK.
LIB: 2006-11-22 23:39:08 [Wed Nov 22 23:39:08 2006] opendeploy 20061122.1396.2 NT AUTHORITY\SYSTEM COMPLETED //IWSERVER/default/main/boc/group/imss/global/extranet/imss_legacy_extranet/EDITION .imss_legacy_extranet.root.seukbocwb02 seukintwts01 172.23.2.14
LIB: 2006-11-22 23:39:08 [Wed Nov 22 23:39:08 2006] 20061122.1396.2 STATS DEPLOYMENT //IWSERVER/default/main/boc/group/imss/global/extranet/imss_legacy_extranet/EDITION -- .imss_legacy_extranet.root.seukbocwb02 OK
LIB: 2006-11-22 23:39:08 File Content transferred: 0 bytes
ENG: 2006-11-22 23:39:08 GMT+00:00 Thread-258 After CLEANUP, res=1
ENG: 2006-11-22 23:39:08 GMT+00:00 Thread-258 exiting task-failed
ENG: 2006-11-22 23:39:08 GMT+00:00 Thread-258 entering task-failed
ENG: 2006-11-22 23:39:10 GMT+00:00 Thread-258 still waiting for 14

Pawan

I'm getting below error..

ERROR: Could not read server status, client OK.
LIB: 2006-11-22 23:39:08 [Wed Nov 22 23:39:08 2006] opendeploy 20061122.1396.2 NT AUTHORITY\SYSTEM COMPLETED //IWSERVER/default/main/boc/group/imss/global/extranet/imss_legacy_extranet/EDITION .imss_legacy_extranet.root.seukbocwb02 seukintwts01 172.23.2.14
LIB: 2006-11-22 23:39:08 [Wed Nov 22 23:39:08 2006] 20061122.1396.2 STATS DEPLOYMENT //IWSERVER/default/main/boc/group/imss/global/extranet/imss_legacy_extranet/EDITION -- .imss_legacy_extranet.root.seukbocwb02 OK
LIB: 2006-11-22 23:39:08 File Content transferred: 0 bytes
ENG: 2006-11-22 23:39:08 GMT+00:00 Thread-258 After CLEANUP, res=1
ENG: 2006-11-22 23:39:08 GMT+00:00 Thread-258 exiting task-failed
ENG: 2006-11-22 23:39:08 GMT+00:00 Thread-258 entering task-failed
ENG: 2006-11-22 23:39:10 GMT+00:00 Thread-258 still waiting for 14

I think the server side firewall may be restricting or the mismatch of the port numbers might be an issue to consider.

Ambuj

Thanks for your reply pawan.. so if we change the receiver server and then test.. it should work.. right??

Adam Stoller

thank you for your reply...

It has some reason but I am not sure that this is the only problem... also I would like to know what is the procedure to change a transactional open deply to filelist based open deploy.. and is there anything we should take care before changing this..

Cheers,
Ambuj

I think you need to do more reading and perhaps take some training (provided by Interwoven) - transactional and filelist deployments are not mutually exclusive - they're two different aspects of a deployment's properties.

Without know a lot more detail about the server configurations, deployment in question and the requirements surrounding the deployment - it is difficult to suggest potential fixes.