Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: Virtual Server|
"<virtual machine>" could not be started because a disk-related error occurred.
|English: Request a translation of the event description in plain English.|
When you try to start a virtual machine with a user account that does not have Write access to the virtual machine configuration folder, you will receive a message such as, "The virtual machine Virtualmachinename could not be started. An unexpected error occurred" or "Virtualmachinename could not be started because a disk-related error occurred". This occurs because Virtual Server creates an empty saved state (.vsv) file in the virtual machine configuration folder when a virtual machine starts up. You can resolve this problem by granting Write permission on the virtual machine configuration folder to the user account for the virtual machine. See the link to "Release Notes for Virtual Server 2005 R2 SP1" to view the source of this information.
|Private comment: Subscribers only. See example of private comment|
|Links: Release Notes for Virtual Server 2005 R2 SP1|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated