Shortdump DYNPRO_ITAB_ERROR after systemcopy

I receive this shortdump when I try to logon after a homogeneous system copy (DB-independent, using sapinst).
This is an ECC 6.0 system and the solution for me was to upgrade Kernel.
Fortunately I made a copy of \usr\sap\SID\sys\exe\run-folder before I imported the system copy at my target system. I could use this copy as my new kernel after finishing the import.
Kernel Patchno 144 is installed during system copy import (db-independent - SR3).

Here is some more details from my shortdump:
Runtime Errors DYNPRO_ITAB_ERROR
Date and Time 2009-07-16 08:18:21

Short text
Error in internal table in screen

What happened?
The current screen processing action was terminated since a situation
occurred where the application could not continue.
This is probably due to an error in the ABAP program or in the current
screen.

Error analysis
The program "SAPMSYST" has terminated.

The following error occurred (short text of cause of error):
"FX099: Wrong fieldtype for CURSOR. Has to be binary/hex type."

The following elements are affected:
Screen name.............. "SAPMSYST"
Screen number............ 0020

This error is connected to the processing of an internal table with the
field or variable "TC_IUSRACL-CURRENT_LINE", and was triggered within in the program.

Trigger Location of Runtime Error
Program SAPMSYST
Include SAPMSYST
Row 1,076
Module type (MODULE PBO)
Module Name D020_LOGON_WITH_SNC

Name or password is incorrect (repeat logon)

You get this message "Name or password is incorrect (repeat logon)" when doing an authorization test for RFC on to ERP2005 or higher. You are using a SAPgui controls that cannot handle case-sensitive passwords. The SAPgui controls convert the password into upper_case.
I experienced this problem for my RFC from BW (BIWREMOTE) into ERP2005.
Solution: Change the password for this user in the target system (the system you try to reach) to only upper-case. Another solution is to install the absolut latest of SAPGui. I have 7.10, but still got this problem....

OB52 - Not modifiable in QA system

You have the possibility to do changes when you access OB52 in Production system.
But when you access transaction OB52 in the QA system you receive this message:
Client 100 has status 'not modifiable'

Reason: In SCC4 the Client Role for this client in QA system is set to "Test". If you change it into "Production" you will have possibility to do changes in OB52 (S_ALR_87003642). Remember to change it back when you are finished.

Another solution is described in note 214132. But this solution was no good for me.

Instance shuts down - paging file too small

Our hosting-partner had some trouble with some SCSI-drivers who lead to disconnection from some of the harddrives.
Our db-disk and sap-disk was harmed.

When the problem was fixed we got problems starting one of our two SAP-instances.

At first both instances went green with the text:
"Running, Message Server connection ok"
But this status changed after some minutes:
"Running but not connected to Message Server"
And then the status changed into:
"Stopped"

I did not find any answers in the log-files (\usr\sap\sid\DVEBM0000\work).
The answer was in the event-viewer.





















[CreateOsShm] CreateFileMapping(6,450000 KB) failed with Err=1455 ERROR_COMMITMENT_LIMIT: The paging file is too small for this operation to complete.

Solution was to set the paging file again.

Shortdump DBIF_REPO_SQL_ERROR

Text in shortdump ST22:
Short text: SQL error 1654 occurred when accessing program
How to correct the error: Database error text........: "ORA-01654: unable to extend index SAPR3.D010TAB~0 by 128 in tablespace PSAPES700I"

This is basic understanding of an oracle-database. Tablespace is full. In this case it's PSAPES700I. Extend with brtools:
http://help.sap.com/saphelp_nw70/helpdata/en/1b/d20f6fe45a9e43b1856ea1b52c9612/content.htm
If you are using the old sap-tool "sapdba" insted of BRTOOLS you can email me (harald.v@epost.no) and I'll help you with the tablespace-extention.

(Photo: http://www.made-in-china.com/)

Shortdump CALL_FUNCTION_NOT_FOUND

The short text in this shortdump is:
Function module "ANLBZW_CREATE_TRANSFER" not found.

The solution for this was in my case note 1276128.
You have to maintain view TRWPR and delete an entry containing function module ANLBZW_CREATE_TRANSFER.
Attached to note 1095424 you will find a script for this action.

CANNOT_CREATE_COFILE during SPAM queue

This is usually solved by:
1. Check authorization for cofiles-folder (sidadm and servicesidadm)
2. Download the affected support package again. It can be corrupted
3. Any full tablespaces?

If you look into SLOG and find this error message:
WARNING: \\\sapmnt\trans\tmp\SAPKKB70014.ARP is already in use (10), I'm waiting 4 sec (20090515192357). My name: pid 7280 on (APServiceARP)

In my case the problem was corrupt support package. I downloaded the package, deleted the cofile and the datafile. Remember to also delete the pending transport request that you will find int the trans\tmp-folder.