Dump when opening infopackage

Hi everybody,
I am getting a dump when trying to open an infopackage in some infoobjects. Mainly it is happening in 0MATERIAL, 0CUSTOMER and some others.
Our BW system is conected to 2 different R3 systems, development and test. D works fine but in the packages in T i get this error.
I add some text of the dump to help...
What happened?
The current application program detected a situation which real
should not occur. Therefore, a termination with a short dump wa
triggered on purpose by the key word MESSAGE (type X).
Error analysis
Short text of error message:
Data request to the OLTP ***
Technical information about the message:
Message classe...... "RSM "
Number.............. 000
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
Information on where termination occurred
The termination occurred in the ABAP program "SAPLRSS1 " in
"RSM1_CHECK_FOR_DELTAUPD".
The main program was "RSABW_START_NEW ".
The termination occurred in line 1348 of the source code of the (Include)
program "LRSS1F11 "
of the source code of program "LRSS1F11 " (when calling the editor 13480).
                                                                                Source code extract
013180 EXCEPTIONS
013190 not_exist = 1
013200 OTHERS = 2.
013210 IF sy-subrc <> 0
013220 MESSAGE x000.
013230 ENDIF.
013240 DATA: l_t_roosprmsc LIKE roosprmsc OCCURS 0.
013250 DATA: l_s_roosprmsc LIKE roosprmsc.
013260 DATA: l_t_roosprms_dummy   LIKE roosprms   OCCURS 0.
013270 DATA: l_t_roosprmsf_dummy LIKE roosprmsf OCCURS 0
013280 DATA: l_t_rorqstprms_dummy LIKE rorqstprms OCCURS 0.
013290 CALL FUNCTION 'RSA1_OLTPSOURCE_GET_SELECTIONS'
013300 DESTINATION l_
013310 EXPORTING
013320 i_oltpsource   = l_oltpsource
013330 i_rlogsys      = l_rlogsys
013340 TABLES
013350 e_t_roosprmsc = l_t_roosprmsc
013360 e_t_roosprms   = l_t_roosprms_dummy
013370 e_t_roosprmsf = l_t_roosprmsf_dummy
013380 e_t_rorqstprms = l_t_rorqstprms_dummy
013390 EXCEPTIONS
013400 communication_failure = 1 MESSAGE msg_
013410 system_failure = 2 MESSAGE msg_text.
013420 if sy-subrc <> 0.
013430 message x051(rsar) with msg_text(50)
013440 msg_text+50(50) '' ''.
013450 endif.
013460 READ TABLE l_t_roosprmsc INTO l_s_roosprmsc INDEX 1.
013470 IF sy-subrc <> 0
     >               MESSAGE x000.
013490 ENDIF.
Any help would be helpul!!!
Thanks a lot
Nacho

Hi Ignacio,
Refer to the OSS note:424848 and run the report RSSM_OLTP_INIT_DELTA_UPDATE, this should solve the issue, note that although this note refers to 2.x, this report is available in BW 3.x and you should be able to run it without any problem.
Hope it helps,
Sree

Similar Messages

Data target error when opening InfoPackage (not loadable)

Hi,
I have transported my objects from the development environment to QA environment, but now when I try to open one specific InfoPackage (in QA) to schedule a data load to an DSO, I receive the following error:
Data target 'P_USUARIO ' removed from list of loadable targets; not loadable RSM 33
Data target 'P_USUARIO ' is not active or is incorrect; no loading allowed RSM 36
I tried to run RS_TRANSTRU_ACTIVATE_ALL program before realizing that it is not relevant in NW04s and I tried to transport many times again this specific data target with no success.
Any suggestion??
Thanks in advance.
Raphael

Hi:
The program you ran is for Transfer Structure.
The error you are gettign is for an Inactive Update Rule.
If the infopackage is loading several data targets and an update rule is inactive, then, you have take off laoding to that Update Rule in Infopackage.
First, see which Update Rule is Inactive. Look in all the tabs of infopackage and you will find it.
Ram C.

Error when open Infopackage

Dear Gurus
When i double click to open an infopackage that attached to flat file source system i'm getting the following error
boldAn internal error occurred during the authorization check.
Message no. RSM894bold
If i open other infopackage within the same source system , i'm abale to open w/o any error
Please advice
thank you
BR

