Report Cancelled PO

How can i genearte a report onf canclled PO?
Thanks
KKSK

Yes You can also dio this via the IMG
Go to Transaction OMEM or Menu path MM-Purchaisng-Reporting-Maintain Purchasing Lists
Click on Scope of list create new entry.
Check on chnage document fields.
Name the new scope with relelvaant name. This will now appear in Scope of list field in all purchasing list display screens.
The output will show the deatils of the changes like date and teim of chnage, old values and new values ect.
Thanks
Vijji

Similar Messages

Report canceled with message 'No forms available',

We are stumped.
I created a simple ABAP HR report using the PNP logical database. It pulls benefits info and master data for displaying on the screen.   (Associates Eligible for FMLA)   No ALV grid, just a simple write to the screen.
The job runs fine in in the background as well as foreground in DEV, QAS, and STA .
But now that the program is in PRD, when we run it in BACKGROUND, the job CANCELS after 10 minutes.
The spool lists the message 'No forms available', several dozen times, and then 'No memory for cua processer'.
Oddly, the program runs fine in forground.
Any clues how I can get this program to run in background?

Job log Messages:
12:48:38    Job started
12:48:38    Step 001 started (program ZPRCR_DISABILBITY_ELIGIBLE)
12:48:50    No forms available
12:57:47    No forms available
12:57:48    No memory for cua processor
12:57:49    Job canceled
I looked at the code and there are no ABAP 'check' statements, nor reference to sy-mandt.
There is code in the 'at selection-screen' section that puts out a warning if the program is ran in foreground without a date.
if pn-begda is initial and sy-batch is initial.
    message e000(zpa) with 'Please enter a run date'.
endif.
Other than that, the program runs fine in foreground in PRD, but cancels in background. The same code runs fine in foreground and background in all our other clients.    Our BASIS group is stumped too.
Thanks
Doug

Controlling approval status report cancel option

Dear Experts,
Is it possible to control the approval status report screen based on Stored Procedure?
Im having problem with users cancelling their draft documents before any approval status is decided upon the draft. Through the images below i want to control the cancel option they have
can the update button be controlled through store procedure? as I cant get the object type of this screen.
thanks in advance
Regards,
Balwant

Hi,
is the approval status report which can be set as read only in SAP B1 9.0 and above?
Cause currently im using SAP B1 8.82 Pl 13 and cant set read only
Regards,
Balwant

Report Job was cancelled upon user request???

Hi,
My reports take more than 10 minutes to complete, most times I get
"Report Job was cancelled upon user request".
error, how to fix this problem? Is there any time limit inside the report I can set.
Thanks

hi ,
There is no limit on the report run time. The most probable reason why you are getting the 'Report cancelled upon user request' message is the users might have hit the "cancel Report" button which is displayed when it is running in 'SYNCHRONOUS MODE'. do not hit that button as it will terminate the report. to increase the speed of returning the results by the report, try improving the sql that you use in the report, or if you have DBA rights try adding in INDEXES on the columns of the tables used by the report.
Hope this helps
Manoj

Oracle Reports Server CGI - Report Job was cancelled upon user request.

I am running reports on the web through Forms using Run_Report_Object built in. I am using Oracle 9iAS Enterprise Edition Release 1(1.2.2.2.2), Forms 6i Patch 9 (6.0.8.18.3) and Reports 6i Patch 9 (6.0.8.18) using CGI implementation. Most reports are running fine, but I have one that produces 125 pages and we are getting the following messages in the browser:
Error: The requested URL was not found, or cannot be served at this time.
Oracle Reports Server CGI - Report Job was cancelled upon user request.
However if you look at the Reports Server Queue Status thru the browser it shows that the report did finish, but it took 16 minutes. But the user gets the above message in their browser window.
Is there a way to get the first page of the report to display, while the rest of the report finishes, so the browser window doesn't timeout and display the above error?
Any help would be greatly appreciated.

hi ,
There is no limit on the report run time. The most probable reason why you are getting the 'Report cancelled upon user request' message is the users might have hit the "cancel Report" button which is displayed when it is running in 'SYNCHRONOUS MODE'. do not hit that button as it will terminate the report. to increase the speed of returning the results by the report, try improving the sql that you use in the report, or if you have DBA rights try adding in INDEXES on the columns of the tables used by the report.
Hope this helps
Manoj

Execution of Reports phase error during SAP EHP4 upgrade with EHPi

