How does Security Manager use the MSDTC log file? (NETIQKB2140)

  • Document ID:7702140
  • Creation Date:02-Feb-2007
  • Modified Date:14-Feb-2008
    • Micro Focus Products:
      Security Manager

Resolution

goal
How does Security Manager use the MSDTC log file?

goal
How do I change the size of the MSDTC log file?

fact
Security Manager 3.X

fact
Security Manager 4.X

fix

The msdtc.log file is used by the Security Manager Database and Data Access Server (DAS) computers as part of the data collection process.  This log file is generated by the Microsoft Distributed Transaction Coordinator service, and is used to ensure successful data-gathering operations in coordination with Microsoft SQL Server.

As part of the Security Manager software requirements, NetIQ recommends increasing the size of the msdtc.log file on both the Database computer and on any DAS computers to 512 MB.  It is also recommended that the MSDTC log be placed on a different storage device from the Security Manager database files.

The DAS server writes to the OnePoint database using two-phase commit processes.  If the input and output (I/O) load is high on the DAS server(s), then the I/O load will also be high on the database computer.  Because of this, the MSDTC log needs to be sized accordingly to ensure that data is successfully collected during times of high activity. 

To adjust the size of the MSDTC.log perform the following steps:

For Windows NT machines:  Note: ensure that the DAC.exe component is installed.  This is available in the NT4 Option Pack:

  1. Ensure you have more than 512 MB available on the hard drive.
  2. Stop the MSDTC service.
  3. Using the NT Option Pack Transaction Server Explorer, navigate to the MSDTC Log File Size screen.
  4. Adjust the slider bar to 512 MB.
  5. Press the RESETLog button. This step has to be taken for the resizing process to occur.
  6. Click OK.
  7. Restart the MSDTC service.

For Windows 2000 machines:

  1. Navigate to Start | Run and type mmc.exe .  The Microsoft Management Console (MMC) window appears.
  2. Select Console | Add/Remove Snap-in....
  3. On the 'Standalone' tab, click the Add button.
  4. From the list of snap-ins, select Component Services, click the Add button, and then click Close.
  5. Click OK.  The Component Services snap-in should appear in the MMC.
  6. Navigate to Component Services | Computers | MyComputer.
  7. Right-click on My Computer and select Properties.
  8. Click on the 'MSDTC' tab.
  9. Click on the Stop button to stop the Distributed Transaction Coordinator service.
  10. In the field labeled Capacity, change the value to 512.
  11. Click the Reset log button.  The DTC Console Message window appears with an informational message.
  12. Click Yes to reset the log file.
  13. Click the Start button to restart the Distributed Transaction Coordinator service.

 

NOTE: Do not delete an existing MSDTC log prior to resizing it! This results in a corrupted MSDTC service and usually requires reinstallation of the operating system.

Please refer to the following Microsoft Knowledge Base article for information about reinstalling the MSDTC service in the event that it becomes unusable:



Additional Information

Formerly known as NETIQKB2140