We deployed an application written using the .NET SDK. We also deployed some of our own custom reports for it. That all works fine. But the customer has some legacy reports they wanted to run through our application and these legacy reports generate these _trace.glf files ... whereas our distributed reports do not.
Otherwise, the reports appear to run properly. Customer does not want these trace files cluttering up their machines.
Here's the contents of the trace file:
FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2
ENCODING:UTF8
RECORD_SEPARATOR:30
COLUMN_SEPARATOR:124
ESC_CHARACTER:27
COLUMNS:Location|Guid|Time|Tzone|Importance|Severity|Exception|DeviceName|ProcessID|ThreadID|ThreadName|ScopeTag|MajorTick|MinorTick|MajorDepth|MinorDepth|RootName|RootID|CallerName|CallerID|CalleeName|CalleeID|ActionID|DSRRootContextID|DSRTransaction|DSRConnection|DSRCounter|User|ArchitectComponent|DeveloperComponent|Administrator|Unit|CSNComponent|Text
SEVERITY_MAP: |Information|W|Warning|E|Error|A|Assertion
HEADER_END
.\tracelog_logger.cpp:188:__thiscall CXLib500::TraceBridge::TraceBridge(void): TraceLog message 1
|f01a1753-672a-7874-eb32-5f57ee88c555|2014 01 15 16:31:42:746|-0600|>>|A| |PCMSCrystalViewer| 468|4844|| ||||||||||||||||||||||The internal logger count not create the required directories
The specified path is not accessible or does not exist: C:\Program Files\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\logging\
Thank you.
