Sm21 log (Transaction Canceled DB 61)

Hi,
Can u pls suggest for the below log, what action should be take to void this error, Iam getting toomany log daily.
08:02:01 BTC 021 300 WF-BATCH                  D0 1 Transaction Canceled DB 612 ( #0000000000001 RSWWDHEX )
Details
Recording at local and central time........................ 12.01.2010 08:02:01
Task...... Process                      User...... Terminal Session TCode Program Cl Problem
01478      Background Processor No. 021 WF-BATCH                  1       RSWWDHEX K SAP Web
Module nam Loc T100................    Parameters
                DB                  612
Documentation for system log message D0 1 :
The transaction has been terminated. This may be caused by a
termination message from the application (MESSAGE Axxx) or by an
error detected by the SAP System due to which it makes no sense to
proceed with the transaction. The actual reason for the termination
is indicated by the T100 message and the parameters.
Thanks
Suman

Hi,
it looks like the job (program RSWWDHEX) for monitoring deadlines in workflow is failing to start. Have you applied support pack recently? You can try to reschedule that job using transaction SWWB. The problem is described in note 618656. There are also some other notes related to this job. So I would suggest to search for additional notes.
Cheers

Similar Messages

SM21 Log - Transaction Termination 01 540

Hi,
Lately, the below error has been creating in SM21 syslog multiple times a minute in our SAP system.
There is no user and txn detected in SM21 syslog.
I have deleted the CUA, its child systems, GUM data and BD64 but it still does not stop.
I have checked SM50/SM51, no suspicious activity going on. I have checked batch jobs across systems, nothing running.
I have checked SM04, no suspicious users/connection. No dumps at ST22.
I am running out of ideas. Does anyone has any clue what could be causing it?
We are running R/3 46C, Oracle 10.2.0.2, AIX 5.3. Kernel 46D_EXT, 2415.
SM21 Syslog
=============
"DIA 00 D01 Transaction termination 01 540 ( )"
Documentation for system log message D0 1 :
The transaction has been terminated. This may be caused by a
termination message from the application (MESSAGE Axxx) or by an
error detected by the SAP System due to which it makes no sense to
proceed with the transaction. The actual reason for the termination
is indicated by the T100 message and the parameters.
Additional documentation for message 01 540
You cannot log on (CUA system authorization missing)
No documentation exists for message 01540
Thanks in advance.

Check for error messages on the developer traces of the dialog instances dev_w*
Also check that the CUA user has proper rights specially S_RFC and that the CUA child is a trusted system
Regards
Juan

Transaction Canceled BT 510

Hello All,
I am getting many system log " Transaction Canceled BT 510" in client 000 user sapsys. There are no dumps occuring and no BTC jobs failing. the system log entry shows. can some body provide me some information about it.
============================
Failed to read step table
&CAUSE&
When a job is started, the individual steps are processed in sequenti
order. For this to function, the steps must be read in their defined
order and then processed.
The appearance of this message means that the read access to the step
in the current job failed.
&SYSTEM_RESPONSE&
The job involved cannot be started normally, and is therefore set to
status "Cancelled". In addition, this message is recorded in the
corresponding job log.
&WHAT_TO_DO&
Check the SAP system log for messages that occurred around the time o
this message. In particular, look for messages from the database
interface, which will normally describe the cause of the problem more
precisely.
If no database-specific log entries exist for this problem, please
contact your SAP system administrator for further analysis.
============================

Hello Kiran,
While deleting any entries you need to be careful enough. Please first check on TEST system before proceeding to DEV to avoid unnecessary complications.
you can also delete the entries from SQL level.
DELETE FROM SAPR3.TBTCO WHERE JOBNAME = 'XXXXX' AND RELUNAME = 'YYYYYY' AND SDLSTRTDT > 'YYYYMMDD'
Please note that SAP will not advise and support if anything goes worng.
when you got SM21 error log "Transaction Canceled BT 510", did you check SM50, SM12, workprocess logs and alert SID log to drill down the issue further?
Thank you,
Shyam

Transaction Cancellation errors- SM21

<b>Hello Forum,
We have WAS installed on Windows clustering with 5 other application servers. We are seeing errors for every minute in sm21 log:</b>
15:00:09 DIA 0 000 SAPSYS            D01 Transaction Canceled 00 152 ( )
15:00:09 DIA 0 000 SAPSYS            R68 Perform rollback
15:01:21 DIA 0 000 SAPSYS            D01 Transaction Canceled 00 152 ( )
15:01:21 DIA 0 000 SAPSYS            R68 Perform rollback
15:02:11 DIA 0 000 SAPSYS            D01 Transaction Canceled 00 152 ( )
<b>We are also seeing errors in Windows Event log for every minute.. not able to trace whether the sap errors are due to Windows errors:</b>
The description for Event ID ( 17898 ) in Source ( SAPCFP_00 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 0, 0, , , , , , , , , , , , , , , , , , , 1, 5, 2, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , 00                  152.
If any one had faced this problem, please throw some light.
Thanks
Guru

Hi,
I have the same problem with this... everyday and every minute...
15:17:58 BTC 008 100 AARON             D01 Transaction Canceled DB 612 ( #0000000000000 RSBATCH_WRITE_PROT_TO_APPLLOG )
15:17:58 BTC 008 100 AARON             R68 Perform rollback
15:22:58 BTC 008 100 AARON             D01 Transaction Canceled DB 612 ( #0000000000000 RSBATCH_WRITE_PROT_TO_APPLLOG )
15:22:58 BTC 008 100 AARON             R68 Perform rollback
15:26:59 BTC 008 100 AARON             D01 Transaction Canceled DB 612 ( #0000000000000 RSBATCH_WRITE_PROT_TO_APPLLOG )
15:26:59 BTC 008 100 AARON             R68 Perform rollback
15:31:59 BTC 009 100 AARON             D01 Transaction Canceled DB 612 ( #0000000000000 RSBATCH_WRITE_PROT_TO_APPLLOG )
15:31:59 BTC 009 100 AARON             R68 Perform rollback
15:36:59 BTC 008 100 AARON             D01 Transaction Canceled DB 612 ( #0000000000000 RSBATCH_WRITE_PROT_TO_APPLLOG )
15:36:59 BTC 008 100 AARON             R68 Perform rollback
15:41:59 BTC 008 100 AARON             D01 Transaction Canceled DB 612 ( #0000000000000 RSBATCH_WRITE_PROT_TO_APPLLOG )
15:41:59 BTC 008 100 AARON             R68 Perform rollback
15:46:59 BTC 008 100 AARON             D01 Transaction Canceled DB 612 ( #0000000000000 RSBATCH_WRITE_PROT_TO_APPLLOG )
15:46:59 BTC 008 100 AARON             R68 Perform rollback
15:51:59 BTC 008 100 AARON             D01 Transaction Canceled DB 612 ( #0000000000000 RSBATCH_WRITE_PROT_TO_APPLLOG )
15:51:59 BTC 008 100 AARON             R68 Perform rollback
What caused this problem? How do I solve this?

SM21 Errors DIA 000 000 SAPSYS D01 Transaction Canceled 00 152

OK I have done almost every search I c an think of in service.sap.com, here and in Google. I have exhausted my mind... I can not figure out what is causing the problem. Here is what I am seeing:
14:16:12 DIA 000 000 SAPSYS            R68 Perform rollback
14:17:13 DIA 000 000 SAPSYS            D01 Transaction Canceled 00 152 ( )
14:17:13 DIA 000 000 SAPSYS            R68 Perform rollback
14:18:13 DIA 000 000 SAPSYS            D01 Transaction Canceled 00 152 ( )
14:18:13 DIA 000 000 SAPSYS            R68 Perform rollback
14:19:13 DIA 000 000 SAPSYS            D01 Transaction Canceled 00 152 ( )
14:19:13 DIA 000 000 SAPSYS            R68 Perform rollback
14:20:13 DIA 000 000 SAPSYS            D01 Transaction Canceled 00 152 ( )
14:20:13 DIA 000 000 SAPSYS            R68 Perform rollback
14:21:13 DIA 000 000 SAPSYS            D01 Transaction Canceled 00 152 ( )
14:21:13 DIA 000 000 SAPSYS            R68 Perform rollback
14:22:14 DIA 000 000 SAPSYS            D01 Transaction Canceled 00 152 ( )
14:22:14 DIA 000 000 SAPSYS            R68 Perform rollback
Double clicking I see:
Documentation for system log message D0 1 :
The transaction has been terminated. This may be caused by a
termination message from the application (MESSAGE Axxx) or by an
error detected by the SAP System due to which it makes no sense to
proceed with the transaction. The actual reason for the termination
is indicated by the T100 message and the parameters.
Additional documentation for message 00                  152
Name or password is incorrect. Please re-enter
No documentation exists for message 00152
As you can see this is happening many times a second. I have checked the batch jobs and can not see anything there. I see that there is a incorrect name or password but where? I can not dig it up. This is a Netweaver 04 XI 3.0 box running on a HP-UX platform. XI Seems to be running fine so I don't want to reset all the JAVA passwords. Is there any way to trace this down. I set the Trace on the Dialog process' to 3 but I can not decipher them.
Please give me any advice as I am stuck. This is not stopping us from working but it is getting hard to read through the logs in SM21 when this is none stop.
Best Regards,
Paul

Hi
The error
14:17:13 DIA 000 000 SAPSYS D01 Transaction Canceled 00 152 ( )
14:17:13 DIA 000 000 SAPSYS R68 Perform rollback
Is basically a logon time error, when you try to logon through SAPGUI in dialog mode, the instance is 000 and logon takes place through dialog process 000.
As SM21 log further says:
Name or password is incorrect. Please re-enter
This is the message you get at bottom screen of gui when you enter wrong user id or password.
Many a times when user wrongly enter the invalid logon data this error is evident in SM21 log.
Now in your case this is occuring every minute, so there might be some process which initiates a dialog logon to the system every minute but unable to do that.
So in this case this could be the CCMS monitoring component on a remote system e.g. a Solution Manager system, which is monitoring your XI system and trying to login to get the data.
Please check if this is possibility in your case.
Hope this might help.
Rahul

Transaction Canceled V1 322 in System Log

Hi All,
We've been having this Transaction Canceled V1 322 messages in sm21 for months now, but we can't really find the cause. Does anyone have any idea why it appears in the logs?
thanks and regards
Carlos

Hi. For starters, Disk Utility won't do anything at all for this issue
I've seen that fairly frequently for the same thing (USB connection from an APC UPS).
It can be safely ignored, from all I've seen.
http://lists.apple.com/archives/usb/2004/Feb/msg00042.html
shows some discussion of the issue from a different angle.
Some info can be read via
less /System/Library/Frameworks/IOKit.framework/Versions/A/Headers/usb/USB.h
less /System/Library/Frameworks/Kernel.framework/Versions/A/Headers/IOKit/usb/USB.h
If you run
strings /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBOHCI.kext/ Contents/MacOS/AppleUSBOHCI
you'll see:
"AppleUSBOHCI[%p]::Found a transaction which hasn't moved in 5 seconds on bus %ld, timing out!"
Possibly cause for concern, but what I think is at fault, is the APC - that it's timing out a (USB) communication. One person said installing a USB2 card made the issue go away, I have no idea if such a move makes sense for anyone else or that it would have the same effect.

SAP-Basis system: Transaction canceled 15

Dear Gurus,
We have ECC 6.0 on DB2 9.1 fp 5 on windows 2003.
I am getting this error in syslog.
SAP-Basis system: Transaction canceled 15
Thanks
Rao.

Thanks for reply
This is the log in SM21.
Can you tell me how to do this in sap or database level.
&CAUSE&
When the update data is reorganized, it deletes inconsistent
(incomplete) update requests. While one user is carrying out a
transaction, the the update data is often in a state of incompletion.
When the transaction is completed and the update begun, the data becomes
complete. If the data is reorganized in productive operation, temporary
inconsistencies may get deleted. A data inconsistency with incomplete
data can therefore arise.
&SYSTEM_RESPONSE&
Reorganize the update tables only where there are no users logged onto
the system.
&SYS_ADMIN&
Regards
Rao.

Transaction Canceled VL650

Hi folks,
I've started seeing a large number of these errors in SM21 in our ERP Production system.
Details Page 2 Line 47 System Log: Local Analysis of srvsap64r3p1             1
|Time    |Type|Nr |Clt|User |TCode|Grp|N|Text                                            |
|09:25:04|BTC |042|900|ADMIN|VL22N|D0 |1|Transaction Canceled VL 650 ( 4501710932 00010 )|
Transaction Canceled VL 650 ( 4501710932 00010 )
Details
Recorded at local time..................................... 01.09.2014 09:25:04
Recording time re-calculated to central time............. 01.09.2014 04:52:00
Entry in collective system log at local time............... 01.09.2014 04:52:00
|Task......|Process                     |User......|Terminal|Session|TCode|Program |Cl|Problem cl        |Package|
|14564     |Background Processor No. 042|ADMIN     |        |      1|VL22N|SAPMV50A|K |SAP Web AS Problem|SLOG   |
|Documentation for system log message E0 3 :                            |
|                                                                       |
|The specified program encountered a problem. A short message in English|
|is output describing the problem.                                      |
|If there are no other related entries in the system log, the program   |
|solved or at least found a workaround to the problem.                  |
|If these messages occur frequently, or the program is unable to        |
|complete processing, notify SAP of the message and include the module |
|name and location, or the line number of the system log message. This |
|helps the support team locate the cause of the error.                  |
|In this context a program is an independent component at the           |
|operating system level.                                                |
Parameter
| 1 .... 4501710932|
| 2 .... 00010     |
Technical details
|File|Offset|RecFm|System log|Grp|N|variable message data |
| 96| 15840|     |          |E0 |3|VL                  650|
I had a look around online but drawing a blank with this one. Just wondered if anyone had seen this sort of thing before?
(Windows/Oracle 11.2.0.2.0)

Thanks for the reply.
Checked all that. User all check outs. Not locked, has SAP_ALL, etc
No dumps.
There are some jobs running as user ADMIN but no issues at a glance. All finished as normal, no jobs cancelled or anything.

ITS Transaction Canceled ITS_P 001 ( )

We have just tranported all the ITS transactions and services to the TEST system exactly as they are in the DEV system and now all the services with ~disconnectonclose = 1 are failing to run. If we change the setting to ~disconnectonclose = 0 they all work, but obviously the user is then still logged in.
All these transactions have ~disconnectonclose = 1 in the DEV system and are all running without any problems.
The error in SM21 just says:
Transaction Canceled ITS_P 001 ( ) which I can't find any notes on.
The trace files just report that the user was logged off and no other errors.
I have added ~disconnectonclose to WEBGUI and this works ok.
I have run out of ideas as to what to look at next. Can anyone point me in the right direction as to what to look for to fix this problem. The ITS, kernnel and patch are also the same on both servers.
Thank you
Karen

Hi everyone,
I'm getting the same error, but for my part I am trying to configure a R/3 system for my Entreprise Portal (EP7, recent SP).
Can anyone help me ?
Thanks a lot.
Fabien.

Transaction Canceled CU 013 ( )

Hi
System Details
============
R/3 4.7 Enterprise Extn set 110
Oracle 10G
Sun Solaris 5.9
Kernel 247
Non Unicode
Issue
====
I get the below following error in sm21 for every thirty minutes. I checked the background job. No background jobs have failed and no short dumps have occurred.
Error Details:
==========
Time     06:32:55
Type.    BTC
Nr         23
Client    040
User      OPERATOR
Tcode    VC/2
MNo      D01
Text      Transaction Canceled CU 013 ( )
Documentation for system log message D0 1 :
===================================
The transaction has been terminated. This may be caused by a
termination message from the application (MESSAGE Axxx) or by an
error detected by the SAP System due to which it makes no sense to
proceed with the transaction. The actual reason for the termination
is indicated by the T100 message and the parameters.
Additional documentation for message CU                  013
===========================================
Internal error: &1, &2, &3, &4
No documentation exists for message CU013
There is a background job which runs every thirty minutes. After this completes I see this message in SM21 which I had suspected was the cause. However a developer who had designed this job does not find any relavance between the job and the error.
Please note that this issue has nothing to do with 10G. We had recently upgraded and this error has been present before the upgrade.
Any ideas would be appreciated.
regards
Ravi

You can check on the logs which process was used, then check the developer traces to see if you can find more info.
Regards
Juan

Transaction Canceled 15 100 ( )

Dear gurus,
I am gettingthis errro in sm21. my environment is ECC 6.0 DB2 Windows 2003
Transaction Canceled 15 100 ( )
The transaction has been terminated. This may be caused by a
termination message from the application (MESSAGE Axxx) or by an
error detected by the SAP System due to which it makes no sense to
proceed with the transaction. The actual reason for the termination
is indicated by the T100 message and the parameters.
Additional documentation for message 15 100
Reorganization of update date not allowed in batch
&CAUSE&
When the update data is reorganized, it deletes inconsistent
(incomplete) update requests. While one user is carrying out a
transaction, the the update data is often in a state of incompletion.
When the transaction is completed and the update begun, the data beco
complete. If the data is reorganized in productive operation, tempora
inconsistencies may get deleted. A data inconsistency with incomplete
data can therefore arise.
&SYSTEM_RESPONSE&
&WHAT_TO_DO&
Reorganize the update tables only where there are no users logged ont
the system.
&SYS_ADMIN&
How to reorganize this.
Regards
Rao.

Hi,
Is there any errors in the SM21 log? What SAP kernel version and patch level are you on?
Cheers!

SAP-Basis System: Transaction Canceled 15 100 ( )

Hi Gurus,
i am getting this error message in event viewer at every night 12.30
SAP-Basis System: Transaction Canceled 15 100 ( )
what exactly could be the reason please help me ASAP
Cheers.

Hi,
Is there any errors in the SM21 log? What SAP kernel version and patch level are you on?
Cheers!

SM21 Logs being deleted

Hi Folks,
I have noticed that some of the entries from the SM21 logs get deleted in few hours.
For example our team report the error "Transaction Canceled DB 645" in sm21 log at 26.05.2011 at 4:00 AM.
When we checked the SM21 logs at 10:00 AM on the same day, the entry was no longer present.
Request you to kindly help me in this.
Regards,
Yasmin

My Stderr file reads the below. Please help me understand the context and if there is any issue.
(22476) New Child Process created.
(22476) Starting local Command:
Command: dw.sapPRD_DVEBMGS00
pf=/usr/sap/PRD/SYS/profile/PRD_DVEBMGS00_ebdchux2
ICM up and operational (pid: 22480) ***
work process W3 died => ThSigHandler: signal
work process W1 died => ThSigHandler: signal
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
work process W1 died => ThSigHandler: signal
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
work process W4 died => ThSigHandler: signal
work process W2 died => ThSigHandler: signal
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
work process W1 died => ThSigHandler: signal
work process W4 died => ThSigHandler: signal
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
work process W1 died => ThSigHandler: signal
work process W2 died => ThSigHandler: signal

Transaction Canceled BT 513

Applying support packs SAPKB70014 on ECC6/NW7 IDES system but SPAM runs forever in DDIC_ACTIVATION phase , I syslog i have following error
Syslog
04:03:26 DIA 004 000 SAPSYS                D0 1 Transaction Canceled BT 513 ( )
04:03:26 DIA 003 000 SAPSYS                D0 1 Transaction Canceled BT 513 ( )
04:03:26 DIA 002 000 SAPSYS                D0 1 Transaction Canceled BT 513 ( )
04:03:26 DIA 000 000 SAPSYS                D0 1 Transaction Canceled BT 513 ( )
04:03:30 DIA 001 000 SAPSYS                D0 1 Transaction Canceled BT 513 ( )
04:03:30 DIA 002 000 SAPSYS                D0 1 Transaction Canceled BT 513 ( )
04:03:30 DIA 003 000 SAPSYS                D0 1 Transaction Canceled BT 513 ( )
04:04:29 DIA 001 000 SAPSYS                D0 1 Transaction Canceled BT 513 ( )
04:04:29 DIA 002 000 SAPSYS                D0 1 Transaction Canceled BT 513 ( )
04:04:29 DIA 003 000 SAPSYS                D0 1 Transaction Canceled BT 513 ( )
and
SLOG1010 has the following
TART tp_getprots          PSD Q      20100308090958              TPFANNST     mucr3psd 20100308090947
WARNING: System PSD. Warning.        20100308091504 :
WARNING:       Background job not running properly. Function: Q Jobcount: 10054700 Status: Y.
      Please check the system. Use transactions SM21, SM37, SM50.
WARNING:       (This warning is harmless if no further warnings follow.)
WARNING: System PSD. Warning.        20100308092004 :
WARNING:       Background job not running properly. Function: Q Jobcount: 10054700 Status: Y.
      Please check the system. Use transactions SM21, SM37, SM50.
WARNING:       (This warning is harmless if no further warnings follow.)
WARNING: System PSD. Warning.        20100308092504 :
WARNING:       Background job not running properly. Function: Q Jobcount: 10054700 Status: Y.
      Please check the system. Use transactions SM21, SM37, SM50.
WARNING:       (This warning is harmless if no further warnings follow.)
WARNING: System PSD. Warning.        20100308093004 :

Hi,
From the log it says "Background job not running properly", hence please check if job RDDIMPDP is scheduled correctly. If not then login to 000 client and execute program RDDNEWPP which will schedule the job RDDIMPDP periodically which is required for support packs and transports.
Also, check if the background work process avaialble are sufficient.
Regards,
Sharath

Syslog messages: Transaction Canceled 00 554 ( )

Hi All,
I have an problem with running my system, there is an messsage:
Transaction Canceled 00 554 ( )
in TA SM21. It seems that some job tooks system down but I can't find an reason so far. The precise sequence of SM21 logs is like following:
13:00:25 BTC 03 100 JOB_USER         D01 Transaction Canceled 00 554 ( )
13:00:25 BTC 00 100 DIA_USER          D01 Transaction Canceled 00 554 ( )
13:00:25 BTC 03 100 JOB_USER          R68 Perform rollback
13:00:25 BTC 00 100 DIA_USER          R68 Perform rollback
13:00:25 ENQ 36                       Q02 Stop Workproc36, PID 3814
then all workprocesses stopped and went down. Is there some general hint how to resolve this problem?
Thanks, Martin

Hi Martin,
Don't worry about the Syslog message Transaction Canceled. Concentrate on why all the work process gone down. Because the system log message had come as the work processes gone down. Please look in to the work process trace to troubleshoot the same.
Regards,
Sanujit

Sm21 log (Transaction Canceled DB 61)

Similar Messages

Maybe you are looking for