black screen, when you open the virtual machine console

Hi guys need help in answering the following questions:
When you open the console of the virtual machine, the connection process is fine, but it stops at a black screen

Screen.jpg

That's what I use:
(1) Windows 7 x 32
VMRC 2) 5.1.0.20447
(3) Mozilla Firefox 18.0.1
(4) VMware vSphere Client 5.1
(5) Vcloud 5.1.0.810718

Here is my log:

13/01/29 10:15:42.100 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
29-01-2013 10:15:42.101 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3
{{2013-01-29 10:15:42.101 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: start: VMRC_MONIKER_vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C}, VMRC_EVENT_vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C}, 5.1\Firefox\vmware-vmrc.exe C:\Program Files VMware Remote Console Plug-ins, "C:\Program Files\Common VMware Remote Console Plug-in 5.1\Firefox\vmware-vmrc.exe - parent-PID 6316 - instance"vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C}"ID - 2 modes - message mode has 2-3
29-01-2013 10:15:42.101 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:205]: process of creating VMRC
29-01-2013 10:15:42.103 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:220]: loop from MsgWait
29-01-2013 10:15:42.821 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:229]: A WAIT_OBJECT_0
29-01-2013 10:15:42.821 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:256]: expect successful moniker
{2013-01-29 10:15:42.832 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: link to [VMRC_MONIKER_vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C]}
29-01-2013 10:15:42.833 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject managed
29-01-2013 10:15:42.845 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: successful startup
29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:379] 10:15:43.901: control of the VM has not been created
29-01-2013 10:15:43.902 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 10:15:43.909 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:15:43.909: control of the VM has not been created
29-01-2013 10:15:43.923 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:15:43.923: control of the VM has not been created
29-01-2013 10:15:43.925 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:15:43.925: control of the VM has not been created
29-01-2013 10:15:44.275 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
29-01-2013 10:15:44.275 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3
{{2013-01-29 10:15:44.275 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: start: VMRC_MONIKER_vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD}, VMRC_EVENT_vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD}, 5.1\Firefox\vmware-vmrc.exe C:\Program Files VMware Remote Console Plug-ins, "C:\Program Files\Common VMware Remote Console Plug-in 5.1\Firefox\vmware-vmrc.exe - parent-PID 6316 - instance"vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD}"ID - 2 modes - message mode has 2-3
29-01-2013 10:15:44.275 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:205]: process of creating VMRC
29-01-2013 10:15:44.276 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:220]: loop from MsgWait
29-01-2013 10:15:44.957 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:229]: A WAIT_OBJECT_0
29-01-2013 10:15:44.957 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:256]: expect successful moniker
{2013-01-29 10:15:44.958 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: link to [VMRC_MONIKER_vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD]}
29-01-2013 10:15:44.959 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject managed
29-01-2013 10:15:44.970 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: successful startup
29-01-2013 10:15:46.770 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
29-01-2013 10:15:46.770 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3
{{2013-01-29 10:15:46.771 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: start: VMRC_MONIKER_vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996}, VMRC_EVENT_vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996}, 5.1\Firefox\vmware-vmrc.exe C:\Program Files VMware Remote Console Plug-ins, "C:\Program Files\Common VMware Remote Console Plug-in 5.1\Firefox\vmware-vmrc.exe - parent-PID 6316 - instance ID 'vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996}' - mode 4 - message mode has 2-3
29-01-2013 10:15:46.771 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:205]: process of creating VMRC
29-01-2013 10:15:46.772 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:220]: loop from MsgWait
29-01-2013 10:15:47.339 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/common/ScriptableObject.cc:321]: ID of property not found: onMessage
29-01-2013 10:15:47.339 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/common/VmrcPlugin.cc:2548]: onMessage Manager call failed
29-01-2013 10:15:47.379 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:229]: A WAIT_OBJECT_0
29-01-2013 10:15:47.379 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:256]: expect successful moniker
{2013-01-29 10:15:47.380 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: link to [VMRC_MONIKER_vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996]}
29-01-2013 10:15:47.381 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject managed
29-01-2013 10:15:47.388 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: successful startup
29-01-2013 10:17:20.197 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:633]: no associated window with control of the virtual machine
29-01-2013 10:59:13.788 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:633]: no associated window with control of the virtual machine
29-01-2013 10:59:13.792 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:633]: no associated window with control of the virtual machine
29-01-2013 10:59:15.303 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 10:59:15.308 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 10:59:15.324 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:59:15.324: control of the VM has not been created
29-01-2013 10:59:15.326 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:59:15.326: control of the VM has not been created
29-01-2013 10:59:33.283 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:59:33.284: control of the VM has not been created
29-01-2013 10:59:33.540 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
29-01-2013 10:59:33.540 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3

