VMware Cloud Community
dragon632
Contributor
Contributor
Jump to solution

Windows could not start the VMWare vCenter Converter

I'm using vCenter Converter standalone on a Windows 2008 server SP2.

In windows services panel, I found all the services of vCenter converter (Agent, Server and Worker) are not started.

When I was trying to start them manually, I got an error message saying "Error 1053: The service did not respond to the start or control request in a timely fashion".

I've already added an entry [ServicesPipeTimeout] in my registry [HKLM\SYSTEM\CurrentControlSet\Control], and I set its value to 3000000000.

However, after I restarted the computer, these services still can't start. The error message was the same as before.

Anyone can help  ?

1 Solution

Accepted Solutions
POCEH
VMware Employee
VMware Employee
Jump to solution

Can you confirm that your machine has not internet access?

What about Event log messages?

View solution in original post

Reply
0 Kudos
25 Replies
patanassov
VMware Employee
VMware Employee
Jump to solution

Hello,

The hack with increasing service start timeout is when the machine is in an isolated network (no internet access). Is that the case?

The value is in milliseconds. A recommended value for that case is about 5min, i.e. 300 000. A value of 3 000 000 000 (3 bln) looks way too big.

What does the event viewer say about these service start failures? Is there anymore info? Is there anything in Converter logs? (they are located in %ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\logs)

Regards,

Plamen

Reply
0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

VMware vCenter Converter Standalone 6.2.0.1 Release Notes

General

  • Converter Standalone fails to start when installed on a computer without internet accessAfter you install Converter Standalone on a computer without internet connection, Converter Standalone services fail to start. The following message is displayed:
    Error 1053: The service did not respond to the start or control request in a timely fashion.
    This issue occurs because the DNS server is not able to resolve host names online and the file integrity check exceeds the default timeout of 30 seconds due to failed access to public certificate authority stores.
  • Workaround 1:
    Open HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control in the Windows Registry Editor and create or modify a ServicesPipeTimeout DWORD32 decimal value to at least 300000 (5 minutes). Restart the system for the changes to take effect.
  • Workaround 2:
    Install the VeriSign Class 3 Public Primary Certification Authority - G5 root certificate in the local Trusted Root Certification Authorities store. See KB 67429

ARomeo

Blog: https://www.aleadmin.it/
Reply
0 Kudos
dragon632
Contributor
Contributor
Jump to solution

Hi,

Thanks for your reply.

I tried both of your workaround, but none of them can work.  I still got the error message "Error 1053: The service did not respond to the start or control request in a timely fashion." when starting the service (Server / Agent / Worker)

The logs folder "C:\ProgramData\VMware\VMware vCenter Converter Standalone\logs" has no log files but an empty folder "bundles".

What can I do next ?

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

Can you confirm that your machine has not internet access?

What about Event log messages?

Reply
0 Kudos
dragon632
Contributor
Contributor
Jump to solution

>Can you confirm that your machine has not internet access?

>What about Event log messages?

Thank you for reminding me the internet access is still available.

There's a little complicate with my machine. It has restricted internet connection. It can connect to DNS server but it cannot connect to other internet website.

Anyway, the error 1053 is now disappear.

But I got another error "Error 1067: The process terminated unexpectedly".  The following is the log.

2019-09-25T16:18:06.240+08:00 Section for VMware vCenter Converter Standalone, pid=8008, version=6.2.0, build=8466193, option=Release

2019-09-25T16:18:06.244+08:00 verbose vmware-converter-server[07556] [Originator@6876 sub=Default] Dumping early logs:

2019-09-25T16:18:06.244+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] Logging uses fast path: true

2019-09-25T16:18:06.244+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] The bora/lib logs WILL be handled by VmaCore

2019-09-25T16:18:06.244+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] Initialized channel manager

2019-09-25T16:18:06.244+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] Current working directory: C:\Program Files\VMware\VMware vCenter Converter Standalone

2019-09-25T16:18:06.244+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] ThreadPool windowsStackImmediateCommit = true

