VFP Project Integration crashes in Windows 7

[wkrzystek]

I've been using VFP project integration with Vault 4.1.4 on Windows XP for quite awhile and now I've upgraded to Windows 7. Whenever I try to open a project in VFP that has been already integrated with Vault, I instantly get a C5 crash. Just to be sure it wasn't something I was doing in the project, I created a brand new project and attempted to add it to vault and again I instantly received the C5 crash. I've posted the crash details below. I'm going to try to setup a virtual machine with Win7 and Vault 5 to see if it happens in the newer version of Vault as well but that will take a little bit to setup.

Problem signature:
Problem Event Name: APPCRASH
Application Name: vfp9.exe
Application Version: 9.0.0.7423
Application Timestamp: 49a31c0c
Fault Module Name: VaultIDE.dll
Fault Module Version: 4.1.4.18402
Fault Module Timestamp: 4926e0f5
Exception Code: c0000005
Exception Offset: 00006a0a
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

[Beth]

Can you look in your Event Viewer logs on your client to see if anything is logged there?

Are you trying to use the Enhanced Client or the Classic Client in Visual Studio?

Does the Vault GUI client work separately for you?

You are likely to have better success with Vault 5 and Windows 7.

[wkrzystek]

OK. I setup Vault 5.0.1 on a Virtual Machine replicating the environment as close as I could. Same issue, adding a new project to Vault threw a C5 exception:

Problem signature:
Problem Event Name: APPCRASH
Application Name: vfp9.exe
Application Version: 9.0.0.5815
Application Timestamp: 4713a6f4
Fault Module Name: VaultIDE.dll
Fault Module Version: 5.0.1.18729
Fault Module Timestamp: 4a8cb05e
Exception Code: c0000005
Exception Offset: 00006a0a
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

The Vault client works fine. In the Application event log:

Log Name: Application
Source: Application Error
Date: 10/23/2009 3:34:53 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WTKWIN7VM.mis.local
Description:
Faulting application name: vfp9.exe, version: 9.0.0.5815, time stamp: 0x4713a6f4
Faulting module name: VaultIDE.dll, version: 5.0.1.18729, time stamp: 0x4a8cb05e
Exception code: 0xc0000005
Fault offset: 0x00006a0a
Faulting process id: 0xfd8
Faulting application start time: 0x01ca5430ff573a3a
Faulting application path: C:\Program Files\Microsoft Visual FoxPro 9\vfp9.exe
Faulting module path: C:\Program Files\SourceGear\Vault Client\VS2003_Client\VaultIDE.dll
Report Id: 47b294d6-c024-11de-8008-000c297ce995
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-10-23T22:34:53.000000000Z" />
<EventRecordID>1041</EventRecordID>
<Channel>Application</Channel>
<Computer>WTKWIN7VM.mis.local</Computer>
<Security />
</System>
<EventData>
<Data>vfp9.exe</Data>
<Data>9.0.0.5815</Data>
<Data>4713a6f4</Data>
<Data>VaultIDE.dll</Data>
<Data>5.0.1.18729</Data>
<Data>4a8cb05e</Data>
<Data>c0000005</Data>
<Data>00006a0a</Data>
<Data>fd8</Data>
<Data>01ca5430ff573a3a</Data>
<Data>C:\Program Files\Microsoft Visual FoxPro 9\vfp9.exe</Data>
<Data>C:\Program Files\SourceGear\Vault Client\VS2003_Client\VaultIDE.dll</Data>
<Data>47b294d6-c024-11de-8008-000c297ce995</Data>
</EventData>
</Event>

There was an MSDTC error about a minute earlier. Could this be related?

Log Name: Application
Source: Microsoft-Windows-MSDTC Client 2
Date: 10/23/2009 3:33:33 PM
Event ID: 4879
Task Category: CM
Level: Warning
Keywords: Classic
User: N/A
Computer: WTKWIN7VM.mis.local
Description:
MSDTC encountered an error (HR=0x80000171) while attempting to establish a secure connection with system WTKWIN7VM.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-MSDTC Client 2" Guid="{155CB334-3D7F-4ff1-B107-DF8AFC3C0363}" EventSourceName="MSDTC Client 2" />
<EventID Qualifiers="32768">4879</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>3</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-10-23T22:33:33.000000000Z" />
<EventRecordID>1002</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>WTKWIN7VM.mis.local</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">80000171</Data>
<Data Name="param2">WTKWIN7VM</Data>
</EventData>
</Event>

[Beth]

I just realized I was thinking you were using Visual Studio. VFP isn't tested nor supported with Vault. Different customers have had different results with it.

Some things that might help you is to make sure your VFP works separately without source control. I'm not sure how well it works on Windows 7.

You might try using Vault and VFP separately without the integration.

The MSDTC error that happens a minute earlier could be related, but it would be hard for me to say exactly. I would think that if it stopped the project from opening fully that it would halt the attempt to connect to source control too.

[wkrzystek]

Well this is certainly a disappointment. I've been using VFP projects integrated with Vault since version 3.1 through the latest 5.0.1 release on Windows XP and Windows 2003. Both VFP and Vault work just fine independently in Windows 7, what appears to have an issue is the MSSCCI interface calls in Win7. The crash happens right before where you would normally get prompted with a Vault login screen. I'll just have remove the source control info from all of my projects and handle the checkin/checkout processing manually with the command line wrapper I hope to have on http://www.codeplex.com/VFPX soon.

[Beth]

One thing that might be contributing to the issue you are seeing is .NET. Do you have the 1.1 .NET framework on your Windows 7 machine?

[wkrzystek]

Woo hoo! That was it. After I installed the .NET 1.1 framework, it works! Thanks for your help with this.

[Beth]

Thanks for the update. This should help other users as well.