Advertisement

Windows 7 x 32

That's kinda our old friend is back.

Two checklists

1. check the version of the VM VGA driver, if that's the case, you must update the WDDM driver display driver.

2. make sure that you use HW 7 and more.

More info here

Tags: VMware

Similar Questions

  • Using vmrun to obtain an IP address when you run the virtual machine mode headless fails customers

    Operating system: OS X Yosemite 10.10.5

    VMware Fusion: Professional Version 8.1.1 (3771013)

    When you run a VM guest in headless mode I can't use vmrun to get IP clients. If I eventually bring to the top/start the merger GUI, the command returns the IP address as planned. It is always reproducible.

    $ vmrun -T fusion start "path/to/MyVMs.vmx" nogui
    2016-06-12T10:55:46.626| ServiceImpl_Opener: PID 11515
    
    ... wait for VM to come up. If the VM has a static IP address I can now ssh into the instance.
    
    $ vmrun -T fusion getGuestIPAddress "path/to/MyVMs.vmx"
    Error: The VMware Tools are not running in the virtual machine: "path/to/MyVMs.vmx"
    
    $ vmrun -T fusion checkToolsState "path/to/MyVMs.vmx"
    installed
    
    ... Start the VMware GUI and ensure the VM's console window is open
    
    $ vmrun -T fusion getGuestIPAddress "path/to/MyVMs.vmx"
    192.168.100.23
    

    I tested with open-vm-tools and tools VMware packaged with the merger and the behavior is the same. I also spoke with others on the channel of freenode #vmware who have confirmed that the problem exists for users of workstation as well.

    Hi danandham,

    Welcome in the vmware community. Iyou s really a problem, we try to fix it.

    After a command, you can use as a workaround:

    vmrun t fusion getGuestIPAddress "path/to/MyVMs.vmx" - wait

    See you soon

  • M40X-141: black screen when you use the WiFi network

    Since I bought my M40X 141 in July 2005, I got black screen frequently when you use the wifi.

    You know this black screen with typical noise from the hard drive.

    I did all the updates without effect. The local seller understood nothing black screen, associated with the use of wifi.

    In the XP world, nobody seems to find this kind of abnormal things so I'm desperate to find a solution to stop the frequent black screens. Recently try a usb dlink wifi dongle (dwl-G122) the constant flow of black screens disappeared
    (An Xp session 10 days was previously impossible).

    Now, I know this is a bug in the original software and I try desespartely to find a patch or updated driver or professional advice.

    Is there someone here who can help a tired multi restart man to use his laptop with the original material?

    Your laptop should still be guaranteed if you bought in June 2005. Take it to your authorized Service Provider nearest and have their say. They should already provide for a procedure for this and know what to do. Sure the frequency that uses WIFI and display inverter coincides, and you get the black screen. Change them should fix this problem.

  • When you access the virtual machine, getting the error "encountered an error when you try to use one of its virtual hard disks". Help?

    I received the "low disk space error" on a hard drive of the virtual machine dynamic expanding. I have increased my space of virtual hard disk using "My Computer" > manage > storage > "Disk management" and choose "Attach VHD" then resizing to max available (64 GB), and now I can not start the virtual machine. It gives the error: encountered an error when you try to use one of its virtual hard disks. Help?

    Hi NatalieFoster,

    The question you posted would be better suited in the TechNet Forums. I would recommend posting your query in the TechNet Forums to get help:

    Windows 7 Virtual PC and XP Mode TechNet Forums

  • How to make a virtual computer to connect to a CD player with an ISO mounted when you start the virtual machine?

    I am the creation of virtual machines using PowerCLI 5.5 on vSphere 5.0; and while the virtual machine is turned off, I am able to mount an ISO on a CD player and change the boot order to boot from the CD-ROM (for another post).  I have the flag startConnected set to true, but am not having much luck getting the virtual machine to connect to the CDDrive

    $cdObj = $Vm | New-CDDrive - IsoPath $isoPathName - StartConnected: $true

    If ($cdObj - no $null)
    {
    #Power off VM if it is on
    $VmState = $Vm.PowerState

    If ($VmState - eq "Receptor")
    {
    $Vm | Stop-Vm-confirm: $false - ea 0
    }

    $BootHardDiskName = 'disk 1 '.
    $VmView = get - VM $VmName - Server $serverObj.Name | Get-View
    $HardDiskDeviceKey = ($VmView.Config.Hardware.Device |) Where-Object {$_.} DeviceInfo.Label - eq $BootHardDiskName}). Key

    $BootableHardDisk = new-Object - TypeName VMware.Vim.VirtualMachineBootOptionsBootableDiskDevice - property @{'DeviceKey' = $HardDiskDeviceKey}
    $BootableCDRom = new-Object-Type VMware.Vim.VirtualMachineBootOptionsBootableCdromDevice

    #Set for CDRom boot order
    $BootIso = new-Object VMware.Vim .VirtualMachineConfigSpec - property @ {}
    "BootOptions' = New-Object VMware.Vim.VirtualMachineBootOptions - property @ {}
    BootOrder = $BootableCDRom
    }
    }

    #Set VM from the start settings at the start of the first CD and forces the display to update (sometimes delayed)
    $VmView.ReconfigVM_Task ($BootIso) | out-null
    $VmView.UpdateViewData ("Config.BootOptions.BootOrder")

    #Power on VM
    $Vm | Start-VM-confirm: $false - ea - global 0EV: vmOpsError | out-null

    When I start the VM, it does start the ISO.

    If I go to vCenter, the CD is pointing to the ISO file, but the 'Connected' to change settings option is not checked;  I can restart the VM of vCenter and then the VM restarts the ISO, but not in the script.

    I even put code to add a lead time of 5 to 10 seconds; I restart the virtual machine twice in the script and I can't CD to connect to start the virtual computer.

    Appreciate any suggestions.

    Maureen

    Have you tried to do a

    Game-CDDrive - CD $cdObj - connected - confirm: $false

    immediately after the start-VM?

  • Projector of Windows closes full screen when you open the pdf file

    Hi, I hope someone here can help with a problem I have.

    I work in CS5, using AS2 on a Mac.

    I built a presentation that requires the need to open pdf files in Acrobat Reader... I built it on a Mac I just used the code geturl, which worked a treat... today when I tested it on a PC it opens the file in a browser window!

    I'm not really a coder and to rely on the search for pieces online that I can change... after many hours, I set the pdf by opening the problem using the method of fscommand, but unfortunately when the pdf file is closed, my presentation (which was running fullscreen) played himself at a window the initial scene size 100%!

    Y at - it a fix for this?

    Thanks in advance.

    I found a solution very simple here: http://www.northcode.com/blog.php/2008/03/16/Problem-with-Fullscreen-Flash-Projectors

  • Black screen when you access the server console

    We are currently experiencing the following intermittent problem...

    When accessing a server through the console vcenter he'll suddenly lock (the console not the server).

    At this stage the existing Remote Desktop connections continue to work, but no new connections can be established.

    This leaves us in the position where the server is running, but we no longer have in any case of it management. In the past, the only way to retrieve the control was to restart the server that resolves the problem. However this is currently perform our mail server/domain controller so I hesitate to do a hard reset and will have to at least wait until that out of office hours to do. Which means I can't do the management and maintenance tasks I have to do today.

    We currently have 2 x hosts running ESX 4.0.0 164009.

    To manage using vSphere 4

    The service that all servers seem to be Windows Server 2008 R2 or Windows Small Business Server 2008

    is there one or more particular services can I restart to solve this problem?

    The vSphere update, I suggest this as follows:

    • first update the server vCenter Server (you need to download the new setup file, run the installation, say I have a database, use the existing ODBC name, and it will perform the update to U1)

    • then install the new AUVS (there is the U1P1 version)

    • then use AUVS to install ESX update (if you have a license of VMotion, it will work automatically, otherwise you will have to manually release each host to put in maintenance mode).

    André

  • "Unable to connect to MKS" when connecting to the virtual machine shared

    Hello

    I have a handful of Shared VMs Im trying to access remotely with VMware Workstation Pro 12 (same version on the client and the host - two Windows 10 machines). I am able to connect to the host that shares virtual machines, I can see all the virtual machines shared, open the virtual machine (as in it opens in a tab within the workstation) and virtually no action on the virtual machine including all power options, instant, change settings, etc.. The problem is that if I turn on a virtual computer (or connect to an existing virtual machine under tension, I get the following error and Im not able to access the actual console since it remains as a black screen.

    Unable to connect to the MKS: (name of user and password) Login incorrect.

    I also noticed that on the client Windows Event Viewer is to launch the following warning events at the same time that the error in the Workstation has been lifted - Im not seeing any on the host are thrown.

    vmware1.png

    vmware2.png

    I've seen a lot of posts here with users who run the question and he usually ended up being a network problem. I turned off the Windows Firewall on both machines, checked ports 443 and 902 listening on the host and Im in telnet from the client to the host on port 902. I also saw another suggestion for updating the client Windows hosts file to include [host name] [IP address] and [FQDN of the host name] [ip address], but this subject seems not helped either.

    Suggestions in this regard does not happen what keeps or where to find more information about the cause?

    Thank you!

    Post edited by: Tim Graffam

    Thank you for using the workstation. I think that this will solve your problem.

    Unable to connect to the MKS: (name of user and password) Login incorrect

  • Computer stops responding with a black screen when you start Windows XP. Cannot select anything advanced startup options

    Original title: can't open Windows
    I can't open my laptop at all... block when I select anything in the mode without failure or screen black normal mode :(
    What should I do? Thank you!!!

    Hi Mihou,

    1 have. what changes you made before the question?

    2. What are the options you see in the advanced startup options?

    You can follow the methods in the article in order to solve the problem.

    Computer stops responding with a black screen when you start Windows XP
    http://support.Microsoft.com/?kbid=314503

    Azeez Nadeem - Microsoft Support [If this post was helpful, please click the button "Vote as helpful" (green triangle). If it can help solve your problem, click on the button 'Propose as answer' or 'mark as answer '. [By proposing / marking a post as answer or useful you help others find the answer more quickly.]

  • Could not open the virtual machine

    I used the customer convertor to create this virtual machine from one which works well on ESxi.  When I try to open on Win7-64 machines running vmplayer 3.1.4 I get the following error:

    Could not open the virtual machine: file "D:\Data\VM Machines\WW S2008_32\WW S2008_32.vmx 10_1 10_1" line 1: syntax error.

    Any ideas?

    "" "WW 10_1 S2008_32.vmx.zip" attached file contains the "WW 10_1 S2008_32.vmx" file created under VMware Player 3.1.4 and was then modified to reflect the values of parameter that you might want to stay the same as uuid etc.  Start VMware Player and then check the settings before running the virtual machine.

  • Getting error: could not open the Virtual Machine: failed to query the Source for more information

    When I have a virtual machine to export to the FVO on an ESXi 4.0 and then try again to import the FVO on VMware Player or Workstation 7.1, I get the following message:

    «Could not open the Virtual Machine: failed to query the Source for more information.» I can successfully re-import this file OVF in an ESXi server without any problems. Anyone know why this is happening and what can be done to remedy this?

    Thank you

    Christopher

    Hello.

    Try to use ovftool to convert a VMX of the FVO.

    Good luck!

  • Satellite U840W-10 t starts when you open the lid

    Hello world.

    I recently bought a U840w-10 t.

    I can solve a problem.
    When I stopped completely win8, I enabled in the BIOS and in the configuration of toshiba software the option this computer do not START with the opening of the SCREEN.

    But even with this option turned off, my laptop STILL BOOT to WINDOWS, simply open up the laptop, NOT by pressing the power button.

    I want to avoid that, because I noticed that when the laptop is on the bag, sometimes it STARTS by itself with a small vibration and milimetter opening of the screen.

    Does anyone have this problem?
    Toshiba is announced on this subject?

    Thanks in advance.

    Have a look here:
    [Why my laptop Windows 8 start automatically when you open the cover of the display? | http://APS2.Toshiba-tro.de/KB0/FAQ2C03FA0001R01.htm]

    + There are two possibilities. A stop of the hybrid were made in Windows 8 (default option) or "Open Panel - Power On" is activated. +

    + If one of these two functions is activated, the notebook starts up automatically when you open the cover of the display. To change it, disable hybrid closing mode or turn off the function "open Panel - Power On. +

  • Computer stops responding with a black screen when you start Windows Vista

    Computer ceases to respond with a black screen when I run Vista, this happen right after the installation of updates. original title: computer stops responding with a black screen when you start Windows XP__

    If you think that Windows updates are loaded:

    Visit the Microsoft Solution Center and antivirus security for resources and tools to keep your PC safe and healthy.  If you have problems with the installation of the update itself, visit the Microsoft Update Support for resources and tools to keep your PC updated with the latest updates.

    MS - MVP - Elephant Boy computers - don't panic!

  • In opening the virtual machine: "could not find a peer valid to connect to" or "error of Transport (VMDB) - 32" / "-14" ""»

    Hello

    Since yesterday after a reboot of my host (DELL E6410, W7 SP1 64-bit, 8 GB RAM, 2x750GB SATA3 running WorkStation 9.0.2 Update Windows Update), I can't open my existing VM.

    I often get "can not find a valid peer to connect to" and sometime before: "Transport (VMDB) - 32 error: Pipe: reading is not'or'error of Transport (VMDB)"-14: fitting broke

    I worked for 2 years on this machine without a hitch, WS7 reclassification in WS9 without any problem.

    FYI: we have changed the domain 3 months ago, but it has never be a problem.

    I have google and search several Forum. So far, I tried to:

    -restart the service vmware-auth as an administrator

    -launch vmware.exe administrator

    stop/start the vmx86 service

    -uninstall / reboot / install Workstation.  3 times. First using uninstall from the Control Panel, then doing a / clean before installation and finally track down any file/reg entry.

    -HE asked if any group policy changes were made recently (like not allowing to run vmware.exe?)

    -Rename vmware.exe (logs I look similar to what is in this post: http://communities.vmware.com/thread/331099?start=0 & tstart = 0 ... but no luck)

    -excluded vmware.exe in my AV (Microsoft ForeFront). Unfortunately, in that I'm not allowed disabled...

    -Open the virtual machine using the drive == > does not work either.

    This isn't a file corrupted in a virtual machine (even backup - 7zipped - don't work on my laptop... but the launch on the other).

    Even a newly created WM (boneless), unbootable! :-(

    *, BUT to BE NOTE *: if a virtual machine is created as a shared virtual machine, I can start the application locally remotely! And this same VM, if started (via the.vmx) does not work using Workstation GUI!

    I have attached 2 newspapers. Work a (vmware.log remotely) and the inactive (vmware-vmx - 4072.log thru WS GUI).

    Of after what I saw (and what little I understand), it's as if the CPU is not detected?

    The two newspapers have this line:

    FeatureCompat: EVC masks:

    but the non-working goes - we with

    Module CPUID initialization failed.

    While working it display information on CPU (hostCPUID name / family / type... etc...)

    Any idea is welcome.

    I'll answer me to my problem!

    A lot of research to this knowledge.

    In summary: don't mess with the processor affinity... or keep it in mind!

    Response to distinguish:

    I installed 6 months ago a small utility named prio (search for "PRI prnwatch"), because it can save the priority of a given process. What I did notice, is that it also save the processor affinity ! What happened: I probably changed the affinity once for a VM running to give greater priority to a 7zip archive process to complete more quickly (setting HT no core to 7zip and one - or 2? - HT core to VM). Everything works until the next reboot, where the CPU detection during * start EVERY * VM has been somewhat "damaged" leading to the wrong log message: failed initialization Module CPUID.

    This is the reason of *my* question. Perhaps it might help someone else?

    TIPS:

    For advanced people who do not want to check the processor affinity of each process in the Task Manager, you can try this Windows Powershell command (remember to launch PowerShell as an administrator):

    Get-Process | Format-Table-PriorityClass name, ProcessorAffinity property

    ProcessorAffinity column gives the number of representation of the authorized core, 1-bit by heart.

    15 = 1111 is all possible core (for a logical processor 4). Mine is 1 CPU with 2 core HT <=>4.

    LSB is the core lowest. So if you allow only core0 and core3 (1001) on a process, the number of ProcessorAffinity will be 9...

    Post edited by: cbiero (LSB and MSB...)

  • Hi, I installed an Alfred Workflow (see code below) that will mark all my mails as read. After you run it for a minute, the mail has crashed and I had to forcequit. However, now, when you open the Mail it crashes instantly, even after restart and repair o

    Hello

    I installed an Alfred Workflow (see code below) that will mark all my mails as read. After you run it for a minute, the mail has crashed and I had to forcequit. However, now, when you open the Mail it crashes instantly, even after restart and repair the permissions. I also used the Ctrl + C and CTRL-Z commands in the Terminal to leave the alfred_script, but nothing helped. I'm running out of ideas here, so I hope you could help me either reinstall the mail.app. I could always just switch to a different mail application, but it's kind of a last resort.

    Code:

    Tell application "Mail".

    Define allAccounts on each account name

    Repeat with currAccount in allAccounts

    the unreadMboxes value (each mailbox to the account currAccount the unread number is not 0)

    Repeat with currMbox in unreadMboxes

    (read status of each message to currMbox including the playback State is set to false) true value

    end repeat

    end repeat

    tell the end

    Any input would be greatly appreciated. Can post the report of crash on demand.

    Not sure that Alfred's, but it's just an Applescript script and it would not cause Mail to be planted.

    However, when running through all the messages, it is possible Mail database has been corrupted and it crashes because of this.

    I'll probably get anything out of the accident report, but others might.

    My first instinct would be to rebuild the mailbox. Because you can't do that with him crashing, you can simply delete the databases and it will rebuild them.

    Navigate to this folder:

    ~/Library/Mail/v3/MailData/

    You can either manually through the files, or copy the full path and paste it into go the folder in the menu go to the Finder.

    Remove the envelope Index files. Open Mail and see if it works well.

    If your library does not appear in your folder, hold down the Option key and select library in the menu go to in the Finder.

Maybe you are looking for