2019-09-25T16:18:06.245+08:00 info vmware-converter-server[03380] [Originator@6876 sub=ThreadPool] Thread enlisted

2019-09-25T16:18:06.245+08:00 info vmware-converter-server[07724] [Originator@6876 sub=ThreadPool] Thread enlisted

2019-09-25T16:18:06.245+08:00 info vmware-converter-server[07556] [Originator@6876 sub=ThreadPool] Thread pool on asio: Min Io, Max Io, Min Task, Max Task, Max Concurency: 1, 121, 2, 60, 2147483647

2019-09-25T16:18:06.245+08:00 info vmware-converter-server[07556] [Originator@6876 sub=ThreadPool] Thread enlisted

2019-09-25T16:18:06.245+08:00 info vmware-converter-server[07360] [Originator@6876 sub=ThreadPool] Thread enlisted

2019-09-25T16:18:06.245+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] Trying converter_server

2019-09-25T16:18:06.289+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] Trying ufa_agent

2019-09-25T16:18:06.297+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] [shutdownMgr,25] Ufa shutdown manager registered.

2019-09-25T16:18:06.297+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] [helper,454] Initializing SSL Contexts

2019-09-25T16:18:06.317+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Libs] FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)

2019-09-25T16:18:06.318+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Libs] FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)

2019-09-25T16:18:06.318+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Libs] FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)

2019-09-25T16:18:06.318+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Libs] FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)

2019-09-25T16:18:06.319+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Libs] FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)

2019-09-25T16:18:06.319+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] Vmacore::InitSSL: handshakeTimeoutUs = 20000000

2019-09-25T16:18:06.322+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] [helper,507] Initializing certificates

2019-09-25T16:18:06.324+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] [task,2069] [LRO] 32 max LROs

2019-09-25T16:18:06.324+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] [task,2071] [LRO] 6 reserved internal LROs

2019-09-25T16:18:06.324+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] [task,2073] [LRO] 6 reserved short LROs

2019-09-25T16:18:06.324+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] [task,2075] [LRO] 12 reserved long LROs

2019-09-25T16:18:06.324+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] [task,2087] [LRO] 86400-second task lifetime

2019-09-25T16:18:06.332+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] Delay loading resources: path (C:\Program Files\VMware\VMware vCenter Converter Standalone\locale\) locale (en) removeable (false) resmap (01dd1038) extKeys (00000000)

2019-09-25T16:18:06.333+08:00 warning vmware-converter-server[07556] [Originator@6876 sub=Locale] Duplicate key 'hi_IN' in file 'C:\Program Files\VMware\VMware vCenter Converter Standalone\locale\iso2win.vlcl', only first one is used

2019-09-25T16:18:06.333+08:00 warning vmware-converter-server[07556] [Originator@6876 sub=Locale] Duplicate key 'az_AZ' in file 'C:\Program Files\VMware\VMware vCenter Converter Standalone\locale\iso2win.vlcl', only first one is used

2019-09-25T16:18:06.334+08:00 warning vmware-converter-server[07556] [Originator@6876 sub=Locale] Duplicate key 'sr_SP' in file 'C:\Program Files\VMware\VMware vCenter Converter Standalone\locale\iso2win.vlcl', only first one is used

2019-09-25T16:18:06.334+08:00 warning vmware-converter-server[07556] [Originator@6876 sub=Locale] Duplicate key 'az_AZ' in file 'C:\Program Files\VMware\VMware vCenter Converter Standalone\locale\isodata.vlcl', only first one is used

2019-09-25T16:18:06.335+08:00 warning vmware-converter-server[07556] [Originator@6876 sub=Locale] Duplicate key 'sr_SP' in file 'C:\Program Files\VMware\VMware vCenter Converter Standalone\locale\isodata.vlcl', only first one is used

2019-09-25T16:18:06.335+08:00 warning vmware-converter-server[07556] [Originator@6876 sub=Locale] Duplicate key 'uz_UZ' in file 'C:\Program Files\VMware\VMware vCenter Converter Standalone\locale\isodata.vlcl', only first one is used

