Uninstall dialog instance

Hi gurus,
Can anyone tell me is it possible to just uninstall a dialog instance in the MSCS node?
regards
Chew Lin

Hi,
Not supported by SAP, not recommended by SAP.
But I did it without problem at home on my test drive
If you have enough experience you can try, if not work you can reinstall it
1. Shut down SAP sytem
2. addapt all profiles start form DEFAULT then START and also instance Profile
3. check /etc/services and add new entries
e.g. sapdp 3200/tcp
new
sapdp 3201/tcp
you can leave the old one , not need to delete them
4. rename all profiles Start and stop
stopsap_<HOST>_00 to stopsap_<HOST>_01
5. adapt enviroment for your user sidadm
corn shell, bourn shell,
6. if you manage to start your system then
RFC - sm59, rz10 - import new profile, SPAD, job managment SM36 and Sm37
Of course I miss something, but it up to you
For you better knowledge you can try it, it will learn you how system works
or simple ask for consulting support from SAP, it will cost just money, nothing else.
Best regards,
Peter Nechala

Similar Messages

How to Uninstall Dialog Instance in a Cluster Environment

Hello Guys,
I have installed my central server and one dialog instance on a windows cluster. But when i am trying to install a Dialog instance on a server I have given Node A profile directory instead of Global Profile path.
Now I am trying to uninstall my dialog instance on windows server I am not able to now. My installation also stuck and thrown a error in between. I would like to uninstall and reinstall DI instance on my 2003 windows server. Can some one help me how to do that ?
I am waiting for your help
Regards,
Sankar.G
BASIS CONSULTANT

Hi ,
Thanks my problem solved already..
Regards,
Sankar.G

How to Uninstall Java Dialog Instance

Does anyone know how to uninstall a Java Dialog instance?
The install instructions, 'SAP Web Application Server 6.40 SR1 Java on Windows: MS SQL Server' suggest that I should go to the control panel and select the add/remove program and then find the instance and remove it. However, the instance does not appear in the list.
Note: I have the ABAP stack (DEV) and the java stack (JDV) installed on the same box. But, the java stack is not an add-in. The ABAP stack instance does appear in the add/remove program list.

ok Doug,
i've a workaround for that.
Go to registry editor.IF YOU Find the Service corresponding to J03(SAP<SID>_03). Delete it. (if you want to be fail safe, export that contents to a file using FILE --> EXPORT and then delete it. you may import it later if you want). and RESTART the PC.
this process will ensure that there is no instance according to your system (coz no registry entry is found). it is as good as removed. but the files that were created during the instance installation will remain in your hard drive.
IN CASE you need this instance later or this workaround gives you any trouble, just import the registry contents file which you have exported earlier and RESTART THE PC.
it is as good as it was!!!
this is an easy work around but slightly risky as u are fiddling with your SYSTEM REGISTRY ENTRIES.
Regards
Arun.
PS: Remove the corresponding entry in the WINDOWS SERVICES file. otherwise, it will give PORT IN USE during later installation with instance number 03.
Message was edited by: Arunkumar

Uninstall J2ee Dialog instance on UNIX environment

HI Everyone,
I am trying to uninstall J2ee Engingine Dialog instance. I saw the procedure on the install document and it talks about deleting the files manually and also i have this not 871523 which says removing dialog instance from database after uninstallation.
I am searching for unistall tool. uninstsap script in Unix. Can someone guide me where i can find it. I am using Was 640 sp 12. Thanks for your help in advance.
Regards
Harish

You should have an Unix user for each version Why do you mean that?
You can have all oracle home with the same user.
$ id -Gn
dba ...
$ export ORACLE_HOME=/u01/app/oracle/product/7.3.4.0
$ export ORACLE_SID=DB1
$ svrmgrl
connect internal
startup$ export ORACLE_HOME=/u01/app/oracle/product/8-9-10
$ export ORACLE_SID=DB2
$ sqlplus "/ as sysdba"
startup$

EHP5 - Uninstall all dialog instance before the downtime begins

Dear Friends
I am working on EHP5 Upgrade on PRD Server HA Environment, the Node B is also the Application Server.
What does means that "Before the downtime [page 82] begins, you uninstall all dialog instances, stop SAP Management Console (MMC) and Software Deployment Manager (SDM), stop jcmon and other standalone monitoring tools
Do i need to uninstall application server from the Node B ? or need to update the SAP Kernel and IGS manually ?
Regards
Anwer Waseem

Hi,
You need not to uninstall application server. But if your kernel directory of application server is different then please make sure that you update kernel and IGS as well.
Thanks
Sunny

Installing 620 SAP_BASIS Dialog Instance with 6.40 Installation Master CD

Greetings,
At present we have a SAP R/3 Enterprise 47x200 which is dsitributed across two (windows 2003) clustered servers, one for the Central Instance and other for the Database (Oracle 9.2.0.5).
Now and due to perfomance issues on the Central Instance we'd lke to add a Dialog Instance and here is where the doubts come up.
Our SAP_BASIS version is 620 (System -> Status) whereas our SAP Kernel level is 640_REL (SM51).
We have the original 6.20 Kernel CD but we don't have any valid SAP Installation Master CD (originally we made an upgrade from a 4.6B version) so I downloaded from service.sap.com/support the 51033746_13.ZIP (Installation_Master_6.20_6.40_06_08) file (I didn't found any other file better that this one).
The first problem is that when I start sapinst.exe it ask (CD Browser Dialog) for a SAP 6.40 Kernel CD and not the 6.20 Kernel CD I already have. I have found a workaround editing LABEL.ASC file but I think it isn't a good practice.
If I download the Kernel 6.40 from service.sap.com 51030763_1.ZIP (DVD_NW04_SR1_6.40_SAP_Kernel_Oracle) the Sapinst application works perfectly, but here comes up our doubts...
- Could be any problem using these 6.40 installation (Master Installation & Kernel) files for a Dialog Instance installatio in our environment? Are there other installation files which could fit better than these one? Where could I find them?
- When I install a Dialog Instance, does it make changes into the Database Server and Central Instance?
- Initially we'd like to install the Dialog Instance in a test Server, try it, check that it works as we expect, and discard it in order to buy a big and powerful server where we'll definitely install the Dialog Instance. In this case, can we simply discard the test server or we have to follow a complex process for uninstall it? (this question is somehow related to the previous one).
Any help would be greatly appreciated. Thanks in advance.
Javier

