did not start (exit code {0})
!Start a logger in the background.
&
Logger did not start after {0} seconds
&
VSLG1013: Unable to delete file '{0}'.
)Unable to locate logger executable image.
-An error occurred on the underlying transport
.Enable or disable instrumentation by the shim.
2VSLG1019: Unable to contact logger with name '{0}'
5An error occurred during website instrumentation: {0}
6An error occurred during environment manipulation: {0}
7Unable to start a logging session for process {0} ({1})
8An error occurred during a website or service reset: {0}
Unable to parse value '{0}' for command-line argument '{1}'
=VSLG1021: An error occurred while closing the log file '{0}'.
BTiming data should have time greater than or equal to the logfile start time in stack frame '{0}'.
CVSLG1007: Cannot start logger: logger name '{0}' is already in use.
Error {0}:
FThere was an error reading the IntelliTrace configuration section: {0}
IEndTime should have time greater than or equal to the logfile start time.
IntelliTrace is unable to function properly since the file is locked, try exiting the processes below and launching IntelliTrace.
IntelliTrace start application.iTrace /n:mylogger
JAn unexpected error occurred and logging session for '{0}' ({1}) has ended
KStartTime should have time greater than or equal to the logfile start time.
SUnable to connect to logger process. Logger may not exist or may be shutting down.
Start Time
The Application Pool {0} is already configured for IntelliTrace collection. To change settings, please stop, then start collection on the Application Pool.
The Application Pool {0} is currently in a Stopped state. Please start the Application Pool before attempting to modify IntelliTrace collection.
Unable to assign NullData to type {0}. NullData is only allowed for reference types. For System.String and System.Object, use DataFactory.CreatePrimitive instead.
Unable to lock the registry for IntelliTrace Collection modifications. Please ensure no other IntelliTrace commands are running.
VSLG1012: Unable to create event '{0}'. Another logger with the same name might be running, or the object name might be in use by another application.
VUnable to access the environment for Application Pool {0}. Please ensure the user for the Application Pool is valid.
ZAn unexpected fatal error has occurred and the logging service and all sessions have ended
[Please use the 64-bit PowerShell command window to start the 64-bit Application Pool {0}.
_The logger exited unexpectedly. Run the above command command to see the logger error message.