I started getting an error message in the "Execution of reports after put" phase
(within the Downtime phase) during the SAP EHP4 upgrade with Enhancement
Package Installer.
***** LIST OF ERRORS
AND RETURN CODES *****
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~XPRA ERRORS and RETURN CODE in SAPRB70104.OPQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~1AETR012XProgram terminated (job: "RDDEXECL", no.: "09064300") Long
text: Cause Program "&V#&", which was started in the background, was
terminated abnormally. System Response The system created a job log for
the terminated program. What to do Proceed as follows: Log onto the
system in which the program was executed. The system is specified at the
beginning of the transport log. Then call transaction SM37 to display the
job log. Enter "&V#&" as job name and "DDIC" as user name. Restrict the
starting date to the starting date specified in the transport log. For
the other selection criteria, select only jobs with the status
"cancelled". Then press <LS>Execute</>. A list of the jobs satisfying the
selection criteria is displayed. You can display the log by pressing
<LS>Job log</>. If the list contains several jobs, you can select the job
with the ID " &V#&" with <LS>Display</> -> <LS>Job details</> or define
further details for the selection criteria in the initial screen of
transaction SM37. If the ABAP processor reports cancellation,
double-clicking on the corresponding message in the job log branches to
the display of the corresponding short dump. 1AEPU320 See job
log"RDDEXECL""09064300""OPQ" 1 ETP111 exit code : "12" >>> PLEASE READTHE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<< XPRAs are
application reports that run at the end of an upgrade.
Most XPRA reportshave a report documentation that explains what the report does and how
errors can be corrected. Call transaction se38 in the SAP system, enter
the report name, select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above
<<<
I tried to follow the instructions in note 1269960, but the enhancement spot
CLASSIFICATION_TOOL was already active. I activated it again and reran the phase
but got the same error. Also, I couldn't implement the note using SNOTE because it is
the middle of the upgrade process.
I also found the following long text in ST22
"Internal error during syntax check: ("//bas/710_REL/src/krn/gen/scsymb.c#11"
Processing had to be terminated because an internal error
occurred when generating the ABAP/4 program
"CL_CLS_BADI_CHARACTERIZATION==CP".
The internal system error cannot be fixed by ABAP means only."
I am on a 64 bit System with CentOS Linux. 8 GB RAM, 250 GB HD with 20 GB free space.
So far, I could not find any information on this. Any help would be greatly appreciated!
Thanks,
Victor

Hi Victor,
Go to SM37 and put in the username as DDIC and see the job log.
Also check Sm50 and see whether you have BTC processes available.
Last but not the least check your filesystem space usage too.
Gerard

How Do I Filter a Report Using a Multi Select List Box and Specifying Date Between Begin Date and End Date

Hope someone can help. I have tried to find the best way to do this and can't seem to make sense of anything. I'm using an Access 2013 Database and I have a report that is based on a query. I've created a Report Criteria Form. I
need the user to be able to select multiple items in a list box and also to enter a Begin Date and End Date. I then need my report to return only the records that meet all selected criteria. It works fine with a ComboBox and 1 selection but can't
get it to work with a List Box so they can select multiple items. Any help is greatly appreciated while I still have hair left.

The query should return all records.
Let's say you have the following controls on your report criteria form:
txtStart: text box, formatted as a date.
txtEnd: text box, formatted as a date.
lbxMulti: multi-select list box.
cmdOpenReport: command button used to open the report.
The text boxes are used to filter the date/time field DateField, and the list box to filter the number field SomeField.
The report to be opened is rptReport.
The On Click event procedure for the command button could look like this:
Private Sub cmdOpenReport_Click()
Dim strWhere As String
Dim strIn As String
Dim varItm As Variant
On Error GoTo ErrHandler
If Not IsNull(Me.txtStart) Then
strWhere = strWhere & " AND [DateField]>=#" & Format(Me.txtStart, "yyyy-mm-dd") & "#"
End If
If Not IsNull(Me.txtEnd) Then
strWhere = strWhere & " AND [DateField]<=#" & Format(Me.txtEnd, "yyyy-mm-dd") & "#"
End If
For Each varItm In Me.lbxMulti.ItemsSelected
strIn = strIn & "," & Me.lbxMulti.ItemData(varItm)
Next varItm
If strIn <> "" Then
' Remove initial comma
strIn = Mid(strIn, 2)
strWhere = strWhere & " AND [SomeField] In (" & strWhere & ")"
End If
If strWhere <> "" Then
' Remove initial " AND "
strWhere = Mid(strWhere, 6)
End If
DoCmd.OpenReport ReportName:="rptMyReport", View:=acViewPreview, WhereCondition:=strWhere
Exit Sub
ErrHandler:
If Err = 2501 Then
' Report cancelled - ignore
Else
MsgBox Err.Description, vbExclamation
End If
End Sub
If SomeField is a text field instead of a number field, change the line
strIn = strIn & "," & Me.lbxMulti.ItemData(varItm)
to
strIn = strIn & "," & Chr(34) & Me.lbxMulti.ItemData(varItm) & Chr(34)
Regards, Hans Vogelaar (http://www.eileenslounge.com)

How can I fix the Microsoft Error Reporting?

I don't remember this problem occurring so often with OS X 10.5. Frequently (approximately 8 times out of 10), when I try to shut down the computer, I get the error message "The application Microsoft Error Reporting canceled shut down". This problem occurs with my MacBook (that I mostly use), but also with my iMac. A subsequent box says: "Microsoft Word has encountered a problem and needs to close. We are sorry for the inconvenience". I then usually click the button to send a report to Microsoft and shut down my computer. I have tried disk utility's repair permissions, but the problem still carries on.
I've ignored this for a while, because it just takes a couple of extra clicks to shut down. I also thought the next Microsoft update would solve it (I have version 12.2.5), but - no change. I hope it's not some kind of Microsoft virus...

Thank you for the link. The problem is solved now. Word cancelling shut down was caused by EndNote's "cite while you write" function. I've disabled it now and Word works fine.
The thread is at the following link:
http://www.officeformac.com/ms/ProductForums/Word/10737/1

Reverse mov. type report

Hi all,
My req. is like this we have 6 plants, with in given period need all reverse mov. type postings report for all plants,is there any standard report for this.pls help me for this.
Regards,
phani.

In MBSM
You can get
The report Cancelled material documents issues a list with the following data:
material documents with the associated reversal documents "or" reversal documents with the associated material documents
MB51 : Material Document List
This report provides you with a list of the material documents which were posted for one or more materials. You can display a material document from the output list.

Orders kept being cancelled and never got any email notification

It's been the third order that has been cancelled recently! I placed an order on 6th but it was cancelled. I changed something and placed another order on 10th but it was still cancelled. Today I just found the last order I placed yesterday was again cancelled! The most rediculous thing is that I didn't get any email notification about these cancellations. Every time I waited for several days to login my account only to find out it was cancelled. Please give me a reason for that.
By the way, I never successfully check my accout information or checkout using my computer. When I want to checkout it always says that my session expired even if I just logged in and already tried for a dozen times. I've changed explorers, cleared cookies, but nothing worked. I can only use my ipad to order or check order status. Is it my computer's problem?
order numbers: {removed per forum guidelines}

Hello hanxiao7,
From personal experience, ordering online should an easy process, so it's regrettable your orders are reportedly canceling without a reason as to why. While we unfortunately have to occasionally cancel orders on our end for various purposes, we should be notifying you of this, and I apologize if this wasn't the case.
After reviewing the online order numbers you provided, I've sent you a private message with my findings as to what happened. You may view it by logging into the forum and clicking on the envelope icon in the upper right-hand corner of the page.
Thank you for posting,
Alex|Social Media Specialist | Best Buy® Corporate
Private Message

ECC 6.0 EHP4 upgrade to EHP5 fails in MAIN_NEWBAS/XPRAS_AIMMRG

from SAPehpi.log
CURRENTPHASE MAIN_NEWBAS/XPRAS_AIMMRG
...started at 20110825140601
...begin processing at 20110825140601
..times self: 0.080000/0.150000 usr/sys, children 0.560000/0.450000 usr/sys.
..finished at 20110825140820 with status UNRESOLVED REQUESTS IN BUFFER.
Error message set: 'Unresolved requests in buffer UT1
Check logfiles 'XPRASUPG.ELG' and '/usr/sap/putUT1/EHPI/abap/log/SAPehpi.ECO''
...begin dialogue at 20110825140821
from SAPehpi.ECO
EXECUTING /usr/sap/UT1/SYS/exe/run/tp (/usr/sap/UT1/SYS/exe/run/tp) pf=/usr/sap/putUT1/EHPI/abap/bin/XPRASUPG.TPP put
UT1
This is /usr/sap/UT1/SYS/exe/run/tp version 380.03.36 (release 720, unicode enabled)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
Process with ID 4903 terminated with status 12
from XPRASUPG.ELG
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR702XPRA00000005.UT1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "14071100")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""14071100""UT1"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
<end of logs>
I have searched for ST22 logs and i got a syntax error on program CL_PROXY_STYLESHEET_RUNTIME.
Upgrade 702 has added a segment in the DELETE_CLASS of the program above:
delete from sproxxsl
 where class = class and method = <sproxxsl>-method and client = <sproxxsl>-client.