Hi,
it is OK that you have 640 kernel even if your BASIS is 620. 620 kernel is no longer supported by SAP.
- Could be any problem using these 6.40 installation (Master Installation & Kernel) files for a Dialog Instance installatio in our environment? Are there other installation files which could fit better than these one? Where could I find them?
You master DVD is correct
- When I install a Dialog Instance, does it make changes into the Database Server and Central Instance?
It does not make any changes to DB, you will see next Dialog instance in SM51 then
- Initially we'd like to install the Dialog Instance in a test Server, try it, check that it works as we expect, and discard it in order to buy a big and powerful server where we'll definitely install the Dialog Instance. In this case, can we simply discard the test server or we have to follow a complex process for uninstall it? (this question is somehow related to the previous one).
You can discard your dialog instance without following special procedures.

EHP4 backup and Dialog instances

Hello All,
We intend to kick off the EHP4 PRD Downtime phase by Friday 10 PM.
Can you please provide me expert thoughts on the following:
1) When should we backup the PRD Database? (a) Anytime After the end of pre-processing phase when production operations are going on (b) after stopping of Application Servers and immediately before commencing the Downtime Phase
2) Is the online database backup fine or do we need a cold backup?
3) What steps specific to Dialog Instances are necassary like any profile parameter changes, explicit kernel upgrade on Dialog Instances before and after the downtime phase?
Thanks,
Antarpreet

Hi,
> 1) When should we backup the PRD Database? (a) Anytime After the end of pre-processing phase when production >operations are going on (b) after stopping of Application Servers and immediately before commencing the Downtime Phase
>
Once you will finish Pre-processing phase then it will ask you take backup of database, backup of upgrade directory and stop all productive operation. And then start downtime phase. At that phase you should take the backup. And this backup should be taken after stopping of application servers.
> 2) Is the online database backup fine or do we need a cold backup?
>
>
I would suggest you to take offline backup only because if you will take online backup then users will be there in the system which makes the backup inconsistent since productive operations will be on that time. Main idea to take backup is because if something goes wrong in downtime phase then you can restore the system at same stage before starting downtime. And if you will take online backup then users will be working that time so I think it defeats the purpose itself.
> 3) What steps specific to Dialog Instances are necassary like any profile parameter changes, explicit kernel upgrade on >Dialog Instances before and after the downtime phase?
>
For dialog instance, you can check SAP note 1245473 Add. Info. - SAP Enhancement Package Installer 7.00. Extract below from this note:
Updating Dialog Instances
After the enhancement package installation on the central instance, you
need to update the dialog instances accordingly. To do this, you install
the new dialog instances on top of the old dialog instances using the
tool SAPinst.
You can now also install more dialog instances, if necessary.
3. Save your dialog instance profiles, if you want to reuse them.
4. In case of a dual-stack system or a Java system, uninstall the old
dialog instances as described in the installation guide for your
source release.
5. To install a new dialog instance, proceed as described in the
document Installation Guide - <SAP NetWeaver / SAP application>
(<Technology>) on <Operating System>: <Database>.
6. If you use other instance numbers than on the source release and
reuse the old dialog instance profiles, adapt the instance numbers
in the profiles.
Thanks
Sunny

Is it really necessary to re-install the dialog instances?

Hi,
We are upgrading from NW04 (WAS 6.40) to NW04s (WAS 7.00) ABAP SR2 only on Windows 2003 with Oracle 9i. There is no JAVA stack in our environment and we don't need it.
In production system we have five separate dialog instances on five different physcial machines. All these application servers runnon Windows 2003 as well.
Reading through the NW04s upgrade guide "SAP NetWeaver 2004s
Application Server ABAP" dated 28th November 2006,
section 6.26 states we have to "install the new dialog instance on top of the old dialog instance".
In the past upgrades eg. upgrade to NW04, we did not have to use SAPINST to re-install the dialog instance. Instead, the official NW04 (WAS6.40) upgrade guide just instructs us to amend instance profile parameters and copy the new version of kernel binaries either manually or using sapcpe.
I want to avoid doing this re-installation work for the five dialog insatnces. Because I want to reduce the production outage period.
Question all the upgrade experts
1) Does any one have experience that indicates I should follow the SAP documentation to un-install 6.40 instance and then re-install at 7.00 level again?
2) Also, what is the technical reason to uninstall and re-install?
The full section 6.26 section paragraph is pasted here.
6.26 Upgrading or Installing Dialog Instances
After the upgrade of the central instance, you need to upgrade the dialog instance to the new release.
To do this, you install the new dialog instance on top of the old dialog instance using the tool SAPinst.
You can now also install additional dialog instances, if necessary.
Procedure
Proceed as described in the document Installation Guide ‒ <SAP NetWeaver / SAP solution> <Technology> on
<Operating System>: <Database>.
Caution
If you upgrade a dialog instance, make sure to use the same instance number as on the source release.