Su53 return no error
When i double click on the Infosource that this infopackage belong to , it return
InfoSource ZBWCH034 (Master Data) is not known
Message no. RSAR208
Please help
I can work with this object in DEV and QAS but after i transport to PRD this errors are coming up
Thank you
BR

Dump when opening RSA1

Hi,
When I am trying to open RSA1 I am getting the following dump,what has to be done to resolve this
Runtime Errors         MESSAGE_TYPE_X
Date and Time          23.12.2006 10:16:22
ShrtText
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
Error analysis
Short text of error message:
Control Framework : Error processing control
Technical information about the message:
Diagnosis
An error occurred when the system tried to process the commands
from the Automation Queue on the presentation server.
There are several possible reasons for this:
- The installation of the SAP GUI on the presentation server is
faulty or obsolete.
- There is an error in the application program
- There is an error in the SAPGUI or an integrated control
Procedure
1. Make sure that you have imported the appropriate Support
Package, the current kernel, and GUI patch for the release of your
system
2. Check whether the error occurs locally on one or a few PCs, or
generally on all PCs. Note whether the error only occurs for some
users, for example because of a specific Customizing setting.
If it only occurs locally, this suggests an installation problem
with the PC. Check the installation; if necessary, reinstall the
software. In the dump, search for the SY-MSGLI field, since it may
point to the cause of the error.
3. Activate the Automation Trace (in accordance with SAP Note
158985).
4.Start the transaction and continue until the screen immediately
before the dump.
5. From the System -> Utilities menu, choose Autom. Queue,
Synchronous Processing.
The status bar of the GUI displays the text:
"Automation synchron flush mode on"
6. If you now proceed with the application, the short dump will
display the ABAP call that caused the error; the Automation Trace
will contain the error on the presentation server.
7. If necessary, load the short dump and trace files on to
sapservX, so that SAP can analyze them.
Message classe...... "CNDP"
Number.............. 006
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
Trigger Location of Runtime Error
Program                                 CL_GUI_CFW====================CP
Include                                 CL_GUI_CFW====================CM002
Row                                     23
Module type                             (METHOD)
Module Name                             FLUSH
Source Code Extract
Line
SourceCde
1
2
METHOD FLUSH .
3
4
data: rc like sy-subrc, msgli like sy-msgli.
5
6
CALL FUNCTION 'AC_FLUSH_CALL'
7
EXPORTING
8
SYSTEM_FLUSH = ' '
9
IMPORTING
10
MESSAGE_NR   = rc
11
MESSAGE_TEXT = msgli.
12
13
sy-subrc = rc.
14
sy-msgli = msgli.
15
16
CASE SY-SUBRC.
17
WHEN 0.
18
WHEN 1.
19
    system_error
20
MESSAGE ID 'CNDP' TYPE 'X' NUMBER 007 RAISING CNTL_SYSTEM_ERROR.
21
WHEN 2.
22
    method_call_error
>>>>>
MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
24
WHEN 3.
25
    property_set_error
26
MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
27
WHEN 4.
28
    property_get_error
29
MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
30
WHEN OTHERS.
31
RAISE CNTL_ERROR.
32
ENDCASE.
33
ENDMETHOD.
Regards,
Maya

Probably ur Tcode RSA1 is locked in something which causes a dump.
What u can do is try RSA11 or RSA12.
Regards

Short dump when opening the segment builder

After the upgrade from CRM 4.0 to 2007, we are no longer able to open the Segment Builder. We always get a short dump (Message_type_X). Anyone encountered this problem before and has a solution?
Thanx in advance!

Hi,
though it is true that in CRM 2007 the GUI transactions should not be used anymore I am able to start the segment builder directly via transactioin CRMD_MKTSEG. It is working without a shortdump.
For documentation I suppose you have to refer to SAP: Help or the documentation available under service.sap.com. The blog posted here might be an alternative as well.
cheers Carsten

Error while opening infopackage

Hi,
I get a short dump when i open infopackage for 2LIS_02_SCLdelta/
MESSAGE_TYPE_X.
Information on where terminated
    Termination occurred in the ABAP program "SAPLRSS1" - in
     "RSM1_CHECK_FOR_DELTAUPD".
    The main program was "RSAWBN_START ".
    In the source code you have the termination point in line 1530
    of the (Include) program "LRSS1F11".
I am not understanding this dumo and that to i am not starting the load but just opening infopackage and getting this dump. Pl help me in resolving this.
Thanks & Regards,
Vijaya

