Failed a general system error occurred missing vstor2 driver or not started

Vmware converter failed general system error occurred

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

FAILED: A general system error occurred: Server closed connection after 0 response bytes read;

I am currently trying to convert Win7 PC to VM and loading it onto a External Hard Drive. How am I getting a response error? I ran as admin and am supposed to be connecting to the same device.

See attached logs for details

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

The most interesting log, worker’s one, is missing. You can find it in «%ALLUSERSPROFILE%VMwareVMware vCenter Converter Standalonelogs» folder and upload here.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

There is no folder with a logs folder.

See below: the folder path for the Vmware converter is: C:Program Files (x86)VMwareVMware vCenter Converter Standalone

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

What about » %ALLUSERSPROFILE% VMwareVMware vCenter Converter Standalonelogs»?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Seems that worker service crashes, are there some .dmp files in folder?

Hopefully dump files will give us a clue what’s happens.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

We had same issue for P2V for Windows 2008 R2

class Vmacore::Http::MalformedHeaderException(Server closed connection after 0 response bytes read; )

Solution: Check disks, uncheck null disks while creating P2V or V2V job, in our case we found 200 MB & 128 MB, verified disk management from physical server, 128 MB disk not exists, unchecked that 128 MB Disk, P2V job completed, conversion completed successfully.

Источник

Vmware converter failed general system error occurred

Hello,
When i try to convert and join physical machine to the VMware Infrastructure ESXi Server i have got this error: «FAILED: A general system error occurred: Unknown exception».
There is status «Running» for moment (but percent bar doesn’t show) and then status «FAILED» appears.
I added log files and screenshot in attachment.
Please help me

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

2012-04-25T11:34:31.195+02:00 [01340 info ‘Default’] [,0] Vmount library: Error 2 while opening VSTOR2 driver’s control device

Try uninstall and clean install of the Converter 5.

If error still happens, check status of VSTOR driver: «sc qc vstor2-mntapi10-shared»

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

2012-04-25T11:34:31.195+02:00 [01340 info ‘Default’] [,0] Vmount library: Error 2 while opening VSTOR2 driver’s control device

Try uninstall and clean install of the Converter 5.

If error still happens, check status of VSTOR driver: «sc qc vstor2-mntapi10-shared»

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Hi. Which version of ESX are you running on your host? I usually use the VmWare Converter designated to that specific version of ESX. Cheers!

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Am having the same issue as above.

I setup esxi 5.0 with a cluster of G7 and G6 server, and vcenter 5.0.
I then used vmware converter standalone 5.0 to convert exiting vms versn 7 on esxi 4.0 host but all kept failing with the errors below.

«FAILED: a general system error occurred: Unknown exception».
The status is «Running» for moment (but percent bar doesn’t show) and then status «FAILED» appears.

For another vm conversion, it gave «a general error occurred: Unknown internal error»

I will appreciate if anyone can help me wit this.

Источник

Vmware converter failed general system error occurred

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I installed on a physical machine i would like to make virtual, vCenter converter standalone version 6.2.0

I am trying now to create a vmware machine and save it to my NAS server and i get this error:

FAILED: A general system error occurred: Logon failure:

unknown user name or bad password.

could any one please help me. i am uploading the log file.

thank you so much.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

In which step are you getting that error? When you try to connect to vCenter?

Maybe the issue are wrong credentials or the user does not have enough permissions.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

when i press FINISH in last step to begin the process it runs very shortly and then returns the error. here is the screen and the last few lines of the export log

2020-06-03T21:59:20.182+03:00 info vmware-converter-server[06140] [Originator@6876 sub=Default] Created new scheduler item with , firstTimeToRun = «2020-06-03 21:59:20.182», source = «», targetRPOInMinutes = «0». — __thiscall Converter::Server::Scheduler::SchedulerItemImpl::SchedulerItemImpl(const class Converter::Server::Scheduler::SchedulerItemSpec &,const int &,const class boost::shared_ptr &,const class Vmacore::Ref &,const class boost::optional &) («d:/build/ob/bora-8466193/bora/sysimage/ufad/server/scheduler/schedulerItemImpl.cpp:87»)

2020-06-03T21:59:20.182+03:00 info vmware-converter-server[06140] [Originator@6876 sub=Default] scheduler item with created — int __thiscall Converter::Server::Scheduler::PriorityQScheduler::AddSchedulerItem(const class boost::shared_ptr &,const class boost::optional &) («d:/build/ob/bora-8466193/bora/sysimage/ufad/server/scheduler/priorityQScheduler.cpp:49»)