Hi Matt,
Thanks for your detailed response. Our system is very much heavy batch processing oriented. Therefore our management does not want to hand over the production system until all dialog instances are ready at the new version.
It would be great if the upgrade process is quick as you pointed out.
Can you show me where this "upgrade dialog instance" option in V7 SAPINST? FYI. I should be able to start sapinst over the next few days to look for this upgrade option.
However, I just got a response from ASIA-PACIFIC OSS that says I have to un-install and re-install the existing dialog instance. Their response is as follows :
The dialog instance does not need to be upgraded since in the dialog
instance, no database exists but only the kernel files and some
profiles exist. After the upgrade, you should re-install the dialog
instance since in the central instance, the kernel release has been
changed to 700 due to the upgrade. But in the old dialog instance,
it should still have the old release kernel files and profiles.
Thus, by using reinstallation, the new release kernel files will be
installed in the dialog instance.
As to the procedure, you should uninstall the old instance firstly since during the installation, the files will be put to the same path of the
old instance.We recommend you to backup the old dialog instance files
before the installation.Sorry there is no related note but you can refer to the upgrade and installation guides.
Thanks for your input and assistance.
Benny Kwan
National Australia Bank

How to delete Dialog instance on NW04

Hi guys
I have an installation NW04 on Cluster MSCS:
Central Instance on node A
SCS instance on Cluster Disk
Dialog instance on node B
We have performed upgrade to NW04s, and now in postprocessin we should deinstall Dialog Instance and install it again with software NW04s.
Here documentation guide:
****************************************+
After the upgrade of the central instance, you need to upgrade the dialog instance to the new release.
Due to the fact that some special settings and binaries on a dialog instance cannot be upgraded
remotely, you can only upgrade a dialog instance by uninstalling the old instance and then installing
a new dialog instance with the tool SAPinst.
Procedure
1. Uninstall the old dialog instances as described in the document Installation Guide ‒ SAP Web Application
Server 6.40 Java on <Operating System>: <Database>, Part II Installation and Post-Installation.
2. Install the new dialog instances as described in the document Installation Guide ‒ <SAP NetWeaver /
SAP application> <Technology> on <Operating System>: <Database>.
Point 1, is :
*************+
1. Log on as a user with domain administration rights.
2. Choose Start u2192 Settings u2192 Control Panel u2192 Add/Remove Programs.
3. The Add/Remove Programs dialog box appears.
4. Find the SAP entries.
. Note
Each SAP instance that is installed on the computer is listed with an entry like SAP Application Server
for System <SAPSID> instance.
5. Choose Remove.
The SAP Uninstall Wizard starts.
6. In the Welcome window, choose Next.
The dialog box Uninstalling SAP System appears for you to select an uninstall method
Depending on your selection, note the following when you use the check box to delete an SAP instance:
-- If your check box is marked gray, you delete or uninstall the following:
The SAP instance directory, for example:
\usr\sap\<SAPSID>\D00
Services, for example:
SAP<SAPSID>_00
The whole system directory, for example:
\usr\sap\<SAPSID>\*
-- If your check box is marked black, you delete or uninstall the following:
The SAP instance directory, for example:
\usr\sap\<SAPSID>\D00
Services, for example, SAP <SAPSID>_00
The whole system directory, for example:
\usr\sap\<SAPSID>\*
Local and domain user accounts
If you have different SAP instances that use the same <SAPSID>, you can delete the instance
directory only.
The wizard informs you when the SAP system or selected instances have been deleted successfully
But in my node B there is no SAP entry on Start u2192 Settings u2192 Control Panel u2192 Add/Remove Programs, however Dialog Instance exists, and windows service exists...and so on...
So how can we deinstall this dialog instance???
Thanks and regards
Javier

Hi
In node A there is JC30 (Java central instance)
In node B there is J32 (Java Dialog instance)
SCS31 (Services Central Instance) is now in node A, but can be switched.
Database Instance is OUTSIDE, is located on a Unix Server. (is not affected in this case)
Looking node B, there is no entry on Adding/Removing Programs regarding to SAP instance.
Of course, I can see windows services on node B, one for J32, other for SAPoscol, and one more for SCS31.
Any idea?
Thanks
Javier

Install additional "dialog" instance on another drive on the server