before:
delete from sproxxsl
 where class = class and method.
"client" field is not part of table SPROXXSL. Which is causing the error.
Any idea on how to continue???
The choices now are:
01) * Repeat phase MAIN_NEWBAS/XPRAS_AIMMRG to continue at the point it stopped
02) - Initialize phase MAIN_NEWBAS/XPRAS_AIMMRG to restart it from the beginning
03) - Accept non-severe errors and repeat phase MAIN_NEWBAS/XPRAS_AIMMRG
04) - Exit this program
Edited by: Rainier Sison on Aug 29, 2011 2:21 PM
Edited by: Rainier Sison on Aug 29, 2011 2:22 PM
Edited by: Rainier Sison on Aug 29, 2011 2:23 PM

Well, I did have a similar issue with RDDEXECL during the import of SAPKB71007.
The solution at that time was updating the kernel to the latest support level, that was released a few weeks after the error with a special modification to fix 'our' issue.
Do you think it's possible to change the kernel on the shadow instance at this moment of EHPI execution?
Hope this helps
Best Regards
Francisco
Edit: The OSS note was: 1551400 - ABAP: Session abort when compiling a deep constant
Edited by: Francisco José Martínez Carretero on Aug 29, 2011 4:54 PM

IE 9 (9.0.8112.16421) causing internal server error on sharepoint 2010 when searching ?

Hi,
We have a sharepoint enterprise installation. We have an exception when trying to search documents on sharepoint.
This can't be reproduce with chrome.
When I try to lookup the correlation ID given with an error
get-splogevent | where {$_Correlation -eq "7ee2bfaa-7ce4-4ac3-b60e-0532d82a42cb" }
I get no results
Fortunately, the error displays the hour it occured, ans the log is giving this information
Timestamp    : 29/01/2014 09:05:27
Continuation : False
Process      : OWSTIMER.EXE (0x1D20)
ThreadID     : 5024
Area         : SharePoint Foundation
Category     : Monitoring
EventID      : nasq
Level        : Medium
Message      : Entering monitored scope (Timer Job SchedulingUnpublish)
Correlation : 2e594c83-42fa-411e-9ea6-97917edf68d6
Context      : {}
Timestamp    : 29/01/2014 09:05:27
Continuation : False
Process      : OWSTIMER.EXE (0x1D20)
ThreadID     : 2244
Area         : SharePoint Foundation
Category     : Monitoring
EventID      : nasq
Level        : Medium
Message      : Entering monitored scope (Timer Job SASCRM_Job)
Correlation : 88f2cb56-6637-4168-ae94-bab3c61bc04e
Context      : {}
Timestamp    : 29/01/2014 09:05:27
Continuation : False
Process      : OWSTIMER.EXE (0x1D20)
ThreadID     : 5024
Area         : SharePoint Foundation
Category     : Monitoring
EventID      : b4ly
Level        : Medium
Message      : Leaving Monitored Scope (Timer Job SchedulingUnpublish). Execution Time=4.50979104886235
Correlation : 2e594c83-42fa-411e-9ea6-97917edf68d6
Context      : {}
Timestamp    : 29/01/2014 09:05:27
Continuation : False
Process      : OWSTIMER.EXE (0x1D20)
ThreadID     : 5024
Area         : SharePoint Foundation
Category     : Monitoring
EventID      : nasq
Level        : Medium
Message      : Entering monitored scope (Timer Job SchedulingUnpublish)
Correlation : 2e594c83-42fa-411e-9ea6-97917edf68d6
Context      : {}
Timestamp    : 29/01/2014 09:05:27
Continuation : False
Process      : OWSTIMER.EXE (0x1D20)
ThreadID     : 2244
Area         : SharePoint Foundation
Category     : Monitoring
EventID      : b4ly
Level        : Medium
Message      : Leaving Monitored Scope (Timer Job SASCRM_Job). Execution Time=11.3905538273719
Correlation : 88f2cb56-6637-4168-ae94-bab3c61bc04e
Context      : {}
Timestamp    : 29/01/2014 09:05:27
Continuation : False
Process      : OWSTIMER.EXE (0x1D20)
ThreadID     : 2244
Area         : SharePoint Foundation
Category     : Performance
EventID      : nask
Level        : Monitorable
Message      : An SPRequest object was not disposed before the end of this thread. To avoid wasting system resources, dispose of this object or its parent (such as an SPSite or S
               PWeb) as soon as you are done using it. This object will now be disposed. Allocation Id: {30F2B069-9B14-44BF-B684-0651FB623DBD} To determine where this object
