Nsryjdtyk

After upgrading system to Windows 10 - os 1803 we are getting below issues while working with ClearCase 8.0.1.x/9.0.1.x

• Unable to checkin/checkout.


• Not able to create views.


• Not able to add any file to source control.

The system hangs & crashes while performing any ClearCase operation.

There is no error message, but I have attached screenshot for reference.

Please let us know if there is any issue with the Windows 10 ver(1803), any security system enabled?

Or has ClearCase provided any fix?

We have tried 9.0.1.5 and issue still persists.

This is what we got from windows event log.

The computer has rebooted from a bugcheck.  

The bugcheck was: 

   0x000000c2 (0x0000000000000004, 0x00000000535be990, 0x000000000004efd3, 0xfffff803e01848b1)

for most of them whoever has upgraded to windows 1803 ver :( for people who are still using ver1709 it is working perfectly fine

Then I would recommand contacting IBM support: only them can update their ClearCase 9/Windows 10 compatibility matrix and confirm if MVFS is supported on a more recent (1803) Windows 10 edition.

We also facing same problem and I have raised the case with IBM. Still not yet resolved. As IBM said there are some limitations to work ClearCase with windows 10 and windows 2016.

We tried all the options except Secure boot disable. If possible please do disable secure boot option in Windows 10 and try to checkin/checkout code from CleraCase

Note : It works for Snapshot views. That means the issue related to MVFS

I'm seconding @VonC's recommendation to open a ticket with IBM. When you do that, save a step and collect a clearbug2 and a kernel memory dump to send in as soon as the case is opened. It will save the turn-around time of us asking you for it. If the installed programs list doesn't list installed security software (DLP, Privilege management sw like Avecto, other endpoint security tools), please list those separately as well.

I would also love to know who @ IBM told you there are "limitations" with Win10-1803.

There are a few issues with Windows 10 "version upgrades" breaking things, but they generally don't cause system crashes. Windows 10 upgrades are actually full OS installs that then (imperfectly) migrate application settings. Anything that uses custom network providers (ClearCase is one example) will find that the network providers will be broken or partially broken. Reinstalling is usually required. Again, that has not yet been reported as a cause of a BSOD.

If the upgrade/reinstall didn't fix view creation, please post a separate question on the view creation issue. There may be things we can do to the SMB 2 caches to allow view creation to work in cases where the view storage is not on the client host.

I noticed that the screen shot you posted is a Terminal Services disconnect screenshot. Does the issue only occur over a Terminal Services client connection or does it also happen on a local connection?