We are running NW2004S (SR2) with BW on SQL 2000, Windows 2003 on a two-node cluster. We have an existing ABAP/Java instance installed on
the "C" drive (#11) on one of the servers. I would like to install
another dialog instance on the same server as instance "01" on the "D"
drive, but when I run the install (sapinst) and select "custom", the
installation recognizes the existing instance on "C" and doesn't give
me the ability to install the new instance on "D" (just "C"). How can
I install this instance on the "D" drive ? Do I need to uninstall the
existing "11" instance on "C". Also, on this server there are two "enq"
server processes installed (ABAP #30, and Java #35) on the "C" drive -
what happens with them ?

Hi Ruchit,
I did specify the CI node when referencing the SAP profiles in the cluster and they are all recognized. My problem is that the installation only gives me the ability to install on the "C" drive. As a follow-up, SAP stated that since this is an additional dialog instance install, sapinst will perform the installation wherever the "saploc" shared says (in my case "C" - /usr/sap). It appears that if I want to basically move my existing dialog instance (11) from the "C" drive to the "D" drive, I need to uninstall the instance, along with the "enq" instances, then re-install the instance on the "D" drive.

Problems in Dialog instance installation for ECC6.0(ABAP+JAVA)

Does anyone can help me what should be a procedure of installing Dialog instance for ECC 6.0 with both ABAP + Java Stacks.
When installing app server do we also choose ABAP and Java or just ABAP. Installation manual does not cover this and when we run the sapinst we have following problem:
The following are the activities that I have done as pre-reqs on the standby on the server that is to host dialog instance
I have mounted the following file systems on ddrsap02. Created the local filesystem /usr/sap/DSP/D00 and NFS mounted the others
/dev/appsaph 5505024 5503856 1% 5 1% /usr/sap/DSP/D00 (is this required or SAPINST should create it itself)
ddrsap00:/stage 419430400 149761708 65% 90835 1% /stage
dprsap01:/sapmnt/DSP 4718592 2888416 39% 12790 2% /sapmnt/DSP
ddrsap12:/usr/sap/trans 2752512 1084932 61% 5107 3% /usr/sap/trans
Then when I run the sapinst from ddrsap02 to install the DI I get the following error
ddrsap02[/tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI]#vi sapinst_dev.log
"sapinst_dev.log" 20516 lines, 641048 characters
TRACE
Running with toplevel file /tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI/toplevel.xml
Running with dialog file /tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI/dialog.xml
Running with keydb file /tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI/keydb.xml
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_exe.397528.1170221882.
Opened iaejs701.o
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI.
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_exe.397528.1170221882.
Opened iacdlib701.o
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI.
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_exe.397528.1170221882.
Opened iaccdlib.o
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI.
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_exe.397528.1170221882.
Opened iapasswdman701.o
INFO 2007-01-31 09:38:52
Working directory changed to /tmp/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAPJAVA/DI.
This is SAPinst, version 701, make variant 700_REL, build 817256
compiled on Mar 14 2006, 23:39:26
TRACE [syxxsyshlp.cpp:175]
 syslib::logSystemState()
Process environment
===================
Environment Variables
=====================
_ = /tmp/sapinst_exe.397528.1170221882/sapinstexe
SAPINST_EXE_DIR = /tmp/sapinst_exe.397528.1170221882
LANG = en_US
LOGIN = root
PATH = /usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java14_64/jre/bin:/usr/java14_64/bin
SAPINST_EXEDIR_CD = /stage/51031797/IM_AIX_PPC64/.
LC__FASTMSG = true
WINDOWID = 8388621
"sapinst_dev.log" 20516 lines, 641048 characters
 EJS_Installer::writeTraceToLogBook()
2007-01-31 09:42:48.898 NWDB.getDBHost() done: undefined
ERROR 2007-01-31 09:42:48 [iaxxinscbk.cpp:271]
 abortInstallation
CJS-00030 Assertion failed: in getSidFromProfiles: Variable dbHost should be defined
TRACE [iaxxejsbas.hpp:388]
 handleException<ESAPinstException>()
Converting exception into JS Exception Exception.
ERROR 2007-01-31 09:42:48
 CJSlibModule::writeError_impl()
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
TRACE [iaxxejsbas.hpp:460]
 EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2007-01-31 09:42:48
FCO-00011 The step assertDBInfo with step key |NW_DI|ind|ind|ind|ind|0|0|NW_GetSidFromProfiles|ind|ind|ind|ind|1|0|assertDBInfo was executed with status ERROR .
<html><head></head><body>An error occurred while processing service SAP ERP 2005 Support Release 1 > SAP Systems > Oracle > High-Availability System > Base
d on AS ABAP and AS Java > Dialog Instance. You may now<ul> <li>press Retry to repeat the current step.</li> <li>press the View Log button
to get more information about the error.</li> <li>stop the task and continue with it later.</li></ul>Log files are written to /tmp/sapinst_instdir/ERP/SYST
EM/ORA/HA/ABAPJAVA/DI.</body></html>
TRACE [iaxxgenimp.cpp:1093]
 showDialog()
waiting for an answer from gui
Am I missing some pre-reqs or variable definitions?
I was going through the documentation and it says that /sapmnt/DSP/exe should be a local filesystem for a DI on a separate server. Will this create a problem ?
Also they talk about starting sapinst with the variable SAPINST_USE_HOSTNAME set to ddrsap02. I have tried this also
We are also not 100% sure about the settings for parameters:
rdisp/mssserv
rdisp/mssserv_internal
Accorss Devault Instance and Services Instance profile.
When we define it as per installation GUIDE (Abap+Java page 64) we get the popup message in SAPINST:
<html>Profile parameter rdisp/msserv_internal is not set for instance DVEBMGS01/DSP on host dprsap01.You have to set the parameter in the default profile and restart the instance.For further information refer to SAP Note 821875.</html>
Other errors follow shortly.
Any help would be appreciated

Hi ,
are you able to resolve this error :Profile parameter rdisp/msserv_internal is not set for instance DVEBMGS01/DSP on host dprsap01.
You have to set the parameter in the default profile and restart the instance.
For further information refer to SAP Note 821875.</html>
? if yes , pls let me know , I am stuck with same issue while installing dialog instance .
Thanks
Hamendra

SAP Dialog Instance Installation.

Hi
Installation of ABAP System ECC6.0
I am trying to install another application server(Dialog Instance) on
different host. My both System Central(main server) and Dialog system in
same domain. I am installing SAP Server as a Local Installation.
I am able to installed Dialog Instance on same Host of Central System. But
when I was trying to installation it on different Host, I got error on
u201CStart Dialog Instanceu201D step that is last step it cant able to start Dialog
Instance.
Can you please tell me the Prerequisite for this type of setup as well as
any other Setting related to u201Chostsu201D and u201Cservicesu201Dfile ? and also central system
side settings.
Following Error is occurred :
u201CCopy Errors detected.................: 0
Sync Errors detected.................: 0
Warnings detected....................: 0
INFO 2008-11-21 13:14:39
Execute step createOsCol of component
|NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0|NW_Instance|i
nd|ind|ind|ind|1|0.
WARNING[E] 2008-11-21 13:14:40
FSL-06002 Error 1060 (The specified service does not exist as an installed
service.
) in execution of a 'OpenService' function, line (266), with parameter
(SAPOsCol).
INFO 2008-11-21 13:14:41
Creating file C:\Program
Files\sapinst_instdir\ERP\SYSTEM\ORA\HA\ABAP\DI\ntscmgr.exe.log.
INFO 2008-11-21 13:14:41
Output of
i3643vm\sapmnt\PT6\SYS\exe\uc\NTI386\ntscmgr.exe remove SAPOsCol
is written to the logfile ntscmgr.exe.log.
INFO 2008-11-21 13:14:41
Execution of the command "
i3643vm\sapmnt\PT6\SYS\exe\uc\NTI386\ntscmgr.exe
remove SAPOsCol" finished with return code 0. Output:
failure: OpenService (0x424)
INFO 2008-11-21 13:14:41
The 'SAPOsCol' service on the 'Local' machine was created successfully.
INFO 2008-11-21 13:14:45
The service 'SAPOsCol' started successfully on host 'Local'.
INFO 2008-11-21 13:14:46
Execute step createService of component
|NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0|NW_Instance|i
nd|ind|ind|ind|1|0.
INFO 2008-11-21 13:14:46
Creating SAP start service of instance PT6/D02...
INFO 2008-11-21 13:14:47
Creating file C:\Program
Files\sapinst_instdir\ERP\SYSTEM\ORA\HA\ABAP\DI\sapstartsrv.exe.log.
INFO 2008-11-21 13:14:47
Output of D:\usr\sap\PT6\D02\exe\sapstartsrv.exe -r -q -p
i3643vm\sapmnt\PT6\SYS\profile\START_D02_I3976vm2 -s PT6 -n 02 -U
I3976vm2\SAPServicePT6 -P XXXXXX -e I3976vm2\pt6adm is written to the
logfile sapstartsrv.exe.log.
INFO 2008-11-21 13:14:53
Execution of the command "D:\usr\sap\PT6\D02\exe\sapstartsrv.exe -r -q -p
i3643vm\sapmnt\PT6\SYS\profile\START_D02_I3976vm2 -s PT6 -n 02 -U
I3976vm2\SAPServicePT6 -P XXXXXX -e I3976vm2\pt6adm" finished with return
code 0. Output:
Service succesfully installed.
INFO 2008-11-21 13:14:53
Execute step setServiceSecurity of component
|NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0|NW_Instance|i
nd|ind|ind|ind|1|0.
INFO[E] 2008-11-21 13:14:58
FSL-01027 Account user="I3976vm2\SAP_PT6_LocalAdmin" does not exist.
INFO 2008-11-21 13:14:58
Successfully set '(S-1-5-21-134454618-3270849815-193169279-1011, NONE, + |
SERVICE_START | SERVICE_STOP)(S-1-5-18, NONE, +o | READ_CONTROL |
SERVICE_ENUMERATE_DEPENDENTS | SERVICE_INTERROGATE | SERVICE_PAUSE_CONTINUE
| SERVICE_QUERY_CONFIG | SERVICE_QUERY_STATUS | SERVICE_START | SERVICE_STOP
| SERVICE_USER_DEFINED_CONTROL | STANDARD_RIGHTS_READ |
STANDARD_RIGHTS_WRITE)(S-1-5-32-544, NONE, + | DELETE | READ_CONTROL |
SERVICE_ALL_ACCESS | SERVICE_CHANGE_CONFIG | SERVICE_ENUMERATE_DEPENDENTS |
SERVICE_INTERROGATE | SERVICE_PAUSE_CONTINUE | SERVICE_QUERY_CONFIG |
SERVICE_QUERY_STATUS | SERVICE_START | SERVICE_STOP |
SERVICE_USER_DEFINED_CONTROL | STANDARD_RIGHTS_READ | STANDARD_RIGHTS_WRITE
| WRITE_DAC | WRITE_OWNER)(S-1-5-4, NONE, + | READ_CONTROL |
SERVICE_ENUMERATE_DEPENDENTS | SERVICE_INTERROGATE | SERVICE_QUERY_CONFIG |
SERVICE_QUERY_STATUS | SERVICE_USER_DEFINED_CONTROL | STANDARD_RIGHTS_READ |
STANDARD_RIGHTS_WRITE)(S-1-5-6, NONE, + | READ_CONTROL |
SERVICE_ENUMERATE_DEPENDENTS | SERVICE_INTERROGATE | SERVICE_QUERY_CONFIG |
SERVICE_QUERY_STATUS | SERVICE_USER_DEFINED_CONTROL | STANDARD_RIGHTS_READ |
STANDARD_RIGHTS_WRITE)(S-1-5-11, NONE, + | SERVICE_USER_DEFINED_CONTROL)(S-
1-5-32-547, NONE, + | READ_CONTROL | SERVICE_ENUMERATE_DEPENDENTS |
SERVICE_INTERROGATE | SERVICE_PAUSE_CONTINUE | SERVICE_QUERY_CONFIG |
SERVICE_QUERY_STATUS | SERVICE_START | SERVICE_STOP |
SERVICE_USER_DEFINED_CONTROL | STANDARD_RIGHTS_READ |
STANDARD_RIGHTS_WRITE)(S-1-5-21-134454618-3270849815-193169279-1009, NONE, +
| DELETE | READ_CONTROL | SERVICE_ALL_ACCESS | SERVICE_CHANGE_CONFIG |
SERVICE_ENUMERATE_DEPENDENTS | SERVICE_INTERROGATE | SERVICE_PAUSE_CONTINUE
| SERVICE_QUERY_CONFIG | SERVICE_QUERY_STATUS | SERVICE_START | SERVICE_STOP
| SERVICE_USER_DEFINED_CONTROL | STANDARD_RIGHTS_READ |
STANDARD_RIGHTS_WRITE | WRITE_DAC | WRITE_OWNER)' security to service
I3976vm2\SAPPT6_02' on computer 'I3976vm2'.
INFO 2008-11-21 13:14:58
Execute step createCCMSService of component
|NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0|NW_Instance|i
nd|ind|ind|ind|1|0.
WARNING[E] 2008-11-21 13:14:58
FSL-06002 Error 1060 (The specified service does not exist as an installed
service.
) in execution of a 'OpenService' function, line (266), with parameter
(sapccmsr.02).
INFO 2008-11-21 13:14:59
Creating file C:\Program
Files\sapinst_instdir\ERP\SYSTEM\ORA\HA\ABAP\DI\ntscmgr.exe.log.
INFO 2008-11-21 13:14:59
Output of
i3643vm\sapmnt\PT6\SYS\exe\uc\NTI386\ntscmgr.exe remove
sapccmsr.02 is written to the logfile ntscmgr.exe.log.
INFO 2008-11-21 13:14:59
Execution of the command "
i3643vm\sapmnt\PT6\SYS\exe\uc\NTI386\ntscmgr.exe
remove sapccmsr.02" finished with return code 0. Output:
failure: OpenService (0x424)
INFO 2008-11-21 13:14:59
Execute step setCCMSServiceSecurity of component
|NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0|NW_Instance|i
nd|ind|ind|ind|1|0.
INFO 2008-11-21 13:15:00
Execute step registerEventsDLL of component
|NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0|NW_Instance|i
nd|ind|ind|ind|1|0.
INFO 2008-11-21 13:15:09
Execute step setICMBndPermissions of component
|NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0|NW_Instance|i
nd|ind|ind|ind|1|0.
INFO 2008-11-21 13:15:09
Execute step copyRFCExecSec of component
|NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0.
INFO 2008-11-21 13:15:10
Copied file '
i3643vm/sapmnt/PT6/SYS/exe/uc/NTI386/rfcexec.sec' to
'D:/usr/sap/PT6/D02/work'.
INFO 2008-11-21 13:15:11
Execute step callSetDB4PWD of component
|NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0.
INFO 2008-11-21 13:15:13
Execute step unpackJ2EEINSTALL of component
|NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0.
INFO 2008-11-21 13:15:13
Execute step runBatchconfig of component
|NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0.
INFO 2008-11-21 13:15:13
Execute step removeTempDirectory of component
|NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0.
INFO 2008-11-21 13:15:14
Execute step start of component
|NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0.
INFO 2008-11-21 13:15:14
Starting instance PT6/DVEBMGS00...
INFO 2008-11-21 13:15:15
Connect to message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:15:15
Disconnect from message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:15:15
Connect to message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:15:15
Disconnect from message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:15:15
Starting instance PT6/D02...
INFO 2008-11-21 13:15:22
Connect to message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:15:22
Disconnect from message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:15:22
Connect to message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:15:22
Disconnect from message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:15:35
Creating file C:\Program
Files\sapinst_instdir\ERP\SYSTEM\ORA\HA\ABAP\DI\stop_PT6_D02.log.
INFO 2008-11-21 13:15:35
Output of
i3643vm\sapmnt\PT6\SYS\exe\uc\NTI386\stopsap.exe name=PT6 nr=02
SAPDIAHOST=I3976vm2 is written to the logfile stop_PT6_D02.log.
INFO 2008-11-21 13:15:43
Execution of the command "
i3643vm\sapmnt\PT6\SYS\exe\uc\NTI386\stopsap.exe
name=PT6 nr=02 SAPDIAHOST=I3976vm2" finished with return code 0. Output:
STOPSAP executed succesfully
INFO 2008-11-21 13:15:46
Connect to message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:15:46
Disconnect from message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:15:46
Connect to message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:15:46
Disconnect from message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:15:48
Creating file C:\Program
Files\sapinst_instdir\ERP\SYSTEM\ORA\HA\ABAP\DI\start_PT6_D02.log.
INFO 2008-11-21 13:15:48
Output of
i3643vm\sapmnt\PT6\SYS\exe\uc\NTI386\startsap.exe name=PT6 nr=02
SAPDIAHOST=I3976vm2 is written to the logfile start_PT6_D02.log.
INFO 2008-11-21 13:16:21
Execution of the command "
i3643vm\sapmnt\PT6\SYS\exe\uc\NTI386
\startsap.exe name=PT6 nr=02 SAPDIAHOST=I3976vm2" finished with return code
0. Output:
STARTSAP continues...
INFO 2008-11-21 13:16:21
Connect to message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:16:21
Disconnect from message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:16:21
Connect to message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:16:21
Disconnect from message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:16:22
State of instance PT6/D02 changed from ABAP: UNKNOWN to ABAP: UNKNOWN.
INFO 2008-11-21 13:16:50
Connect to message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:16:50
Disconnect from message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:16:50
Connect to message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:16:50
Disconnect from message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:17:23
Connect to message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:17:23
Disconnect from message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:17:23
Connect to message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:17:23
Disconnect from message server (i3643vm/3900) succeeded.
INFO 2008-11-21 13:17:24
State of instance PT6/D02 changed from ABAP: STARTING to ABAP: STARTING.
ERROR 2008-11-21 13:17:24
CJS-30105 Instance PT6/D02 reached state UNKNOWN after having state
STARTING. Giving up.
ERROR 2008-11-21 13:17:24
FCO-00011 The step start with step key
|NW_DI|ind|ind|ind|ind|0|0|NW_DI_Instance|ind|ind|ind|ind|10|0|start was
executed with status ERROR .
Thanks in advance.
Regards
Manoj

Hi, I'm Josephine and I almost have the same scenario as this problem reported earlier but it's just that we are using SAP Netweaver 04 SR1.
However, I'm installing additional SAP Application server to our existing one.
Our existing main server is in MS cluster. SAPPRD1 (DB Server in node A) and SAPPRD2 (SAP App Server in node B). System ID is PRD and the CI Instance number is 00. The hostname where the USR folder is SAPPRD (hostname in the cluster environment but this is the SAPPRD2 server in node B).
Now I'm installing additional SAP App server into a new host (SAPPRD3 & SAPPRD4) they are all in the same domain.
But I would like to install the 2nd and 3rd SAP App server in a local host.
While installing there was an error "Output: Service not started" the process "Create or reregister services" during the installation stopped.
I used the installer under the folder InstMaster\IM01_NT_I386\SAPINST\NT\I386\sapinst.exe and run the Dialog Instance under the SAP Netweaver\ABAP System\MS SQL Server\Unicode\.
This is the part of the sapinst log where the error starts:
PHASE 2009-01-28 08:39:29
Preparing DBMS-specific profile parameters
INFO 2009-01-28 08:39:30
Adapt operation t_SAPComponent_Profiles_SHARED processed successfully.
PHASE 2009-01-28 08:39:31
Handle services
INFO 2009-01-28 08:39:32
Creating file C:\Program Files\sapinst_instdir\NW04SR1\WEBAS_ABAP_MSS_UC\DI\sapstartsrv.exe.log.
INFO 2009-01-28 08:39:32
Output of C:\usr\sap\PRD\D02\exe/sapstartsrv.exe '-r' '-q' '-p' '
sapprd\sapmnt\PRD\SYS\profile\START_D02_sapprd4' '-s' 'PRD' '-n' '02' '-U' 'sapprd4\SAPServicePRD' '-P' 'XXXXXX' '-e' 'sapprd4\prdadm' is written to the logfile sapstartsrv.exe.log.
WARNING 2009-01-28 08:39:35
Execution of the command "C:\usr\sap\PRD\D02\exe/sapstartsrv.exe '-r' '-q' '-p' '
sapprd\sapmnt\PRD\SYS\profile\START_D02_sapprd4' '-s' 'PRD' '-n' '02' '-U' 'sapprd4\SAPServicePRD' '-P' 'XXXXXX' '-e' 'sapprd4\prdadm'" finished with return code -1. Output: Service not started.
ERROR 2009-01-28 08:39:35
MOS-01011 'C:\usr\sap\PRD\D02\exe/sapstartsrv.exe' returned with '-1'.
Please help me on this I can't successfully install another dialog instance to add to our existing one now.
Thank you and hoping for your reply.
Yours truly,
Josephine Dejolde

BI : dialog instance does not start

Hi all.
--> Before explain you our problem, I'm going to tell you our scenario: We have an HP-UX cluster where we have installed BI system ABAP+JAVA stack (NW 701). We have got one central package with SAP and oracle in node1 and one dialog instance in node2.
--> When we start the cluster, central instance starts succesfully and all works fine. But at the moment we start dialog one in second node, for this instance only starts ABAP stack, but not java one. All logs shows a clear error, and it is that not connect to database. But at the same time, in central instance we are not able to start configtool because not connection to database. It's strange because in all nodes, processes are running. Just at the moment we stop dialog instance, central one works fine again and configtool access is succesfully.
Lot of bootstrap logs appear, so we are thinking that some parameters are wrong in configtool, but we are not so sure.
Can anybody help us with this issue? What can be causing that database connection is lost when starting dialog instance?
Thanks a lot to all in advance.
Best regards

Hi,
which way you apply kernel patch on application server for iseries?
use following method to apply kernel patch on application server for iseries.
stop application server.
download the kernel sapexe.sar and saexedb.sar application server on windows for iseries.
extract both file in one folder. i.e kernel
also download patch for IGS i.e igs.sar
and extract it in same folder. i.e kernel
now
backup NTI386 folder on iSeries host.
\usr\sap\SID\SYS\exe\uc\NTI386
now copy the content of extracted kernel from folder kernel to NTI386 folder.
now start the application server host.
consider following to install application server for iseries on windows server.
if you use a 64 bit windows server, please have look to Note 734428:
This Application Server (64 bit) is available for EM64T/AMD64 technologies and NOT for Itanium
also check Note 680617 - INST: Appl.Server in Heterogeneous SAP System Environment
regards,
kaushal
Edited by: kaushal malavia on Apr 1, 2008 10:16 AM

Installing Java Dialog Instance - Error while connecting to DB

We would like to add a dialog instance to our production Portal server. We installed Portal as stand-alone on the central instance. We have another server we would like to setup to serve as a Portal dialog instance.
So far I have installed Windows 2003 Server Standard. Installed MSSQL server client tools (database is mssql server). Installed jdk 1.4.62. Set java home and path environmental variables. I'm now installing the Java dialog instance (I can't find any documentation on this). From Netweaver installation CD> SAP NetWeaver '04 Support Release 1> Java System> MS SQL Server> Dialog Instance Installation>
SAP System ID: (sid) ES2
Central Host: SAPEPS02
Path to JAVA DVD supplied> JDK Directory confirmed> Domain paramaters confirmed> domain<sid> account passwords supplied> domain<service><sid> account password supplied> Instance number confirmed>
Installation started> It gets to step 8 and fails stating "Error while connecting to DB". I looked through all the log files and couldn't come up with anything (i'm very thorough).
I tried adding the users to the database as dbowners (no luck). I installed SQL server 2000 with SP4. No where during this installation did I get prompted for database parameters?
Is there something basic i'm missing? Does this scenario not work? Any help would be greatly appreciated. Pointing me in the right direction of the correct documentation would also be appreciated. Thank you in advance.
Sincerely,
Brad Dridi