2019-09-25T16:18:06.336+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] Added locale path C:\Program Files\VMware\VMware vCenter Converter Standalone\locale\ to locale map

2019-09-25T16:18:06.336+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] Delay loading resources: path (C:\Program Files\VMware\VMware vCenter Converter Standalone\coreLocale\) locale (de) removeable (false) resmap (01dd92b0) extKeys (00000000)

2019-09-25T16:18:06.336+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] Delay loading resources: path (C:\Program Files\VMware\VMware vCenter Converter Standalone\coreLocale\) locale (en) removeable (false) resmap (01dd1038) extKeys (00000000)

2019-09-25T16:18:06.336+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] Delay loading resources: path (C:\Program Files\VMware\VMware vCenter Converter Standalone\coreLocale\) locale (fr) removeable (false) resmap (01dd92d0) extKeys (00000000)

2019-09-25T16:18:06.336+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] Delay loading resources: path (C:\Program Files\VMware\VMware vCenter Converter Standalone\coreLocale\) locale (ja) removeable (false) resmap (01dd92f0) extKeys (00000000)

2019-09-25T16:18:06.336+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] Delay loading resources: path (C:\Program Files\VMware\VMware vCenter Converter Standalone\coreLocale\) locale (zh_CN) removeable (false) resmap (01dd9310) extKeys (00000000)

2019-09-25T16:18:06.336+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] Added locale path C:\Program Files\VMware\VMware vCenter Converter Standalone\coreLocale\ to locale map

2019-09-25T16:18:06.337+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] Delay loading resources: path (C:\Program Files\VMware\VMware vCenter Converter Standalone\vimLocale\) locale (de) removeable (false) resmap (01dd92b0) extKeys (00000000)

2019-09-25T16:18:06.338+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] Delay loading resources: path (C:\Program Files\VMware\VMware vCenter Converter Standalone\vimLocale\) locale (en) removeable (false) resmap (01dd1038) extKeys (00000000)

2019-09-25T16:18:06.338+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] Delay loading resources: path (C:\Program Files\VMware\VMware vCenter Converter Standalone\vimLocale\) locale (fr) removeable (false) resmap (01dd92d0) extKeys (00000000)

2019-09-25T16:18:06.340+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] Delay loading resources: path (C:\Program Files\VMware\VMware vCenter Converter Standalone\vimLocale\) locale (ja) removeable (false) resmap (01dd92f0) extKeys (00000000)

2019-09-25T16:18:06.341+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] Delay loading resources: path (C:\Program Files\VMware\VMware vCenter Converter Standalone\vimLocale\) locale (zh_CN) removeable (false) resmap (01dd9310) extKeys (00000000)

2019-09-25T16:18:06.341+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] Added locale path C:\Program Files\VMware\VMware vCenter Converter Standalone\vimLocale\ to locale map

2019-09-25T16:18:06.349+08:00 warning vmware-converter-server[07556] [Originator@6876 sub=Locale] Requested locale '' and/or derived locale 'Chinese_Hong Kong' not supported on OS. Using English.

2019-09-25T16:18:06.349+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] Locale subsystem initialized from C:\Program Files\VMware\VMware vCenter Converter Standalone\locale\ with default locale en.

2019-09-25T16:18:06.351+08:00 warning vmware-converter-server[07556] [Originator@6876 sub=Locale] Requested locale '' and/or derived locale 'Chinese_Hong Kong' not supported on OS. Using English.

2019-09-25T16:18:06.351+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] LoadResources path (C:\Program Files\VMware\VMware vCenter Converter Standalone\locale\) locale (en) removeable (false) resMap (01dd1038) extKeys (00000000)

2019-09-25T16:18:06.360+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] LoadResources path (C:\Program Files\VMware\VMware vCenter Converter Standalone\coreLocale\) locale (en) removeable (false) resMap (01dd1038) extKeys (00000000)

2019-09-25T16:18:06.361+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Locale] LoadResources path (C:\Program Files\VMware\VMware vCenter Converter Standalone\vimLocale\) locale (en) removeable (false) resMap (01dd1038) extKeys (00000000)

