Add-On ST error in Prepare Upgrade from 46D to ECC 6.0

I have getting Error Add-On ST 2D, and undecided, I don't know what to do, I had installed Solution Manager for 46D and ST 2D, If anybody has this situation, how do I download the Add on
I will appreciate any help on this matter.
Thanks
Jagraj Dhillon

> Dear,
>
> I believe you have the addon component 'SAPKITL02D
> "SAP Solution Manager - Installation 4.6C (02D) "
> installed in 4.6C , is that right?
>
> Since the ST (Solution Manager) cannot be upgraded
> from current version
> to the latest using the R3 upgrade, You need to
> Deinstall the addon. (with import of SAPKITL029 in
> SAINT) Please reset prepare as described in the
> upgrade manual (SAPup reset prepare + empty DIR_PUT)
> and next import the request SAPKITL029 using SAINT
> which should take care of the de-installation of ST
> 02D.
>
> I hope this helps.
>
> Lucio Rodrigues
> SAP AGS
Hello, Lucio. I am in the same boat, only with R/3 version 4.6C, and ST 0.2C (SAPKITL02Y). Would the SAPKITL029 work for me as well, or is there another SAINT package designed to remove ST 0.2C?
SAP support has not been very helpful to this point. If you have an import which would help with uninstalling the addon, please email it to [email protected], or please let me know where to download it if it is available for download.
Mike McCrory - BMW Global Data Center America's
Message was edited by:
McCrory Michael

Similar Messages

Error in Prepare Upgrade from 46C to ERP 2005 - R3trans too old

I have seen a few threads on this issue, but I am still slightly puzzled.
The error message in Prepare ( initialisation - 02 ) is that the R3trans is too old, it needs to be at least 07/05/2007.
The version of R3trans in the put directory is a 46D one ( 6.05 ) and the date is previous to that mentioned, however the most recent version of the 46D that I can download is the 22/04/2007 and you will get the same error.
Ther error seems odd in that it would normally complain about the version rather than a date and it is happy about tp etc.
I could download a more recent version of R3trans, but that would be a 6.40 or 7.0 !
I have the FIX_ERP2005SR2.UPG in /usr/sap/put.
Has anybody tripped over this issue ? Cheers

The 46D R3trans was a bit of a red herring, however I do have a problem.
The 7.00 kernel goes into \usr\sap\put\exe etc and it is a 7.00 R3trans ( 6.14 ). When the initialisation phase is run ( 2 ), it complains that the R3trans is too old and it quotes 07/05/2007.
If I download the newest version of R3trans it fails with a connect problem. For some reason it goes off to /usr/sap/SID/SYS/exe/run to reference the dboraslib.dll, while the earlier version of the 7.0 R3trans references it within /usr/sap/put.
It could be something like Oracle Client environmental settings !
Anybody had this issue ?
Cheers
The R3trans was R3trans_119-20000961.SAR
ETW000 D:\usr\sap\put\exe\R3trans.exe version 6.14 (release 700 - 10.07.07 - 13:48:00).
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time   : 08.08.2007 - 17:45:45
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: D:\usr\sap\put\exe\R3trans.exe -d -w D:\usr\sap\put\log\DBCONNCHK.LOG
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc     ,00000] Wed Aug 08 17:45:45 2007                               0 0.000000
4 ETW000 [dev trc     ,00000] db_con_init called                                     0 0.000000
4 ETW000 [dev trc     ,00000] create_con (con_name=R/3)                              0 0.000000
4 ETW000 [dev trc     ,00000] Loading DB library 'dboraslib.dll' ...                 0 0.000000
4 ETW000 [dev trc     ,00000] load shared library (dboraslib.dll), hdl 0          5202 0.005202
4 ETW000 [dev trc     ,00000]      using "D:\usr\sap\DV2\sys\exe\run\dboraslib.dll"
4 ETW000                                                                              20 0.005222
4 ETW000 [dev trc     ,00000] Library 'dboraslib.dll' loaded                         8 0.005230
4 ETW000 [dev trc     ,00000] function DbSlExpFuns loaded from library dboraslib.dll
4 ETW000                                                                              14 0.005244
4 ETW000 [dbcon.c     ,00000] *** ERROR => Version mismatch between kernel (700.08) and DBSL shared library (46D.00)
4 ETW000                                                                              32 0.005276
2EETW169 no connect possible: "connect failed with DBLI_RC_LOAD_LIB_FAILED."