Hi Brad,
I am facing the same problem. I hope by now you must have got the solution for this.
Can you please let me know how did you overcome this situation?
Thank you!!
Regards,
Abhijeet Bhagat

Error installing Dialog Instance ABAP+JAVA

Hi,
We're having a little issue with installation of a ERP dialog instance. The problem is, when the initial
installation was made, it was a system copy but not in the traditional way, the partner performed a copy
in OS level (cp -rp .... , etc). Once it was finished, renaming of certain this happended.
As we can see, DEV was the initial installation (normal way) but QAS and PRD were copies of DEV ( oracle
schema in PRD is SAPDEV too) this apparently doesn't cause a problem. But now the installer of a dialog
instance stops with this error:
PerfTimes : loadNativeLayer: loading jperflib failed. no jperflib in java.library.path
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>
(DBConnectionPool.java:115)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>
(PersistenceHandler.java:38)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>
(ConfigurationCache.java:149)
 at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init
(ConfigurationManagerBootstrapImpl.java:236)
 at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>
(ConfigurationManagerBootstrapImpl.java:49)
 at com.sap.engine.configtool.batch.BatchConfig.go(BatchConfig.java:47)
 at com.sap.engine.configtool.batch.BatchConfig.main(BatchConfig.java:83)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: The encryption key
