on 02-23-2007 11:48 PM
I just successfully installed 4.6c on new 64-bit hardware for starting our upgrade to mySAP ERP 2005. After the install, I requested a new license key to work with the new hardware key, and the new license is showing up as useable when running saplicense -show. However, when trying to log on using SAPGUI, the "license is expired" error prevents any logins.
are you using the 46D_EXT kernel ? Is it the latest available kernel from SAPNET?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
well, this may happen because there was not 46D_EXT Kernel CD for 46 and SQLServer.
You may unpack the latest SAPEXE.CAR from service.sap.com/swdc
Support Packages and Patches- SAP Application Components- SAP R/3" SAP R/3 4.6C- Entry by Component- SAP Kernel 46D EXT 32-Bit- Windows Server IA32- 32 Bit- #database independend
and SAPEXEDB.SAR from the MS-SQLServer directory.
unpack them into \usr\sap\<sid>\sys\exe\run directory after stopping all services.
regards
Peter
I may have bad news for you:
<b>Mainstream maintenance for SAP R/3 4.6C ended on December 31, 2006.
From January 01, 2007 to December 31, 2009, SAP offers extended maintenance for this release. As of January 01, 2007, new SAP R/3 Support Packages and SAP HR Support Packages (Legal Change Packages, LCPs) for SAP 4.6C are only available as part of extended maintenance.
Please note:
If you have not ordered extended maintenance, all Support Packages provided to the end of mainstream maintenance are available in the Software Download Center Archive. </b>
So, in order to get access to these patches, you must pay for additional maintenance fees. Contact your SAP representative... or use the following link ot order Extended maintenance:
We are currently under extended contract maintenance.
We are in the upgrade process now to get to mySAP ERP 2005.
Getting our system up and running on the new 64-bit hardware is part of the process for the upgrade. We install our current system on the new hardware and then upgrade from that point. Utilizing the new hardware is the only way we can have dry-runs before the actual upgrade of our landscape, so being able to install the 4.6D kernel on 64-bit hardware is a pretty critical event.
open a SAP message ( http://service.sap.com/message ) under component XX-SER-SWFL and ask the mto send you the 46D_EXT 64-bit kernel for Windows 2003 ans MS-SQL
have you tried to download a CD-kit?
Joey,
can you please try the path mentioned in note <a href="http://service.sap.com/sap/support/notes/52505">52505</a>
close to the bottom of the note you will find download paths and addtional information on how to get needed components for upgrades.
sorry - we as SAP employes have a different (not contract related) view to the single components on the service market place. therefore it is not possible for me to test your view of SMP.
regards
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
login with SAP* and use tcode SLIC or SLICENSE
chances are that your hardware key is not valid
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You would think if it was a license issue, I would be able to log in using SAP* or DDIC? But the gui gives the "License is expired" message even when trying to login using these accounts in client 000.
I am thinking the license error message is bogus and there is something else causing this.
The WP logs are showing the following errors:
M *** ERROR => OS release Windows NT 5.2 3790 Service Pack 1 8x Intel 801586 (Mod 65 Step 2) is not supported with this kernel (46D) [thxxsick.c 288]
A *** ERROR => OS release Windows NT 5.2 3790 Service Pack 1 8x Intel 801586 (Mod 65 Step 2) is not supported with this kernel (46D) [sapicc.c 729]
M ***LOG R68=> ThIRollBack, roll back () [thxxhead.c 10125]
Is there a different 4.6D kernel for the AMD x64?
I have it figured out.
I had to use a TSQL backdoor approach to reset the SAP* user (I am sure everybody here knows how to do this, but I won't expound) and was able to log in and run SLICENSE. For some reason, SAP was not recognizing the SAP* user as SAP* before, but as a regular dialogue user, so it was not allowing it in with an incorrect license key. After finally getting in, I was able to resolve the license issue and now I can continue with the upgrade to ECC 6.0
Thanks for everyone's input/help.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.