MSP Target error due to corrupt Global.mpt file

Document ID : KB000004085
Last Modified Date : 14/02/2018
Show Technical Document Details

Microsoft Office® Project (MSP) Target "Out of Range" or Target "Openfromdatabase" error due to corrupt Global.MPT file. Error shown when opening MSP from CA PPM may be something like: 

Target: Microsoft.Vbe.Interop.VBProject Item(System.Object) 
Error: Subscript out of range 
Trace: at Microsoft.Vbe.Interop._VBProjects.Item(Object index) 
at CAClarityAddIn.ClarityUI.updateMacros() 
at CAClarityAddIn.ClarityUI.ClarityUI_Load(Object sender, RibbonUIEEventsArgs e)

Steps to Reproduce:

  1. Log in to PPM
  2. Navigate to a project and from the Properties or Tasks tab, click on the "Open in Scheduler" drop down to open the project in Microsoft Project in Read or Read/Write mode

Expected Result: Project opens successfully
Actual Result: Receive a Target error which may reference "Out of Range" or  "Openfromdatabase" in the Error line of the message     

This issue applies to all supported PAS environments for specified releases.

This is typically due to a corruption of the Global.MPT


Delete the Global.MPT that PPM creates on the user workstation and generate a new Global.MPT using the steps below:

1.      Close MSP
2.      Rename the Global.MPT file under Documents and Settings\username\Application Data\Microsoft\MS Project
  • The file will most likely be in a folder path similar to: C:\Documents and Settings\{username}\Application Data\MicroSoft\MS Project\15\1033
  • If you run into issues finding the Global.MPT ensure hidden folders are made visible:
    • In the folder directory, select Folder and search Options
    • Click the View tab
    • Select the radio button for 'Show hidden files, folders, and drives'
3.      Open MSP and then close MSP

Important: DO NOT DELETE the global.mpt file that MSP creates in the following folder:


C:\Program Files\Microsoft Office\OFFICE11\1033

Additional Information:

-  See: TEC1262892 for Target errors including the "Openfromdatabase" error due to the wrong bit level of the MSP Interface being installed