(usually in the key file) is not the key that is required to decrypt the data in the secure store file or
the system name (SID) is wrong..
 at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
 at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>
(DBConnectionPool.java:112)
 ... 11 more
Caused by: com.sap.security.core.server.secstorefs.WrongKeyException: The encryption key (usually in the
key file) is not the key that is required to decrypt the data in the secure store file or the system name
(SID) is wrong.
 at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:2017)
 at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:802)
 at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)
 ... 13 more
Caused by: com.sap.security.core.server.secstorefs.InvalidStateException: Internal error during the
decryption process.
 at com.sap.security.core.server.secstorefs.Crypt.decrypt(Crypt.java:850)
 at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:1985)
 ... 16 more
Caused by: javax.crypto.BadPaddingException: Invalid PKCS#5 padding length: 176
 at iaik.security.cipher.s.b(Unknown Source)
 at iaik.security.cipher.w.a(Unknown Source)
 at iaik.security.cipher.w.engineDoFinal(Unknown Source)
 at javax.crypto.Cipher.doFinal(DashoA12275)
 at com.sap.security.core.server.secstorefs.Crypt.decrypt(Crypt.java:825)
 ... 17 more
Error while connecting to DB.
The error occurs when the installer tries to connect to oracle via jdbc, but the files
SecStore.properties and SecStore.key are from DEV, and they were created with the values of DEV, so when
the installer tries with PRD as central instance name, it doesn't work, how can we recreate this files or
reconfigure the j2ee engine so the installer can connect and finish installation ?
Thanks in advance

