Generate the XML and MPP Files
- Ensure that general is set to debug in the logger.properties file to keep the .xml file in the MSP save directory from being removed:
- Navigate to your Document\logs folder
- Open the logger.properties file in a text editor
- Set general=debug
- Save your changes to the file
- Capture the project ID for the project from Clarity
- Reproduce the issue
- If the issue is on opening the project from Clarity, export the project from Clarity to MSP.
- If the issue is saving a project back to Clarity, then attempt to Save the project back to Clarity)
- Navigate to the MSP Default Save location (typically the Documents folder)
- Look for the file(s) with the project ID as the name and the type Microsoft Project Document (which will be the mpp file) and xml
- Copy the file(s) and send this to Broadcom Support if requested (or if you are running into an issue with a specific project)
- Once the XML has been captured, set general back to general=error in the logger.properties as the XML can take up a lot of space
Note: If the XML is not generating even after following the steps above, check to see if Clarity is connected using Citrix. Citrix is limited in support (See: Can the MSP Integration be deployed using Citrix?), and this is one issue that has been noticed when exporting projects from Citrix Servers.
Provide the MSP Workstation logs
- Ensure debugging is set as listed below:
Make the below changes to the logger.properties file found in the Document/logs folder. To edit the logger.properties file, open the file in a text editor such as Notepad or Microsoft Word. By default, each of the options should be set to 'error'.
archive=error (Note, this option is not yet available, this can be left to the default)
- Reproduce the issue
- Close MSP
- Navigate to your Document\Logs folder
- Copy the following logs and send to Broadcom Support:
Save Failed errors
Additionally, if you are seeing a Save Failed message when attempting to save the project back to Clarity, the app-ca.logs may provide more details on root cause. See Accessing the app-ca.log or other Clarity Logs for more details on how to get this log.