wa
               s allocated, set Microsoft.SharePoint.Administration.SPWebService.ContentService.CollectSPRequestAllocationCallStacks = true.
Correlation : 88f2cb56-6637-4168-ae94-bab3c61bc04e
Context      : {}
Timestamp    : 29/01/2014 09:05:27
Continuation : False
Process      : OWSTIMER.EXE (0x1D20)
ThreadID     : 5024
Area         : SharePoint Foundation
Category     : Monitoring
EventID      : b4ly
Level        : Medium
Message      : Leaving Monitored Scope (Timer Job SchedulingUnpublish). Execution Time=4.79586092645853
Correlation : 2e594c83-42fa-411e-9ea6-97917edf68d6
Context      : {}
Timestamp    : 29/01/2014 09:05:27
Continuation : False
Process      : OWSTIMER.EXE (0x1D20)
ThreadID     : 2244
Area         : SharePoint Foundation
Category     : Monitoring
EventID      : nasq
Level        : Medium
Message      : Entering monitored scope (Timer Job SASCRM_Job)
Correlation : 88f2cb56-6637-4168-ae94-bab3c61bc04e
Context      : {}
Timestamp    : 29/01/2014 09:05:27
Continuation : False
Process      : OWSTIMER.EXE (0x1D20)
ThreadID     : 2244
Area         : SharePoint Foundation
Category     : Monitoring
EventID      : b4ly
Level        : High
Message      : Leaving Monitored Scope (EnsureListItemsData). Execution Time=15.7581480327807
Correlation : 88f2cb56-6637-4168-ae94-bab3c61bc04e
Context      : {}
Timestamp    : 29/01/2014 09:05:27
Continuation : False
Process      : OWSTIMER.EXE (0x1D20)
ThreadID     : 2244
Area         : SharePoint Foundation
Category     : Database
EventID      : 4ohp
Level        : High
Message      : Enumerating all sites in SPWebApplication Name=SALES.
Correlation : 88f2cb56-6637-4168-ae94-bab3c61bc04e
Context      : {}
Timestamp    : 29/01/2014 09:05:27
Continuation : False
Process      : OWSTIMER.EXE (0x1D20)
ThreadID     : 2244
Area         : SharePoint Foundation
Category     : Database
EventID      : 4ohq
Level        : Medium
Message      : Site Enumeration Stack:    at Microsoft.SharePoint.SPBaseCollection.GetEnumerator()     at Afv.SharePoint.Crm.Job.SASCRM_Job.RelocateUpdatedDocuments(SPList listSAS
               CRM, SPWeb webElev, SPSite site)     at Afv.SharePoint.Crm.Job.SASCRM_Job.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke
               Internal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke
               (TimerJobExecuteData& data, Int32& result)
Correlation : 88f2cb56-6637-4168-ae94-bab3c61bc04e
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : mssdmn.exe (0x21F8)
ThreadID     : 9152
Area         : SharePoint Server
Category     : Unified Logging Service
EventID      : b8fx
Level        : High
Message      : ULS Init Completed (mssdmn.exe, Microsoft.Office.Server.Native.dll)
Correlation : 00000000-0000-0000-0000-000000000000
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : mssdmn.exe (0x21F8)
ThreadID     : 9152
Area         : SharePoint Server Search
Category     : FilterDaemon
EventID      : e4uf
Level        : High
Message      : filter daemon memory quota: 838860800 838860800
[fltrdaemon.cxx:1505] d:\office\source\search\native\mssdmn\fltrdaemon.cxx
Correlation : 00000000-0000-0000-0000-000000000000
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : w3wp.exe (0x1434)
ThreadID     : 4428
Area         : SharePoint Foundation
Category     : Monitoring
EventID      : nasq
Level        : Medium
Message      : Entering monitored scope (Request (GET:http://--My server/--MY Site--/_layouts/crm_searchresults/tablesearchresults.aspx?k=infreportid%3D4c7894e3-3388-e311-af
               af-0050568e004e&accountid=0b8cbdd5-3388-e311-afaf-0050568e004e&inf_reportid=4c7894e3-3388-e311-afaf-0050568e004e&prospectnumber=P14001043&reportnumber=FALST140102))
