Trace Level X activated after SAPGUI patch upgrade
Greetings,
After upgrading SAPGUI 6.40 from patch level 7 to patch level 14, many of our users are getting a dialog box appearing after the Portal auto launches the SAPGUI:
SAPGUI 640 (header)
Environment information: working directory:'.'
Trace level 3 activated
Logging activated
For maximum data security, delete the setting(s) as soon as possible!
We've tried the following fixes to no avail: emptying the temp files in working directory, reinstalling the update, checking the GUI options to make sure that the SAPGUI trace level is not turned on.
Any suggestions are greatly appreicated.
Regards,
Dan Kuhlmann
[email protected]
Hi John,
Thank you very much for 'patching' my trouble.
I have another trouble with SAP shortcut - "Working Dir".
SAP GUI do not use this setting for tracing from shortcut.
Probably, you could 'patch' this trouble also?
P.S. I'd like to award you with points but do not know how.
-- Sam
Similar Messages
-
When I open BEx, error message appears: "....trace level 8 activated.."
Hi,
when i open bex, then it appears:
"SAPGUI 640
Enviroment information:
Directory: 'C:\Documents and Setting\ ...\SapWorkDir
trace level 8 activated
logging activated
For maximum data security delete the settings as soon as possible."
But I dont know, which setting it is meaning.
Thanks zd.Jan,
The "*." should NOT be in the registry.
We are still experiencing the problem and have a customer message into SAP. The problem only occurs logging on through SAP Portal. It occurs on Sun J2SE version 1.5 and 1.4.2 consistently. It occurs using the Microsoft VM occaisionaly. Deleting cookies, temporary internet files and clearing the history in IE seems to solve the problem for users using the Microsoft JVM.
We are on XP SP2 with all the latest MS security patches. Since we use Portals as the main logon process, we have the registry key set to prevent saplogon from launching when the user logs on.
Hope that helps,
John -
After recent patch upgrade, BW delta Data loads for 2LIS_02_ITM failing
Hi All
We have patched our BW 3.5 system from 16 to 25. After updating patches, I am geetting delta load issues.
2lis_02_itm and 2lis_02_scl delta loads are taking long long time. Deltas are failing even for 3000 records . some time it is taking 14 hours . Delta loads are failing and I am getting below message. Please advise.
I am still getting below dump and i could not find any errors in
ST22. Please see below error.
Processing in Warehouse timed out; processing steps mising
Diagnosis
Processing the request in the BW system is taking a long time and the
processing step Update rules has still not been executed.
System response
<DS:DE.RSCALLER>Caller is still missing.
Procedure
Check in the process overview in the BW system whether processes are
running in the BW system under the background user.
If this is not the case, check the short dump overview in the BW system.
Thanks
PramodHello Pramod,
Is this load is to load to initial level ODS? If Yes I understand that you have issue in loading but not at activation of the ODS?
Normally this kind of issue comes during the activation of ODS.
1. If you are getting this during the data loads, then try to check loading only to PSA first and then from PSA to target? And check how much time that it's taking as this will help to track the issue whether its present in Source or in BW?
2. If the load is fine till PSA then try loading the same to ODS and then check whether this issue is present or not?
3. At the same you need to check the source side the system load and the number of processors which are available?
4. Did you perform the delta queue draining before the stack upgrade in R/3 or not? Normally as a pre-requisite this needs to be done if not then you will have issues in extracting the data!
5. Finally this can be avoided by having Initwithout data transfer and then performing the Delta loads. BUt for this need to first extract all the data from Source to BW and then take a down time in R/3 for few min and perform this activity so that the Init Timstamp will be reset properly and the Delta should work fine for you.
Do get back to us with more details.
Thanks
Murali M -
System Core Dumped after Oracle patch upgrade 9.2.0.6 to 9.2.0.8
Hi,
We are continously getting dumps on our BW Central instance server after we did an Oracle patch upgrade from 9.2.0.6 to 9.2.0.8.
Following is our system environment
SAP Release.............. "640"
Application server....... "abci"
Operating system......... "SunOS"
Release.................. "5.10"
Hardware type............ "sun4v"
Database server.......... "abdb"
Database type............ "ORACLE"
Database name............ "ABP"
Database owner........... "SAPABP"
SAP kernel............... "640"
Database version......... "OCI_920 "
Patch level.............. "175"
Following below is the Core Dump that is generated for any process chains that we schedule on our BW server
Runtime Errors SYSTEM_CORE_DUMPED
Date and Time 14.04.2008 09:26:17
ShrtText
Process terminated by signal 11.
What happened?
The current ABAP program had to be terminated because the
ABAP processor detected an internal system error.
The current ABAP program "SAPMSSY2" had to be terminated because the ABAP
processor discovered an invalid system state.
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An SAP System process was terminated by an operating system signal.
Possible reasons for this are:
1. Internal SAP System error.
2. Process was terminated externally (by the system administrator).
Last error logged in SAP kernel
Component............ "Taskhandler"
Place................ "SAP-Server awci_ABP_00 on host awci (wp 5)"
Version.............. 1
Error code........... 11
Error text........... "ThSigHandler: signal"
Description.......... " "
System call.......... " "
Module............... "thxxhead.c"
Line................. 9780
How to correct the error
The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often
contains a file called 'core'.
Save this file under another name.
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
Kindly help.
Regards
Sachin
Edited by: Sachin N on Apr 14, 2008 12:26 PMNo. If the environment would be wrong the system wouldn´t start up.
Core dumps are in 99 % of the cases program errors (in the SAP kernel or in an interface (libdbora*)), misaligend accesses of data etc.
If you encounter such an error have a look in the C-Stack. If you can´t see where the error is happening opening an OSS call. Most of those errors are fixed by installing the latest patches for the kernel and the database interface.
Markus -
Adobe form not working after MSS Patch Upgrade
Hi,
We have implemented ESS/MSS and in one of the MSS scenario to create a new personnel chnage request we have an Adobe interactive form (WD) which actually validates the users Social Security number by calling an RFC in the ECC 6.0 and updates the form's filed on the front end. There was an issue of "Expired SSO Ticket" and to resolve this SAP recommended to apply SAP_JTECHS (SAPJTECHS13P_14-10003467) and SAP_JTECHF (SAPJTECHF13P_15-10003468) patches to fix the problem. But after applying these patches Adobe form for PCR has stopped working and it just gets hanged, form appears on the front end and when user enters the values and hit enter to validate, it doesnt communicate with the Backend ECC system only the SAP status picture keeps rotating, i turned the trace ON and checked it, its not at all communicating with the ECC system. Where as in other systems where we have not appplied the pacthes, those are working fine. One of the error i noticed in the server log is as below:
jco.client.mysapsso2=AjExMDAgAA5wb3J0YWw6QkNPTFNUT4gAE2Jhc2ljYXV0aGVudGljYXRpb24BAAdCQ09MU1RPAgADMDAwAwADU1BEBAAMMjAwODExMDMxNjU3BQAEAAAAEAoAB0JDT0xTVE//AQUwggEBBgkqhkiG9w0BBwKggfMwgfACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHATGB0DCBzQIBATAiMB0xDDAKBgNVBAMTA1NQRDENMAsGA1UECxMESjJFRQIBADAJBgUrDgMCGgUAoF0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDgxMTAzMTY1NzQwWjAjBgkqhkiG9w0BCQQxFgQUfD7V7TS!58cgzIFyucxCSL4ltuswCQYHKoZIzjgEAwQvMC0CFA4Q0!Rr2xYFPwFwXz8WeFF1UALlAhUAmHiTdHw!3s4Q!Jc9gDyY4QSvxa4=, user=, mshost=sapdv2.company.com, r3name=DV2, jco.client.type=B, jco.client.trace=0, group=SRS, codepage=1100}
Client not connected#
#1.5 #76C1EDD07B440026000000000007501600045ACC2EF6809D#1225732914577#/Applications/BusinessLogic#sap.com/home~zb2bzsrs#com.sap.isa.core.eai.sp.jco.JCoConnectionStateful#BCOLSTO#1480##hadspd1.bnet_SPD_306896250#BCOLSTO#daca9e30a9cb11dd99c976c1edd07b44#SAPEngine_Application_Thread[impl:3]_19##0#0#Error#1#/Applications/BusinessLogic#Java###Error occcurred in EAI layer "".#2#com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Error in module RSQL of the database interface.#parameters: [client]='null' [user]='null' [language]='null' [ashost]='null' [systemnumber]='null' [mshost]='null' [gwhost]='null' [gwserv]='null' [group]='null' [systemid]='null'
Properties: {passwd=?, lang=en, client=150,
Can someone please suggest what could be the possible reason for such a problem with Adobe form and whats the way out to resolve this. Appreciate a quick help in this regard.
Thanks in advance,
Sarabjeet.Hi,
We had the same issue after the Patch update to SP17 in both Backend as well in Portal, to resolve my colleagues had a look at the standard forms which were working and found that because of the patch update the script used in the custom forms was changed and not the standard and
on event trigger which was processed in the container they replace the script to the standard one. and it started working.
But this is not the solution we are looking at solution on having the same version of script as in the standard even after the patch update.
So to your point to resolve compare the scripts in both standard and customized forms and do the same.
And also have a look at the SAP Note: 1109392
.... this is a temporary solution.....
Hope this helps.
Cheers-
Pramod -
Backup error after kernel patch upgrade
Hi.
I have a backup problem after the kernel patch upgrade. I have SAP R3 4.6C on HPUX11.0 with an Oracle 8.17 database.
I have upgraded kernel patch from 1655 to 2337.
Afterward, I am getting following backup error:
BR280I Time stamp 2007-11-06 09.29.01
BR279E Return code from '/usr/sap/HAD/SYS/exe/run/backint -u HAD -f backup -i /oracle/HAD/sapbackup/.bdwnpztp.lst -t file_online -c': 2
BR232E 0 of 115 files saved by backup utility
BR280I Time stamp 2007-11-06 09.29.01
BR231E Backup utility call failed
Does anyone know how to correct this?
Thank you.Hi Jun,
backint is a link file that is in SAP kernel directory which links to the backup client on the server.
eg:
lrwxrwxrwx 1 root other 32 Aug 13 2004 backint -> /usr/openv/netbackup/bin/backint
As part of kernel upgrade process, the kernel is backed up, mostly on the disk before upgrading. Check if this link exists and recreate it in the kernel directory, if no backup was done, compare it with other systems to get the details of the backint link.
Cheers,
Nisch -
Repository connect issue after MDM Patch Upgrade
MDM Expert
We recently upgraded our MDM patch from SP06 5.5.63.73 to SP06 5.5.65.91
after patch upgrade we are not able to connect to repository.SAP is saying that we have wong NLS Character set.It should be 'UTF8' or 'AL32UTF8'
We checked and found that we do not have character set as per SAP Recommendation but everything was working fine before upgrading the patch.As per SAP in new Patch MDM is lokking for Unicode Character set
SAP is asking to create new DB Instance for MDM.
If we create new instance for MDM then how we are going to use our existing repository.Our environment is clustered environment and name of MDM DB instance is also mentioned in cluster.We have to use same Instance name.We are also using oracle failsafe
Creating new instance seems to be risky for Production environment.Currently we are applying the Patch in Sandbox Environment
has anyone of you faced this problem while upgrading MDM patch, if yes then how you resolve the issue
Please help
Thanks
DeelipSolution provided by sAP
-
Activity After BI Content Upgradation
Hi Experts,
Is there any we require to do as a necessary step after BI content Upgradation. In my development system BI content is already upgraded, but I didnt do anything but now the upgradation is on Production system so can anyone tell me the steps if any.
Regards,
MayankSuggest performing the steps related to data load, change run, query & web template execution. Make sure you are selecting the standard objects (delivered by SAP) pertaining to the respective area while performing the test.
Hope this helps.
Bala -
Adjustment Modifications after Patch upgrade?
Hello,
Is it possible that the Modifications Adjustments (done in SPAU and SPDD and occured due to SAP_BASIS and SAP_ABA patches) be carried out after the patches upgrade?
To be more clear, instead of Adjusting the Modifications while patch upgrade is in progress can i configure the patch upgrade in SPAM transaction someway that the Modification Adjustments is directly shown to the user upon their login after my patch upgrade?
Regards,
VasuHi Vasu,
Yes you just need to transport the request to next system.
Than you don't need to redo the adjustment.
But some time due to incosystency between the system, you still get some object not adjusted after you apply the request, and for this you need to transport the object from your development or direct adjust.
After 12 days than when you change the object, SAP will ask you for the object key, and you need to request the key in SAP MarketPlace before you can change the object.
Regards,
Fendi Suyanto -
Dialogue instance not starting up after performing stack upgrade.
Dear Experts,
We have performed stack upgrade on ERP 6.0 EHP5 system. In configuration phase we have not got the option to update dialog instances.
We proceeded without that option and completed the upgrade successfully but the dialog instance is not getting started.
Kernel level got upgraded in all instance with the same level. Below is the work process log content of dialog instance.
Loading DB library '/usr/sap/MMD/D10/exe/dboraslib.so' ...
M *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("/usr/sap/MMD/D10/exe/dborasli
b.so") FAILED
"I/O error mapping in '/usr/sap/MMD/D10/exe/dboraslib.so'." [dlux.c 445
B *** ERROR => Couldn't load library '/usr/sap/MMD/D10/exe/dboraslib.so'
[dbcon.c 5768]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 008192) [thxxhead.c 1519]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thx
xhead.c 11532]
As per SUM guide we need to uninstall the dialog instances before downtime and re-install the dialog instances after upgrade but we didn't uninstalled dialog instances before downtime.
Kindly let me know if there is any other process start up the dialog instance with out going for re-installing it.
Also suggest on re-installing the dialog instance since we didn't uninstalled dialog instances before downtime.
Thanks,
Bharath.Dear Divyanshu,
Please find the work process log of dialog instance.
trc file: "dev_w0", trc level: 1, release: "721"
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS all, MJ
M sysno 04
M sid MMD
M systemid 274 (HP (IA-64) with HP-UX)
M relno 7210
M patchlevel 0
M patchno 300
M intno 20020600
M make single threaded, Unicode, 64 bit, optimized
M profile /sapmnt/MMD/profile/MMD_D10_msdprd
M pid 266
M
M
M Fri Oct 3 02:46:33 2014
M kernel runs with dp version 139000(ext=121000) (@(#) DPLIB-INT-VERSION-139000-UC)
M length of sys_adm_ext is 592 bytes
M ThStart: taskhandler started
M ThTHPInit: thp initialized
M ThInit: initializing DIA work process W0
M ***LOG Q01=> ThInit, WPStart (Workp. 0 1 266) [thxxhead.c 1349]
M ThInit: running on host msdprd
M calling db_connect ...
B Loading DB library '/usr/sap/MMD/D10/exe/dboraslib.so' ...
M *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("/usr/sap/MMD/D10/exe/dboraslib.so") FAILED
"I/O error mapping in '/usr/sap/MMD/D10/exe/dboraslib.so'." [dlux.c 445]
B *** ERROR => Couldn't load library '/usr/sap/MMD/D10/exe/dboraslib.so'
[dbcon.c 5768]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 008192) [thxxhead.c 1519]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 11532]
M
M Info for wp 0
M
M pid = 266
M severity = 0
M status = 0
M stat = WP_NEW
M waiting_for = NO_WAITING
M reqtype = DP_RQ_DIAWP
M act_reqtype = NO_REQTYPE
M req.req_info =
M req.tid = -1
M req.uid = 4294967295
M req.mode = 255
M req.len = 0
M req.rq_id = 65535
M req.rq_source =
M last_tid = 0
M last_uid = 0
M last_mode = 0
M locked semaphores (), locking ()
M act_cs_count = 1
M csTrack = 0
M csTrackRwExcl = 0
M csTrackRwShrd = 0
M mode_cleaned_counter = 0
M control_flag = 0
M int_checked_resource(RFC) = 0
M ext_checked_resource(RFC) = 0
M int_checked_resource(HTTP) = 0
M ext_checked_resource(HTTP) = 0
M report = > <
M action = 0
M tab_name = > <
M attachedVm = no VM
M
M ThIErrHandle: current request:
M
M -IN-- sender_id ? tid -1 wp_ca_blk -1 wp_id -1
M -IN-- action - uid -1 appc_ca_blk -1 type -
M -IN-- new_stat NO_CHANGE mode 255 len 0 rq_id -1
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 867]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 302]
sapcpe.log of dialog instance
2014/10/03 02:45:39
sapcpe version UC: @(#) $Id: //bas/721_REL/src/ccm/sapstart/sapxxcpe.c#21 $ SAP
Command line:
0: /usr/sap/MMD/SYS/exe/run/sapcpe
1: pf=/sapmnt/MMD/profile/MMD_D10_msdprd
Trace level (profile): 1
** INFO: Try to find file table sapcpeft (default:sapcpeft)
** INFO: Try to find file table in the central directory /usr/sap/MMD/SYS/exe/run/sapcpeft
** INFO: Found file table: /usr/sap/MMD/SYS/exe/run/sapcpeft
source: /usr/sap/MMD/SYS/exe/run
target: /usr/sap/MMD/D10/exe
Checking the files in the file table for copy type
** INFO: file /usr/sap/MMD/SYS/exe/run/db4cncl is not existing and status -copy when file exists- is set
** INFO: file /usr/sap/MMD/SYS/exe/run/dbdb2slib.so is not existing and status -copy when file exists- is set
** INFO: file /usr/sap/MMD/SYS/exe/run/dbdb2slib9.so is not existing and status -copy when file exists- is set
** INFO: file /usr/sap/MMD/SYS/exe/run/dbdb2slibx.so is not existing and status -copy when file exists- is set
** INFO: file /usr/sap/MMD/SYS/exe/run/dbdb4slib.so is not existing and status -copy when file exists- is set
** INFO: file /usr/sap/MMD/SYS/exe/run/dbinfslib.so is not existing and status -copy when file exists- is set
** INFO: file /usr/sap/MMD/SYS/exe/run/dbsldb4ccm.so is not existing and status -copy when file exists- is set
** INFO: file /usr/sap/MMD/SYS/exe/run/libsecude.so is not existing and status -copy when file exists- is set
** INFO: file /usr/sap/MMD/SYS/exe/run/setdb4pwd is not existing and status -copy when file exists- is set
** INFO: file /usr/sap/MMD/SYS/exe/run/xdnxdaapi.so is not existing and status -copy when file exists- is set
** INFO: no extern File-List defined. Look for the default File-List(s).
Checking File-List(s).
** INFO: File-List "/usr/sap/MMD/SYS/exe/run/instance.lst" exists.
** INFO: File-List "/usr/sap/MMD/SYS/exe/run/instancedb.lst" exists.
** INFO: File-List "/usr/sap/MMD/SYS/exe/run/tools.lst" does not exist.
** INFO: File-List "/usr/sap/MMD/SYS/exe/run/inhouse.lst" does not exist.
** INFO: File-List "/usr/sap/MMD/SYS/exe/run/dbclient.lst" does not exist.
** INFO: File-List "/usr/sap/MMD/SYS/exe/run/igsexe.lst" exists.
** INFO: File-List "/usr/sap/MMD/SYS/exe/run/sapcrypto.lst" does not exist.
Current list file: see table below
ActualizeLocalFileOrDir: instance.lst (FPM:0x0)
ActualizeLocalFile: instance.lst
ActualizeLocalFileOrDir: sapmanifest.mf (FPM:0x0)
ActualizeLocalFile: sapmanifest.mf
ActualizeLocalFileOrDir: saproot.sh (FPM:0x0)
ActualizeLocalFile: saproot.sh
ActualizeLocalFileOrDir: scsclient.lst (FPM:0x0)
ActualizeLocalFile: scsclient.lst
ActualizeLocalFileOrDir: j2eeinst.lst (FPM:0x0)
ActualizeLocalFile: j2eeinst.lst
ActualizeLocalFileOrDir: sapmanifestj2ee.mf (FPM:0x0)
ActualizeLocalFile: sapmanifestj2ee.mf
ActualizeLocalFileOrDir: scs.lst (FPM:0x0)
ActualizeLocalFile: scs.lst
ActualizeLocalFileOrDir: webdispinst.lst (FPM:0x0)
ActualizeLocalFile: webdispinst.lst
ActualizeLocalFileOrDir: gateway.lst (FPM:0x0)
ActualizeLocalFile: gateway.lst
ActualizeLocalFileOrDir: disp+work (FPM:0x1)
ActualizeLocalFile: disp+work
*** ERROR: CopyFile: write <dst> failed: -1 <> 1048576, 28, No space left on device, [sapxxcpe.c:2714]
*** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/disp+work -> /usr/sap/MMD/D10/exe/disp+work (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
ActualizeLocalFileOrDir: rsyn.bin (FPM:0x1)
ActualizeLocalFile: rsyn.bin
ActualizeLocalFileOrDir: ABAP.pad (FPM:0x1)
ActualizeLocalFile: ABAP.pad
ActualizeLocalFileOrDir: aci_ABAP.pad (FPM:0x1)
ActualizeLocalFile: aci_ABAP.pad
ActualizeLocalFileOrDir: aci_ABAP.gram (FPM:0x1)
ActualizeLocalFile: aci_ABAP.gram
ActualizeLocalFileOrDir: R3trans (FPM:0x1)
ActualizeLocalFile: R3trans
*** ERROR: CopyFile: write <dst> failed: -1 <> 1030984, 28, No space left on device, [sapxxcpe.c:2714]
*** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/R3trans -> /usr/sap/MMD/D10/exe/R3trans (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
ActualizeLocalFileOrDir: R3ta (FPM:0x0)
ActualizeLocalFile: R3ta
*** ERROR: CopyFile: write <dst> failed: -1 <> 1048576, 28, No space left on device, [sapxxcpe.c:2714]
*** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/R3ta -> /usr/sap/MMD/D10/exe/R3ta (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
ActualizeLocalFileOrDir: R3check (FPM:0x0)
ActualizeLocalFile: R3check
*** ERROR: CopyFile: write <dst> failed: -1 <> 704256, 28, No space left on device, [sapxxcpe.c:2714]
*** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/R3check -> /usr/sap/MMD/D10/exe/R3check (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
ActualizeLocalFileOrDir: tp (FPM:0x0)
ActualizeLocalFile: tp
ActualizeLocalFileOrDir: dipgntab (FPM:0x0)
ActualizeLocalFile: dipgntab
*** ERROR: CopyFile: write <dst> failed: -1 <> 1048576, 28, No space left on device, [sapxxcpe.c:2714]
*** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/dipgntab -> /usr/sap/MMD/D10/exe/dipgntab (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
ActualizeLocalFileOrDir: saplicense (FPM:0x1)
ActualizeLocalFile: saplicense
*** ERROR: CopyFile: write <dst> failed: -1 <> 1048576, 28, No space left on device, [sapxxcpe.c:2714]
*** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/saplicense -> /usr/sap/MMD/D10/exe/saplicense (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
ActualizeLocalFileOrDir: saplikey (FPM:0x1)
ActualizeLocalFile: saplikey
*** ERROR: CopyFile: write <dst> failed: -1 <> 620472, 28, No space left on device, [sapxxcpe.c:2714]
*** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/saplikey -> /usr/sap/MMD/D10/exe/saplikey (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
ActualizeLocalFileOrDir: sapcpeft (FPM:0x0)
ActualizeLocalFile: sapcpeft
ActualizeLocalFileOrDir: startsap (FPM:0x0)
ActualizeLocalFile: startsap
*** ERROR: CopyFile: write <dst> failed: -1 <> 92600, 28, No space left on device, [sapxxcpe.c:2714]
*** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/startsap -> /usr/sap/MMD/D10/exe/startsap (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
ActualizeLocalFileOrDir: stopsap (FPM:0x0)
ActualizeLocalFile: stopsap
*** ERROR: CopyFile: write <dst> failed: -1 <> 92600, 28, No space left on device, [sapxxcpe.c:2714]
*** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/stopsap -> /usr/sap/MMD/D10/exe/stopsap (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
ActualizeLocalFileOrDir: jdbcconnect.jar (FPM:0x0)
ActualizeLocalFile: jdbcconnect.jar
ActualizeLocalFileOrDir: SAPCAR (FPM:0x0)
ActualizeLocalFile: SAPCAR
*** ERROR: CopyFile: write <dst> failed: -1 <> 1048576, 28, No space left on device, [sapxxcpe.c:2714]
*** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/SAPCAR -> /usr/sap/MMD/D10/exe/SAPCAR (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
ActualizeLocalFileOrDir: rslgsend (FPM:0x1)
ActualizeLocalFile: rslgsend
*** ERROR: CopyFile: write <dst> failed: -1 <> 249984, 28, No space left on device, [sapxxcpe.c:2714]
*** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/rslgsend -> /usr/sap/MMD/D10/exe/rslgsend (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
ActualizeLocalFileOrDir: rslgcoll (FPM:0x1)
ActualizeLocalFile: rslgcoll
*** ERROR: CopyFile: write <dst> failed: -1 <> 324120, 28, No space left on device, [sapxxcpe.c:2714]
*** ERROR: ActualizeLocalFile: FAILED /usr/sap/MMD/SYS/exe/run/rslgcoll -> /usr/sap/MMD/D10/exe/rslgcoll (rc = 2), 28, No space left on device, [sapxxcpe.c:2528]
ActualizeLocalFileOrDir: gwrd (FPM:0x1)
Kindly suggest.
Thanks,
Bharath. -
Kernel patch Upgrade Form 994 to1068(40B_EXT)
Hi,
We are migrating OS,DB From V5R2 to V5R4. We are currently working with COM kernel on our OLD boxes. Now we have applied 4.0B_EXT kernel 994 successfully from CD(51020599) in new Box. Now need to apply 1068 patch to support our V5R4 box. How can i apply 1057/1068 patch available in archive service market?.
Detail Steps are appreciated/rewarded.
SAP Version : 4.0B
Thanks
Jibin.Hi victor,
As you know we have migrated our SAP 4.0B from V5R2 to V5R4, now we are facing some problem when we access table CDPOS, we get SQL -901 dump. In the dev_w0 trace, iam getting "Missing PTFs from the IBM InfoAPAR" but all the PTF's are upto date when i check with from OS and SAP(CHKR3PTF). Here is trace file
Directory /usr/sap/QAS/DVEBMGS10/work
Name: dev_w0
trc file: "dev_w0", trc level: 1, release: "40B"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, M
M
M Tue Dec 18 12:12:42 2007
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 112) dpxxdisp 0876
M
M relno 40B
M
M makevariant 40B_EXT
M patchlevel 1068
M compiled on OS/400 V5R3
M compiled at Feb 21 2007 16:54:22
M pid 112
M
X <ES> client 0 initializing ....
X ES initialized.
M calling db_connect ...
C
C Tue Dec 18 12:12:43 2007
C Connection to database done without problems.
C ==== Init of DbSl ego structure done, values ====
C SAPSYSTEMNAME = QAS
C process class = dialog process
C workprocess id = 0
C local host = chisap1.chisap1
C dbhost = chisap1
C dbname = QASchisap1
C dblib = R3QASDATA
C application server = DVEBMGS10
C db connect type = LOCAL
C pid = 112
C dbjobname = DISP
C dbjobuser = SAP10
C dbjobno = 054174
C wpjobname = DISP
C wpjobuser = SAP10
C wpjobno = 054174
C dbversion = V5R4
C da_cache_size = 100
C reopen = ON
C timeout_retry = 3
C ODP threshold = 1200
C ODP commit thresh. = 1210
C ODP open thresh. = 1250
C nqe_optimize_method = O - All I/O (compatibility mode)
C query_compl_reval = O
C Start DB monitor: DBMON: functionality disabled (see as4/dbmon/enable)
M
M Tue Dec 18 12:12:48 2007
M db_connect o.k.
X
X Tue Dec 18 12:12:57 2007
X <ES> client 0 initializing ....
X ES initialized.
A
A Tue Dec 18 12:13:00 2007
A Attached to PXA (address SPP:0000 :19efQP0ZSHMK11006I401:0:0:2, size 3688736)
S
S Tue Dec 18 12:13:06 2007
S initialize debug system
T Stack direction is upwards.
T debug control: prepare exclude for printer trace
T new memory block SPP:0000 :1aefDISP SAP10 054174 :3565d0:1:2
S
S Tue Dec 18 12:13:07 2007
S 1 spool work process(es) found
S frontend print server enabled
S printer list size is 150
S queue size (profile) = 300
S hostspool list size = 3000
S found processing queue enabled
S found spool memory service RSPO-RCLOCKS at SPP:0000 :19efQP0ZSHMK11049I404:65180:2:2
S doing lock recovery
S setting server cache root
S
S Tue Dec 18 12:13:08 2007
S found spool memory service RSPO-SERVERCACHE at SPP:0000 :19efQP0ZSHMK11049I404:653e0:3:2
M ThSetProcessPriority: Run priority adjusted to 20
M MBUF info for hooks: MS component UP
M EnqIdCheck is active
M EnqIdCheck is active
E
E Tue Dec 18 12:13:16 2007
E ObjShMem_CheckAuthoritativeEnqId: EnqId is initial in ShMem
E ObjShMem_CheckAuthoritativeEnqId: Overwrite incoming auth EnqId, continue
E EnqId inscribed into initial ObjShMem: (ObjShMem_CheckAuthoritativeEnqId)
E -SHMEM--
E EnqId: EnqTabCreaTime/RandomNumber = 18.12.2007 12:13:08 1197960188 / 112
E ReqOrd at Srv: TimeInSecs/ReqNumberThisSec = 18.12.2007 12:13:16 1197960196 / 1
E ReqOrd at Cli: TimeInSecs/ReqNumberThisSec = 18.12.2007 12:13:16 1197960196 / 1
E Status: STATUS_OK
E
B dbtran INFO (init_connection '<DEFAULT>' DB400:A.01.00):
B max_blocking_factor = 20, max_in_blocking_factor = 40,
B min_blocking_factor = 10, min_in_blocking_factor = 10,
B prefer_union_all = 0, prefer_union_for_select_all = 0,
B prefer_fix_blocking = 1, prefer_in_itab_opt = 1,
B convert AVG = 1, alias table FUPD = 1,
B escape_as_literal = 0, opt GE LE to BETWEEN = 0,
B select * = 0x1,
B use_hints = abap->0, dbif->0, first->0,
B rule_in->0, rule_fae->0, concat_fae->0
M
M Tue Dec 18 12:15:03 2007
M SecAudit: new day, change current audit file
M SecAudit(check_daily_file): audit file opened /usr/sap/QAS/DVEBMGS10/log/20071218
B
B Tue Dec 18 12:15:46 2007
B dbrclu2.c : info : my major identification is 3282948402, minor one 10.
B dbrclu2.c : info : Time Reference is 1.12.2001 00:00:00h GMT.
C
C Tue Dec 18 12:17:15 2007
C *** ERROR => Missing PTFs from the IBM InfoAPAR (OSS note 144149)
http://dbsldb4. 5255
C PTF 5722SS1/SF99504 not found. DB Fix Pack, Order SF99504. The DB fixpack, SF99504
C PTF 5722SS1/SF99539 not found. Hiper Fix Pack, Order SF99539. The current
C PTF 5722JV1/SF99291 not found. Java Fix Pack, Order SF99291. The JDK fixpack, SF99291
C *** ERROR => Error -901 in function exec_cached_op
http://dbsldb4. 7725
C Cursor name: "CACHEDCSRN00018"
C Library name: R3QASX0000
C Package name: CDCLS
C Statement name: "IOEINEHBOOHFIAAA"
C withhold: NO
B ***LOG BY4=> sql error -901 performing SEL on table CDCLS 6347
B ***LOG BY0=> SQL system error. Job=054174/SAP10/DISP. Refer to dev. trace of dev_w0 (ST11). 6347
B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'SEL'
B FHDR: {tab='CDCLS ', fcode=5, mode=2, bpb=0, dbcnt=0, crsr=1,
B hold=0, reuse=0, xfer=0, pkg=0, upto=0, init:b=0,
B init:p=00000000000000000000000000000000, init:#=0, wa:p=00000000000000000000000000000000, wa:#=0}
B dbtran ERROR LOG (hdl_dbsl_error): DbSl SEL'
B STMT:
B CRSR: {tab='CDCLS ', id=-1, hold=0, prop=0, maxin=1, fae:blk=10,
B con:nm='R/3', con:id=0, con:vndr=2, val=2,
B key:1=0, key:#=5, xfer=0, xin:#=0, xout:#=0, upto=0,
B wa:p=8000000000000000EEA0F6CE59381800, init:p=00000000000000000000000000000000, init:#=0, init:b=0}
M ***LOG R68=> ThIRollBack, roll back () thxxhead 9613
X <ES> RecoverAll
X <ES> RecoverFreeList
X <ES> RecoverAll
X <ES> RecoverFreeList
A
A Tue Dec 18 12:17:18 2007
A Tue Dec 18 12:17:18 2007
A ABAP/4 Program /1BCDWB/DBCDPOS .
A Source /1BCDWB/DBCDPOS Line 598.
A Error Code DBIF_RSQL_SQL_ERROR.
A Module $Id: //bas/40B/src/absapsql.c#2 $ SAP.
A Function ExecuteCall Line 5285.
A SQL error -901 occurred when accessing table CDPOS ..
A
I try to delete SQL packages(DLTR3PKG) sucessfull.but no use still we are get dump.
Please advise to sort out the error.
Regards,
Jibin. -
Hello,
When I logged in, I got pop up saying:
Environment Information:
working Dir.
Trace level 3 activated
logging activated:
for maximum data security delete the settings as soon as possible !
Regards,
Tushar Chavan.Hi Tushar,
do you use shortcuts to logon? The tracelevel can be defined there too. To check, open the shortcut in notepad and look for the line 'Trace=3' in the section [Configuration].
Peter
Points always appreciated -
Work process trace level automatically increasing
Hello All,
MY env is SAP R3 4.6C (DB2 7.1.0) ,and suddenly many of the work process of all the appl.servers(4) trace level is increasing to level 2 . Which is causing FileSystem full (usr/sap/<sid>) ...
Even after manually changing the trace level to 1 , after some time it automatically changing to level 2.
Can some one help me to fix this issue .
Best Regards
RakeshDear,
Please look into the foloowing link this will be very helpful for you for solution.
http://help.sap.com/saphelp_nw04/helpdata/en/8c/20213c16fd7c70e10000000a11405a/content.htm
warm regards
Mohammed Hassan Naveed. -
Client Stop reporting in WSUS after Approval patches
Hi Team,
Recently i faced lot of issue in my wsus server during patching activity, After approving patches certain client stop reporting in wsus . I have tried all the troubleshooting but no one help.
can any one help me and provide troubleshooting steps which required in this type of cases
Regards, TriyambakI am facing same issue in one of server , here is the log file
2014-06-24 02:56:11:066
852 c18
PT WARNING: SOAP Fault: 0x00012c
2014-06-24 02:56:11:066
852 c18
PT WARNING: faultstring:Fault occurred
2014-06-24 02:56:11:066
852 c18
PT WARNING: ErrorCode:ServerChanged(4)
2014-06-24 02:56:11:066
852 c18
PT WARNING: Message:Server rolled back since last call to GetCookie
2014-06-24 02:56:11:066
852 c18
PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
2014-06-24 02:56:11:066
852 c18
PT WARNING: ID:2f956ab6-fac3-4e68-bffa-48557d580e88
2014-06-24 02:56:11:066
852 c18
PT WARNING: PTError: 0x80244015
2014-06-24 02:56:11:066
852 c18
PT WARNING: GetCookie_WithRecovery failed : 0x80244015
2014-06-24 02:56:11:066
852 c18
PT WARNING: RefreshCookie failed: 0x80244015
2014-06-24 02:56:11:066
852 c18
PT WARNING: RefreshPTState failed: 0x80244015
2014-06-24 02:56:11:066
852 c18
PT WARNING: Sync of Updates: 0x80244015
2014-06-24 02:56:11:066
852 c18
PT WARNING: Cached cookie has expired or new PID is available
2014-06-24 02:56:11:066
852 c18
PT Initializing simple targeting cookie, clientId = 60adbf7d-5194-4cd9-90c7-e00efccedcb7, target group = WSUS 2003 x32 Prod Group 1, DNS name = lpsjcmwbp13.sumcweb.com
2014-06-24 02:56:11:066
852 c18
PT Server URL = http://lpchweb-wsus.sumcweb.com/SimpleAuthWebService/SimpleAuth.asmx
2014-06-24 02:56:30:488
852 c18
Agent * WARNING: Failed to synchronize, error = 0x80244015
2014-06-24 02:56:30:504
852 c18
Report CWERReporter finishing event handling. (00000000)
2014-06-24 02:56:30:504
852 c18
DnldMgr File locations for service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 changed
2014-06-24 02:56:30:504
852 c18
Agent Server changed and need resyncing with server
2014-06-24 02:56:30:895
852 c18
PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-06-24 02:56:30:895
852 c18
PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://lpchweb-wsus.sumcweb.com/ClientWebService/client.asmx
2014-06-24 02:56:35:692
852 c18
PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2014-06-24 02:56:35:692
852 c18
PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://lpchweb-wsus.sumcweb.com/ClientWebService/client.asmx
an AU detection already in progress
2014-06-24 01:35:37:030
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:030
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:37:077
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:077
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:37:296
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:296
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:37:562
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:562
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:37:655
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:655
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:37:968
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:37:968
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:015
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:015
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:343
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:343
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:515
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:515
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:655
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:655
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:937
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:937
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:38:999
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:38:999
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:39:421
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:39:421
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:39:421
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:39:421
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:39:640
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:39:640
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:39:859
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:39:859
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:39:968
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:39:968
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:40:312
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:40:312
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:40:374
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:40:374
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:40:609
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:40:609
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:40:859
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:40:859
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:030
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:030
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:202
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:202
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:374
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:374
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:515
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:515
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:796
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:796
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:41:952
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:41:952
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:42:077
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:42:077
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:42:374
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:42:374
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:42:499
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:42:499
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:42:671
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:42:671
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:42:952
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:42:952
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:062
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:062
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:327
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:327
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:499
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:499
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:624
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:624
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:859
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:859
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:43:984
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:43:984
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:44:218
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:44:218
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:44:343
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:44:343
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:44:687
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:44:687
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:44:859
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:44:859
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:44:984
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:44:984
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:45:281
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:45:281
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:45:343
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:45:343
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:45:749
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:45:749
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:45:749
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:45:749
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:45:984
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:45:984
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:46:281
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:46:281
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:46:452
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:46:452
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:46:593
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:46:593
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:46:765
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:46:765
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:46:968
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:46:968
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:47:124
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:47:124
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:47:343
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:47:343
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:47:515
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:47:515
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:47:734
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:47:734
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:015
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:015
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:109
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:109
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:327
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:327
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:499
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:499
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:702
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:702
832 1378
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:48:906
832 700
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:48:906
832 700
AU Piggybacking on an AU detection already in progress
2014-06-24 01:35:49:234
832 1378
AU Triggering AU detection through DetectNow API
2014-06-24 01:35:49:234
832 1378
AU Piggybacking on an AU detection already
Regards, Triyambak -
Par application - Trace level=all after j2ee restart
Hello,
I'm not sure that is the right place to post this question so, don't hesitate to root me to another thread.
We use the SAP Enterprise Portal EP6 base on NW2004 SPS16.
We have developped some Portal Application. (par). Those applications contain a logger.xml file to describe the trace settings.
In visual Admin\Log configurator, we define the trace level to "Error" for those applications nodes. But, after application deployment, or after j2ee engine restart, the trace level level is automaticaly set to "All". It only appens to our applications and not to other WAS traces.
I think problem is due to the logger.xml but, after lookup on a lot of thread, it seems we use it in the good way.
<u>eg:</u>
<Server>
<Logger name="corp.mycompany.application.myApplicationName.logger"
loggerInterface="com.sapportals.portal.prt.logger.ILogger"
locationName="corp.mycompany.application.myApplicationName"
pattern="%d # %20t %15s %m #"
isActive="true">
<LoggerClass className="com.sapportals.portal.prt.logger.SimpleFileLogger" level="Error">
</LoggerClass>
</Logger>
</Server>
Did we miss something ? Do we manage our traces in thge good way ?
Please advice.
Thanks for your support
LaurentLaurent,
Do have a look at this<a href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1794">weblog</a>
check this
<a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5f04b290-0201-0010-1387-d2df53065422">pdf</a>
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/e2/75a74046033913e10000000a155106/frameset.htm">Active Tracing</a>
Are all the configurations nd settings done are accordingly?
Thanks,
Swathi
Maybe you are looking for
-
When I drag a loop into my arrange area, it no longer sounds the way it did in my loops menu.
-
After setting for Mail for Exchange, my Nokia E7 phone shows low memory. I checked C Memory & there are only important files & that too of small sizes. All major Applications are installed in Mass Memory only. Is "Low Memory" issue due to Mail for Ex
-
Hi all We want to generate a pdf at runtime in new window on click of a button suppose 'Show PDF'. We have written following code using MVC module. In HANDLE_EVENT for the button we are calling a controller method say 'Preview_PDF' which is generatin
-
Hi all. I am experiencing the problem. Need help with this. all UCCE logs disabled or don't work. For example pim1 log on PG: - I set log level to 3 in Portico -When I am trying to download logs via portico(listTraceFiles) - empty archieve is downloa
-
System Alias reappears in the System Configuration
Hi All, This is a bit of a strange one but I wondered if anyone else has ever come across this with EP6 SP2. I have a System Object which I do not want to delete, since it might be required again in the future, so I am just removing the system alias