2019-09-25T16:18:06.503+08:00 warning vmware-converter-server[07556] [Originator@6876 sub=Locale] Key 'Internal.Tasks.SingleSpacedList' in module 'task' under 'C:\Program Files\VMware\VMware vCenter Converter Standalone\vimLocale\en/' was previously defined; ignored

2019-09-25T16:18:06.532+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Libs] [ADS] Failed to get host ADS object in ACE initialization (0x80070057)

2019-09-25T16:18:06.532+08:00 warning vmware-converter-server[07556] [Originator@6876 sub=Libs] Failed to initialize active directory

2019-09-25T16:18:06.532+08:00 error vmware-converter-server[07556] [Originator@6876 sub=Default] [user,280] Failed to initialize Active Directory

2019-09-25T16:18:06.532+08:00 error vmware-converter-server[07556] [Originator@6876 sub=Default] [plugin,149] ServerPlugin Init failure

2019-09-25T16:18:06.557+08:00 info vmware-converter-server[07556] [Originator@6876 sub=Default] CoreDump: Writing minidump

2019-09-25T16:18:08.711+08:00 panic vmware-converter-server[07556] [Originator@6876 sub=Default]

-->

--> Panic: TerminateHandler called

--> Backtrace:

-->

--> [backtrace begin] product: VMware vCenter Converter Standalone, version: 6.2.0, build: build-8466193, tag: vmware-converter-server

--> backtrace[00] vmacore.dll[0x0017D73D]

--> backtrace[01] vmacore.dll[0x00051604]

--> backtrace[02] vmacore.dll[0x000528D1]

--> backtrace[03] vmacore.dll[0x00198100]

--> backtrace[04] vmacore.dll[0x001981E7]

--> backtrace[05] vmacore.dll[0x0019B15A]

--> backtrace[06] vmware-converter.exe[0x000012E8]

--> backtrace[07] kernel32.dll[0x000A1064]

--> backtrace[08] ntdll.dll[0x000783B3]

--> backtrace[09] ntdll.dll[0x00041502]

--> [backtrace end]

-->

Could you help to check this ?

Reply
0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

Have you tried removing it and reinstalling it?

The "Vmware vCenter Converter Standalone Server" Service is based on the workstation service ... verifies that all dependencies are activated.

ARomeo

 

Blog: https://www.aleadmin.it/
Reply
0 Kudos
dragon632
Contributor
Contributor
Jump to solution

Now, the agent and worker services is running normally. The server services is repeatedly restarted due to the error that I mentioned above.

How to check the dependencies of the server service ?

Thanks.

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

Unfortunately server crashes (repeatedly). As an option: stop the server service and convert machine via Converter Agent (from other machine with Converter choose Powered on Windows Machine).

HTH

Reply
0 Kudos
Alex_Romeo
Leadership
Leadership
Jump to solution

Hi,

pastedImage_0.png

ARomeo

Blog: https://www.aleadmin.it/
Reply
0 Kudos
dragon632
Contributor
Contributor
Jump to solution

Hi,

>As an option: stop the server service and convert machine via Converter Agent (from other machine with Converter choose Powered on Windows Machine).

Do you mean the target Windows machine just needs to run Agent and Worker service, and I can run the server service on another PC ?

Is that also mean the target Windows machine will be converted to Virtual Machine and transferred to the PC which is running the server service ?

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

Yes, you need only Agent service to convert the local machine via other Converter server/worker pair.

Also you need to check open ports requirement.

Reply
0 Kudos
dragon632
Contributor
Contributor
Jump to solution

Hi,

So, is it possible to direct transfer the converted virtual machine to an ESXi server ?

Actually, I'm trying to migrate a physical machine to a virtual machine to deploy it on an ESXi server.

If it supports this, how to setup on ESXi server ?

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

Yes, this is the prime idea of the Converter. Just select as destination your ESX.

Reply
0 Kudos
dragon632
Contributor
Contributor
Jump to solution

Hi POCEH,

I got an error message saying "Failed to connect to VMWare vCenter Converter Standalone server at xxxx on port 443" when connecting my convert target machine.