Correlation : 00000000-0000-0000-0000-000000000000
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : w3wp.exe (0x1434)
ThreadID     : 4428
Area         : SharePoint Foundation
Category     : Logging Correlation Data
EventID      : xmnv
Level        : Medium
Message      : Name=Request (GET:http://--My server/--MY Site--/_layouts/crm_searchresults/tablesearchresults.aspx?k=infreportid%3D4c7894e3-3388-e311-afaf-0050568e004e&accou
               ntid=0b8cbdd5-3388-e311-afaf-0050568e004e&inf_reportid=4c7894e3-3388-e311-afaf-0050568e004e&prospectnumber=P14001043&reportnumber=FALST140102)
Correlation : e87e2210-e512-44c8-927e-83d50e6b3879
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : w3wp.exe (0x1434)
ThreadID     : 4428
Area         : SharePoint Foundation
Category     : Monitoring
EventID      : b4ly
Level        : Medium
Message      : Leaving Monitored Scope (Request (GET:http://--My server/--MY Site--/_layouts/crm_searchresults/tablesearchresults.aspx?k=infreportid%3D4c7894e3-3388-e311-afa
               f-0050568e004e&accountid=0b8cbdd5-3388-e311-afaf-0050568e004e&inf_reportid=4c7894e3-3388-e311-afaf-0050568e004e&prospectnumber=P14001043&reportnumber=FALST140102)).
                Execution Time=1,25267317494263
Correlation : e87e2210-e512-44c8-927e-83d50e6b3879
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : w3wp.exe (0x1434)
ThreadID     : 8116
Area         : SharePoint Foundation
Category     : Monitoring
EventID      : nasq
Level        : Medium
Message      : Entering monitored scope (Request (GET:http://--My server/--MY Site--/_layouts/crm_searchresults/tablesearchresults.aspx?k=infreportid%3D4c7894e3-3388-e311-af
               af-0050568e004e&accountid=0b8cbdd5-3388-e311-afaf-0050568e004e&inf_reportid=4c7894e3-3388-e311-afaf-0050568e004e&prospectnumber=P14001043&reportnumber=FALST140102))
Correlation : 00000000-0000-0000-0000-000000000000
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : w3wp.exe (0x1434)
ThreadID     : 8116
Area         : SharePoint Foundation
Category     : Logging Correlation Data
EventID      : xmnv
Level        : Medium
Message      : Name=Request (GET:http://--My server/--MY Site--/_layouts/crm_searchresults/tablesearchresults.aspx?k=infreportid%3D4c7894e3-3388-e311-afaf-0050568e004e&accou
               ntid=0b8cbdd5-3388-e311-afaf-0050568e004e&inf_reportid=4c7894e3-3388-e311-afaf-0050568e004e&prospectnumber=P14001043&reportnumber=FALST140102)
Correlation : 197c3750-c383-49aa-859f-48376ba4105f
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : w3wp.exe (0x1434)
ThreadID     : 8116
Area         : SharePoint Foundation
Category     : Monitoring
EventID      : b4ly
Level        : Medium
Message      : Leaving Monitored Scope (Request (GET:http://--My server/--MY Site--/_layouts/crm_searchresults/tablesearchresults.aspx?k=infreportid%3D4c7894e3-3388-e311-afa
               f-0050568e004e&accountid=0b8cbdd5-3388-e311-afaf-0050568e004e&inf_reportid=4c7894e3-3388-e311-afaf-0050568e004e&prospectnumber=P14001043&reportnumber=FALST140102)).
                Execution Time=1,26775889114399
Correlation : 197c3750-c383-49aa-859f-48376ba4105f
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : w3wp.exe (0x1434)
ThreadID     : 4428
Area         : SharePoint Foundation
Category     : Monitoring
EventID      : nasq
Level        : Medium
Message      : Entering monitored scope (Request (GET:http://--My server/--MY Site--/_layouts/crm_searchresults/tablesearchresults.aspx?k=infreportid%3D4c7894e3-3388-e311-af
               af-0050568e004e&accountid=0b8cbdd5-3388-e311-afaf-0050568e004e&inf_reportid=4c7894e3-3388-e311-afaf-0050568e004e&prospectnumber=P14001043&reportnumber=FALST140102))
Correlation : 00000000-0000-0000-0000-000000000000
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : w3wp.exe (0x1434)
ThreadID     : 4428
Area         : SharePoint Foundation
Category     : Logging Correlation Data
EventID      : xmnv
Level        : Medium
Message      : Name=Request (GET:http://--My server/--MY Site--/_layouts/crm_searchresults/tablesearchresults.aspx?k=infreportid%3D4c7894e3-3388-e311-afaf-0050568e004e&accou
               ntid=0b8cbdd5-3388-e311-afaf-0050568e004e&inf_reportid=4c7894e3-3388-e311-afaf-0050568e004e&prospectnumber=P14001043&reportnumber=FALST140102)