2020-06-03T21:59:20.183+03:00 info vmware-converter-server[06164] [Originator@6876 sub=Default] Scheduler scheduling item 2 to run at time = 2020-06-03 21:59:20.183. — void __thiscall Converter::Server::Scheduler::SimpleScheduler::Run(void) («d:/build/ob/bora-8466193/bora/sysimage/ufad/server/scheduler/simpleScheduler.cpp:109»)

2020-06-03T21:59:20.285+03:00 info vmware-converter-server[05628] [Originator@6876 sub=ThreadPool] Thread enlisted

2020-06-03T21:59:20.304+03:00 info vmware-converter-server[06256] [Originator@6876 sub=Default] Started task «task-5″ for job=»job-5″, item =»2» — void __thiscall Converter::Server::Job::JobProcessorImpl::StartProcessingJobs(void) («d:/build/ob/bora-8466193/bora/sysimage/lib/converter/server/job/jobProcessorImpl.cpp:384»)

2020-06-03T21:59:20.371+03:00 info vmware-converter-server[06184] [Originator@6876 sub=Default] ConverterConnection: KeepAlive timer canceled, StopKeepAlive succeeded

2020-06-03T21:59:20.374+03:00 info vmware-converter-server[05628] [Originator@6876 sub=Default] [task,338] [task-5] — BEGIN — Convert

2020-06-03T21:59:20.405+03:00 info vmware-converter-server[05628] [Originator@6876 sub=Default] [taskSpec,620] [task-5] [TaskMap] task-5:task-2

2020-06-03T21:59:20.764+03:00 error vmware-converter-server[05628] [Originator@6876 sub=Default] [task,350] [LRO] Unexpected Exception: vmodl.fault.SystemError

2020-06-03T21:59:20.766+03:00 info vmware-converter-server[05628] [Originator@6876 sub=Default] [task,379] [task-5] — ERROR — Convert: vmodl.fault.SystemError

—> faultCause = (vmodl.MethodFault) null,

—> reason = «Logon failure: unknown user name or bad password. «,

2020-06-03T21:59:20.767+03:00 info vmware-converter-server[05628] [Originator@6876 sub=Default] [diagnosticManager,265] Retrieved taskInfo for «converter.task.Task:task-5» mapping it to «converter.task.Task:task-5».

2020-06-03T21:59:20.767+03:00 info vmware-converter-server[05628] [Originator@6876 sub=Default] [diagnosticManager,305] The task with was found to be a «recent» task.

2020-06-03T21:59:20.767+03:00 info vmware-converter-server[05628] [Originator@6876 sub=Default] [diagnosticManager,319] No existing log bundle found for task with . The task is still «recent» so a log bundle will now be generated for it.

2020-06-03T21:59:20.767+03:00 info vmware-converter-server[05628] [Originator@6876 sub=Default] [diagnosticManager,1097] Retrieving task related diagnostics for server task with .

2020-06-03T21:59:20.792+03:00 info vmware-converter-server[03460] [Originator@6876 sub=Default] Run 0 of job «job-5» finished with an error. — struct Converter::Server::Job::JobExecutor::SchedulerUpdateSpec __thiscall Converter::Server::Conversion::ConversionJobExecutorImpl::UpdateJob(class Converter::Server::Job::InternalJob &,bool,const class Converter::Server::Scheduler::SchedulerItemStatistics &,const class Converter::Task::TaskInfo &) («d:/build/ob/bora-8466193/bora/sysimage/lib/converter/server/conversion/conversionJobExecutorImpl.cpp:405»)

2020-06-03T21:59:20.814+03:00 info vmware-converter-server[03460] [Originator@6876 sub=Default] Suspended 1 scheduler items for job (job-5) — void __thiscall Converter::Server::Job::JobProcessorImpl::SuspendJobAux(const class Converter::Server::Job::InternalJob &,class Converter::VdbConnection &) («d:/build/ob/bora-8466193/bora/sysimage/lib/converter/server/job/jobProcessorImpl.cpp:829»)

2020-06-03T21:59:21.339+03:00 info vmware-converter-server[05628] [Originator@6876 sub=Default] ConverterConnection: KeepAlive timer canceled, StopKeepAlive succeeded

2020-06-03T21:59:21.342+03:00 warning vmware-converter-server[05628] [Originator@6876 sub=vmomi.soapStub[4]] Terminating invocation: server= , moref=vmodl.query.PropertyCollector:UfaPropertyCollector, method=waitForUpdates

2020-06-03T21:59:21.358+03:00 info vmware-converter-server[05628] [Originator@6876 sub=ThreadPool] Thread delisted