Hi,
We need to make some changes in delta settings.
See this SAP Note providing exact solution. Need to delete some table entries in PRD and BW DEV BOX.
Refer Note # 852443.
Summary
Symptom
If a MESSAGE_TYPE_X runtime error occurs in the LRSSMU36 include program in the SAPLRSSM ABAP program of the RSSM_OLTPSOURCE_SELECTIONS function module, proceed as described in the solution below.
This dump occurs if you try to open an InfoPackage for a DataSource/source system combination for which an initialization terminated incorrectly and a new INIT with overlapping selections was executed without the delta-administration being cleaned up.
The dump can also occur if you import a system copy/backup into only one of the two BW/OLTP systems without first deleting all delta queues for this BW/OLTP combination because the delta administration is always inconsistent. In such cases, contact the SAP consulting department.
A similar dump occurs in
perform "RSM1_CHECK_FOR_DELTAUPD in the LRSS1F11 include if the source system does not recognize any more inits (the roosprmsc and roosprmsf tables are empty) but if there are still entries in the RSSDLINIT/RSSDLINITSEL tables in the BW system.
This is the same as the problem described in Notes 424848 and 591382.
Other terms
Dump, include LRSSMU36, RSSM_OLTPSOURCE_SELECTIONS, MESSAGE_TYPE_X,
Init, delta queue, system copy, backup, initialization, InfoPackage,
RSM1_CHECK_FOR_DELTAUPD, LRSSMU36, LRSS1F11,
RSSDLINIT, RSSDLINITSEL, RSSM_OLTP_INIT_DELTA_UPDATE.
Reason and Prerequisites This problem is caused by a program error.
Solution
You can implement this correction only for load times from an OLTP system because transaction RSA7 is used for the delta administration/deletion.
For a DataMart, you may have to delete using transaction SE16 or a native SQL.
1. The entries for the initialization in the BW system are contained in the RSSDLINIT table for the DataSource/source system combination. Compare these with the entries in the ROOSPRMSC table in the OLTP system.
2. If there are NO entries in the RSSDLINIT table in BW, use transaction RSA7 to delete the delta queue for this DataSource/BW application combination in the source system (OLTP). For a DataMart source system, manually delete the entries in the ROOSPRMSC and ROOSPRMSF tables for your DataSource using transaction SE16 or a native SQL on the database. A DataMart can be identified by the DataSource that starts with '8', and by the fact that you CANNOT find it in RSA7 of the source system.
3. If the RSSDLINIT table in the BW system already contains entries, check the requests listed there in the RNR column in the monitor (transaction RSRQ). Compare these entries with the entries in the ROOSPRMSF and ROOSPRMSC tables with the INITRNR field. If, in the ROOSPRMSF and ROOSPRMSC tables for your DataSource source system combination, there are more entries with different INITRNR numbers, use transaction RSA7 in an OLTP source system to delete all entries and then use the RSSM_OLTP_INIT_DELTA_UPDATE report mentioned in the next section. For a DataMart source system, delete the entries that you cannot find in the RSSDLINIT table using the procedure described above.
4. Read also Notes 591382 and 424848. The errors described there also occur if you delete entries using transaction RSA7 in the source system but there is no RFC connection to the BW system. In the source system, there are no more entries in the ROOSPRMSC and ROOSPRMSF tables, but in the BW system, there are still entries in the RSSDLINIT and RSSDLINITSEL tables. Execute the RSSM_OLTP_INIT_DELTA_UPDATE report and then delete all init selections in the 'Scheduler/Init selections in the source system' menu in the InfoPackage.
5. When you have completed this procedure, you should be able to create a new InfoPackage or open an InfoPackage.
You can then open the InfoPackage again.
Check that there are no more entries in the
'Scheduler'/'Initialization options for source system' menu
If you do find some entries, delete them.
You can then start a new initialization.
If, despite the first incorrect init, you want to be able to create a second init with overlapping selections, which means that this dump will then occur, enter a detailed description of your procedure in a customer message and send it to Development. SAP has never been able to reproduce this behavior, therefore, a great deal of testing and the option to debug in your system would be required.
OR
Note 405943 - Calling an InfoPackage in BW causes short dump
Symptom
Calling an InfoPackage in BW causes a short dump (MESSAGE_TYPE_X).
Other terms
OLTP, DataSource, extractor, data extraction, delta, MESSAGE_TYPE_X
Reason and Prerequisites
The following conditions must be met:
1. The DataSource that is extracted using this InfoPackage must be a delta-capable transaction data DataSource or a master data or text DataSource if there is flexible updating of InfoObjects in BW. Additional prerequisites are listed below (there are several cases in which the dump may occur):
2
Case 1
3. There are several initialization selections for this DataSource.
4. A subset of the initialization selections was deleted before the dump.(Scheduler -> Menu scheduler -> Initialization selections source system)
5. The RSSDLINIT table in BW and the ROOSPRMSC table in the source system display different entries concerning the DataSource in question. More precisely: The RSSDLINIT table contains entries for the DataSource that have no corresponding entry in the ROOSPRSMC.
Case 2.
Alternatively, the problem may occur after a BW 12B upgrade.
Case 3.
Alternatively, the problem may occur if you have copied your OLTP system.
Case 4.
Alternatively, the problem may occur if you have installed a back-up in the OLTP system but not in BW.
Case 5.
Alternatively, the problem may occur if you load master data with flexible updating as a delta requests (0MATERIAL_ATTR, 0VENDOR_ATTR, 0CUSTOMER_ATTR and others).
Solution
You can apply note 0424848 if you are sure that this behavior only occurred because an upgrade was carried out 1.2B to 2.0B or 2.1C (Case 2) and, therefore, the roosprmsc and roosprmsf tables do not contain any entries for their Datasource/source system combination.This will copy the entries from BW into the source system and fill the roosprmsc and roosprmsf tables.
You can also use this solution for case 5 (as a workaround; the final solution is currently in progress).
IMPORTANT: You must only use this program in case 2 or case 5. We recommend that you do not use it in any other case as it may lead to data inconsistencies in BW.
If the problem is caused by individually deleted Delta Inits (Case 1), then implement the following steps according to your source system release:
1. As of 4.0B
Currently the only solution is reinitializing the delta update.To eliminate all inconsistencies, call the transaction RSA7 in your source system and delete the corresponding DataSource's delta queue for the relevant BW system.After that you must request the data again in the DeltaInit mode from BW.
If you no longer have any entries in the delta queue (RSA7) in OLTP, the inconsistencies must be eliminated by SAP BW support service.
The next PI patch contains a correction that no longer deletes all initialization selections in the source system when the deletion of a subset is called in the scheduler.
Alternatively you can import the correction instructions provided in this note into the OLTP.
2. 3.1H and 3.1I
The only way of eliminating the inconsistency is to reinitialize the delta update.In the scheduler menu, delete all the remaining initialization selections and reload data in 'Initialization of delta process' mode with or without the 'Simulation of delta initialization' flag.
If you can no longer access the scheduler because of a dump displaying this problem, ask your system consultant to implement note 419923.
If the problem is caused by a system copy (Case 3):
Ask your system consultant or SAP Support service to clean up the BW delta tables (the consultant can find the names of the tables in Note 419923 mentioned above) because you will have to reinitialize the delta again in all cases.
OR
Execute the FM "RSS1_QUEUE_DELETED_IN_OLTP", by giving OLTP source & logical system.
In RSSDLINIT table in BI entry for this datasourceROOSPRMSC table in OLTP.
Error - RSM1_CHECK_FOR_DELTAUPD
Short Dump when opening Info Package
Delete Initialization request
Hope this helps.
Thanks,
JituK

