Event ID 1000 Errors From Source 'logging-bailout' Appear In Windows Application Event Logs in Profile Unity 6.0

Product: ProfileUnity

Product Version: 6.0 and above

Expires on: 365 days from publish date

Updated: August 15, 2014



Windows Event viewer is showing the following Error information

Log Name:      Application
Source:        logging-bailout
Date:          4/25/2014 3:29:13 PM
Event ID:      1000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     XYZ.pc
The description for Event ID 1000 from source logging-bailout cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

failed to write message to log file



The problem  is that the default locations specified in XML configurations are not available until the are created at logon.

For some short period of time the errors will be generated, because the destination of the log files is not available.

The workaround is to point the log path to a specific existing system or network directory with appropriate permissions.


Possible Resolution(s)

In ProfileUnity client tools, typically located in %logonserver%\netlogon\profileunity,  there are several XML files that include a log path reference.


NOTE: The log path must point to an existing folder.

NOTE: The XML files that needs to be changed are compressed. It is possible to simply open these compressed directories and edit the contents just like regular files as an administrator.


The list is showing  the files that require change in the log path.

ProfileService.xml (located in

Change the line

<log level="debug" path="%LOGPATH%"/>

to (for example)

<log level="debug" path="C:\logs"/>


lwl_userapp.xml (located in

<log level="debug" path="%temp%\ProfileUnity"/>

to (for example)

<log level="debug" path="C:\logs"/>


lwl_userapp_player.xml (located in

<log level="debug" path="%temp%"/>

to (for example)

<log level="debug" path="C:\logs"/>


lwl_elevation_service.xml (located in

<log level="debug" path="%LOGPATH%"/>

to (for example)

<log level="debug" path="C:\Logs"/>


For the newly modified files to make it to the desktop you will need to edit the LwL.ProfileUnity.Client.Startup.exe.config located in netlogon or share where the ProfileUnity clients reside.  


Edit the following line by incrementing the original version (example: 6.5.5661 to 6.5.5662).

<setting name="ClientVersion" serializeAs="String">


Once done you will need to either reboot persistent/physical machines or recompose the pool so the computer related startup GPO run again.  

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Article is closed for comments.