Event ID 173 — UDDI Services File Logging

Applies To: Windows Server 2008

UDDI Services provides file logging, which developers can use to debug issues.

Event Details

Product: Windows Operating System
ID: 173
Source: UDDIRuntime
Version: 6.0
Symbolic Name: CannotModifyLogFile
Message: Could not write to log file %1.



Enable file logging

To ensure that messages are written to the log file:

  1. Review the details that are provided in the event message about the failure to write to the log file.
  2. Depending on the details that are provided, determine the root cause, and then take steps to correct the issue. For example, if the details indicate that the hard disk is full, free up some space on the disk. If the details indicate that the security principal that is running UDDI Services does not have rights to access the log file, take the appropriate corrective action.


To verify that file logging is enabled:

  1. Open the UDDI Services Management Console. To open the UDDI Services Management Console, click Start, click Control Panel, click Administrative Tools, and then click UDDI Services.
  2. Right-click the computer name, and then click Properties.
  3. On the Logging tab, under Log File Settings, move the slider to Verbose.
  4. Make a simple inquiry request to the UDDI server either through the Simple Object Access Protocol (SOAP) application programming interface (API) or through the Web user interface (UI).
  5. Open the log file, and confirm that new messages were written to the log.

UDDI Services File Logging

UDDI Services