Exactly, the problem is when the installer tries to execute the following:
/usr/j2se/bin/java -classpath /tmp/sapinst_instdir/ERP/LM/AS/ORA/DI/install/shar
edlib/launcher.jar -Xmx256m -d64 -d64 com.sap.engine.offline.OfflineToolStart co
m.sap.engine.configtool.batch.BatchConfig /usr/sap/PRD/SYS/global/security/lib/t
ools/iaik_jce.jar:/usr/sap/PRD/SYS/global/security/lib/tools/iaik_jsse.jar:/usr/
sap/PRD/SYS/global/security/lib/tools/iaik_smime.jar:/usr/sap/PRD/SYS/global/sec
urity/lib/tools/iaik_ssl.jar:/usr/sap/PRD/SYS/global/security/lib/tools/w3c_http
.jar:/tmp/sapinst_instdir/ERP/LM/AS/ORA/DI/install/lib:/tmp/sapinst_instdir/ERP/
LM/AS/ORA/DI/install/sharedlib:/oracle/client/10x_64/instantclient/ojdbc14.jar /
tmp/sapinst_instdir/ERP/LM/AS/ORA/DI/BatchConfig.xml
The file /tmp/sapinst_instdir/ERP/LM/AS/ORA/DI/BatchConfig.xml has this:
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE config [
<!ELEMENT config (dbproperties, task*)>
 <!ELEMENT dbproperties (property*)>
 <!ELEMENT task (property*)>
 <!ATTLIST task name CDATA #REQUIRED>
 <!ELEMENT property (#PCDATA)>
 <!ATTLIST property key CDATA #REQUIRED>
 <!ATTLIST property value CDATA #REQUIRED>
]>
<config>
<dbproperties>
 <property key="rdbms.maximum_connections" value="5"/>
 <property key="system.name" value="PRD"/>
 <property key="secstorefs.keyfile" value="/sapmnt/PRD/global/security/data/S
ecStore.key"/>
 <property key="secstorefs.secfile" value="/sapmnt/PRD/global/security/data/S
ecStore.properties"/>
 <property key="secstorefs.lib" value="/sapmnt/PRD/global/security/lib"/>
 <property key="rdbms.driverLocation" value="/oracle/client/10x_64/instantcli
ent/ojdbc14.jar"/>
 <property key="rdbms.connection" value="jdbc/pool/PRD"/>
 <property key="rdbms.initial_connections" value="1"/>
As you can see the are values "system.name" with PRD. This cause an error:
PerfTimes : loadNativeLayer: loading jperflib failed. no jperflib in java.library.path
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:115)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
 at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
 at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
 at com.sap.engine.configtool.batch.BatchConfig.go(BatchConfig.java:47)
 at com.sap.engine.configtool.batch.BatchConfig.main(BatchConfig.java:83)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: The encryption key (usually in the key file) is not the key that is required to decrypt the data in the secure store file or the system name (SID) is wrong..
 at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
 at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:112)
 ... 11 more