Dump when displaying target group

Hi,
When I try to display a target group I get this error:
Line types of an internal table and a work area not compatible
The problem is that in method SELECT_BP_ENHANCEMENTS from class CL_DEF_IM_CRM_MKTTG_SEG_MEM_EX, the method tries to insert a line of linetype crmt_mkttg_member_guid into an internal table with type BUPA_DATA_ALL.
This dump occurs since we upgraded to ehp2 sp10.
Anyone who had the same problem or knows how to fix this?
Kind regards,
R.W.

Hi Robbe,
maybe this note will solve your problem:
1937689 - Dump when opening a target group with out
relationship
Kind regards

Facing short dumps when trying to open session in CSA

Hi
All am facing Short dump when i am trying to open session in CSA
Error detials:
go to System Administration workcenter task management up CSA. Choose the Solution
got short dump:
Short text
    Length error occurred in IMPORT statement.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
     not caught in
    procedure "LOAD" "(METHOD)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    During import the system discovered that the target object has
    a different length than the object to be imported.
Missing RAISING Clause in Interface
    Program                                 SAPLDSVAS_PROC
    Include                                 LDSVAS_PROCTAI
    Row                                     1.431
    Module type                             (METHOD)
    Module Name                             LOAD
Trigger Location of Exception
    Program                                 SAPLDSVAS_PROC
    Include                                 LDSVAS_PROCTAI
    Row                                     1.514
    Module type                             (METHOD)
    Module Name                             LOAD