It looks the converter server service has to run on the target machine. But now, the server service still cannot be started due to the error 1067.

The last error log is

2019-09-26T15:14:10.259+08:00 warning vmware-converter-server[06596] [Originator@6876 sub=Locale] Key 'Internal.Tasks.SingleSpacedList' in module 'task' under 'C:\Program Files\VMware\VMware vCenter Converter Standalone\vimLocale\en/' was previously defined; ignored

2019-09-26T15:14:10.290+08:00 info vmware-converter-server[06596] [Originator@6876 sub=Libs] [ADS] Failed to get host ADS object in ACE initialization (0x80070057)

2019-09-26T15:14:10.290+08:00 warning vmware-converter-server[06596] [Originator@6876 sub=Libs] Failed to initialize active directory

2019-09-26T15:14:10.290+08:00 error vmware-converter-server[06596] [Originator@6876 sub=Default] [user,280] Failed to initialize Active Directory

2019-09-26T15:14:10.290+08:00 error vmware-converter-server[06596] [Originator@6876 sub=Default] [plugin,149] ServerPlugin Init failure

2019-09-26T15:14:10.742+08:00 info vmware-converter-server[06596] [Originator@6876 sub=Default] CoreDump: Writing minidump

2019-09-26T15:14:12.848+08:00 panic vmware-converter-server[06596] [Originator@6876 sub=Default]

-->

--> Panic: TerminateHandler called

--> Backtrace:

-->

--> [backtrace begin] product: VMware vCenter Converter Standalone, version: 6.2.0, build: build-8466193, tag: vmware-converter-server

--> backtrace[00] vmacore.dll[0x0017D73D]

--> backtrace[01] vmacore.dll[0x00051604]

--> backtrace[02] vmacore.dll[0x000528D1]

--> backtrace[03] vmacore.dll[0x00198100]

--> backtrace[04] vmacore.dll[0x001981E7]

--> backtrace[05] vmacore.dll[0x0019B15A]

--> backtrace[06] vmware-converter.exe[0x000012E8]

--> backtrace[07] kernel32.dll[0x000A1064]

--> backtrace[08] ntdll.dll[0x000783B3]

--> backtrace[09] ntdll.dll[0x00041502]

--> [backtrace end]

-->

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

Please read the User's Manual - it explains in detail what is *source* and what is *target* machine!

In short - your *source* machine is where server didn't start but once the agent works you can run server on *other* machine and then convert (*source*) machine with agent into,

Reply
0 Kudos
dragon632
Contributor
Contributor
Jump to solution

Understood.

In conversion dialog box, I selected "Powered On" Remote Windows Machine, and then specified the IP address and User name / Password.

When I clicked the next button, it asked me to deploy the Agent on source machine. I clicked "Yes" and then I got an error message "Multiple connections to 'xxxxx' by the same users, using more than one user name, are not allowed. Disconnect all previous connections to the host and try again.".

Actually, I have logged out the account to my source machine, and there's no active user on the source machine.

What does this error message mean ?

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

That's the Windows issue, restart and try again (multiple users accessing same share etc.). Also check the source machine firewall - it must allow connection at port 9089 - this is the way Converter "recognize" the availability of Agent.

HTH

Reply
0 Kudos
dragon632
Contributor
Contributor
Jump to solution

Hi POCEH,

finally, the conversion task was running last night. But it failed at 13%.

The error message is "Error: Unable to clone volume 'D:'", "FAILED: An error occurred during the conversion: 'File-level volume clone error failed with sourcevolume id \WindowsBitmapDriverVolumeId=[D6-67-A3-C0-00-00-10-35-0C-00-00-00] and target volume id 6-763*0,00000153<0000000. Error code:
112'"

In my convert configuration, I saw the default copy data is block-level clone, but how it used File-level volume clone for 'D:' drive ?

How to resolve it ?

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

File level copy is triggered by disk shrinking or 4KN disks.

However I see error 112 which means "There is not enough space on the disk." for better analyze full logs are required.

Reply
0 Kudos