Checkin to a locked activity fails with Internal Error detected

Symptom

The following scenario can produce unexpected results for ClearCase versions 2003.06.xx :

1. Create an activity, act1
   
   
2. Checkout a file on that activity, act1
   
   
3. Create a new activity, actlock
   
   
4. Lock the new activity, actlock
   
   
5. Try to checkin the file on the locked activity, actlock. This will fail, as is expected.
   
   
6. Try to check in the file on another, non-locked activity, act1. This will also fail, resulting in the following error:

• At the command line:
  cleartool: Error: INTERNAL ERROR detected and logged with the NT Event Service.
  See the Event Viewer for the error message.
  cleartool: Error: Unable to check in "<file name>".
  
  
• From the GUI:
  Error checking in '<path to file>'
  INTERNAL ERROR detected and logged with the NT Event Service.
  See the Event Viewer for the error message.
  Internal Error detected in "../vob_act.c" line 1225.
  Unexpected error.

The problem persists even if the locked activity is unlocked or if the activity is reset on the command line.

The locked activity shows no change sets, but does show a hyperlink when cleartool describe -long -ahlink -all activity:<activity>@\PVOB-tag is run against it. This indicates that a checkin was started against the locked activity, even though it could not complete.

The activity that the element was originally checked out from, act1, in this example, will also show a hyperlink.