2020-06-03T21:59:47.384+03:00 info vmware-converter-server[03924] [Originator@6876 sub=Libs] [ADS] GetTokenInformation failed: 1312

2020-06-03T21:59:47.387+03:00 info vmware-converter-server[03924] [Originator@6876 sub=Default] [diagnosticManager,809] The log bundle for task with already exists. Returning the serialized bundle info for it.

Источник

Vmware converter failed general system error occurred

I’m having issue using vm converter 5.5 to convert a physical Windows 2003 SP2 machine to VM. The vm converter is installed on the machine that I want to convert. When I start the conversion I will get an error A general system error occurred: unknown internal error.

I have tried restarting the server and restart the conversion but it did not work.

Attached is the log file.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I think that upgrading to R2 is a drastic step and you should consider the full impact before making the decision to do so. I wouldn’t advise it at this stage.

Do you have multiple system drives you are trying to convert? (C: , D:, etc?) If so, try just converting the C: to see if the converter process works. I’m not sure what role the server has but if the other disks are just data you could plan to copy or image the disk separate later (if it works).

Another option I might suggest if the above doesn’t work, is clean up all of the VM Converter files from your source machine manually, reboot the server and try the 5.1 converter process again cleanly. (Something could be left from the 5.5 install or now stuck).

Good luck trying this!

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I notice that you are trying to convert a a Windows Server 2003 Standard SP2 server. Can you check and make sure it is R2 as that is the only guest for 2003 that is listed on the supported guests site.

Failing that, are you trying to change any disk configuration with the converter? (Increase disk size, add extra disk, reduce disk size, etc)? I’ve seen this be a problem in the past and it causes the converter to error quite quickly. When we tried not changing the disk layouts it worked fine.

Also, have you tried following the best practices regarding P2V’ing servers? There are quite a few good articles out there, but it involves things such as stopping all unnecessary services before starting the P2V.

Happy to help further!

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

The Windows 2003 is not R2. I can try upgrading it as an option but have to check with the programmer if the programs running inside there is safe to upgrade to Win 2003 R2.

No changes to the disk size. I left it as default.

I haven’t check on the best practices yet. Thanks for the tips. I will try stopping some services and see if it helps.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Another possible option might be to go back to a slightly older version of VMware Converter that supports the 2003 Standard SP2 guest O/S? You are using the latest one which cuts out a lot of previous versions so maybe the 5.1 version might work (if you can get it?)

Good luck! Let me know how you get on!

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Tried with VM Converter 5.1 and disable most of the services but still no luck.

The only thing I can think of now is on the Windows 2003 upgrade to R2. Any other ways before I go for R2 upgrade?

Here are some errors I get from the GUI log:

[04360 error ‘Default’] SourceSelectPluginModel::BuildFilter 3rd party type microsoftVirtualPCVM not found

2015-02-18T01:29:45.734+08:00 [04360 error ‘Default’] SourceSelectPluginModel::BuildFilter 3rd party type parallelsVM not found

2015-02-18T01:29:45.734+08:00 [04360 error ‘Default’] SourceSelectPluginModel::BuildFilter 3rd party type vmwareVCBBackup not found

2015-02-18T01:29:45.734+08:00 [04360 error ‘Default’] SourceSelectPluginModel::BuildFilter 3rd party type livestateBackup not found

2015-02-18T01:29:45.734+08:00 [04360 error ‘Default’] SourceSelectPluginModel::BuildFilter 3rd party type shadowProtectBackup not found

2015-02-18T01:29:45.734+08:00 [04360 error ‘Default’] SourceSelectPluginModel::BuildFilter 3rd party type acronisBackup not found

2015-02-18T01:29:45.734+08:00 [04360 error ‘Default’] SourceSelectPluginModel::BuildFilter 3rd party type vmwareVM not found

2015-02-18T01:29:45.734+08:00 [04360 error ‘Default’] SourceSelectPluginModel::BuildThirdpartyHostedExtVector 3rd party type vmwareVM not found

[04384 error ‘wizardController’] Unable to submit job: vmodl.fault.SystemError

[04360 error ‘ConversionState’] Submit job failed: A general system error occurred: unknown internal error

[04360 error ‘ConverterWizardWindow’] Next/Finish failed: A general system error occurred: unknown internal error

[04372 error ‘wizardController’] Unable to submit job: vmodl.fault.SystemError

[04360 error ‘ConversionState’] Submit job failed: A general system error occurred: unknown internal error

[04360 error ‘ConverterWizardWindow’] Next/Finish failed: A general system error occurred: unknown internal error

