BSOD using Beyond Compare 3, Clearcase and Symantec Endpoint Protection 12.1.2x

[sgagnon]

Normally, BC3 cannot cause a BSOD. We normally see this with poor device driver support and a combination of over-taxing the hardware. It is surprising to see this open issue between Clearcase and Symantec. It is unlikely this is something we could workaround without knowing more about the cause. We do not have a license for either Clearcase or Symantec, so it would be difficult for us to recreate this environment (while our trial is free and easily available for any testing they may want to do).

When they "point fingers" is there any technical information included with that? Are they able to reproduce the crash with their software or BC3?

The temporary files exist because BC3 does not directly overwrite the file during a save. If this were interrupted (for example, by a BSOD) this would result in a corrupted/partial file. Instead, we create a temporary version while saving to disk, and then overwrite the original file with the saved.tmp version. BC3 is not the only program to save this way, while most simple editors (notepad) save directly into the original file.

First of all, thank you very much for your prompt and honest reply!

As we, our development team, had already suspected, BC3 is the victim in all of this rather than the culprit. We already had concluded that it was normal file operations that BC3 uses that would cause the crash, it just did not occur to us right away that temporary files were being moved during the process, overwriting the original file, we always assumed their contents were being replaced.

In light of BC3's saving process details you have provided us, we performed a very basic test that exposed the very nature of the problem and raised even greater concerns amongst our teams.

Here is the exact details on how to replicate the issue WITHOUT BC3 :

1) Create a view-private text file on a clearcase dynamic view with random content, i.e. Readme.txt.
2) Create a second view-private text file on a clearcase dynamic view with random, but different content, i.e. Readme2.txt
3) Open a dos prompt, naviguate to the location of the text files and execute the following command :

move Readme.txt Readme2.txt

This test will cause the STOP error (BSOD) 100% of the time.

As this is a very basic file system operation, I am sure you will understand that under a development perspective it is cause to great concerns with build procedures.

One thing I forgot to mention in my original post was that the implementation of Symantec Endpoint Protection version 12.1.4013 was currently under testing by a select few developers as the rest of the team is still on version 11. Our IT department is pushing for the update of Symantec due to immediate malware threats that is circumventing version 11. They are the ones in contact with both Symantec and Clearcase teams over phone support to try and get this issue resolved, hence why I do not have more technical details of their "finger pointing".

In light of the recent discovery, we were able to build a valid business case to delay the update to Symantec 12.1.4013 due to important risks unrelated to Beyond Compare and that may affect global development productivity and costs.


Here are some more details from IBM related to this issue and of course, none of the workarounds will work for us besides not upgrading Symantec :

BSOD when saving files in remote or local dynamic views when Symantec 12.1.2.x is installed

Error description
When saving view private files in IBM Rational ClearCase dynamic
views using Microsoft Visual Studio 2008 or Scooter Software
Beyond Compare, you may receive a STOP error.

The issue occurs in both local and remote dynamic views.

To workaround the issue:

1. Use an editor such as Notepad, UltraEdit or Emacs. Make sure
to select the appropriate editor based on the text mode of your
views.

2. Use Microsoft Visual Studio.NET 2010 or Visual Studio.NET
2012.

3. Continue using Symantec 11.x or 12.1.1.x and do not upgrade
at this time to Symantec 12.1.2x

BSOD when moving a file from local disk to dynamic view when SEP 12 is installed

Error description
You may experience a Microsoft Windows STOP Error (BSOD) when
moving a file from the local disk on Windows 7 or later to an
IBM Rational ClearCase Dynamic View when Symantec EndPoint
12.1.1.x is installed.

WORKAROUNDS:

1) Copy the file into the dynamic view rather than do a move

2) Add the value MvfsViewAttachMup of type REG_DWORD and assign
it a value of 1, under
HKLM\SYSTEM\CurrentControlSet\Services\Mvfs\Parame ters.

This requires a reboot.

Note: It is possible that you may experience some performance
degradation after implementing this fix. However, this does not
occur in all environments.

Do not upgrade to Symantec 12.1.2.x as this workaround will not
work.

As for Beyond Compare, we are glad we can keep using it. It is very useful software in development and we always underestimate its significance until we lose it (or risk losing it in this case ).

Continue the good work and thanks for your help!

Regards,
Sebastien
Programmer Analyst

[Aaron]

Normally, BC3 cannot cause a BSOD. We normally see this with poor device driver support and a combination of over-taxing the hardware. It is surprising to see this open issue between Clearcase and Symantec. It is unlikely this is something we could workaround without knowing more about the cause. We do not have a license for either Clearcase or Symantec, so it would be difficult for us to recreate this environment (while our trial is free and easily available for any testing they may want to do).

When they "point fingers" is there any technical information included with that? Are they able to reproduce the crash with their software or BC3?

The temporary files exist because BC3 does not directly overwrite the file during a save. If this were interrupted (for example, by a BSOD) this would result in a corrupted/partial file. Instead, we create a temporary version while saving to disk, and then overwrite the original file with the saved.tmp version. BC3 is not the only program to save this way, while most simple editors (notepad) save directly into the original file.

[sgagnon]

Hi everyone,

I work for a governmental agency which develops Java software and who has spent considerable time, effort and money into finding a solution to our current dilemna. I post here as a last resort to see if there is anything we might have overlooked in terms of workarounds.

I will elaborate the facts first, so here is our current work environment:

- Windows 7 Enterprise 64 bit with all windows updates.
- IBM Rational Clearcase 7.1.2.6 with Dynamic views.
- Symantec Endpoint Protection 12.1.4013
- Beyond Compare 3.3.8 build 16340 Standard Edition (fully integrated as the compare tool for clearcase diff merges and comparison)

Here is the problem :

We often do file comparison on dynamic views, either for 2 distinct files
or for its previous version from CC. Whenever we attempt to save either file on the dynamic view from the compare, we get a BSOD.

As an example, lets say I check out the file Readme.txt and I beyond Compare it to a 2nd file named Readme2.txt (which is a view-private) which has differences with the first one, make changes to either one then save it, it will BSOD.

When we reboot, the dynamic view will have two extra files, something similar to : D34564.TMP (which contains the contents of the left file from beyond compare) and a 2nd one named similar to Readme2~D67428247.tmp which is completely empty.

We CANNOT change our use of either Clearcase or Symantec, as these are imposed to us. Our usage of Beyond Compare is for work efficiency as none of the other alternatives satisfies our needs, and we did spend some time investigating.

We are aware of the currently opened ticket with IBM, which can viewed here : http://www-01.ibm.com/support/docvie...id=swg21638422

Both Symantec and IBM companies are pointing fingers at each other, but no concrete solution has been brought up yet. This issue does not seem to only affect Beyond Compare, but in our case, we could only identify the current issue we are facing.

We do not wish to move away from Beyond Compare, but it may be the only option until a fix is brought up.

Does anyone have any ideas of a possible workaround ?

Regards,
Sebastien
Programmer Analyst