Converter Standalone Agent installation failed (Error Code: 1618)

[jbriggs3]

I have two pretty much identical Windows 2000 servers that I am doing P2V conversions using Converter 4.0.1

My first server converted without any problems...however, my second server gets to the Converter Standalone Agent deployment and then fails with an error message "Converter Standalone Agent installation failed on 'XXX.XX.XXX.XXX'. Error Code: 1618.

I have used Port Query against the ports that are indicated in support document 1010056 and noticed that port 9089 is "listening" on the first server but "not listening" on the second server...I suspect this is the problem, but I have no idea how to resolve it...how do I go about making port 9089 a "listening" port?

[admin]

I found this KB article that looks like your problem. http://kb.vmware.com/kb/1021465

Rick Blythe

Social Media Specialist

VMware Inc.

[pcerda]

Hi,

Both of servers are in the same subnet?

Check the network requirements for vCenter Converter:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101238...

On the second server, check out the logs of Converter Installer located at:

C:\Program Files\VMware\VMware vCenter Converter Standalone\logs\




Regards / Saludos

-

---

Patricio Cerda !http://www.images.wisestamp.com/linkedin.png!

VMware VCP-410

Join to Virtualizacion en Español group in Likedin

See My Blog

See My Linkedin Profile

-

---

Si encuentras que esta o cualquier otra respuesta ha sido de utilidad, vótalas. Gracias.

If you find this or any other answer useful please consider awarding points by marking the answer helpful or correct. Thank you.

[jb61264]

Well...interestingly enough, the issue posted here had to do with the server thinking it was in the middle of another installation?...When I went to install the converter agent directly on the server console, I was getting error messages stating that another installation was already in process, etc...when I went to review log files, it appeared as though it had to do with .NET as there were process failures indicating .NET as the problem...so I decided to update my server (using Windows/Update through IE) and there were .NET updates that showed as being necessary...I did the updates, restarted the machine and everything installed just fine after that.