Caused by: com.sap.security.core.server.secstorefs.WrongKeyException: The encryption key (usually in the key file) is not the key that is required to decrypt the data in the secure store file or the system name (SID) is wrong.
 at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:2017)
 at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:802)
 at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)
 ... 13 more
Caused by: com.sap.security.core.server.secstorefs.InvalidStateException: Internal error during the decryption process.
 at com.sap.security.core.server.secstorefs.Crypt.decrypt(Crypt.java:850)
 at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:1985)
 ... 16 more
Caused by: javax.crypto.BadPaddingException: Invalid PKCS#5 padding length: 176
 at iaik.security.cipher.s.b(Unknown Source)
 at iaik.security.cipher.w.a(Unknown Source)
 at iaik.security.cipher.w.engineDoFinal(Unknown Source)
 at javax.crypto.Cipher.doFinal(DashoA12275)
 at com.sap.security.core.server.secstorefs.Crypt.decrypt(Crypt.java:825)
 ... 17 more
The same as configtool with PRD value.
So can we change the system.name value to PRD and is there a posibility to change the encpytion key so it can be used with PRD value ??
My theory is: The SecStore.key file is used to decript the SecStore.properties but the system.name value plays an important role in decryption, am I right??
Can I regenerate the key with the system.name = PRD so the error solves??
Regards.

Uninstall dialog instance

Similar Messages

Maybe you are looking for