- This topic has 3 replies, 2 voices, and was last updated 2025-01-21 at 7:00 am by
.
-
Posts
-
-
I’m trying to track down a bug in some code that’s only affecting one customer so we’re logging to file to try and catch the problem. I’m using the following code which seems to work for a day or two but then just stops logging anything further to the file. In that time it seems to have created 2 x 500MB files and then the last one if just 84MB. Plenty of disk space remaining. Any suggestion as to what could cause it please ?
Dest := TCodeSiteDestination.create(Vcl.SvcMgr.Application);
Dest.LogFile.Active := DebugHook = 0; // sets file logging if no debugger
Dest.LogFile.FileName := ‘HireTrack NX Integration Server.csl’;
Dest.LogFile.FilePath := ‘$(HireTrack)’;
Dest.LogFile.MaxSize := 500000;
Dest.LogFile.MaxParts := 10;Dest.Viewer.Active := true;
CodeSite.Destination := Dest;
CodeSite.ConnectUsingTcp;Cheers
David
-
Hi David,
Interesting that it logs to the file for a day or two and then stops. Typically, if there is an issue with file logging, it’s immediately apparent, such as file permissions, wrong path, etc. Is it possible that the CodeSite logger is getting disabled at some point in your application? That would cause messages to stop getting logged.If you have access to the computer, or can get someone to grab a file from the computer, I would like to see the CSDispatcherLog.txt file. It is located in the following path:
C:\Users\\AppData\Local\Raize\CodeSite\5.0\CSDispatcherLog.txt If you are able to get this file, please send it to support@raize.com and I’ll take a look.
Ray
-
-
-
- You must be logged in to reply to this topic.