This tracing/logging content applies to the new AD RMS client, Active Directory Rights Management Service Client 2.x. This client is also known as the MSIPC client. Office 2013 installs this client.

Office 2013 offers additional application logging capabilities. This content utilizes both the MSIPC client and Office application logging functionality.

For information on logging in the MSDRM client please see AD RMS Troubleshooting: Client-Side Tracing (MSDRM).

Prerequisites:

1. Download the Sysinternals Debug View tool. Place this on the client desktop. (Debug View download link)
2. Create a batch file on the client desktop to enable logging.
3. Create a batch file on the client desktop to disable logging.
4. Run Debug View as an administrator.
5. Accept the EULA if prompted.
6. Under the Capture menu enable the Capture Global Win32 option.
7. Ensure the capture icon is “on” (it is by default).
8. Once the data collection completes stop capturing by clicking the capture icon.
9. Under the File menu select Save As.
10. Save the data to a file.

Using Debug View:

Screenshots:

Create an enable logging batch file:

Create a batch file with the following commands. These commands create or update the needed registry values to enable the logging. I typically create a file named “ENABLE_IPC_Logging.bat.”

Create a disable logging batch file:

Create a batch file with the following commands. These commands update the needed registry values to disable the logging. I typically create a file named “DISABLE_IPC_Logging.bat.”

Office Application logging:

Everything I know about the Office application logging I found in this KB article. Once enabled the log files are written to the user’s temp directory. One may use the Windows start menu or command prompt to get to the temp directory. If using the start menu just type %temp% and press enter. If using a command prompt type “cd %temp%” followed by a “start .” command.

Various files may be generated when using this logging. Typically a file named <application>.exe.log for the application in question is the one needed for troubleshooting. For instance, if Word is the application having issues, the Office application logging generates “winword.exe.log” file.

Data Gathering (Troubleshooting):

1. Close any open Office applications.
2. Open an administrative command prompt.
3. In the command prompt run the “ENABLE_IPC_Logging.bat” file.
4. Run Debug View as an administrator and configure it as shown earlier.
5. Open the appropriate Office application and reproduce the issue.
6. Save off the Debug View data.
7. Gather the Office application logging.