Error in upgrade from 46c to ecc 6.0

hi experts,
we are facing an error at the time of upgrade from 46c to ecc 6.0 in the phase JOB_RSUPGAIMEXE.
did anyone face this error anytime during upgrade on windows plotform?
Please let us know your comments..
regards
raghu

Hello,
Can you please look in the /put/log directory and copy the error from the appropriate log file. You should find a log file with a name similar the to upgrade phase that is causing the error.
Thanks
N.P.C

ITS upgrade from 46D to 620

Hi
I am about to do ITS upgrade from 46D to 620. Could any one please tell me the step by step procedure to do this activity. Whether I need to uninstall 46D and do fresh installation of 620 or is it possible to do an upgrade to 620 without uninstalling 46D?
Please guide me.
Regards,
Vinodh.

Hi Vinodh
I Think the best way to go is Install ITS 6.20 and run both ITS's in parallel until the new ITS is tested, then remove the old ITS.
Best regards
Juan!

Error in Prepare upgrading ECC6 to EHP4

I'm receiving this error message during prepare phase while upgrading from ECC6 to EHP4 using the EHP Installer. Please help with this. Thanks in advance.
ERROR: Unable to generate addon queue due to missing addons or support packages.
Missing Support Package(s):
(ECC-DIMP)
Kha

Sunny,
The support packages exist in the download and EPS/IN directories. There are additional error messages where it says "The Enhancement Package Stack does not fit to the current system."
ERROR: Unable to generate addon queue due to missing addons or support packages.
Missing Support Package(s):
(ECC-DIMP)
The Enhancement Package Stack does not fit to the current system.
Thanks,
Kha

Error after SPS upgrade from SP10 to SP12

Hi Friends,
Recently we have done SOLMAN 7.1 sp upgrade from sp10 to sp12.
Now I want to perform configuration activities in SOLMAN_SETUP.
But when I am trying to do SYSTEM PREPARATION, I am facing error in first step(Maintain Users).
"Error: Number of elements in the collection of node COMPONENT CONTROLLER.1.NAMESPACES violates the carnality".
Kindly suggest me how to clear this above error and proceed further. Further please let me know as a SOLUTION MANAGER consultant what are the steps I need to perform post SP upgrade. I am not BASIS guy. So please let me know what are the activities which need to be performed by BASIS guy and SOLMAN guy
Please find the attached screen shot for the error screen.
Thanks & Regards,
Solman Starter

Go the transaction STMS, if a window appears when you start the transaction that's mean it is not configured.
Only in this case :
1.     Logon on to client 000 with DDIC.
2.     Execute transaction SE06
3.     Select the Database Copy or migration option
4.     Press the Post-installation Processing button.
5.     When prompted Do you want to re-install the CTS? Press the Yes button
6.     When prompted for the Source System of Database Copy?, make sure that the <SID> of the production system is selected. Press the checkmark button to continue.
7.     When prompted Change originals from PRD to QUA?, press the Yes button
8.     When prompted Delete TMS Configuration?, press the Yes button
9.     When prompted Delete old TMS configuration?, press the Yes button
10.     When prompted Delete Old Versions of transport routes?, press the No button
Concerning the initial problem, i found this note :
http://service.sap.com/sap/support/notes/2025884

Error 1015 when upgrading from 3.0 to 3.0.1

Hello,
I recently purchased an iPhone and my first time connecting it to iTunes it asked to upgrade from 3.0 to 3.0.1, which I assumed was fairly standard so I let it go.
However, it made it about 75% through the progress bar on the iPhone display and to the "restoring iPhone firmware" stage in iTunes, then it gave the 1015 error. I have tried it on several computers since then and it happens every time regardless of which computer/OS I use.
After this every time I turn the iphone on, connect to the computer or not, it displays a USB with an arrow to the iTunes icon, and I have no control. Basically nothing on it works anymore.
When I searched on google I found a lot of hits for people trying to downgrade/jailbreak, neither of which I was trying to do, I was simply upgrading based on iTunes request.
Thanks for any help, right now my iPhone is useless to me, and it's really frustrating.
Thanks,
Boyd

I just got this link off Apple Support. It is a KB article that describes issues with that particular error code. Try and see if that solves your problem.
http://support.apple.com/kb/TS1275

