That error is a generic catch all. If iwodcmd cannot connect to the daemon, then it returns a 256.You will need to peruse the OD server logs for more details.Andy
Since the deployement didnot start ,I cannot check the OD logs for the same.And the error by running the OD command on command line is "Reason from server: SERVER_INITIATORDetails : Fail to get server initator. It was null.Thanks,Natasha
If the deployment didn't start then you will not find deployment logs but still you can check the od logs and od error logs for any other specific information.
Could you please tell me the location for OD logs and OD error logs... if the OD has not been started or initiated.
If deployment has started then the logs will be created under \iw-home\OpenDeployNG\log directory...but od.log file exists at \iw-home\OpenDeployNG..It may contain some useful information.. Correct me if my understanding is wrong...
Mentioning the OD has not been initiated .. how could one can get the logs with OD log directory? The only way to track the error... is to check the logs of your customised script or run the command as CLT.What i can get out of post.. that receiver server has not responded properly to the OD request.
If this is the case (receiver server has not responded properly to the OD request)... then don't we have any way to check any log... or can't we get any information as why this is happening??
Take help from OD server administrator.
Ok I will check this out as now I’m curious to know about it in details. Thanks & Regards,Nitesh Ambuj
Not sure If this is the solution for the issue but I restarted the OpenDeploy and re-deployed. It works now!Sarang
