Trace transferred from remote client

[Former Member]

Hi All,

I am getting frequent entries ( system logs ) in SM21 "Trace transferred from remote client" from last 5-6 days.

what might be the cause of this logs ? As far as I know we didn't activate any trace too.

the below are the details of the log message. 1

Time Type Nr Clt User TCode Grp N Text

13:00:56 DIA 000 R1 M Trace transferred from remote client

Trace transferred from remote client

Details

Recording at local and central time........................ 02.02.2009 13:00:56

Task...... Process User...... Terminal Session TCode Program Cl Problem cl Package

00908 Dialog work process No. 000 1 W Warning STSK

Further details for this message type

Module nam Line Error text Caller.... Reason/cal

thxxhead 5020 ThRqAcc activat

Documentation for system log message R1 M :

To be able to run a trace for server-wide processes, the trace

setting is inherited when RFC function modules are called.

Technical details

File Offset RecFm System log type Grp N variable message data

1892 31320 m Error (Function,Module,Row) R1 M ThRqAccactivatthxxhead5020

regards,

Sen

[Former Member]

Hi Sen,

please look at "Note 357683 - Trace adopted by remote client".

It looks like another system has the trace turned on and connects to your system via RFC.

Regards,

ulf

[Former Member]

Hi Ulf,

Thanks for the response.

I had already gone through this particular note. since it happen in production server I was checking for any other options where we can stop these error logs without changing the profile parameter.

Want to know if there are any effect of this in the server

Regards,

Sen

[Former Member]

If the file system whre the traces are stored are full, your server will have problems, so i'd have a look at it. You can limit the size by adapting rstr/*-parameters in RZ11. And you can change the parameters which will stop adopting the trace from remote dynamically in RZ11

Beside of the filesystem, there are no problems i know. But the fs can get full pretty quickly if all workprocesses write a trace

[Former Member]

I think as of the Trace file it will be overwritten with the new trace.

It can be stop trace transfer by changing the profile parameter which will require to restart the SAP again.

[Former Member]

Hello,

Can u please help me in solving this . I'm also getting same error in Pro sys, SM21 .

How did u check in SM04 . Please help

I see profile parameter is dynamic so no need to restart SAP .

Thanks

Dharmendra.