Error during MaxDB upgrade from 7.3.00.42 to 7.5.00.32

Hello all,
I am attempting to upgrade from MaxDB 7.3.00.42 to 7.5.00.32, as part of a migration from HP-UX 11.11 to Windows Server 2003. The MaxDB database supports a Content Server 6.30 application, and from what I have found so far, I need to upgrade/patch to 7.5.00.51 on the HP-UX server, before I can migrate using the loadercli (as per note 962019).
While performing the upgrade to 7.5.00.32 (following the steps in the Upgrade Guide to MaxDB 7.5), I receive the following error.
chperm 660 sdb:sdba /sapdb/data/config/SDB.mmm
user sdb can access /sapdb/data/config/SDB.mmm
remove /sapdb/data/wrk/dbmsrv.prt
remove /sapdb/data/wrk/SDB.knl
remove /sapdb/data/wrk/SDB.mdf
permissions for databases as of version 7.5.00 are used on your system
database owner is sdb
administrators group is sdba
owner of SDB is sdb (sdba sdba)
user_logon failed
Obviously there is a permissions problem of some kind, but I have not been able to pinpoint where. I allowed the DDUPDATE.SH script to create the user SDB, and it appears to have been created successfully and was used during the earlier steps of the upgrade script.
While working with SAP support I confirmed that I could connect to the database using the SDB user and I also executed the sdbverify, which completed successfully. As per the upgrade guide, I am logged in to HP-UX as root when running the upgrade (and when I ran sdbverify).
If anyone has suggestions on the cause of this error, I would greatly appreciate any assistance.
Best Regards,
Rusty Robbins

Isn't that how it always goes...
I have been fighting this for 4-5 days, and had replied back and forth with support, with no luck on a resolution. But of course just as soon as I post my question here, support comes back with the answer!. I guess that just goes to show how good the SDN site is! ;p
Anyway, the answer to my problem was related to the group permissions on this HP-UX server. The ddupdate script did create the SDB user and set the primary group as SDBA, which normally would give the SDB user all rights for that group. However, in this case the error continued to occur, until I explicitly added the user SDB to group SDBA (at the request of SAP support). This upgrade step did finish successfully, and I am now continuing on with the other steps to migrate to Windows. Hopefully the rest of the steps will go smoother...
Regards,
Rusty Robbins

WCF-SAP Adapter throwing errors after SAP Upgrade from ECC 5 to ECC6 Release 640 to 700