Please help me to solve this problem
Regards,
Neni

Hello Neni
According to the information I saw in that post it could be caused by a sort of inconsistency of the program code vs a structure.
Wether that is a bug that is in your SAP Solution Manager release or something that is caused by administrative actions (perhaps solving SPAU entries after SP stack update or upgrade) I cannot tell.
I would recommend you either try and find a relative SAP note (narrowing down result to only your SAP Solution Manager system) and searching using the dump keywords. If you cannot find anything I would recommend you to open a customer message so SAP can take a look at the specific error.
If you give more information, perhaps someone on the forum can help you out abit better, which SAP Solution Manager version and so on.
You also didn't answer my question, any recent changes you are aware of ?
Kind regards
Tom

Short Dump when trying to open C-project due to status

Hi,
We have a daily batch job in CRM that reports all the project ID's and
sends e-mails out to recipients.
As part of this report it retrieves the statuses for the project ID's,
however the report short dumps when retrieving the status for one of
the projects because it is not finding an active status.
When we try and open the project in C-projects we get the same short
dump error: CX_DPR_FATAL_ERROR so we cannot view or update the status.
When we investigate this issue we find that in table CRM_JCDS there are
3 entries for this project ID. One of the statuses is inactive (I1703)
but there is another status that is active (I1701). The two status
entries were created at exactly the same date and time and by the same
user.
In table CRM_JEST there is only one entry shown which shows an inactive
status and we believe this to be the wrong status. Please can you
advise if this status conflict is causing the problem and also how to
resolve this issue?

Hi Paul,
generally, the project and its elements must have an active status in table CRM_JEST, however, at this point it is not clear how this inconsistency arised. There is no SAP standard report or a 'generally valid' solution that could solve this issue, however, I found a customer message that you have opened in September with exactly the same problem. A colleague from the development team already provided you with a correction report, but there was no feedback from your side if it helped or not.
It is very difficult to provide help as inconsistencies can have several different causes, so the best would be to have this checked in a customer message with an example.
Regards,
Silvia

Error_Exception dump while opening the report in RRMX

Hi All,
When User trying to open the report Error_Exception dump is coming for few Info Providers. Please find attached dump for your reference.

Issue is res loved, We have analyze the short dump ,when loads were running and at that if time user executed the queries then that dump was occuring.

Why PSA data show red status when opened but green on PSA page?

Run RSA1 -> click PSA to open PSA page, locate one infosource and find the PSA under it, find the status column shows it's green, but when opening it, find the 1st column shows red for each row. How does the inconsitance occur?
BTW, if we open the infopackage monitor for the above one, find a weird thing is that each request get two consecutive processes running with a circle of red ball and green ball in the left frame. Double click one of them, in the right frame and click the monitor Status tab, the msg window is as following (in between two dashed lines below):
Incorrect data records - error requests (total status GREEN)
Diagnosis
Data records were recognized as incorrect.
System response
The valid records were updated in the data target and can be used in reporting.
The incorrect records were not written to the data target, but were posted retractively under a new request number in the PSA.
Procedure
Check the data in the error requests, correct the errors, and post the error requests.
Sounds like the data failed to uploaded to data target due to error in PSA, but why the status show green in somewhere? And if clicking the Details tab, all show green! Weird!
Thanks

Hi Kevin,
In your InfoPackage Update tab, click the Error Handling button. It seems that the Valid records update, request green option is chosen. This is why you see the green request and some error records.
This means that the corect reocrds were loaded and are available for reporting, but the incorrect ones were left behind. This is used to check the erro records separatelt so that they do not disrupt the entire data load.
Hope this helps...

Office 2013 Crashes when Opening Downloaded Files

Hello,
I am running Office 2013 on Windows 7; anytime I attempt to open a Word document that has been downloaded from my email, the program crashes. I see the Word splash screen, then the document opens for about two seconds, then it crashes. Upon reopening
Word, I am prompted to repair the program. After I repair the program and reopen Word again, I am prompted to reactivate the software.
If the attachment is saved directly to the computer, then opened from Word internally, the program works fine. I have already unchecked the boxes in the Trust Center and disabled the COM add-ons.
Any assistance would be appreciated!

