VSLG4006: 64-bit TracelogProfiler.dll is not registered; historical data may fail to record for 64-bit processes. Use 'regsvr32 TracelogProfiler.dll' to fix the problem.
VSLG1001: Logger name '{0}' is not valid. Logger name must contain only letters, number, period(.), dash (-) or underscore ...
VSLG1012: Unable to create event '{0}'. Another logger with the same name might be running, or the object name might be in ...
VSLG4004: TracelogProfiler.dll is not registered; historical data may fail to record. Use 'regsvr32 TracelogProfiler.dll' ...
VSLG4005: 32-bit TracelogProfiler.dll is not registered; historical data may fail to record for 32-bit processes. Use 'regsvr32 ...
VSLG4006: 64-bit TracelogProfiler.dll is not registered; historical data may fail to record for 64-bit processes. Use 'regsvr32 ...
VSP 7003: "{0}" Failed to stop monitor. This could happen if VSPerfMon.exe is detached before VSPerfASPNetCmd.exe finished ...
VSP 7006: The specified profiling type "{0}" is not a valid profiling type. Check the /? help text for valid profiling types. ...
VSP 7007: The website path is set to "{0}". "{1}" will be ignored. If this, or "{0}", was intended as a flag, check that ...
VSP1713: Dynamic Hardware Partitioning happened during data collection. File contains inaccurate data: {0} Use /Admin:driver ...