Hello Everyone,
We were able to communicate(Send and Receive Idoc's) to SAP via WCF-SAP Adapter in BizTalk 2010.
SAP Servers were upgraded to ECC5 to ECC 6 and we started facing below issue communicating on send and receive both.
I am aware that there is a hotfix available but that is more on the Receive Side from SAP. Nevertheless I installed the hotfix but issue still persists. Any suggestions will be highly appreciated.
Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: E2EDP01006GRP   IDOCTYP: ORDERS05
Release: 700    CIMTYP: . Ensure that your message xml validates against the operation schema.
Server stack trace:
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.
Thanks,
Vikingss

I am aware that there is a hotfix available but that is more on the Receive Side from SAP. Nevertheless I installed the hotfix but issue still persists. Any suggestions will be highly appreciated.
For this issue, you can contact Microsoft support directly(http://support.microsoft.com).

Short dump in MIGO and VL02N when upgrading from 46C to ECC 6.0

Hello,
We are doing an upgrade from R/3 46C to ECC 6.0 and we face a shortdump in trx MIGO (upon saving the document).
DBIF_RSQL_INVALID_REQUEST
a BKPF_INSERT in program SAPLF005
The same shortdump happens when doing a Goods Issue on the SD side.
Looking at the program, this is not modyfied so I guess it is a standard SAP error.
OSS however, up to know did not respond to my message and there does not seem to be a SAP Note on this issue!
Anyone had this problem before. How did they solve it.
Thanks for any reply,
Aart

Posted in another forum

Re:Upgrade from 4.6c - Ecc 6.0

Hello SAP Friends,
I am involved in a project of Technical Upgrade from 4.6 to ECC 6.0.I am a functional Consultant and with the Help of ABAPers i have to complete this Technical Upgrade. We have identified some Standard objects through SPAU/SPDD which need to be REMEDIATED.
Can someone please explain as to what is the detailed process and the Steps Involved for the Remediation process like how to compare the codes and testing and all.
Thanks in advance,
Julie Mehta

What you need to do is to make the programs that you've, UNICODE compatibel.
This will solve lots of errors in your SPAU.
greetings
Tom

Upgrading from 46C to ECC 7.0

Guys,
My company is going to upgrade R/3 46C to ECC 7.0 later this year. From the development (ABAP programs, any ABAP objects) standpoint, any suggestions on preparation, or what can be done in our current 46C environment to ensure a smooth transition from 46C to ECC (unicode, obsolete ABAP syntax, etc)? Also any idea and recommendation on planning the upgrade, as well as things to watch out for are welcome.
Thanks,
Yan.

First ECC 7.0 does not exist, so you will be upgrading to ECC 6.0. And yes, you can start by doing a start for any calls to WS_UPLOAD and WS_DOWNLOAD. You will need to change these calls to call the GUI_UPLOAD or GUI_DOWLOAD function modules.
Other syntax issues will need to be handled after the upgrade, like using the ECODING extension on all OPEN DATASET statements.
Regards,
Rich Heilman

Error in invoice posting from CRM to ECC

Dear Guru's ,
when we release the billing document from CRM to ECC , system throughs error messages and while we checking the confimation the below green message is appering .
--> Object link not known in CO
Whatever the master data we maintained in the order and confimation is perfect .Kindly advise why this green error is coming???
Regards ,
Pakalapati

solved by my self

Upgrade from 46C to ECC 6

Hello:
We are planning to begin technical upgrade in SAP, from 46C to ECC 6.0.
I have the next landscape:
-Current SAP (CS): SAP 46C with Oracle 8.1.7 and Solaris 8
-New Server (NS): Without SAP, 40% more of capacity, with Oracle 10.2 and Solaris 10 already installed.
We want to install SAP ECC 6.0 in NS and get the data from CS.
Which is the best and easy way to do this? SAP manuals are quite generic. I have two ideas but I would like your comments:
1st way
1. Homogeneous copy of CS
2. I install ECC 6.0 in NS with the option to import data generated in 1. (is this possible??)
3. Finish installation and aditional configurations. I begin to test.
2nd way
1. Homogeneous copy of CS
2. I install 4.6C in NS with the option to import data generated in step 1. (Not sure if 4.6C will accept Solaris 10 and Oracle 10.2).
3. I suppose I don't need to reconfigure after installation and import.
4. I do necessary tests. At this point I would have 46C on the new versions of Solaris and Oracle.
5. I begin the SAP upgrade to ECC 6.0 in NS
6. .... The remaining processes indicated by SAP
Thanks for your attention.

> -Current SAP (CS): SAP 46C with Oracle 8.1.7 and Solaris 8
> -New Server (NS): Without SAP, 40% more of capacity, with Oracle 10.2 and Solaris 10 already installed.
The database software is usually installed during the run of sapinst/R3setup, not before. You may run into problems if you pre-install Oracle (environment, necessary database options not set etc.)
The easiest way would be do to a system copy.
I would then
- install the latest Oracle instantclient
- install the latest kernel 46D_EX2 kernel
Markus

Recommandations for upgrading from 46C to ECC 6.0

Hello
Our SAP system landscape is actually in 46c and is only composed of 3 servers with almost 40 users declared (25 actives) on production system. Modules FI/CO HR MM are actually implemented.
We plan to upgrade the system to ECC 6.0 between March and August of 2009. The evaluation of the upgrade should begin as soon as possible. Do you think it can be possible to realise the upgrade alone, without the help and expertise of a SAP consultant? Do you think the delay for preparing the upgrade is suffisant?
Thank you.

As suggested earlier, refer to Master and technological guides for reference.
also for information, the upgrade can fall under any below scenarios.
1. Strategic Business Improvement
Focus on functionality extension and improvement
Enablement of new and optimized business processes and scenarios based on new ERP core functionality
2. Functional/Retrofit Upgrade
New functionality to be implemented as part of the upgrade, modification clearing
Focus on reduction of system complexity
3. Technical Upgrade
Focus on pure technology upgrade
Retain functionality used
Review Usage of custom developments
As per the requirement. knowledge and experience the decision can be made.

Add-On ST error in Prepare Upgrade from 46D to ECC 6.0

Similar Messages

Maybe you are looking for