VirtualBox

Opened 10 years ago

Closed 10 years ago

#13110 closed defect (invalid)

Fatal Error Win8, vmware-view-usbd supplied a NULL target name for the pszTargetName parameter when calling the InitializeSecurityContext API

Reported by: OzBob Owned by:
Component: USB Version: VirtualBox 4.3.12
Keywords: InitializeSecurityContext API Cc:
Guest type: other Host type: Windows

Description

Virtual Box 4.3.12r93733 with Guest Additions installed on a win8 64bit machine running a Intel core2duo chip.

The message in the Event Log is:

The program vmware-view-usbd.exe, with the assigned Process ID 2124, supplied a NULL or empty target name for the pszTargetName parameter when calling the InitializeSecurityContext API to initiate an outbound NTLM security context. This is a security risk when mutual authentication is required.

To help protect against a malicious attack, make your code more secure. To do this, change the program so that it specifies a target name in the pszTargetName parameter field, and then recompile the code.

The Event log details are:

  • <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  • <System> <Provider Name="LsaSrv" Guid="{199fe037-2b82-40a9-82ac-e1d46c792b99}" EventSourceName="LsaSrv" /> <EventID Qualifiers="0">6036</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2014-06-07T23:34:08.000000000Z" /> <EventRecordID>33891</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>na</Computer> <Security /> </System>
  • <EventData> <Data>2124</Data> <Data>vmware-view-usbd.exe</Data> </EventData> </Event>

There was also a portable harddrive attached at the time of the error, the Event log also recorded that " \Device\Harddisk1\DR1, has a bad block."

Attachments (1)

VBoxSVC.log (1.9 KB ) - added by OzBob 10 years ago.
VirtualBox SVC log with error

Download all attachments as: .zip

Change History (2)

by OzBob, 10 years ago

Attachment: VBoxSVC.log added

VirtualBox SVC log with error

comment:1 by Klaus Espenlaub, 10 years ago

Resolution: invalid
Status: newclosed

Scratching my head. VBoxSVC.log does contain a few error messages, but none are alarming and additionally none are even remotely related to the originally reported issue.

The original issue is apparently a bug in some component of the VMware tools, and that's part of a product by a totally different company. Ask VMware to get this issue fixed, this is way outside our control.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use