My company has developed a Windows Service that acts as a RFC Server application and pings SAP for remote function calls every so often. We have been running into an issue with the generation of a trace file when the SAP client is shut down. We have tried multiple methods to stop the generation of the trace file but each time it is generated as soon as the connection to the SAP client is severed. Below are the three methods we have used:
1) Pass TraceLevel = 0 into the RegisterRFCServer method when we register our server application.
2) Set the CPIC_TRC and even CPIC_TRACE environment variables to 0.
3) Unchecked the 'Trace' checbox on the RFC destination in SAP.
Each time we have tried this, even after setting the environment variables and rebooting we see that a CPICTRC file is being generated in the System32 folder with the contents similar to below:
-
trc file: "CPICTRC1968", trc level: 1, release: "711"
-
[Thr 5836] Sat Sep 19 17:06:15 2009
[Thr 5836] opened by SAP_CMACCPTP (version=711.2008.04.28)
[Thr 5836] *** ERROR => NiSockToHdl: sock 620 not found [nixx.c 1629]
[Thr 5836] *** ERROR => NiSockToHdl: sock 620 not found [nixx.c 1629]
[Thr 5836] *** ERROR => NiSockToHdl: sock 620 not found [nixx.c 1629]
[Thr 5836] *** ERROR => NiSockToHdl: sock 620 not found [nixx.c 1629]
[Thr 5836] *** ERROR => NiSockToHdl: sock 620 not found [nixx.c 1629]
[Thr 5836] *** ERROR => NiSockToHdl: sock 620 not found [nixx.c 1629]
[Thr 5836] *** ERROR => NiSockToHdl: sock 620 not found [nixx.c 1629]
Does anyone have any idea why this file is being generated even though we are setting the trace level to 0 and, more importantly, how we can go about preventing this file from being generated?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.