Correlation : dffeb360-ca1c-4496-814b-63a970a4b24e
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : w3wp.exe (0x1434)
ThreadID     : 4428
Area         : SharePoint Foundation
Category     : Logging Correlation Data
EventID      : xmnv
Level        : Medium
Message      : Site=--MY Site--
Correlation : dffeb360-ca1c-4496-814b-63a970a4b24e
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : w3wp.exe (0x1434)
ThreadID     : 4428
Area         : SharePoint Foundation
Category     : General
EventID      : 72nz
Level        : Medium
Message      : Videntityinfo::isFreshToken reported failure.
Correlation : dffeb360-ca1c-4496-814b-63a970a4b24e
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : w3wp.exe (0x1434)
ThreadID     : 4428
Area         : SharePoint Server Search
Category     : Query
EventID      : dn4s
Level        : High
Message      : FetchDataFromURL start at(outside if): 1 param: start
Correlation : dffeb360-ca1c-4496-814b-63a970a4b24e
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : w3wp.exe (0x1434)
ThreadID     : 4428
Area         : SharePoint Server Search
Category     : Query
EventID      : g1j9
Level        : Exception
Message      : Internal server error exception: System.ArgumentNullException: Value cannot be null. Parameter name: The property RequestedLanguage cant not set to NULL     at Mic
               rosoft.Office.Server.Search.Query.Location.set_RequestedLanguage(CultureInfo value)     at Microsoft.Office.Server.Search.WebControls.CoreResultsDatasourceView.Crea
               teLocationList()     at Microsoft.Office.Server.Search.WebControls.CoreResultsDatasourceView.SetPropertiesOnQdra()     at Microsoft.Office.Server.Search.WebControls
               .SearchResultsBaseWebPart.EnsureWebpartReady() System.ArgumentNullException: Value cannot be null. Parameter name: The property RequestedLanguage cant not set to N
               ULL     at Microsoft.Office.Server.Search.Query.Location.set_RequestedLanguage(CultureInfo value)     at Microsoft.Office.Server.Search.WebControls.CoreResultsDatas
               ourceView.CreateLocationList()     at Microsoft.Office.Server.Search.WebControls.CoreResultsDatasourceView.SetPropertiesOnQdra()
at Microsoft.Office.Server.Sear
               ch.WebControls.SearchResultsBaseWebPart.EnsureWebpartReady()
Correlation : dffeb360-ca1c-4496-814b-63a970a4b24e
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : w3wp.exe (0x1434)
ThreadID     : 4428
Area         : SharePoint Server
Category     : Unified Logging Service
EventID      : c91s
Level        : Monitorable
Message      : Watson bucket parameters: SharePoint Server 2010, ULSException14, 06175311 "sharepoint server search", 0e00129b "14.0.4763.0", 17853a8f "microsoft.office.server.sea
               rch", 0e00129a "14.0.4762.0", 4bad937d "sat mar 27 06:11:25 2010", 000037d1 "000037d1", 00000032 "00000032", e9fbee3b "argumentnullexception",
67316a39 "g1j9"
Correlation : dffeb360-ca1c-4496-814b-63a970a4b24e
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : w3wp.exe (0x1434)
ThreadID     : 4428
Area         : SharePoint Server
Category     : General
EventID      : 7888
Level        : Warning
Message      : A runtime exception was detected. Details follow. Message: Thread was being aborted. Technical Details: System.Threading.ThreadAbortException: Thread was being ab
               orted.     at System.Threading.Thread.AbortInternal()     at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()     at System.Web.
               HttpServerUtility.Transfer(String path)     at Microsoft.SharePoint.Utilities.SPUtility.TransferToErrorPage(String message, String linkText, String linkUrl)
at
               Microsoft.Office.Server.Search.WebControls.QueryUIError.GetErrorMessageOrRedirectToErrorPage(Exception ex, Boolean showMessages)     at Microsoft.Office.Server.Sear
               ch.WebControls.SearchResultsBaseWebPart.EnsureWebpartReady()     at Microsoft.Office.Server.Search.WebControls.SearchResultsBaseWebPart.OnLoad(EventArgs
e)
Correlation : dffeb360-ca1c-4496-814b-63a970a4b24e
Context      : {}
Timestamp    : 29/01/2014 09:05:28
Continuation : False
Process      : w3wp.exe (0x1434)
ThreadID     : 4428
Area         : SharePoint Server Search
Category     : Query
EventID      : g1j9
Level        : Exception
Message      : (Watson Reporting Cancelled) System.Threading.ThreadAbortException: Thread was being aborted.     at System.Threading.Thread.AbortInternal()     at System.Threading
               .Thread.Abort(Object stateInfo)     at System.Web.HttpResponse.End()     at System.Web.HttpServerUtility.Transfer(String path)
at Microsoft.SharePoint.Utilities
               .SPUtility.TransferToErrorPage(String message, String linkText, String linkUrl)     at Microsoft.Office.Server.Search.WebControls.QueryUIError.GetErrorMessageOrRedi
               rectToErrorPage(Exception ex, Boolean showMessages)     at Microsoft.Office.Server.Search.WebControls.SearchResultsBaseWebPart.EnsureWebpartReady()
at Microsoft
               .Office.Server.Search.WebControls.SearchResultsBaseWebPart.OnLoad(EventArgs e)
Correlation : dffeb360-ca1c-4496-814b-63a970a4b24e
Context      : {}
Any idea ?
regards

