Where and what is the folder d:\build\ob\bora-xxxxx\

[ian_loyola]

Dear Colleagues,

This may be a stupid question but I am unable to find a clear and straight answer anywhere.

Can someone tell me where I can find this following folder "d:\build\ob\bora-xxxxx\" What is it for?

Reason being, I'm trying to find the following file:

File: d:\build\ob\bora-621624\bora-vmso...\hgfssharedmem.c Line: 773

Expression: gHgfsSharedMemoryData.mutex

I have no idea where to look for this file and what does it do. Could someone explain this to me please?

I need this information in order to troubleshoot the following error. I'm not sure how to proceed.

========================================

Microsoft Visual C++ Runtime Library

Assertion failed!

Program: D:\Program Files\Foundstone\FSAssessment.exe

File: d:\build\ob\bora-621624\bora-vmso...\hgfssharedmem.c

Line: 773

Expression: gHgfsSharedMemoryData.mutex

For more information on how your program can cause an assertion failure, see the Visual C++ documentaion on asserts

(Press Retry to debug the application - JIT must be enabled)

========================================

Best regards,

Ian

[a_p_]

Welcome to the Community,

you won't see this directory. It's the directory structure used by the developer to compile/build the binaries.

André

[ian_loyola]

Hi André,

Thanks for this. Ok, so you mean that it's a temporary VMware directory? The thing is The McAfee Foundstone Application (FSassessement.exe) does not create such directories.

This is a virtual Win Server 2003. Whenever the scan runs on this server it triggers this error. It works fine on other servers but I'm not sure what this is

File: d:\build\ob\bora-vmso\bora-vmso...\hgfssharedmem.c

Line: 773

Expression: gHgfsSharedMemoryData.mutex

I've seen a lot of similar errors on the VMware KB but not sure what it means

Best regards.

Ian

[steve_goddard]

Hi Ian,

Thanks so much for reporting this issue.

I am the developer for the feature which has hit an assert failure.

The path and file is from when the build that the application components were compiled. This information is purely for the developers of the application.

This helps me to pinpoint where exactly the issue was raised in the application. This is immensely helpful, so thank you.

Next comes trying to understand why this issue was hit in your case and not by others.

It looks like you have a Foundstone (McAfee) product installed, can you share with me which components exactly and what version?

Also can you tell me which build of VMware tools you have installed?

(In a Command Prompt Window type "C:\Program Files\VMware\VMware Tools\vmwaretoolboxcmd.exe" -v)

Or the file version of the following file at least:

"C:\Windows\System32\vmhgfs.dll"

(In Explorer select the file and right click, select Properties, and then select the Details tab of the dialog box. Please update here with that information as it will help me locate the exact version you are running in your virtual machine.)

Finally, when do you hit this assertion? Are there any specific set of steps you do to make this occur?

Thanks

Steve

[steve_goddard]

This looks like you are hitting an assert due to a race condition that has been fixed since the release of tools you have installed.

One thing you can consider, if you are running the virtual machine in the ESX environment, you can rerun the VMware Tools install and remove the Shared Folders component, as that is not going to be used in these cases. If you are running the virtual machine in a Workstation environment then you can try upgrading the tools if you still need to use the file sharing Shared Folders feature.

Steve

[ian_loyola]

Hi Steve,

Terribly sorry for the very late reply. McAfee Foundstone is a vulnerability scanner application. This error occurs while running a vulnerability scan from that server onto target systems. The servers have multiple versions Visual C++ installed.

Here are the details

Host Name	OS	VMware Tools version	Microsoft Visual C++ Name	Microsoft Visual C++ Version
Server1	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual C++ 2005 Redistributable	8.0.59193
Server1	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual C++ 2005 Redistributable	8.0.61001
Server1	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual C++ 2008 Redistributable - KB2467174 - x86 9.0.30729.5570	9.0.30729.5570
Server1	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148	9.0.30729.4148
Server1	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161	9.0.30729.6161
Server1	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual C++ 2010 x86 Redistributable - 10.0.30319	10.0.30319
Server1	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual Studio 2005 Premier Partner Edition - ENU	8.0.50727.42
Server2	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual C++ 2005 Redistributable	8.0.59193
Server2	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual C++ 2005 Redistributable	8.0.61001
Server2	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17	9.0.30729
Server2	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148	9.0.30729.4148
Server2	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161	9.0.30729.6161
Server3	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual C++ 2005 Redistributable	8.0.59193
Server3	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual C++ 2005 Redistributable	8.0.61001
Server3	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17	9.0.30729
Server3	Microsoft Windows Server 2003 Standard Edition 32-Bit	8.6.5.11214	Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148	9.0.30729.4148

Best regards,

Ian

[steve_goddard]

Hi there Ian,

Thanks for the additional information. I am pretty sure that what you are hitting has already been addressed with newer versions.

It would help to know which environment you are running this in to be sure that the fixes are in the releases you can upgrade to.

Also what is the Foundstone binary tool you are running when you trip on the assert (the ".exe" file if you know it)? You said Security Scan application tool but what is the application's file name?

That way I should be able to see if can exactly replicate what you set up is doing  and confirm the issue for sure.

Thanks.
Steve

[ian_loyola]

Hi Steve,

The Foundstone binary is a part of McAfee Vulnerability Manager (version 7.0) http://www.mcafee.com/us/products/vulnerability-manager.aspx#vt=vtab-Overview

I've requested my colleague to verify the environment that is being used (ESX / Workstation/ vCenter or so). We'll get back to you with the details.

Also, we are going to try your recommendation of re-installing the VMware tools and removing the Shared Folders component. (fingers crossed)

Cheers,

Ian

[ian_loyola]

Hi Steve,

Got it... it's running in an ESX environment (ESXi 5.0)

VMware tools version: 8.6.5.11214 (build-621624)

Cheers,

Ian

[ian_loyola]

Ah ha! So now I understand a bit more....

VMware tools version: 8.6.5.11214 (build-621624)

File: d:\build\ob\bora-621624\bora-vmso...\hgfssharedmem.c Line: 773

Expression: gHgfsSharedMemoryData.mutex

The build number 621624 and the "bora-621624" is the same. So does bora-xxxxxx indicate the build number of the component that hits an assert failure?

[steve_goddard]

Ian

Thanks for the information about the environment and your setup.

You will be fine without the file sharing client installed as it is not used on ESX.

your conclusions are correct about the build number used in the build path name.

it is extremely critical for us to have that information so we know what exactly you are running.

I have been looking over the Foundstone components and will try out the trial versions for now.

thanks

Steve