Источник

One of the VM’s after the P2V was throwing error message

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 10/11/2008
Time: 12:41:43 PM
User: N/A
Computer: xxxx
Description:
The Vstor2 Converter Virtual Storage Driver service failed to start due to the following error:
The system cannot find the file specified.

It was really strange to find out why I am getting driver error when I had uninstalled all the drivers. After little bit of research I found that same physical machine was used for P2V using VMware converter and this version has some known issue
http://www.vmware.com/support/converter/doc/releasenotes_conv3.html

Manual cleanup required of some Converter Agent files from remote source physical machineIn some cases, the automatic cleanup of Converter Agent files from the system on which it ran is incomplete. If there are vmware-ufad-p2v-XXXXX subdirectories remaining under %SystemRoot% on the remote source physical machine after completion of the import (either successful or failed), automatic cleanup was not totally successful, and might cause future import attempts to fail. To clean up manually (recommended), follow these steps:
1. Launch regedit and navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices
2. Remove the stcp2v30 key
3. Remove the vstor2-p2v30 key
4. Remove all vmware-ufad-p2v-XXXXX keys
5. Remove all courier-XXXXX keys
6. Reboot
Under %SystemRoot%system32, remove all vmware-ufad-p2v-XXXXX subdirectories

So when did P2V for the same physical machine everything got virtualized with the same settings and that was causing the problem. After looking at the registry of virtual machine I found the key for “Vstor2” HKLMSYSTEMConterSet001Services . Delete the key and rebooted the VM and error went off.

Vstor2-ws60.sys

Классические проблемы Vstor2-ws60.sys

Большинство ошибок %% knowledgebase_file_name%%, с которыми вам придется столкнуться, связано с ошибками типа «синий экран» (также известными как «BSOD» или «ошибка ОСТАНОВКИ»), которые появляются в Windows XP, Vista, 7, 8 и 10:

• «Была обнаружена проблема, и Windows была выгружена, чтобы предотвратить повреждения компьютера. Очевидно, проблема вызвана следующим файлом: vstor2-ws60.sys.»
• «: (Windows столкнулась с проблемой с vstor2-ws60.sys и нуждается в перезапуске. «
• «0x0A: IRQL_NOT_LESS_EQUAL — vstor2-ws60.sys»
• 0x0000001E ОСТАНОВКА: КМОДЕ_ИСКЛЮЧЕНИЕ_НЕТ_ОБРАБАТЫВАЕТСЯ — vstor2-ws60.sys
• 0×00000050 ОСТАНОВКА: СТРАНИЦА_FAULT_IN_NONPAGED_AREA — vstor2-ws60.sys

Ошибки Vstor2-ws60.sys, которые вызывают синий экран смерти, часто следуют за новой установкой программного обеспечения (VMware Converter Hosted) или связанного с ним оборудования. Во время установки VMware Converter Hosted могут возникнуть ошибки vstor2-ws60.sys, во время работы программы, связанной с vstor2-ws60.sys, во время загрузки драйвера устройства, связанного с VMware, Inc., или во время запуска/завершения работы. Отслеживание того, когда и где возникает ошибка STOP, является важной информацией при устранении проблемы. Notating при возникновении ошибок vstor2-ws60.sys STOP имеет первостепенное значение для поиска причины проблем, связанных с VMware Converter Hosteds, и сообщая о них за помощью.

Причины ошибок в файле Vstor2-ws60.sys

Проблемы BSOD, связанные с vstor2-ws60.sys, обычно создаются соответствующим оборудованием, программным обеспечением, драйверами устройств или микропрограммным обеспечением. Они могут быть связаны с оборудованием VMware Converter Hosted или VMware, Inc., но не всегда.

Именно ошибки vstor2-ws60.sys проистекают из:

• Устаревшие, поврежденные или неправильно настроенные драйверы устройств VMware, Inc./VMware Converter Hosted.
• Поврежденный или недопустимый реестр vstor2-ws60.sys из VMware Converter Hosted или изменение, связанное с оборудованием.
• Вирус или вредоносное ПО, которые повредили файл vstor2-ws60.sys или связанные с VMware Converter Hosted программные файлы.
• Установка оборудования, связанная с NewVMware, Inc., создает конфликты vstor2-ws60.sys.
• Удалены или повреждены системные файлы (vstor2-ws60.sys) после установки VMware Converter Hosted или драйвера.
• Сбой жесткого диска, связанный с vstor2-ws60.sys Синий экран смерти.
• Ошибка Vstor2-ws60.sys STOP, созданная в результате повреждения оперативной памяти.