Hi!
I believe it is a problem regarding the preferred language for the user:
"Internal server error exception: System.ArgumentNullException: Value cannot be null. Parameter
name: The property RequestedLanguage cant not set to NULL "
Please refer to this thread (http://social.technet.microsoft.com/Forums/en-US/230896a4-a928-4b44-91a2-3e7f767b8b3f/internal-server-error-exception-on-search-results-page-when-no-language-is-set-in-browser?forum=sharepointgeneralprevious)
as I think it's related.
Cheers

Urgently Upgrade Stop In XPRAS_UPG Phase

Hi all,
This is our infrastructure:
Windows 2000
Oracle 9.2.0.7
SAP 4.6B
Kernel Release 46D
We are upgrading our DEV System to R/3 Enterprise 4.7 Ext. 2 Sr1
Our Upgrade Process Stop in the XPRAS_UPG Phase. Basically it gives this error:
WARNING: tp terminated with status 12
R3up> ERROR: tp terminated with error status -1
R3up> ERROR: 2 errors detected during XPRAS_UPG
R3up> ERROR: 1 activities have been aborted in XPRAS_UPG
R3up> ERROR: Operation(s) not completely processed.
 Remaining change request found in buffer TVD.
 Ignoring aborted import steps will cause severe inconsistencies
Logs that we reviewed:
XPRASUPG.ECO and R3up.ECO
the problem is with the RDDEXECL JOB. Which is in the status CANCELED
When we Check the JOB LOG it gives this:
 22.10.2007 10:59:35 Job started
22.10.2007 10:59:35 Step 001 started (program RDDEXECL, variant , user ID DDIC)
22.10.2007 10:59:35 All DB buffers of application server vensapd were synchronized PU
22.10.2007 11:01:17 ABAP/4 processor: CONVT_CODEPAGE_INIT
22.10.2007 11:01:17 Job cancelled 00
When you click on ABAP/4 processor: CONVT_CODEPAGE_INIT you get this:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17

The conversion of some code pages is not supported.
What happened? 
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
Error analysis
 An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
 'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure "READ_TEXTLINES" "(FORM)".
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the
LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X u00F0####u00CCu00FF#,").
Please Some help!
We saw this note:
122597 Ignoring errors in the phase XPRAS
So we try with the option "u00CFgnore" + "Repair Severe Errors" but nothing happens, in remains in the same place, Start the Phase a again and Stop at the same point.
676135 Short Dump when you import Support Packages
This notes explain this: (Page 3 Paragraph 3)
If you are still upgrading, import the transport order into the system using 'R3trans -i <data file name>'. Enter the correct path to the data file (possibly DIR_PUT).
But we are scared about to STOP the upgrade here (Like 'cancel' option instead of continue and after restart the upgrade) does somebody apply this note?
This are the logs:
XPRASUPG.ECO
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR620ZF1.TVD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "10593502")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""10593502""TVD"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
R3up.ECO:
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 15160 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Copying file D:\usr\sap\put\bin\XPRASUPG.TPP to D:\usr\sap\put\bin\AKKU.TMP
Copying file D:\usr\sap\put\buffer\TVD to D:\usr\sap\put\buffer\AFTXPRAS.BUF
Phase XPRAS_UPG:
Deleting file D:\usr\sap\put\log\CONNECT.LOG
R3up> Starting subprocess tp.exe with id 4196 at 20071022101802
EXECUTING D:\usr\sap\TVD\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\XPRASUPG.TPP put TVD
Environment: dbs_ora_schema=SAPR3
Environment: dbs_ora_tnsname=TVD
Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC
Environment: ORACLE_HOME=D:\oracle\TVD\920
Environment: ORACLE_SID=TVD
This is D:\usr\sap\TVD\SYS\exe\run\tp.exe version 340.16.37 (release 640)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
STARTSAP continues...
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 16400 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Copying file D:\usr\sap\put\bin\XPRASUPG.TPP to D:\usr\sap\put\bin\AKKU.TMP
Copying file D:\usr\sap\put\buffer\TVD to D:\usr\sap\put\buffer\AFTXPRAS.BUF
Phase XPRAS_UPG:
Deleting file D:\usr\sap\put\log\CONNECT.LOG
R3up> Starting subprocess tp.exe with id 4196 at 20071022105721
EXECUTING D:\usr\sap\TVD\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\XPRASUPG.TPP put TVD
Environment: dbs_ora_schema=SAPR3
Environment: dbs_ora_tnsname=TVD
Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC
Environment: ORACLE_HOME=D:\oracle\TVD\920
Environment: ORACLE_SID=TVD
This is D:\usr\sap\TVD\SYS\exe\run\tp.exe version 340.16.37 (release 640)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
STARTSAP continues...
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 15096 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Best Regards,
Desiree Cardenas

Hi Eric,
In fact in the previous post you can see:
the problem is with the
RDDEXECL JOB. Which is in the status CANCELED
When we Check the JOB LOG it gives this:
22.10.2007 10:59:35 Job started
22.10.2007 10:59:35 Step 001 started (program RDDEXECL, variant , user ID DDIC)
22.10.2007 10:59:35 All DB buffers of application server vensapd were synchronized PU
22.10.2007 11:01:17 ABAP/4 processor: CONVT_CODEPAGE_INIT
22.10.2007 11:01:17 Job cancelled 00
When you click on ABAP/4 processor: CONVT_CODEPAGE_INIT you get this:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
The conversion of some code pages is not supported.
What happened?
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure "READ_TEXTLINES" "(FORM)".
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the
LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X ð####Ìÿ#,").
Sorry for the big amount of information. I will put the complete JOB LOG.
LOG:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
The conversion of some code pages is not supported.
What happened?
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that 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.
If the application required you to enter a code page, you may be able to
avoid the error by restarting the application and entering a different
code page.
You can display the available codepages using the transaction SCP. For
more utilities for codepages, use the transaction SNLS.
Error analysis An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure
"READ_TEXTLINES" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X ð####Ìÿ#,").
How to correct the error
The exception must either be prevented, caught within the procedure
"READ_TEXTLINES"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"CONVT_CODEPAGE_INIT" CX_SY_CODEPAGE_CONVERTER_INITC
"SAPLSTXD" or "LSTXDFDB"
"READ_TEXTLINES"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
 To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
 To obtain this, call the system log with Transaction SM21
 and select the "Print" function to print out the relevant
 part.