Hi,
I’m a little confused about the difference between “open a Word document downloaded from your email” and “attachment is saved directly to the computer”. What is the difference between
them?
Do you open the document on OWA or from Outlook client?
If there is no issue when opening it from OWA, this issue may be related to Outlook client.
Let's troubleshoot this from running Outlook in Safe Mode, to determine if it is 3rd-party add-ins related. Press Win + R and type “outlook.exe /safe” in the blank box, then press Enter. Then we may try to open the attachment, if there’s no problem in Safe
Mode, disable the suspicious add-ins to verify which add-ins caused this issue.
We may also perform a clean boot to determine if background programs are interfering with Word:
http://support.microsoft.com/kb/929135
If Word crash still appears on local disk, we can analyze crash file.
Let’s enable app crash dump collection by copying following words into notepad, saving it as dump.reg and importing it:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\localdumps\WORD.EXE]
"DumpFolder"=hex(2):63,00,3a,00,5c,00,63,00,72,00,61,00,73,00,68,00,64,00,75,\
00,6d,00,70,00,73,00,00,00
"DumpCount"=dword:00000010
"DumpType"=dword:00000001
"CustomDumpFlags"=dword:00000000
Then, open Word to repro the issue. If crash issue appeared, please find the crash dump file under c:\.
To further help you, please upload this file into OneDrive and shared the link here.
Also, you can try to analyze dump by yourself if you would like to:
How to analyze app crash dump file:
http://blogs.technet.com/b/askperf/archive/2007/05/29/basic-debugging-of-an-application-crash.aspx

Dump: while opening the view

Hi Team,
I am getting dump, when i am trying to open the view either in display or change mode.
Can someone tell me what would be the root cause.
Thanks & Regards,
Sankar Gelivi

Hi,
In the view, did you used Grid Layout? Please implement the SAP Note 1868501 to fix this issue.
Hope this helps u,
Regards,
Kiran

Short dump while scheduling infopackage

Hi,
im getting short dump while scheduling infopackage for( 0cfm_init_positions )as it is giving dump like MESSAGE_TYPE_X runtime error in BI test system but in dev it's working fine if anybody knows how to resolve??.

hi
this is due to existence of TRFC-Packages for old failed requests in the source system.
so for this QM-Action in the request monitor change manually to red.
if you wont find the solution contact basis team.
or
use SE16. Look at RSSDLINIT table. Match up the LOGSYS with your OLTPSOURCE (for the infopackage that is causing the problem). Delete that line(s) Now you can open the infopackage. (be sure to delete the initialization) before you run the info pack again.)
Also you can check SAP Note : 852443
check this links
Short dump MESSAGE_TYPE_X while trying to open infopackage
DUMP IS COMMING WHILE CREATING INFOPACKAGE

Acrobat Reader 9 Crashes PC When Opening 2 Documents Simultaneously (2D Graphics Acceleration Relate

Hey all,
Weird issue. I noticed my Adobe Acrobat Reader 9 crashes when opening two PDF's simultaneously. The first one opens just fine. The second one, a new window opens, but there's only black inside the 2nd Reader window. It finally (after way too long) begins to show the document, and then I get a blue screen of death with a fault in nvlddmkm.sys, the nVidia display driver for my video card. It says it was unable to reset the display drivers, dumps the memory, and reboots. One interesting note is that if I close the "black" window before it blue screens, I can continue using the computer with no crash. It's only if I give it time to try to display.
I already found the temporary fix for this, which is disabling 2D Graphics Acceleration in the Acrobat Reader (Edit -> Preferences -> Page Setup). Fortunately I'm on a fast computer, so this doesn't affect performance much, but it still obviously isn't ideal, and I'd like to see the problem resolved.
I don't experience this problem with any other programs at the moment, so I'm thinking it's an issue with Adobe's product or possibly the nVidia drivers, but thought I should mention it and see if anyone has any other possible fixes where 2D Graphics Acceleration can remain enabled.
Thanks all!

I am having the exact same issue... it's so frustrating! Does anyone have a solution to this?
Running CS4 on a Core i7 workstation w/ Win 7 64-bit, latest BIOS and video card drivers (ATI Radeon 4890). Acrobat is version 9.3 with all updates. It freezes for 30 seconds just as described, every single time you launch it.

Dump when opening infopackage

Similar Messages

Maybe you are looking for