This document provides the steps on how to generate the xml, mpp, and MSP (Microsoft Project) Workstation logs used for troubleshooting of MSP Issues integrating with Clarity
Broadcom Support may request additional information for troubleshooting MSP issues including the xml and mpp. This document provides the steps on how to provide this information. The xml can also be useful for customers in troubleshooting MSP issues. (Example: MSP Error: 'We're sorry. There seems to be a problem with this file' due to issue with Notes when opening a project)
Release: All Supported
2. Capture the project ID for the project from Clarity
3. 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)
4. Navigate to the MSP Default Save location (typically the Documents folder)
5. 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 (if new Driver)
6. Copy the file(s) and send this to CA Support if requested or if running into an issue with a specific project
7. 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 This is good to use for troubleshooting, but can also take up a lot of space, so make sure to set general back to error when not in use for troubleshooting
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.
1. Ensure debugging is set as listed below:
2. Reproduce the issue
3. Close MSP
4. Navigate to your Document\Logs folder
5. Copy the following logs and send to Broadcom Support:
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.