3. If the programs are your own programs or modified SAP programs,
 supply the source code.
 To do this, you can either use the "PRINT" command in the editor or
 print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
File attributes no file
System environment
SAP Release.............. "620"
Application server....... "vensapd"
Network address.......... "10.55.46.71"
Operating system......... "Windows NT"
Release.................. "5.0"
Hardware type............ "4x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 11
Short dump setting....... "full"
Database server.......... "VENSAPD"
Database type............ "ORACLE"
Database name............ "TVD"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Jun 25 2004 20:55:59"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "21"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Program............. "SAPLSTXD"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLSTXD" in "READ_TEXTLINES".
The main program was "RDDEXECU ".
The termination occurred in line 82 of the source code of the (Include)
program "LSTXDFDB"
of the source code of program "LSTXDFDB" (when calling the editor 820).
The program "SAPLSTXD" was started as a background job.
Processing was terminated because the exception "CX_SY_CODEPAGE_CONVERTER_INIT"
occurred in the
procedure "READ_TEXTLINES" "(FORM)" but was not handled locally, not declared
in the
RAISING clause of the procedure.
The procedure is in the program "SAPLSTXD ". Its source code starts in line 75
of the (Include) program "LSTXDFDB ".
Best Regards,
Desiree Cardenas

Checks after phase MAIN_NEWBAS/XPRAS_UPG were negative

Hi Gurus,
am upgrading from ecc 6.0 to ehp5 on dual stack system OS:Windows 2003 DB:oracle 10.2.0.2
i got below error in the MAIN_NEWBAS/XPRAS_UPG phase
XPRASUPG.ELG log:
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-500AGINCPRXRPM.IJE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "14152200")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""14152200""IJE"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
RDDEXECL job log:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server admin0001 were synchronized
Internal session terminated with a runtime error (see ST22)
Job cancelled
Dump at ST22:
Error analysis
 The following syntax error was found in the program
 CL_DPR_TASK_O=================CP :
 "Formal parameter "IV_PLANSTART" does not exist."
please help me solve
Thanks,
Venkat

Hi Sunny,
here is dump details..
Category ABAP Programming Error
Runtime Errors SYNTAX_ERROR
ABAP Program CL_DPR_TASK_O=================CP
Application Component PPM-PRO-STR
Date and Time 06.12.2011 16:34:41
User and Transaction
 Client.............. 000
 User................ "DDIC"
 Language key........ "E"
 Transaction......... " "
 Transaction ID...... "04FA1FE12F6DF16DB7E400145E69764F"
 EPP Whole Context ID.... 34454438393637453445443839363745
 EPP Connection ID....... 34454442374143323445444237414332
 EPP Caller Counter...... 1
 Program............. "CL_DPR_STATUS_CHANGE_OBSERVER=CP"
 Screen.............. "SAPMSSY0 1000"
 Screen Line......... 6
 Debugger Active..... "none"
What happened?
 Error in the ABAP Application Program
 The current ABAP program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" had to be
 terminated because it has
 come across a statement that unfortunately cannot be executed.
 The following syntax error occurred in program
 "CL_DPR_TASK_O=================CP " in include
 "CL_DPR_TASK_O=================CM021 " in
 line 74:
 "Formal parameter "IV_PLANSTART" does not exist."
 The include has been created and last changed by:
 Created by: "SAP "
 Last changed by: "SAP "
 Error in the ABAP Application Program
 The current ABAP program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" had to be
 terminated because it has
 come across a statement that unfortunately cannot be executed.
Error analysis
 The following syntax error was found in the program
 CL_DPR_TASK_O=================CP :
 "Formal parameter "IV_PLANSTART" does not exist."
Information on where terminated
 Termination occurred in the ABAP program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" -
 in "SET_HANDLER".
 The main program was "R_DPR_PROJECT_ROLES_XPRA ".
 In the source code you have the termination point in line 12
 of the (Include) program "CL_DPR_STATUS_CHANGE_OBSERVER=CM00A".
 The program "CL_DPR_STATUS_CHANGE_OBSERVER=CP" was started as a background job.
 Job Name....... "RDDEXECL"
 Job Initiator.. "DDIC"
Thanks in advance
Venkat

XPRAS_UPG error in DOWNTIME phase in EHP4

Hi,
I am getting the below error in XPRAS_UPG in DOWNTIME phase of EHP4 installation in ERP 6.0 on HP-UNIX and Oracle.
XPRA ERRORS and RETURN CODE in SAPRW70104.HD1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "10302400")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""10302400""HD1"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
I was successfully able to umlock the system and in SM37 I could see the job log pointing to ST22. In ST22 we have many dumps related to error PXA_NO_FREE_SPACE. I found many notes in marketplace but all are referring the parameter abap/buffersize which needs to increased. I am a bit apprehensive about the fact that since we are in DOWNTIME phase and in the middle of XPRA execution phase should we increase the parameter and restart the system and then continue with the upgrade???
I have also tried to run the phase many times but the same error persists.
Please can anyone help me to come out of this problem.....
Thanks & regards,
Rozal

Hello Rozal,
You are correct XPRAS is a downtime 2 phase, but actually your system is up and running. It was started way back in phase "STARTSAP_NBAS" its just that you cannot use your system productively. XPRAS executes the XPRAS methods in the running system.
Its absolutely safe, you can change the parameter take a restart and continue further.
- Niraj

Report Cancelled PO

Similar Messages

Maybe you are looking for