RE:[sap-basis] TYPELOAD_NEW_VERSION & LOAD_PROGRAM_CLASS_MISMATCH dumps !!
Posted by
Admin at
|
Share this post:
|
|
0 Comments
 | Posted by D. Caddick (SAP NetWeaver/BASIS Consultant) on Mar 4 at 3:39 AM |  Mark as helpful |
Hi Mittun,
Have you consulted with the SAP Globalization Group you can send a e-mail to:
globalization AT sap DOT com.
Regards
---------------Original Message---------------
From: mittun_hazra
Sent: Thursday, March 04, 2010 1:14 AM
Subject: TYPELOAD_NEW_VERSION & LOAD_PROGRAM_CLASS_MISMATCH dumps !!
> Hello Friends,
> We are process of Unicode Conversion of one R3 4.7 EX110 System. After the import the system is up all wp are running. But we were geting an error: "Syntax error in program SAPFSPOR" while trying to open the SAP GUI. We were not able to see the logon screen. We finally realized SAPFSPOR came as Non-Unicode to the new Unicode System. We raised an OSS message & they suggested me to put a 'X' on the field UCCHECK on the table trdir for the program SAPFSPOR from database level. I did that & we were able to login. But now are getting dumps on almost every transaction, The dumps are mostly 2 types:
>
> 1> Runtime errors TYPELOAD_NEW_VERSION
> Data type "TADIR" was found in a newer version than required.
>
>
>
> Error analysis
>
>
> The data type "TADIR" was reloaded from the database while the program
> was running.
> However, the system found a version of the type that was newer than
> the one required.
>
>
>
> How to correct the error
>
>
> Try to restart the program.
> ********************************
>
> 2> Runtime errors LOAD_PROGRAM_CLASS_MISMATCH
>
> The class interface was changed at runtime.
>
> Error analysis
>
>
> Section "PUBLIC" of the interface of class "CL_GUI_ALV_GRID"
> was changed while the program was running. Consequently, inconsistencies
> occurred at runtime.
> The program "SAPLSVAR" uses the interface version 20100211182322.
> The program "SAPLBTCH" uses the interface version 20090329011522.
> The internal session was started at 20100304114154.
>
>
> How to correct the error
>
>
> Try to restart the program.
> *******************************
>
> We tried to SGEN but it is also giving the same error.
>
> SAP is taking too much time to reply. Do you have any suggestion to overcome this??
>
> Thanks,
> Mittun
__.____._ Have you consulted with the SAP Globalization Group you can send a e-mail to:
globalization AT sap DOT com.
Regards
---------------Original Message---------------
From: mittun_hazra
Sent: Thursday, March 04, 2010 1:14 AM
Subject: TYPELOAD_NEW_VERSION & LOAD_PROGRAM_CLASS_MISMATCH dumps !!
> Hello Friends,
> We are process of Unicode Conversion of one R3 4.7 EX110 System. After the import the system is up all wp are running. But we were geting an error: "Syntax error in program SAPFSPOR" while trying to open the SAP GUI. We were not able to see the logon screen. We finally realized SAPFSPOR came as Non-Unicode to the new Unicode System. We raised an OSS message & they suggested me to put a 'X' on the field UCCHECK on the table trdir for the program SAPFSPOR from database level. I did that & we were able to login. But now are getting dumps on almost every transaction, The dumps are mostly 2 types:
>
> 1> Runtime errors TYPELOAD_NEW_VERSION
> Data type "TADIR" was found in a newer version than required.
>
>
>
> Error analysis
>
>
> The data type "TADIR" was reloaded from the database while the program
> was running.
> However, the system found a version of the type that was newer than
> the one required.
>
>
>
> How to correct the error
>
>
> Try to restart the program.
> ********************************
>
> 2> Runtime errors LOAD_PROGRAM_CLASS_MISMATCH
>
> The class interface was changed at runtime.
>
> Error analysis
>
>
> Section "PUBLIC" of the interface of class "CL_GUI_ALV_GRID"
> was changed while the program was running. Consequently, inconsistencies
> occurred at runtime.
> The program "SAPLSVAR" uses the interface version 20100211182322.
> The program "SAPLBTCH" uses the interface version 20090329011522.
> The internal session was started at 20100304114154.
>
>
> How to correct the error
>
>
> Try to restart the program.
> *******************************
>
> We tried to SGEN but it is also giving the same error.
>
> SAP is taking too much time to reply. Do you have any suggestion to overcome this??
>
> Thanks,
> Mittun
Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
D. CaddickSAP Basis Top Contributor
Contributed the most posts in a group for 3 consecutive months to earn a Gold Achievement
In the Spotlight
Earn Recognition for Your Contributions at Toolbox for IT. Gain Points for Community Achievements
View this thread online
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
