Starting Issue??

[Former Member]

Hello Exports,

I have problem during the login to SAP server.

I have recently perform system copy off my production server.

This is homogeneous copy i.e. I haven`t changed any Database or O.S. Level.

I have done system copy by Export Import method.

My Source System Details are,

ECC Release 6.0 SR3

Database: DB2 9.1.007

O.S. Windows Server 2003.

Target System is same as Source.

I have successfully completed System Copy without any error. But when I am try to login my new Server

It gives Short Dump DYNPRO_ITAB_ERROR

Follow is Detail Dump analysis

Runtime Errors         DYNPRO_ITAB_ERROR

Date and Time          29.11.2012 18:43:02

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.

What can you do?

     Note which actions and input led to the error.

     For further help in handling the problem, contact your SAP administrator.

     You can use the ABAP dump analysis transaction ST22 to view and manage

     termination messages, in particular for long term reference.

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.

How to correct the error

      If the error occures in a non-modified SAP program, you may be able to

    find an interim solution in an SAP Note.

    If you have access to SAP Notes, carry out a search with the following

    keywords:

    "DYNPRO_ITAB_ERROR" " "

    "SAPMSYST" or "SAPMSYST"

    "D020_LOGON_WITH_SNC"

      If you cannot solve the problem yourself and want to send an error

    notification to SAP, include the following information:

    1. The description of the current problem (short dump)

       To save the description, choose "System->List->Save->Local File

    (Unconverted)".

    2. Corresponding system log

       Display the system log by calling transaction SM21.

       Restrict the time interval to 10 minutes before and five minutes

    after the short dump. Then choose "System->List->Save->Local File

    (Unconverted)".

    3. If the problem occurs in a problem of your own or a modified SAP

    program: The source code of the program

       In the editor, choose "Utilities->More

    Utilities->Upload/Download->Download".

    4. Details about the conditions under which the error occurred or which

    actions and input led to the error.

System environment

    SAP-Release 700

    Application server... "prdsrv"

    Network address...... "192.168.100.111"

    Operating system..... "Windows NT"

    Release.............. "5.2"

    Hardware type........ "2x AMD64 Level"

    Character length.... 16 Bits

    Pointer length....... 64 Bits

    Work process number.. 0

    Shortdump setting.... "full"

    Database server... "prdsrv"

    Database type..... "DB6"

    Database name..... "PRD"

    Database user ID.. "SAPPRD"

    Terminal................. " "

    Char.set.... "C"

    SAP kernel....... 700

    created (date)... "Jan 24 2008 01:15:15"

    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"

    Database version. "DB6_81 "

    Patch level. 144

    Patch text.. " "

    Database............. "DB6 08.02.*, DB6 09.*"

    SAP database version. 700

    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

Memory consumption

Roll.... 16192

EM...... 4189840

Heap.... 0

Page.... 0

MM Used. 1038640

MM Free. 3148576

Client.............. 000

User................ " "

Language key........ "E"

Transaction......... "SESSION_MANAGER "

Transactions ID..... "7F263AE2D791F17592D6B8AC6F45C59B"

Program............. "SAPMSYST"

Screen.............. "SAPMSYST 0020"

Screen line......... 21

Active Calls in SAP Kernel

Lines of C Stack in Kernel (Structure Differs on Each Platform)

SAP (R) - R/3(TM) Callstack, Version 1.0

Copyright (C) SAP AG. All rights reserved.

Callstack without Exception:

App       : disp+work.EXE (pid=1532)

When      : 11/29/2012 18:43:1.265

Threads   : 2

Computer Name       : PRDSRV

User Name           : SAPServicePRD

Number of Processors: 2

Processor Type: EM64T Family 6 Model 15 Stepping 13

Windows Version     : 5.2 Current Build: 3790

State Dump for Thread Id aa0

FramePtr         ReturnAd         Param#1          Function Name

0000000007d8bc70 0000000077d704bf 0000000031e11870 ntdll!ZwWaitForSingleObject

0000000007d8bd10 000000000172a631 000000000000044c kernel32!WaitForSingleObjectEx

0000000007d8bf60 00000000006134a5 0000000000000001 disp+work!NTDebugProcess [ntstcdbg.c (501)]

0000000007d8bf90 0000000000afeb9c 0000000000000001 disp+work!CTrcStack [dptstack.c (182)]

0000000007d8bfe0 0000000000b03dc0 0000000000000001 disp+work!rabax_CStackSave [abrabax.c (7091)]

0000000007d8c9c0 000000000066115f 000000000288f6f0 disp+work!ab_rabax [abrabax.c (1231)]

0000000007d8ca50 00000000006b32fc 000007fe5720d3ee disp+work!dyRabaxA [dybas.c (550)]

0000000007d8cab0 00000000006bbc1a 000007fe5720df2c disp+work!dyLoopItbCursor [dyloopitb.c (1061)]

0000000007d8cb30 0000000000671c8d 0000000000000004 disp+work!dynplbeg [dyloopstp.c (129)]

0000000007d8ccb0 0000000000675e7d 000007fe57208e20 disp+work!dynpmcal [dymainstp.c (2284)]

0000000007d8cd40 000000000067587a 0000000000000000 disp+work!dynppbo0 [dymainstp.c (543)]

0000000007d8cdf0 00000000006341d5 0000000000000000 disp+work!dynprctl [dymainstp.c (360)]

0000000007d8fc30 00000000004d868d 0000000000000001 disp+work!dynpen00 [dymain.c (1629)]

0000000007d8feb0 000000000042d706 0000000007e1bb50 disp+work!TskhLoop [thxxhead.c (4525)]

0000000007d8fee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1122)]

0000000007d8ff10 00000000019d3301 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]

0000000007d8ff70 0000000077d5964c 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]

0000000007d8ffa0 0000000000000000 00000000019d3190 kernel32!BaseProcessStart

State Dump for Thread Id 3bc

FramePtr         ReturnAd         Param#1          Function Name

000000000ee6fe40 0000000077d5f691 0000000007ddb1a0 ntdll!NtFsControlFile

000000000ee6feb0 00000000018b954f 0000000000000000 kernel32!ConnectNamedPipe

000000000ee6ff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]

000000000ee6ff70 0000000077d6b6da 0000000077d6b6a0 msvcrt!endthreadex

000000000ee6ffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart

Please help me to solve this.

Your advice is most appreciable.

[Former Member · Accepted solution]

Hello,

please have a look at note 1287210.

The important lines are these two in your case:

If the issue occurs, all servers of the system should be patched to a SAP kernel with at least the patchlevel of the source system.
As a workaround, the table DYNPLOAD can be emptied by database means. It contains the dynpro loads which are created on demand if not already there.

I guess this will help a lot.

Kind regards,

Jann