KB20074: "Process was canceled due to an interrupt" error when deleting a project that times out after 50 minutes in MicroStrategy Desktop 9.x and Developer 10.x

SYMPTOM:
In a project source containing a large number of projects, and projects containing a very high number of objects, deleting one of the projects can time-out after 50 minutes and produce the following error message:
Process was cancelled due to an interrupt
CAUSE:
The DELETE statement issued by Strategy when a whole project is deleted is taking longer than the hard-coded limit of 50 minutes to complete execution.
 
ACTION:
There are two ways to approach this condition:
 

1. For all versions, carry out a manual delete process of individual or groups of objects. For example, instead of deleting the whole project itself at one time. A possible approach can be to delete Documents first, Reports second, then other objects, and finally the project. The goal is to ensure that each group of DELETE operations execute successfully and fall inside the alloted timeout.
    
   
2. In 9.4.1 and higher, the hard-coded limit can be increased by increasing the value of the MDBaseQueryTimeOut key. The default value for 'short' metadata operations set as "0" is 300 seconds (not unlimited). To override the hard coded limit for 'short' metadata operations, perform the following steps:
    
   
1. Shut down Strategy Desktop.
2. Create the following new DWORD in the registry:
   HKLM > SOFTWARE > Strategy > DATASOURCES > > MDBaseQueryTimeOut = 3000
   
3. In 2-tier, is the project source name used to connect to the project. In 3-tier, will be called "CastorServer", and the registry change must be done on the Strategy Intelligence Server machine.
    
   
4. After making this registry change, close regedit and re-launch Strategy Desktop. The timeout for 'short' metadata operations for this particular data source now will no longer be set at 300 seconds but rather at 3000 seconds. 'Long' metadata operations will now have a timeout of 30000 seconds, or 500 minutes.
   Note: For 3-tier connections, the Strategy Intelligence Server must be re-started.
    
    
   

Registry Modification:
WARNING:
Modifying registry values incorrectly may cause serious, system-wide problems that may require the re-installation of Microsoft Windows NT. Any edit of the registry is done at the user`s own risk. Since these are user-initiated changes, they are not covered by any Strategy warranty. If using Microsoft Windows NT, the user should backup the registry and/or update an Emergency Repair Disk (ERD) prior to alterations.