SDM deployment error during XI 3.0 installation

(nobody in the PI forum replied, so I'm reposting here)
I need to install a sandbox using this old version. Installation base is 6.40 WebAS plus Java addon SR1. System installs fine, however during final SDM deployment I get a problem during the J2EE engine restart:
errors:
service sld ================= ERROR =================
Cannot start service com.sap.aii.af.cpa.svc; it has hard reference to service sld which is not started.
and around 20 more services which have a dependency on sld
sld does not start because:
/Applications/SLD#sap.com/com.sap.lcr#com.sap.lcr.sagent.BuilderDirector#J2EE_
GUEST#328####e4cd3451819411dec19c001d72bd0666#SAPEngine_Application_Threadimpl:3_0##0#0#Error#1#com.sap.lcr.sagent.BuilderDirector#Plain###Can't access http store#
OR:
SAPEngine_System_Threadimpl:5_32##0#0#Error#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service sld error. Nested exception is: com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='sld_3012', A
rguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key sld_3012
at com.sap.sldserv.SldServerFrame.start(SldServerFrame.java:109)
at com.sap.sldserv.SldServerFrame.start(SldServerFrame.java:78) ...........
further suspicious warnings:
Aug 5, 2009 12:51:17 AM Info: No action: Selected development component 'com.sap.aii.af.ms.svc'/'sap.com'/'SAP AG'/'3.0.0920041027171222.0000' will not be deployed because containing software component 'SAP-XIAFC'/'sap.com'/'SAP AG'/'1000.3.0.9.1.20041028052722' will not be deployed.
and this for around 20 more components from comp.sap.aii*
What went wrong, and, what can I do to fix this? Redeploy sld ? I could not find how.
Java version is latest 1.4.2 x86_64 from IBM (1.4.2_13) for my architecture (x86_64 Linux RHEL5), DB is maxdb 7.6
Any help is appreciated, Thanks.
Sanjay

Can you please check thet if you have given a central SLD then that SLD is up and running as you are getting the message.
Cannot start service com.sap.aii.af.cpa.svc; it has hard reference to service sld which is not started.
Please check this note it will solve your issue.
Note 994433 - XI AF on J2EE Engine terminates with OutOfMemoryError
you can manually start th services.
Thanks Rishi Abrol

Similar Messages

  • Error during sap r/3 installation  at update databse statistics

    Hi friends,
    I am getting an error during sap r/3 installation almost at the last stage.
    the error is  at update database statistics.
    my configuration is
    os: windows 2000 server.
    d/b: oracle 9i.
    erp: sap 4.7 ee
    During oracle installation stage the oui is asking for create a database, i am chechking it ok. Is that a problem ?.
    I am sending the log file. Please can anybody help me, where i am going wrong-
    The log file----
    Click Browse and give location of export1, as shown in the bellow figure
    INFO 2007-02-04 21:46:32
    Creating directory D:\oracle\DRS\sapdata4\drs620_5.
    INFO 2007-02-04 21:46:32
    Creating file system node D:\oracle\DRS/sapdata4\drs620_5 with type DIRECTORY succeeded.
    INFO 2007-02-04 21:46:32
    Creating directory D:\oracle\DRS\sapdata5\drs620_6.
    INFO 2007-02-04 21:46:32
    Creating file system node D:\oracle\DRS/sapdata5\drs620_6 with type DIRECTORY succeeded.
    INFO 2007-02-04 21:46:32
    Creating directory D:\oracle\DRS\sapdata5\drs620_7.
    INFO 2007-02-04 21:46:32
    Creating file system node D:\oracle\DRS/sapdata5\drs620_7 with type DIRECTORY succeeded.
    INFO 2007-02-04 21:46:32
    Creating directory D:\oracle\DRS\sapdata6\drs620_8.
    INFO 2007-02-04 21:46:32
    Creating file system node D:\oracle\DRS/sapdata6\drs620_8 with type DIRECTORY succeeded.
    INFO 2007-02-04 21:46:32
    Creating directory D:\oracle\DRS\sapdata6\drs620_9.
    INFO 2007-02-04 21:46:32
    Creating file system node D:\oracle\DRS/sapdata6\drs620_9 with type DIRECTORY succeeded.
    INFO 2007-02-04 21:46:32
    Creating directory D:\oracle\DRS\sapdata6\drsusr_1.
    INFO 2007-02-04 21:46:32
    Creating file system node D:\oracle\DRS/sapdata6\drsusr_1 with type DIRECTORY succeeded.
    INFO 2007-02-04 21:46:32
    Creating directory D:\oracle\DRS\sapdata2\roll_1.
    INFO 2007-02-04 21:46:32
    Creating file system node D:\oracle\DRS/sapdata2\roll_1 with type DIRECTORY succeeded.
    INFO 2007-02-04 21:46:32
    Creating directory D:\oracle\DRS\sapdata3\temp_1.
    INFO 2007-02-04 21:46:32
    Creating file system node D:\oracle\DRS/sapdata3\temp_1 with type DIRECTORY succeeded.
    INFO 2007-02-04 21:46:32
    Creating directory D:\oracle\DRS\sapdata1\system_1.
    INFO 2007-02-04 21:46:32
    Creating file system node D:\oracle\DRS/sapdata1\system_1 with type DIRECTORY succeeded.
    INFO 2007-02-04 21:46:32
    Processing of all file system node operations of table tORA_SapdataNodes succeeded.
    INFO 2007-02-04 21:46:33
    Processing of all file system node operations of table tORA_DatabaseServerNodes succeeded.
    INFO 2007-02-04 21:46:34
    Processing of all file system node operations of table tORA_SapdataNodes succeeded.
    INFO 2007-02-04 21:46:35
    Creating file c:\oracle\ora90\database\initDRS.ora.
    INFO 2007-02-04 21:46:36
    Creating file C:\oracle\ora90\database\initDRS.sap.
    INFO 2007-02-04 21:46:37
    Copying file F:/sap4.7/ker/NT/COMMON/INSTALL/INITSID.DBA to: c:\oracle\ora90/database/initDRS.dba.
    INFO 2007-02-04 21:46:37
    Creating file c:\oracle\ora90\database\initDRS.dba.
    INFO 2007-02-04 21:46:38
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 21:46:39
    Moving file c:/oracle/ora90/database/initDRS.ora to: orig_init_ora_tmp.txt.
    INFO 2007-02-04 21:46:39
    Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: c:\oracle\ora90\database\initDRS.ora.
    INFO 2007-02-04 21:46:39
    Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
    INFO 2007-02-04 21:46:40
    Creating file C:\SAPinst ORACLE KERNEL\oradim.log.
    INFO 2007-02-04 21:46:45
    See 'c:\oracle\ora90/bin/oradim -new -sid DRS -STARTMODE auto' output in 'C:\SAPinst ORACLE KERNEL\oradim.log'.
    INFO 2007-02-04 21:46:45
    'c:\oracle\ora90/bin/oradim -new -sid DRS -STARTMODE auto' returned with '0'.
    INFO 2007-02-04 21:46:46
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 21:46:49
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 21:59:57
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:00:00
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:00:44
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:00:46
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:01:31
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:01:34
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:02:18
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:02:20
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:03:06
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:03:09
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:03:55
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:03:57
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:04:44
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:04:46
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:05:32
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:05:35
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:06:21
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:06:23
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:07:10
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:07:12
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:07:58
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:08:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:08:48
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:08:50
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:09:38
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:09:40
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:09:44
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:09:46
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:10:06
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:10:09
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:10:39
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:10:41
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:10:44
    Moving file c:/oracle/ora90/database/initDRS.ora to: orig_init_ora_tmp.txt.
    INFO 2007-02-04 22:10:44
    Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: c:\oracle\ora90\database\initDRS.ora.
    INFO 2007-02-04 22:10:44
    Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
    INFO 2007-02-04 22:10:45
    Creating file C:\SAPinst ORACLE KERNEL\lsnrctl.log.
    INFO 2007-02-04 22:10:46
    See 'c:\oracle\ora90/bin/lsnrctl stat' output in 'C:\SAPinst ORACLE KERNEL\lsnrctl.log'.
    INFO 2007-02-04 22:10:46
    'c:\oracle\ora90/bin/lsnrctl stat' returned with '3'.
    INFO 2007-02-04 22:10:46
    Creating file C:\SAPinst ORACLE KERNEL\lsnrctl.log.
    INFO 2007-02-04 22:10:48
    See 'c:\oracle\ora90/bin/lsnrctl start' output in 'C:\SAPinst ORACLE KERNEL\lsnrctl.log'.
    INFO 2007-02-04 22:10:48
    'c:\oracle\ora90/bin/lsnrctl start' returned with '0'.
    INFO 2007-02-04 22:10:48
    Copying file F:/sap4.7/ker/NT/COMMON/INSTALL/ORADBUSR.SQL to: ./oradbusr.sql.
    INFO 2007-02-04 22:10:48
    Creating file C:\SAPinst ORACLE KERNEL\oradbusr.sql.
    INFO 2007-02-04 22:10:49
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:10:52
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    PHASE 2007-02-04 22:10:54
    Database Load
    INFO 2007-02-04 22:10:58
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:10:59
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:00
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:01
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:02
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:02
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:02
    Task files created
    INFO 2007-02-04 22:11:03
    Command files created
    INFO 2007-02-04 22:11:05
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:05
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-04 22:11:05
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 00:06:44
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 03:43:19
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 04:55:23
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 05:17:24
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 05:39:25
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 05:45:25
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 05:57:26
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:00:26
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:03:26
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:05:26
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:07:26
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:08:27
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:09:28
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:24:46
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:24:46
    Processes finished successfully
    INFO 2007-02-05 06:26:23
    Creating file C:\SAPinst ORACLE KERNEL\ddicora.sql.
    INFO 2007-02-05 06:26:25
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:26:30
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:26:32
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:26:43
    Moving file c:/oracle/ora90/database/initDRS.ora to: orig_init_ora_tmp.txt.
    INFO 2007-02-05 06:26:43
    Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: c:\oracle\ora90\database\initDRS.ora.
    INFO 2007-02-05 06:26:43
    Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
    INFO 2007-02-05 06:26:43
    Moving file c:/oracle/ora90/database/initDRS.ora to: orig_init_ora_tmp.txt.
    INFO 2007-02-05 06:26:43
    Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: c:\oracle\ora90\database\initDRS.ora.
    INFO 2007-02-05 06:26:43
    Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
    INFO 2007-02-05 06:26:43
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:26:45
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:26:48
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:26:52
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:26:55
    Creating file C:\SAPinst ORACLE KERNEL\brconnect.log.
    INFO 2007-02-05 06:26:55
    Changed working directory to C:\SAPinst ORACLE KERNEL.
    INFO 2007-02-05 06:26:55
    See 'D:\usr\sap\DRS\SYS\exe\run/brconnect -c -f crsyn -o SAPDRS' output in 'C:\SAPinst ORACLE KERNEL\brconnect.log'.
    ERROR 2007-02-05 06:26:55
    MOS-01012  PROBLEM: 'D:\usr\sap\DRS\SYS\exe\run/brconnect -c -f crsyn -o SAPDRS' returned with '128' which is not a defined as a success code.
    ERROR 2007-02-05 06:26:55
    FJS-00012  Error when executing script.
    kindly help me where i am going wrong.
    Yours friendly,
    Bharath.

    Hi Andreas,
    many thanks to you for the timely help.
    a.)I want to know why there is an error at brconnect ? why is it returning an error code (128) at UPDATE DATABASE STATISTICS stage.
    I have read in this forum itself that the UPDATE STATISTICS need not be suceesfully completed and we can edit database.r3s
    " ..on the other hand you can easily invoke the update statistics after the installation has ended (succesfully!)...edit DATABASE.R3S (or the appropriate template file you are using) by changing the status=ERROR to status=OK...this will let you finish the installation..-GreetZ, AH."
    I have searched for this file (database.r3s) in my system in vain Where can i find this file database.r3s?.
    Have i done any configuration mistake at the pre-installation stage. I have installed Oracle 9.0 using setup.exe of oracle. should i use sapserver.cmd to install oracle?.I havent applied any patch for Oracle 9.0
    Should I apply any patch just the same way we do for Oracle 8.1.x ?.  If so, where can i get the patch for Oracle 9.0 .?.
    b.) You said there should not be any spaces in file path (ex: C:/SAPinst ORACLE KERNEL/) . But I havent specified file path, the r/3 setup itself has created the directory path.
    c.) I want to know one thing- should we create a database before installing r/3. When we are installing Oracle 8/9. x what are the components that we are installing?
    Your friend,
    Bharath.

  • Getting "The product key is not valid. INS00140" error during Crystal Report 2013 installation

    We are getting “The product key is not valid. INS00140” error during Crystal Report 2013 installation. We are trying to install crystal report on Windows 7 64 bit OS.
    Can anyone help?

    What is CrystalReportsJava-2013? Where did this come from - download link? CD?
    - Ludek
    Senior Support Engineer AGS Product Support, Global Support Center Canada
      Follow us on Twitter

  • Errors During sap 4.7 installation-kindly help

    Hi friends,
    I am getting  3 errors during sap 4.7 installation.kindly help.
    i herewwith giving the error details:-
    1. R/3 Basis System Initialization DB-Connect Failed, Return code 000256
    2. R/3 Basis System: operating system call   Recv failed error no. 10054
    3. R/3 Basis System: Database connection Disconnected.
    After i have strated the sap server(MMC) first it will goto yellow and then green and againg goes to yellow color. message and dispatcher turned to gray.
    Pls help.your advise is considered very useful
    Thanks and Regards,
    willaim

    William
    What OS are you using please? (Windows I assume) On the surface, it sounds like a socket error. (i.e. the message server port is blocked by an existing application).
    The dispatcher will fail as a result of the message server not being available. Would you check and post the contents of the 'dev_ms" file in the work directory? Also, contents of the dev_disp would be helpful here also.
    Thanks,
    Tim

  • Error during early phase of installation

    Hello,
    I am facing an error during an installation. Our setup is as follows:
    empty Oracle 10.2.0.2 Database on HPUX
    Installation of BO Enterprise Server on Linux
    To meet expected performance issues and ressource consumption it should be a distributed installation.
    When I start the installation script I can enter some values. After adding the database parameters I am getting this error:
    Failure to validate the database credential has a potential to crash the database at a later stage. Enter the correct information. (STU00104)
    The error log in the installation directory is not very helpful:
    BusinessObjects Enterprise CMS: Unable to connect to the CMS system database ""B01"". Reason: ?Tj?A
    Has anyone had an error like this? Do you know whether there are other logfiles that can be forced to show up somehow?
    Thanks for hints or ideas,
    André

    Problem solved: The error has been caused by wrong versions of some database client libraries. Unfortunaly I was not able to find some helpful log entries so it has been a fluke...
    Best regards
    André

  • SDM deploy error in NW2004's

    Hi ,
    During installation of NW2004S I am facing the below error
    WARNING
    SDM call of deploySdaList ends with returncode 16. See output of logfile Z:\usr\sap\SAPinst\NW04S\SYSTEM\DB4\CENTRAL\AS\callSdmViaSapinst.log.
    callSdmviaSapinstlog:
    ERROR: Cannot connect to Host: [hostname] with user name: [J2EE_ADMIN]
                        Check your login information.
                        Exception is:
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
         at java.lang.Throwable.<init>(Throwable.java:180)
         at java.lang.Exception.<init>(Exception.java:29)
         at javax.naming.NamingException.<init>(NamingException.java:109)
         at com.sap.engine.services.jndi.persistent.exceptions.NamingException.<init>(NamingException.java:119)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:494)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:363)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.sap.engine.deploy.manager.DeployManagerImpl.checkCredentials(DeployManagerImpl.java:2983)
         at com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthMethodInvoker.invokeCheckCredentialsInternal(DeployManagerAuthMethodInvoker.java:51)
         at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:45)
         at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.java:32)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineOnlineDeployerImpl.checkLoginCredentials(EngineOnlineDeployerImpl.java:173)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performDeployment(EngineJ2EE620OnlineDeployerImpl.java:233)
         at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
         at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
         at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
         at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
         at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
         at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
         at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
         at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:120)
         at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:89)
         at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:179)
         at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:53)
         at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)
         at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)
         at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)
         at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)
         at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)
         at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)
         at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)
         at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:54)
         at com.sap.sdm.control.command.decorator.SyntaxChecker.execute(SyntaxChecker.java:37)
         at com.sap.sdm.control.command.Command.exec(Command.java:42)
         at SDM.main(SDM.java:21)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
         at java.lang.Throwable.<init>(Throwable.java:195)
         at java.lang.Exception.<init>(Exception.java:41)
         at java.security.GeneralSecurityException.<init>(GeneralSecurityException.java:43)
         at javax.security.auth.login.LoginException.<init>(LoginException.java:53)
         at com.sap.engine.services.security.exceptions.BaseLoginException.<init>(BaseLoginException.java:113)
         at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34)
         at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)
         ... 35 more
    Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/172.16.10.5,port=50004,localport=24156]
         at java.lang.Throwable.<init>(Throwable.java:195)
         at java.lang.Exception.<init>(Exception.java:41)
         at java.io.IOException.<init>(IOException.java:40)
         at java.io.EOFException.<init>(EOFException.java:44)
         at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:420)
         at java.lang.Thread.run(Thread.java:534)
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.checkLoginCredentials.DMEXC)
    Apr 24, 2008 7:48:48 PM  Info: Starting to save the repository
    Apr 24, 2008 7:48:52 PM  Info: Finished saving the repository
    Apr 24, 2008 7:48:52 PM  Info: Starting: Initial deployment: Selected software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.00.9.0.20060827113300''/'0' will be deployed.
    Apr 24, 2008 7:48:52 PM  Error: Aborted: software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.00.9.0.20060827113300''/'0':
    Failed deployment of SDAs:
    development component 'com.sap.ip.bi.biloggingconfig'/'sap.com'/'SAP AG'/'7.0009.20060825141640.0000'/'0' : aborted
    Please, look at error logs above for more information!
    Apr 24, 2008 7:48:52 PM  Info: Starting to save the repository
    Apr 24, 2008 7:48:56 PM  Info: Finished saving the repository
    Apr 24, 2008 7:48:56 PM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Apr 24, 2008 7:48:56 PM  Error: -
    At least one of the Deployments failed -
    Apr 24, 2008 7:49:03 PM  Info: Summarizing the deployment results:
    Apr 24, 2008 7:49:03 PM  Error: Aborted: /tmp/sid/Java1/J2EE_OSINDEP/UT/BIIBC09_0.SCA
    Apr 24, 2008 7:49:03 PM  Info: OK: /tmp/sid/Java1/J2EE_OSINDEP/UT/BIWEBAPP09_0.SCA
    Apr 24, 2008 7:49:03 PM  Info: OK: /tmp/sid/Java1/J2EE_OSINDEP/UT/BIBASES09_0.SCA
    Apr 24, 2008 7:49:03 PM  Error: Admitted: /tmp/sid/Java1/J2EE_OSINDEP/UT/BIREPPLAN09_0.SCA
    Apr 24, 2008 7:49:03 PM  Error: Admitted: /tmp/sid/Java1/J2EE_OSINDEP/UT/BIWDALV09_0.SCA
    Apr 24, 2008 7:49:03 PM  Error: Admitted: /tmp/sid/Java1/J2EE_OSINDEP/UT/VCKITBI09_0.SCA
    Apr 24, 2008 7:49:04 PM  Error: Processing error. Return code: 4
    thanks in advance

    hi prasanna ,
    please go through the logs of std_server & std_dispatcher and let me know the reason
    stdout/stderr redirect
    node name   : dispatcher
    pid         : 694
    system name :SID
    system nr.  : 00
    started at  : Thu May  1 18:59:21 2008
    [Thr  1] Thu May  1 18:59:26 2008
    [Thr  1] MtxInit: -2 0 0
    GC: initial heap(KB) 65536; maximum heap(KB) 2097152; virtual machine identifier C8C2406445003900;  heap identifier C8C2406445003900.
    GC 1: starting collection, reason  external thread attached.
    GC 1: collection starting 05/01/08 18:59:33
    GC 1: live objects 2615; collected objects 1646; collected(KB) 144.
    GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
    GC 1: current heap(KB) 6508; current threshold(KB) 65536.
    GC 1: collect (milliseconds) 67.
    GC 1: current cycle allocation(KB) 1911; previous cycle allocation(KB) 4155.
    GC 1: total weak references 0; cleared weak references 0.
    GC 1: total final references 6; cleared final references 0.
    GC 1: total phantom references 0; cleared phantom references 0.
    GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 1: collection ending 05/01/08 18:59:33
    Attaching Java program to /usr/sap/GBV/DVEBMGS00/j2ee/cluster/dispatcher/bin/boot/boot.jar.
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Loading: LogManager ... 12302 ms.
    Loading: PoolManager ... 93 ms.
    Loading: ThreadManager ... 1687 ms.
    Loading: IpVerificationManager ... 667 ms.
    Loading: ConnectionsManipulator ... 1166 ms.
    Loading: ClassLoaderManager ... 44 ms.
    Loading: ClusterManager ... 4756 ms.
    Loading: PortsManager ... 669 ms.
    Loading: LockingManager ... 3256 ms.
    Loading: ConfigurationManager ... GC 2: starting collection, threshold allocation reached.
    GC 2: collection starting 05/01/08 19:00:24
    GC 2: live objects 59229; collected objects 284349; collected(KB) 50255.
    GC 2: queued for finalization 0; total soft references 60; cleared soft references 0.
    GC 2: current heap(KB) 83164; current threshold(KB) 65536.
    GC 2: collect (milliseconds) 552.
    GC 2: current cycle allocation(KB) 5455; previous cycle allocation(KB) 66441.
    GC 2: total weak references 35; cleared weak references 0.
    GC 2: total final references 216; cleared final references 62.
    GC 2: total phantom references 0; cleared phantom references 0.
    GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 2: collection ending 05/01/08 19:00:24
    36868 ms.
    Loading: LicensingManager ... 642 ms.
    Loading: CacheManager ... 4029 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service security started. (1561 ms).
      Service licensing started. (1387 ms).
      Service sld started. (2637 ms).
      Service httptunneling started. (2648 ms).
      Service timeout started. (2472 ms).
      Service memory started. (2449 ms).
      Service r3startup started. (2340 ms).
      Service webservices started. (2981 ms).
      Service jmx_notification started. (1773 ms).
      Service keystore started. (2061 ms).
    GC 3: starting collection, threshold allocation reached.
    GC 3: collection starting 05/01/08 19:00:56
      Service iiop started. (2812 ms).
      Service shell started. (3721 ms).
    GC 3: live objects 103453; collected objects 372425; collected(KB) 56714.
    GC 3: queued for finalization 0; total soft references 162; cleared soft references 0.
    GC 3: current heap(KB) 109196; current threshold(KB) 65536.
    GC 3: collect (milliseconds) 1198.
    GC 3: current cycle allocation(KB) 5183; previous cycle allocation(KB) 65548.
    GC 3: total weak references 198; cleared weak references 0.
    GC 3: total final references 643; cleared final references 367.
    GC 3: total phantom references 0; cleared phantom references 0.
    GC 3: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 3: collection ending 05/01/08 19:00:57
      Service telnet started. (298 ms).
      Service ssl started. (9290 ms).
    May 1, 2008 7:01:05 PM                com.sap.engine.services.ssl [SAPEngine_System_Thread[impl:6]_20] Fatal: Source: com.sap.engine.services.keystore.exceptions.BaseRemoteException: Remote call errored; Description: SSL server identity keystore view not found; Consequences: SSL transport protocol not available; Countermeasures:create keystore view "service_ssl" with at least one private key entry, restart the SSL service
      Service p4 started. (13628 ms).
      Service classload started. (0 ms).
      Service log_configurator started. (15935 ms).
      Service configuration started. (23 ms).
      Service http started. (4921 ms).
      Service jmx started. (14325 ms).
      Service basicadmin started. (3789 ms).
      Service adminadapter started. (52 ms).
      Service jms_provider started. (17803 ms).
    GC 4: starting collection, threshold allocation reached.
    GC 4: collection starting 05/01/08 19:01:41
      Service tc.monitoring.logviewer started. (20999 ms).
    GC 4: live objects 155285; collected objects 260747; collected(KB) 57227.
    GC 4: queued for finalization 0; total soft references 492; cleared soft references 0.
    GC 4: current heap(KB) 132084; current threshold(KB) 65536.
    GC 4: collect (milliseconds) 3227.
    GC 4: current cycle allocation(KB) 12710; previous cycle allocation(KB) 65591.
    GC 4: total weak references 429; cleared weak references 0.
    GC 4: total final references 1238; cleared final references 771.
    GC 4: total phantom references 0; cleared phantom references 0.
    GC 4: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 4: collection ending 05/01/08 19:01:45
      Service monitor started. (26655 ms).
    ServiceManager started for 72516 ms.
    Framework started for 139690 ms.
    SAP J2EE Engine Version 7.00   PatchLevel is running!
    PatchLevel September 11, 2006 16:35 GMT
    >
    Login :GC 5: starting collection, threshold allocation reached.
    GC 5: collection starting 05/01/08 19:56:01
    GC 5: live objects 186102; collected objects 462345; collected(KB) 60574.
    GC 5: queued for finalization 0; total soft references 1320; cleared soft references 0.
    GC 5: current heap(KB) 144312; current threshold(KB) 65536.
    GC 5: collect (milliseconds) 18649.
    GC 5: current cycle allocation(KB) 0; previous cycle allocation(KB) 65543.
    GC 5: total weak references 654; cleared weak references 10.
    GC 5: total final references 1171; cleared final references 741.
    GC 5: total phantom references 0; cleared phantom references 0.
    GC 5: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 5: collection ending 05/01/08 19:56:20
    SAP J2EE Engine Version 7.00   PatchLevel is shutting down!  PatchLevel September 11, 2006 16:35 GMT
    Stopping services.
      Service tc.monitoring.logviewer stopped. (654 ms)
      Service classload stopped. (210 ms)
      Service p4 stopped. (450 ms)
      Service ssl stopped. (1040 ms)
      Service keystore stopped. (469 ms)
      Service iiop stopped. (2129 ms)
      Service adminadapter stopped. (164 ms)
      Service monitor stopped. (1193 ms)
      Service security stopped. (6 ms)
      Service basicadmin stopped. (52 ms)
      Service jms_provider stopped. (1201 ms)
      Service jmx stopped. (69 ms)
      Service webservices stopped. (25 ms)
      Service sld stopped. (4 ms)
      Service telnet stopped. (1105 ms)
      Service http stopped. (1089 ms)
      Service timeout stopped. (7 ms)
      Service configuration stopped. (93 ms)
      Service log_configurator stopped. (66 ms)
      Service memory stopped. (15 ms)
      Service r3startup stopped. (38 ms)
      Service licensing stopped. (39 ms)
      Service httptunneling stopped. (35 ms)
      Service shell stopped. (168 ms)
      Service jmx_notification stopped. (5 ms)
    stdout/stderr redirect
    node name   : dispatcher
    pid         : 694
    system name : SID
    system nr.  : 00
    started at  : Thu May  1 20:02:03 2008
    [Thr  1] Thu May  1 20:02:06 2008
    [Thr  1] MtxInit: -2 0 0
    GC: initial heap(KB) 65536; maximum heap(KB) 2097152; virtual machine identifier F83A6D6E7B003900;  heap identifier F83A6D6E7B003900.
    GC 1: starting collection, reason  external thread attached.
    GC 1: collection starting 05/01/08 20:02:14
    GC 1: live objects 2817; collected objects 1704; collected(KB) 149.
    GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
    GC 1: current heap(KB) 6544; current threshold(KB) 65536.
    GC 1: collect (milliseconds) 54.
    GC 1: current cycle allocation(KB) 1911; previous cycle allocation(KB) 4155.
    GC 1: total weak references 0; cleared weak references 0.
    GC 1: total final references 6; cleared final references 0.
    GC 1: total phantom references 0; cleared phantom references 0.
    GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 1: collection ending 05/01/08 20:02:14
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Loading: LogManager ... 3104 ms.
    Loading: PoolManager ... 40 ms.
    Loading: ThreadManager ... 539 ms.
    Loading: IpVerificationManager ... 107 ms.
    Loading: ConnectionsManipulator ... 266 ms.
    Loading: ClassLoaderManager ... 93 ms.
    Loading: ClusterManager ... 1040 ms.
    Loading: PortsManager ... 57 ms.
    Loading: LockingManager ... 511 ms.
    Loading: ConfigurationManager ... GC 2: starting collection, threshold allocation reached.
    GC 2: collection starting 05/01/08 20:02:29
    GC 2: live objects 107477; collected objects 418716; collected(KB) 64931.
    GC 2: queued for finalization 0; total soft references 59; cleared soft references 0.
    GC 2: current heap(KB) 103592; current threshold(KB) 65536.
    GC 2: collect (milliseconds) 1114.
    GC 2: current cycle allocation(KB) 22125; previous cycle allocation(KB) 65803.
    GC 2: total weak references 30; cleared weak references 0.
    GC 2: total final references 218; cleared final references 65.
    GC 2: total phantom references 0; cleared phantom references 0.
    GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 2: collection ending 05/01/08 20:02:30
    13732 ms.
    Loading: LicensingManager ... 294 ms.
    Loading: CacheManager ... 2235 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service security started. (262 ms).
      Service sld started. (371 ms).
      Service httptunneling started. (452 ms).
      Service licensing started. (234 ms).
      Service r3startup started. (419 ms).
      Service webservices started. (416 ms).
      Service memory started. (600 ms).
      Service timeout started. (619 ms).
      Service jmx_notification started. (451 ms).
      Service iiop started. (631 ms).
      Service keystore started. (725 ms).
    GC 3: starting collection, threshold allocation reached.
    GC 3: collection starting 05/01/08 20:02:46
    GC 3: live objects 98384; collected objects 238422; collected(KB) 42389.
    GC 3: queued for finalization 0; total soft references 142; cleared soft references 0.
    GC 3: current heap(KB) 112560; current threshold(KB) 65536.
    GC 3: collect (milliseconds) 452.
    GC 3: current cycle allocation(KB) 4333; previous cycle allocation(KB) 65537.
    GC 3: total weak references 193; cleared weak references 0.
    GC 3: total final references 652; cleared final references 367.
    GC 3: total phantom references 0; cleared phantom references 0.
    GC 3: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 3: collection ending 05/01/08 20:02:46
      Service ssl started. (794 ms).
      Service shell started. (2602 ms).
      Service jmx started. (1587 ms).
      Service telnet started. (138 ms).
      Service p4 started. (6246 ms).
      Service classload started. (1 ms).
      Service log_configurator started. (7255 ms).
      Service configuration started. (24 ms).
      Service http started. (1365 ms).
      Service jms_provider started. (1628 ms).
      Service basicadmin started. (1209 ms).
      Service adminadapter started. (35 ms).
    GC 4: starting collection, threshold allocation reached.
    GC 4: collection starting 05/01/08 20:02:56
      Service tc.monitoring.logviewer started. (2642 ms).
    GC 4: live objects 160497; collected objects 282434; collected(KB) 57082.
    GC 4: queued for finalization 0; total soft references 491; cleared soft references 0.
    GC 4: current heap(KB) 139048; current threshold(KB) 65536.
    GC 4: collect (milliseconds) 386.
    GC 4: current cycle allocation(KB) 14679; previous cycle allocation(KB) 65740.
    GC 4: total weak references 419; cleared weak references 0.
    GC 4: total final references 1406; cleared final references 896.
    GC 4: total phantom references 0; cleared phantom references 0.
    GC 4: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 4: collection ending 05/01/08 20:02:56
      Service monitor started. (4371 ms).
    ServiceManager started for 19752 ms.
    Framework started for 42188 ms.
    SAP J2EE Engine Version 7.00   PatchLevel is running!
    PatchLevel September 11, 2006 16:35 GMT
    >
    Login :GC 5: starting collection, threshold allocation reached.
    GC 5: collection starting 05/01/08 20:38:07
    GC 5: live objects 185219; collected objects 409132; collected(KB) 57626.
    GC 5: queued for finalization 0; total soft references 778; cleared soft references 0.
    GC 5: current heap(KB) 142692; current threshold(KB) 65536.
    GC 5: collect (milliseconds) 15208.
    GC 5: current cycle allocation(KB) 423; previous cycle allocation(KB) 65588.
    GC 5: total weak references 624; cleared weak references 11.
    GC 5: total final references 1173; cleared final references 717.
    GC 5: total phantom references 0; cleared phantom references 0.
    GC 5: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 5: collection ending 05/01/08 20:38:22
    SAP J2EE Engine Version 7.00   PatchLevel is shutting down!  PatchLevel September 11, 2006 16:35 GMT
    Stopping services.
      Service tc.monitoring.logviewer stopped. (1054 ms)
      Service classload stopped. (174 ms)
      Service p4 stopped. (555 ms)
      Service ssl stopped. (403 ms)
      Service keystore stopped. (69 ms)
      Service iiop stopped. (3292 ms)
      Service adminadapter stopped. (417 ms)
      Service monitor stopped. (3190 ms)
      Service security stopped. (24 ms)
      Service basicadmin stopped. (431 ms)
      Service jms_provider stopped. (1217 ms)
      Service jmx stopped. (126 ms)
      Service webservices stopped. (50 ms)
      Service sld stopped. (17 ms)
      Service telnet stopped. (1357 ms)
      Service http stopped. (1204 ms)
      Service timeout stopped. (38 ms)
      Service configuration stopped. (390 ms)
      Service log_configurator stopped. (232 ms)
      Service memory stopped. (97 ms)
      Service r3startup stopped. (126 ms)
      Service licensing stopped. (126 ms)
      Service httptunneling stopped. (61 ms)
      Service shell stopped. (200 ms)
      Service jmx_notification stopped. (21 ms)
    stdout/stderr redirect
    node name   : dispatcher
    pid         : 694
    system name : GBV
    system nr.  : 00
    started at  : Thu May  1 21:06:38 2008
    [Thr  1] MtxInit: -2 0 0
    GC: initial heap(KB) 65536; maximum heap(KB) 2097152; virtual machine identifier C6F3A9F0B8003900;  heap identifier C6F3A9F0B8003900.
    GC 1: starting collection, reason  external thread attached.
    GC 1: collection starting 05/01/08 21:06:47
    GC 1: live objects 2649; collected objects 1704; collected(KB) 149.
    GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
    GC 1: current heap(KB) 6544; current threshold(KB) 65536.
    GC 1: collect (milliseconds) 54.
    GC 1: current cycle allocation(KB) 1911; previous cycle allocation(KB) 4155.
    GC 1: total weak references 0; cleared weak references 0.
    GC 1: total final references 6; cleared final references 0.
    GC 1: total phantom references 0; cleared phantom references 0.
    GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 1: collection ending 05/01/08 21:06:47
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Loading: LogManager ... 3558 ms.
    Loading: PoolManager ... 51 ms.
    Loading: ThreadManager ... 394 ms.
    Loading: IpVerificationManager ... 119 ms.
    Loading: ConnectionsManipulator ... 120 ms.
    Loading: ClassLoaderManager ... 68 ms.
    Loading: ClusterManager ... 1019 ms.
    Loading: PortsManager ... 80 ms.
    Loading: LockingManager ... 695 ms.
    Loading: ConfigurationManager ... GC 2: starting collection, threshold allocation reached.
    GC 2: collection starting 05/01/08 21:07:04
    GC 2: live objects 58479; collected objects 282635; collected(KB) 50395.
    GC 2: queued for finalization 0; total soft references 58; cleared soft references 0.
    GC 2: current heap(KB) 82336; current threshold(KB) 65536.
    GC 2: collect (milliseconds) 332.
    GC 2: current cycle allocation(KB) 3761; previous cycle allocation(KB) 65896.
    GC 2: total weak references 30; cleared weak references 0.
    GC 2: total final references 213; cleared final references 62.
    GC 2: total phantom references 0; cleared phantom references 0.
    GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 2: collection ending 05/01/08 21:07:05
    12764 ms.
    Loading: LicensingManager ... 192 ms.
    Loading: CacheManager ... 956 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service security started. (247 ms).
      Service sld started. (380 ms).
      Service httptunneling started. (462 ms).
      Service webservices started. (501 ms).
      Service r3startup started. (447 ms).
      Service licensing started. (307 ms).
      Service memory started. (472 ms).
      Service timeout started. (569 ms).
      Service jmx_notification started. (546 ms).
      Service iiop started. (684 ms).
    GC 3: starting collection, threshold allocation reached.
    GC 3: collection starting 05/01/08 21:07:15
      Service keystore started. (646 ms).
      Service shell started. (786 ms).
      Service telnet started. (64 ms).
      Service ssl started. (687 ms).
      Service jmx started. (1865 ms).
    GC 3: live objects 128135; collected objects 368341; collected(KB) 55808.
    GC 3: queued for finalization 0; total soft references 137; cleared soft references 0.
    GC 3: current heap(KB) 117676; current threshold(KB) 65536.
    GC 3: collect (milliseconds) 4067.
    GC 3: current cycle allocation(KB) 14745; previous cycle allocation(KB) 65575.
    GC 3: total weak references 187; cleared weak references 0.
    GC 3: total final references 635; cleared final references 368.
    GC 3: total phantom references 0; cleared phantom references 0.
    GC 3: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 3: collection ending 05/01/08 21:07:19
      Service p4 started. (5623 ms).
      Service classload started. (0 ms).
      Service log_configurator started. (7555 ms).
      Service configuration started. (7 ms).
      Service basicadmin started. (746 ms).
      Service adminadapter started. (28 ms).
    GC 4: starting collection, threshold allocation reached.
    GC 4: collection starting 05/01/08 21:07:25
      Service tc.monitoring.logviewer started. (2513 ms).
    GC 4: live objects 169322; collected objects 304225; collected(KB) 58510.
    GC 4: queued for finalization 0; total soft references 478; cleared soft references 0.
    GC 4: current heap(KB) 144236; current threshold(KB) 65536.
    GC 4: collect (milliseconds) 1835.
    GC 4: current cycle allocation(KB) 21225; previous cycle allocation(KB) 65597.
    GC 4: total weak references 411; cleared weak references 0.
    GC 4: total final references 1345; cleared final references 861.
    GC 4: total phantom references 0; cleared phantom references 0.
    GC 4: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 4: collection ending 05/01/08 21:07:27
      Service jms_provider started. (4492 ms).
      Service http started. (4399 ms).
      Service monitor started. (29724 ms).
    ServiceManager started for 43503 ms.
    Framework started for 64037 ms.
    SAP J2EE Engine Version 7.00   PatchLevel is running!
    PatchLevel September 11, 2006 16:35 GMT
    >
    Login :GC 5: starting collection, threshold allocation reached.
    GC 5: collection starting 05/01/08 21:31:12
    GC 5: live objects 184326; collected objects 378511; collected(KB) 56530.
    GC 5: queued for finalization 0; total soft references 801; cleared soft references 0.
    GC 5: current heap(KB) 144508; current threshold(KB) 65536.
    GC 5: collect (milliseconds) 74315.
    GC 5: current cycle allocation(KB) 49; previous cycle allocation(KB) 65589.
    GC 5: total weak references 706; cleared weak references 10.
    GC 5: total final references 1138; cleared final references 684.
    GC 5: total phantom references 0; cleared phantom references 0.
    GC 5: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 5: collection ending 05/01/08 21:32:26
    GC 6: starting collection, threshold allocation reached.
    GC 6: collection starting 05/02/08 03:03:17
    GC 6: live objects 199214; collected objects 762329; collected(KB) 61062.
    GC 6: queued for finalization 0; total soft references 779; cleared soft references 0.
    GC 6: current heap(KB) 168484; current threshold(KB) 65536.
    GC 6: collect (milliseconds) 12090.
    GC 6: current cycle allocation(KB) 341; previous cycle allocation(KB) 65553.
    GC 6: total weak references 589; cleared weak references 0.
    GC 6: total final references 1688; cleared final references 1235.
    GC 6: total phantom references 0; cleared phantom references 0.
    GC 6: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 6: collection ending 05/02/08 03:03:29
    stdout/stderr redirect
    node name   : server0
    pid         : 694
    system name : GBV
    system nr.  : 00
    started at  : Thu May  1 18:59:21 2008
    [Thr  1] Thu May  1 18:59:26 2008
    [Thr  1] MtxInit: -2 0 0
    GC: initial heap(KB) 1048576; maximum heap(KB) 4194304; virtual machine identifier F9A676BFAF003900;  heap identifier F9A676BFAF003900.
    GC 1: starting collection, reason  external thread attached.
    GC 1: collection starting 05/01/08 18:59:33
    GC 1: live objects 2518; collected objects 1665; collected(KB) 146.
    GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
    GC 1: current heap(KB) 6544; current threshold(KB) 1048576.
    GC 1: collect (milliseconds) 53.
    GC 1: current cycle allocation(KB) 1911; previous cycle allocation(KB) 4155.
    GC 1: total weak references 0; cleared weak references 0.
    GC 1: total final references 6; cleared final references 0.
    GC 1: total phantom references 0; cleared phantom references 0.
    GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 1: collection ending 05/01/08 18:59:33
    Attaching Java program to /usr/sap/GBV/DVEBMGS00/j2ee/cluster/server0/bin/boot/boot.jar.
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Loading: LogManager ... Attaching Java program to /usr/sap/GBV/DVEBMGS00/j2ee/cluster/server0/bin/system/bytecode.jar.
    12427 ms.
    Loading: PoolManager ... 7 ms.
    Loading: ApplicationThreadManager ... 1200 ms.
    Loading: ThreadManager ... 639 ms.
    Loading: IpVerificationManager ... 10 ms.
    Loading: ClassLoaderManager ... 757 ms.
    Loading: ClusterManager ... 5440 ms.
    Loading: LockingManager ... 3369 ms.
    Loading: ConfigurationManager ... 36874 ms.
    Loading: LicensingManager ... 642 ms.
    Loading: CacheManager ... 4042 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service runtimeinfo started. (975 ms).
      Service timeout started. (2182 ms).
      Service memory started. (1863 ms).
      Service userstore started. (1000 ms).
      Service jmx_notification started. (867 ms).
      Service cross started. (3029 ms).
      Service file started. (3829 ms).
      Service trex.service started. (12103 ms).
      Service p4 started. (11079 ms).
      Service classpath_resolver started. (858 ms).
      Service log_configurator started. (19432 ms).
      Service locking started. (4 ms).
      Service http started. (15405 ms).
      Service naming started. (17125 ms).
      Service failover started. (840 ms).
      Service appclient started. (1785 ms).
      Service javamail started. (2268 ms).
      Service ts started. (2197 ms).
      Service licensing started. (6 ms).
      Service jmsconnector started. (2781 ms).
      Service iiop started. (5166 ms).
      Service connector started. (3628 ms).
      Service deploy started. (35090 ms).
      Service MigrationService started. (634 ms).
      Service bimmrdeployer started. (171 ms).
      Service configuration started. (1237 ms).
      Service webservices started. (25127 ms).
      Service dbpool started. (24840 ms).
      Service com.sap.security.core.ume.service started. (60071 ms).
      Service security started. (11292 ms).
      Service shell started. (379 ms).
      Service tceCATTPingservice started. (701 ms).
      Service telnet started. (1087 ms).
      Service applocking started. (3204 ms).
      Service webdynpro started. (2064 ms).
      Service classload started. (7995 ms).
      Service cafummetadata~imp started. (1979 ms).
      Service jmx started. (1446 ms).
      Service tc.monitoring.logviewer started. (17911 ms).
      Service keystore started. (36345 ms).
      Service ssl started. (829 ms).
      Service basicadmin started. (29864 ms).
      Service cafumrelgroups~imp started. (41597 ms).
      Service dsr started. (35451 ms).
      Service com.adobe~LicenseService started. (2324 ms).
      Service servlet_jsp started. (52833 ms).
      Service tcsecsecurestorage~service started. (7895 ms).
      Service com.adobe~DataManagerService started. (53112 ms).
      Service adminadapter started. (23450 ms).
      Service monitor started. (22187 ms).
      Service com.adobe~DocumentServicesBinaries2 started. (499 ms).
      Service com.adobe~DocumentServicesConfiguration started. (12876 ms).
      Service com.adobe~FontManagerService started. (4482 ms).
      Service ejb started. (87561 ms).
      Service com.adobe~DocumentServicesLicenseSupportService started. (3687 ms).
      Service com.adobe~PDFManipulation started. (2417 ms).
      Service com.adobe~TrustManagerService started. (1811 ms).
      Service tcsecdestinations~service started. (26759 ms).
      Service tcsecwssec~service started. (16232 ms).
      Service apptracing started. (29230 ms).
      Service com.adobe~DocumentServicesDestProtoService started. (2891 ms).
      Service CUL started. (84303 ms).
      Service rfcengine started. (12183 ms).
      Service pmi started. (2564 ms).
      Service com.adobe~XMLFormService started. (14499 ms).
      Service cafruntimeconnectivity~impl started. (269831 ms).
      Service sld started. (38976 ms).
      Service tcsecvsi~service started. (8136 ms).
      Service jms_provider started. (119482 ms).
    ServiceManager started for 300168 ms.
    Framework started for 367378 ms.
    SAP J2EE Engine Version 7.00   PatchLevel is running!
    PatchLevel September 11, 2006 16:35 GMT
    >
    Login :GC 2: starting collection, threshold allocation reached.
    GC 2: collection starting 05/01/08 19:07:44
    GC 2: live objects 657606; collected objects 5135128; collected(KB) 936066.
    GC 2: queued for finalization 0; total soft references 6782; cleared soft references 0.
    GC 2: current heap(KB) 1196680; current threshold(KB) 1048576.
    GC 2: collect (milliseconds) 76581.
    GC 2: current cycle allocation(KB) 54165; previous cycle allocation(KB) 1048613.
    GC 2: total weak references 2318; cleared weak references 33.
    GC 2: total final references 23528; cleared final references 21721.
    GC 2: total phantom references 0; cleared phantom references 0.
    GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 2: collection ending 05/01/08 19:09:01
    GC 3: starting collection, threshold allocation reached.
    GC 3: collection starting 05/01/08 19:15:13
    GC 3: collected class sun/reflect/GeneratedMethodAccessor3630385287.
    GC 4: starting collection, reason  stop the world collection.
    GC 3: live objects 1309097; collected objects 5717926; collected(KB) 1021549.
    GC 3: queued for finalization 0; total soft references 9700; cleared soft references 0.
    GC 3: current heap(KB) 1603768; current threshold(KB) 1048576.
    GC 3: collect (milliseconds) 148590.
    GC 3: current cycle allocation(KB) 49; previous cycle allocation(KB) 1350524.
    GC 3: total weak references 3025; cleared weak references 5.
    GC 3: total final references 18457; cleared final references 16313.
    GC 3: total phantom references 0; cleared phantom references 0.
    GC 3: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 3: collection ending 05/01/08 19:17:41
    GC 4: collection starting 05/01/08 19:17:41
    GC 4: collected class com/sap/engine/admin/model/monitoring/j2eeimpl/Messages.
    GC 4: live objects 1040398; collected objects 2212819; collected(KB) 296348.
    GC 4: queued for finalization 0; total soft references 10054; cleared soft references 0.
    GC 4: current heap(KB) 1585208; current threshold(KB) 1048576.
    GC 4: collect (milliseconds) 2101.
    GC 4: current cycle allocation(KB) 49; previous cycle allocation(KB) 0.
    GC 4: total weak references 3191; cleared weak references 50.
    GC 4: total final references 3574; cleared final references 1377.
    GC 4: total phantom references 0; cleared phantom references 0.
    GC 4: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 4: collection ending 05/01/08 19:17:44
    SAP J2EE Engine Version 7.00   PatchLevel is shutting down!  PatchLevel September 11, 2006 16:35 GMT
    Stopping services.
      Service rfcengine stopped. (518 ms)
      Service ejb stopped. (20000 ms) - Timeout expired.
      Service failover stopped. (75 ms)
      Service classload stopped. (178 ms)
      Service cafumrelgroups~imp stopped. (275 ms)
      Service telnet stopped. (13 ms)
      Service webdynpro stopped. (57 ms)
      Service tceCATTPingservice stopped. (6 ms)
      Service shell stopped. (705 ms)
      Service jms_provider stopped. (416 ms)
      Service com.adobe~TrustManagerService stopped. (341 ms)
      Service sld stopped. (62 ms)
      Service ssl stopped. (19 ms)
      Service tcsecvsi~service stopped. (202 ms)
      Service pmi stopped. (743 ms)
      Service com.adobe~DocumentServicesDestProtoService stopped. (161 ms)
      Service tcsecdestinations~service stopped. (14 ms)
      Service com.adobe~DocumentServicesConfiguration stopped. (50 ms)
      Service tcsecwssec~service stopped. (66 ms)
      Service tcsecsecurestorage~service stopped. (0 ms)
      Service keystore stopped. (85 ms)
      Service servlet_jsp stopped. (20000 ms) - Timeout expired.
      Service dsr stopped. (464 ms)
      Service cafummetadata~imp stopped. (68 ms)
      Service applocking stopped. (56 ms)
    stdout/stderr redirect
    node name   : server0
    pid         : 694
    system name : GBV
    system nr.  : 00
    started at  : Thu May  1 20:02:28 2008
    [Thr  1] Thu May  1 20:02:31 2008
    [Thr  1] MtxInit: -2 0 0
    GC: initial heap(KB) 1048576; maximum heap(KB) 4194304; virtual machine identifier D45A23E848003900;  heap identifier D45A23E848003900.
    GC 1: starting collection, reason  external thread attached.
    GC 1: collection starting 05/01/08 20:02:36
    GC 1: live objects 2329; collected objects 1650; collected(KB) 145.
    GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
    GC 1: current heap(KB) 5484; current threshold(KB) 1048576.
    GC 1: collect (milliseconds) 57.
    GC 1: current cycle allocation(KB) 864; previous cycle allocation(KB) 4155.
    GC 1: total weak references 0; cleared weak references 0.
    GC 1: total final references 6; cleared final references 0.
    GC 1: total phantom references 0; cleared phantom references 0.
    GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 1: collection ending 05/01/08 20:02:36
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Loading: LogManager ... 1580 ms.
    Loading: PoolManager ... 47 ms.
    Loading: ApplicationThreadManager ... 348 ms.
    Loading: ThreadManager ... 139 ms.
    Loading: IpVerificationManager ... 34 ms.
    Loading: ClassLoaderManager ... 108 ms.
    Loading: ClusterManager ... 1194 ms.
    Loading: LockingManager ... 482 ms.
    Loading: ConfigurationManager ... 9102 ms.
    Loading: LicensingManager ... 62 ms.
    Loading: CacheManager ... 761 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service runtimeinfo started. (164 ms).
      Service cross started. (288 ms).
      Service memory started. (332 ms).
      Service timeout started. (555 ms).
      Service userstore started. (5 ms).
      Service file started. (1915 ms).
      Service trex.service started. (1695 ms).
      Service jmx_notification started. (202 ms).
      Service p4 started. (1638 ms).
      Service classpath_resolver started. (210 ms).
      Service log_configurator started. (41195 ms).
      Service locking started. (3 ms).
      Service deploy started. (41554 ms).
      Service http started. (2008 ms).
      Service MigrationService started. (398 ms).
      Service bimmrdeployer started. (134 ms).
      Service naming started. (2915 ms).
      Service failover started. (289 ms).
      Service jmsconnector started. (848 ms).
      Service javamail started. (836 ms).
      Service appclient started. (678 ms).
      Service ts started. (981 ms).
      Service licensing started. (27 ms).
      Service connector started. (2930 ms).
      Service configuration started. (983 ms).
      Service iiop started. (4286 ms).
      Service webservices started. (13478 ms).
      Service dbpool started. (24229 ms).
      Service com.sap.security.core.ume.service started. (22463 ms).
      Service security started. (5515 ms).
      Service shell started. (270 ms).
      Service tceCATTPingservice started. (60 ms).
      Service applocking started. (690 ms).
      Service telnet started. (228 ms).
      Service classload started. (1409 ms).
      Service webdynpro started. (1192 ms).
      Service keystore started. (1750 ms).
      Service ssl started. (166 ms).
      Service jmx started. (2980 ms).
      Service dsr started. (2423 ms).
      Service tcsecsecurestorage~service started. (1903 ms).
      Service tcsecwssec~service started. (1804 ms).
      Service ejb started. (9909 ms).
      Service cafummetadata~imp started. (9484 ms).
      Service basicadmin started. (5061 ms).
      Service servlet_jsp started. (12051 ms).
      Service com.adobe~DataManagerService started. (5543 ms).
      Service com.adobe~LicenseService started. (1450 ms).
      Service tcsecdestinations~service started. (9840 ms).
      Service com.adobe~DocumentServicesConfiguration started. (4484 ms).
      Service rfcengine started. (6033 ms).
      Service com.adobe~DocumentServicesBinaries2 started. (2353 ms).
      Service tc.monitoring.logviewer started. (14836 ms).
      Service pmi started. (998 ms).
      Service com.adobe~FontManagerService started. (3991 ms).
      Service com.adobe~DocumentServicesDestProtoService started. (2826 ms).
      Service com.adobe~PDFManipulation started. (1639 ms).
      Service com.adobe~DocumentServicesLicenseSupportService started. (2373 ms).
      Service com.adobe~TrustManagerService started. (1498 ms).
      Service sld started. (18028 ms).
      Service CUL started. (17248 ms).
      Service apptracing started. (8930 ms).
      Service cafumrelgroups~imp started. (15606 ms).
      Service adminadapter started. (10318 ms).
      Service tcsecvsi~service started. (8219 ms).
      Service com.adobe~XMLFormService started. (5849 ms).
      Service cafruntimeconnectivity~impl started. (139211 ms).
      Service monitor started. (15138 ms).
      Service jms_provider started. (52820 ms).
      Service com.sap.portal.prt.sapj2ee started. (5383 ms).
      Service prtbridge started. (39544 ms).
    ServiceManager started for 207093 ms.
    Framework started for 221438 ms.
    SAP J2EE Engine Version 7.00   PatchLevel is running!
    PatchLevel September 11, 2006 16:35 GMT
    >
    Login :GC 2: starting collection, threshold allocation reached.
    GC 2: collection starting 05/01/08 20:08:08
    GC 2: live objects 755454; collected objects 5496751; collected(KB) 930552.
    GC 2: queued for finalization 0; total soft references 6634; cleared soft references 0.
    GC 2: current heap(KB) 1153380; current threshold(KB) 1048576.
    GC 2: collect (milliseconds) 47233.
    GC 2: current cycle allocation(KB) 62234; previous cycle allocation(KB) 1048576.
    GC 2: total weak references 2795; cleared weak references 28.
    GC 2: total final references 17170; cleared final references 15377.
    GC 2: total phantom references 0; cleared phantom references 0.
    GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 2: collection ending 05/01/08 20:08:56
    GC 3: starting collection, threshold allocation reached.
    GC 3: collection starting 05/01/08 20:11:21
    GC 3: collected class com/sap/engine/admin/model/monitoring/j2eeimpl/Messages.
    GC 3: live objects 1246857; collected objects 6993092; collected(KB) 1017416.
    GC 3: queued for finalization 0; total soft references 9636; cleared soft references 0.
    GC 3: current heap(KB) 1399752; current threshold(KB) 1048576.
    GC 3: collect (milliseconds) 10774.
    GC 3: current cycle allocation(KB) 42367; previous cycle allocation(KB) 1048625.
    GC 3: total weak references 3387; cleared weak references 10.
    GC 3: total final references 11622; cleared final references 9210.
    GC 3: total phantom references 0; cleared phantom references 0.
    GC 3: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 3: collection ending 05/01/08 20:11:32
    May 1, 2008 8:11:42 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.ivs.iviewservice
    May 1, 2008 8:11:42 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.netweaver.bc.util
    May 1, 2008 8:11:42 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.ivs.api_portalpcm
    May 1, 2008 8:11:42 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.pcd.glservice
    May 1, 2008 8:11:42 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.pcm.admin.apiservice
    May 1, 2008 8:11:42 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.runtime.config
    May 1, 2008 8:11:42 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.usermanagement
    May 1, 2008 8:11:42 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.ivs.api_landscape
    May 1, 2008 8:11:56 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.pcd.glservice
    May 1, 2008 8:11:56 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.contentmigration.contentmigrationservice
    May 1, 2008 8:11:56 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.httpconnectivity.urlfetcherservice
    May 1, 2008 8:11:56 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.ivs.connectorservice
    May 1, 2008 8:11:56 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.runtime.application.jcoclient
    May 1, 2008 8:11:56 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.ivs.systemlandscapeservice
    May 1, 2008 8:11:56 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.ivs.iviewservice
    May 1, 2008 8:11:56 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.themes.designservice
    May 1, 2008 8:11:56 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.themes.lafservice
    May 1, 2008 8:11:56 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.productivity.resolverservice
    May 1, 2008 8:11:56 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/com.sap.portal.runtime.config
    May 1, 2008 8:11:56 PM           com.sap.portal.prt.sapj2ee.error [SAPEngine_System_Thread[impl:5]_49] Fatal: Exception while starting: sap.com/irj
    SAP J2EE Engine Version 7.00   PatchLevel is shutting down!  PatchLevel September 11, 2006 16:35 GMT
    Stopping services.
      Service com.sap.portal.prt.sapj2ee stopped. (176 ms)
      Service com.adobe~DocumentServicesLicenseSupportService stopped. (818 ms)
      Service sld stopped. (118 ms)
      Service com.adobe~DocumentServicesBinaries2 stopped. (259 ms)
      Service rfcengine stopped. (92 ms)
      Service cafumrelgroups~imp stopped. (50 ms)
      Service cafummetadata~imp stopped. (71 ms)
    GC 4: starting collection, threshold allocation reached.
    GC 4: collection starting 05/01/08 20:59:48
      Service applocking stopped. (410 ms)
      Service com.adobe~LicenseService stopped. (29 ms)
      Service tc.monitoring.logviewer stopped. (5966 ms)
      Service com.adobe~TrustManagerService stopped. (205 ms)
      Service com.adobe~XMLFormService stopped. (312 ms)
      Service com.adobe~FontManagerService stopped. (193 ms)
      Service com.adobe~PDFManipulation stopped. (335 ms)
      Service com.adobe~DocumentServicesDestProtoService stopped. (330 ms)
      Service com.adobe~DataManagerService stopped. (337 ms)
      Service com.adobe~DocumentServicesConfiguration stopped. (20 ms)
      Service monitor stopped. (11508 ms)
      Service adminadapter stopped. (10 ms)
      Service basicadmin stopped. (435 ms)
      Service CUL stopped. (29 ms)
      Service apptracing stopped. (316 ms)
      Service jms_provider stopped. (441 ms)
      Service prtbridge stopped. (43 ms)
      Service jmx stopped. (11 ms)
    stdout/stderr redirect
    node name   : server0
    pid         : 694
    system name : sid
    system nr.  : 00
    started at  : Thu May  1 21:07:00 2008
    [Thr  1] MtxInit: -2 0 0
    GC: initial heap(KB) 1048576; maximum heap(KB) 4194304; virtual machine identifier EBD4A45A98003900;  heap identifier EBD4A45A98003900.
    GC 1: starting collection, reason  external thread attached.
    GC 1: collection starting 05/01/08 21:07:06
    GC 1: live objects 2311; collected objects 1655; collected(KB) 146.
    GC 1: queued for finalization 0; total soft references 3; cleared soft references 0.
    GC 1: current heap(KB) 5484; current threshold(KB) 1048576.
    GC 1: collect (milliseconds) 60.
    GC 1: current cycle allocation(KB) 864; previous cycle allocation(KB) 4155.
    GC 1: total weak references 0; cleared weak references 0.
    GC 1: total final references 6; cleared final references 0.
    GC 1: total phantom references 0; cleared phantom references 0.
    GC 1: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 1: collection ending 05/01/08 21:07:06
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Loading: LogManager ... 1458 ms.
    Loading: PoolManager ... 43 ms.
    Loading: ApplicationThreadManager ... 393 ms.
    Loading: ThreadManager ... 92 ms.
    Loading: IpVerificationManager ... 42 ms.
    Loading: ClassLoaderManager ... 135 ms.
    Loading: ClusterManager ... 698 ms.
    Loading: LockingManager ... 257 ms.
    Loading: ConfigurationManager ... 6882 ms.
    Loading: LicensingManager ... 39 ms.
    Loading: CacheManager ... 992 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service DQE started. (106 ms).
      Service runtimeinfo started. (814 ms).
      Service memory started. (1000 ms).
      Service cross started. (986 ms).
      Service timeout started. (1112 ms).
      Service userstore started. (237 ms).
      Service jmx_notification started. (282 ms).
      Service file started. (2739 ms).
      Service trex.service started. (2105 ms).
      Service p4 started. (6490 ms).
      Service classpath_resolver started. (614 ms).
      Service log_configurator started. (41399 ms).
      Service locking started. (14 ms).
      Service http started. (3587 ms).
      Service naming started. (4369 ms).
      Service failover started. (278 ms).
      Service appclient started. (976 ms).
      Service javamail started. (1537 ms).
      Service jmsconnector started. (1752 ms).
      Service ts started. (2010 ms).
      Service licensing started. (69 ms).
      Service deploy started. (44892 ms).
      Service connector started. (4269 ms).
      Service MigrationService started. (657 ms).
      Service bimmrdeployer started. (119 ms).
      Service iiop started. (5427 ms).
      Service configuration started. (1895 ms).
      Service webservices started. (18814 ms).
      Service dbpool started. (21073 ms).
      Service com.sap.security.core.ume.service started. (41934 ms).
      Service security started. (9841 ms).
      Service applocking started. (991 ms).
      Service shell started. (1442 ms).
      Service classload started. (1888 ms).
      Service tceCATTPingservice started. (250 ms).
      Service telnet started. (763 ms).
      Service webdynpro started. (1402 ms).
      Service keystore started. (4630 ms).
      Service ssl started. (240 ms).
      Service tcsecsecurestorage~service started. (1102 ms).
      Service dsr started. (3796 ms).
      Service ejb started. (8102 ms).
      Service servlet_jsp started. (6737 ms).
      Service jmx started. (5763 ms).
      Service tcsecwssec~service started. (2560 ms).
      Service basicadmin started. (2749 ms).
      Service cafummetadata~imp started. (12205 ms).
      Service com.adobe~LicenseService started. (845 ms).
      Service adminadapter started. (1835 ms).
      Service prtbridge started. (7226 ms).
      Service cafumrelgroups~imp started. (3700 ms).
      Service com.sap.portal.pcd.gl started. (52 ms).
      Service CUL started. (13400 ms).
      Service monitor started. (10580 ms).
      Service tc.monitoring.logviewer started. (16568 ms).
      Service com.sap.portal.prt.sapj2ee started. (642 ms).
      Service rfcengine started. (23940 ms).
      Service com.adobe~DataManagerService started. (23670 ms).
      Service com.adobe~DocumentServicesBinaries2 started. (760 ms).
      Service com.adobe~DocumentServicesConfiguration started. (22272 ms).
      Service apptracing started. (20484 ms).
      Service com.adobe~PDFManipulation started. (776 ms).
      Service com.adobe~DocumentServicesLicenseSupportService started. (1062 ms).
      Service com.adobe~FontManagerService started. (1476 ms).
      Service tcsecdestinations~service started. (30901 ms).
      Service sld started. (32153 ms).
      Service cafruntimeconnectivity~impl started. (172286 ms).
      Service pmi started. (310 ms).
      Service com.adobe~TrustManagerService started. (358 ms).
      Service com.adobe~DocumentServicesDestProtoService started. (583 ms).
      Service com.adobe~XMLFormService started. (3334 ms).
      Service tcsecvsi~service started. (2789 ms).
      Service jms_provider started. (41330 ms).
    ServiceManager started for 202642 ms.
    Framework started for 214111 ms.
    SAP J2EE Engine Version 7.00   PatchLevel is running!
    PatchLevel September 11, 2006 16:35 GMT
    >
    Login :GC 2: starting collection, threshold allocation reached.
    GC 2: collection starting 05/01/08 21:12:43
    GC 2: live objects 821653; collected objects 5507929; collected(KB) 930171.
    GC 2: queued for finalization 0; total soft references 6661; cleared soft references 0.
    GC 2: current heap(KB) 1411040; current threshold(KB) 1048576.
    GC 2: collect (milliseconds) 70928.
    GC 2: current cycle allocation(KB) 342021; previous cycle allocation(KB) 1048597.
    GC 2: total weak references 2851; cleared weak references 22.
    GC 2: total final references 17577; cleared final references 15585.
    GC 2: total phantom references 0; cleared phantom references 0.
    GC 2: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 2: collection ending 05/01/08 21:13:54
    GC 3: starting collection, threshold allocation reached.
    GC 3: collection starting 05/01/08 21:15:55
    GC 3: collected class com/sap/engine/admin/model/monitoring/j2eeimpl/Messages.
    GC 3: live objects 1141518; collected objects 7001492; collected(KB) 1015923.
    GC 3: queued for finalization 0; total soft references 9542; cleared soft references 0.
    GC 3: current heap(KB) 1478764; current threshold(KB) 1048576.
    GC 3: collect (milliseconds) 4943.
    GC 3: current cycle allocation(KB) 18409; previous cycle allocation(KB) 1048578.
    GC 3: total weak references 3416; cleared weak references 10.
    GC 3: total final references 11311; cleared final references 8870.
    GC 3: total phantom references 0; cleared phantom references 0.
    GC 3: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 3: collection ending 05/01/08 21:16:00
    GC 4: starting collection, threshold allocation reached.
    GC 4: collection starting 05/01/08 21:19:12
    GC 4: live objects 1712827; collected objects 9309307; collected(KB) 995205.
    GC 4: queued for finalization 0; total soft references 10433; cleared soft references 0.
    GC 4: current heap(KB) 1791312; current threshold(KB) 1048576.
    GC 4: collect (milliseconds) 12627.
    GC 4: current cycle allocation(KB) 83189; previous cycle allocation(KB) 1048615.
    GC 4: total weak references 4320; cleared weak references 42.
    GC 4: total final references 15130; cleared final references 12235.
    GC 4: total phantom references 0; cleared phantom references 0.
    GC 4: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 4: collection ending 05/01/08 21:19:25
    GC 5: starting collection, threshold allocation reached.
    GC 5: collection starting 05/01/08 21:20:48
    GC 5: live objects 1995994; collected objects 11111932; collected(KB) 1029776.
    GC 5: queued for finalization 0; total soft references 10641; cleared soft references 0.
    GC 5: current heap(KB) 1980804; current threshold(KB) 1048576.
    GC 5: collect (milliseconds) 8913.
    GC 5: current cycle allocation(KB) 66502; previous cycle allocation(KB) 1049216.
    GC 5: total weak references 4535; cleared weak references 4.
    GC 5: total final references 14318; cleared final references 11227.
    GC 5: total phantom references 0; cleared phantom references 0.
    GC 5: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 5: collection ending 05/01/08 21:20:57
    GC 6: starting collection, threshold allocation reached.
    GC 6: collection starting 05/01/08 21:22:45
    GC 6: live objects 1953332; collected objects 6193794; collected(KB) 1035355.
    GC 6: queued for finalization 0; total soft references 11241; cleared soft references 0.
    GC 6: current heap(KB) 2028284; current threshold(KB) 1048576.
    GC 6: collect (milliseconds) 4005.
    GC 6: current cycle allocation(KB) 53049; previous cycle allocation(KB) 1049147.
    GC 6: total weak references 5352; cleared weak references 1.
    GC 6: total final references 8606; cleared final references 5381.
    GC 6: total phantom references 0; cleared phantom references 0.
    GC 6: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 6: collection ending 05/01/08 21:22:49
    GC 7: starting collection, threshold allocation reached.
    GC 7: collection starting 05/01/08 21:23:36
    GC 7: live objects 1990485; collected objects 5358483; collected(KB) 1045077.
    GC 7: queued for finalization 0; total soft references 12197; cleared soft references 0.
    GC 7: current heap(KB) 2081188; current threshold(KB) 1048576.
    GC 7: collect (milliseconds) 2336.
    GC 7: current cycle allocation(KB) 51278; previous cycle allocation(KB) 1048587.
    GC 7: total weak references 6594; cleared weak references 0.
    GC 7: total final references 5444; cleared final references 2179.
    GC 7: total phantom references 0; cleared phantom references 0.
    GC 7: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 7: collection ending 05/01/08 21:23:38
    GC 8: starting collection, threshold allocation reached.
    GC 8: collection starting 05/01/08 21:24:01
    GC 8: live objects 2324130; collected objects 5128151; collected(KB) 1046573.
    GC 8: queued for finalization 0; total soft references 12474; cleared soft references 0.
    GC 8: current heap(KB) 2047444; current threshold(KB) 1048576.
    GC 8: collect (milliseconds) 5092.
    GC 8: current cycle allocation(KB) 133699; previous cycle allocation(KB) 1048650.
    GC 8: total weak references 6957; cleared weak references 0.
    GC 8: total final references 4232; cleared final references 831.
    GC 8: total phantom references 0; cleared phantom references 0.
    GC 8: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 8: collection ending 05/01/08 21:24:06
    GC 9: starting collection, threshold allocation reached.
    GC 9: collection starting 05/01/08 21:24:27
    GC 9: live objects 2268890; collected objects 5671964; collected(KB) 1057910.
    GC 9: queued for finalization 0; total soft references 13224; cleared soft references 0.
    GC 9: current heap(KB) 2073064; current threshold(KB) 1048576.
    GC 9: collect (milliseconds) 4319.
    GC 9: current cy

  • SDM Deploy Error

    Hello! I'm deploying a J2EE project and the J2EE Server gives me the following error :
    18-may-2005 14:02:06 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [005]Deployment aborted
    Settings
    SDM host : linux2
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/ADMINI1/CONFIG~1/Temp/temp31738Isicres_J2EE.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/ADMINI1/CONFIG~1/Temp/temp31738Isicres_J2EE.ear
    Aborted: development component 'Isicres_J2EE'/'sap.com'/'localhost'/'2005.05.18.13.59.43':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Cannot deploy application sap.com/Isicres_J2EE.. Reason: null; nested exception is:      java.lang.NullPointerException (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    I haven't idea to solve this problem!! any help, please?
    Thank you

    Hi Carlos,
    You can find the root exception in the defaultTrace.trc file under /usr/sap/<SID>/<INSTANCE>/j2ee/cluster/server<N>/log.
    Hope it helps,
    Vladimir

  • Error during Step14 of Portal installation

    Hi,
    When I run Oracle 9iAS Portal 3.0 Configuration Assistant, I get the following error:
    STEP 14 : Installing seed data for all layers
    INSTALL_ACTION: installSeedData() : ..\..\bin\sqlplus portal32/ portal32@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROT
    OCOL=TCP)(HOST=myportal)(PORT=1521)))(CONNECT_DATA
    =(SID=ORCL))) @..\..\portal30\admin\plsql\wwc\wwcinsd.sql portal32 OP30_DEF TEMP wwcinsd.log OP30_DOC OP30_DOC portal32_NULL portal32_sso portal32_DEMO
    INSTALL_ACTION:installSeedData() :..\..\bin\sqlplus portal32/ portal32@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROT
    OCOL=TCP)(HOST=myportal)(PORT=1521)))(CONNECT_DATA
    =(SID=ORCL))) @..\..\portal30\admin\plsql\wwv\wwvinsd.sql portal32 OP30_DEF TEMP wwvinsd.log OP30_DOC OP30_DOC portal32_NULL portal32_sso portal32_DEMO
    ORA-03114: not connected to ORACLE
    Errors encountered in the Install process. Installation Aborted.
    I have got this error twice and during the second time, I made sure that I had started the listener using the lsnrctl and I was able to connect as internal, sys and manager through the svrmgrl . I was also able to run the query "Select * from global_name" which returned ORCL.WORLD.
    Please help with this problem.
    Thank you.
    Shakti Saran

    Hy
    thank for your answer...you did me in the right way to solve the problem.
    In my case the problem was the source ID . In configtool the box-number was the same that i have put in
    cluster_switch.id properties but the problem still occurred.
    I was sure about the name but following the OSS note  966752 there is an important sentence:
    Note: The default value is crucial! If a custom value other than the default value was applied, we highly recommend that you restore the default value.
    well....in configtool of source system ...File -> Configuration Editor and open Configurations -> cluster_data -> Property sheet instance.properties.IDXXXXXXX  you have two click on instence.properties and a popup appears and you have to do attention to the default hostname that in my case was different from box number.
    I've put the default hostname in cluster_switch.id properties following the note and the migration ended succesfully.
    thanks a lot
    nickk

  • Deployment error during deployment of the process flow...

    i have made a program using OMB to deploy an OWB process flow. i have used tcl programming to run it on UNIX.
    when i run the program it gives me a strange error saying:
    an unknown error has occured during deployment .
    when i open the OWB design center to check the status i find the the process folw is stuck during the generation part and it continues but the generation never takes place.. for that i wrote an OMBALTER to alter the generation language of the mappings used in the process flow ,but it does not help...
    also after the error in the program when i see the mapping through the desibn center i do not see the original mapping when i open the mapping editor.
    then if I run the again program again i get the process flow deployed successfully ,obviously with the incorrect mappings.
    can anybody plz help me out with it???

    Hello!
    I searched metalink on error RTC-5161 and found a reference in note 392263.1
    It is a bug but there is a patch available ( bug 5504848, patch number 5525337).
    Read the note on metalink to check if you really hit this bug and apply the patch.
    Regards,
    Robert

  • Sdm deployment error

    Hi all,
    When I tried deploying a simple webdynpro application in the server I get the error like this
    Jul 25, 2007 1:09:01 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [003]Deployment aborted
    Deployment exception : Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !
    1. I tried to connect to sdm via remote_gui and entered password and it connected correctly there without any error.
    2. In NWDS I selected the sap j2ee engine as
    sap j2ee engine is installed on local host
    system name : F06
    J2EE Instance : 30
    SCS Instance : 31
    3.  I went through all the post about this issue and none helped me out.
    Thanks in advance,
    Pls help
    Best Regards,
    Suresh.

    In Window=>Preferences>SAP j2ee Engine.
    I selected
    SAP J2ee Engine installed in local host. Clicked the Browse button and then selected F06.  This populated
    System Name: F06
    J2ee instance:30
    SCS Instance:31
    So what could be the problem.

  • SP2-0027: Input is too long error during Apex 4.0 installation

    I have come across an error while installing Apex 4.0.
    The installation reached the point where it gave a SP2-0027 error
    ...PAGE 72: Workspace Schemas
    ...PAGE 73: &PRODUCT_NAME. Workspace Creation
    ...PAGE 74: Page Views By Day Report
    ...PAGE 75: Page Views by Application and Page
    ...PAGE 76: Hourly Usage
    ...PAGE 77: Usage by Application, for selected hour
    ...PAGE 78: Page Performance Dashboard
    ...PAGE 79: Database
    SP2-0027: Input is too long (> 2499 characters) - line ignored
    wwv_flow_api.create_report_region (
    ERROR at line 16:
    ORA-06550: line 16, column 1:
    PLS-00703: multiple instances of named argument in list
    ORA-06550: line 16, column 1:
    PL/SQL: Statement ignored
    Disconnected from Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
    Following this, I looked up Apex help, and so checked dba_registry
    C:\apex>C:\oraclexe\app\oracle\product\10.2.0\server\BIN\sqlplus /nolog
    SQL*Plus: Release 10.2.0.1.0 - Production on Tue Jul 13 15:40:05 2010
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    SQL> connect sys as sysdba
    Enter password:
    Connected.
    SQL> SELECT STATUS FROM DBA_REGISTRY
    2 WHERE COMP_ID = 'APEX';
    STATUS
    LOADING
    Please help
    Edited by: user4477408 on Jul 19, 2010 3:35 PM
    Edited by: user4477408 on Jul 26, 2010 11:29 AM

    Did you keep any kind of external references to your pages/reports? From what it looks like, one of your report regions exceeds 2500 characters and APEX is having a hard time crunching it. See if you can find that page, then export that page, delete the region, and import the page on it's own later.
    Not sure why it would be such a small area, though. I usually don't have any trouble until I hit 32K characters.

  • Error during Live Cache Server Installation on SCM 4.1 system

    Hi All,
    I have an SCM 4.1 ABAP system running on MSSQL2005 and Win2003 server.I would like to install Live Cache Server on the same Server.Livecache client was installed as part of SCM 4.1 installation.
    I have installed MAXDB software and now when im trying to install Live Cache Server Instance i get the below error
    Im performing the installation with user root and it is an Administrator.
    WARNING 2011-12-09 11:01:25
    Execution of the command "change 'user' '/install'" finished with return code 1. Output: Install mode does not apply to a Terminal server configured for remote administration.
    Installation start: Friday, 09 December 2011, 11:01:23; installation directory: G:\SCM_4.1_Media\Media_Live_Cache\New_Media\51031447_2\CD_SAP_SCM_4.1_liveCache_64bit\SAPINST\NT\AMD64; product to be installed: SAP SCM 4.1> Additional Services> Install a liveCache Server instance
    Transaction begin ********************************************************
    WARNING 2011-12-09 11:02:33
    Error 3 (The system cannot find the path specified.
    ) in execution of a 'CreateProcess' function, line (265), with parameter (G:\SCM_4.1_Media\Media_Live_Cache\New_Media\51031447_2\CD_SAP_SCM_4.1_liveCache_64bit\NT\AMD64\SDBUPD.EXE -l).
    Transaction end **********************************************************
    WARNING 2011-12-09 11:02:34
    The step Fill_sapdb_db_instance_context with step key LIVECACHESERVER|ind|ind|ind|ind|ind|0|LC_SERVER_INSTALL|ind|ind|ind|ind|ind|0|Fill_sapdb_db_instance_context was executed with status ERROR.
    Has anyone seen this error before ? Any pointers would be helpful.
    Regards,
    Ershad Ahmed.

    Subprocess starts at 20111209154957
    Execute Command : C:\Program Files\sdb\programs\pgm\dbmcli.exe -n XXXXXXXXX db_enum
    Execute Session Command : exit
    > Subprocess stops at 20111209154957
    OK
    > Subprocess starts at 20111209155027
    Execute Command : C:\Program Files\sdb\programs\pgm\dbmcli.exe -n XXXXXXXXX db_enum
    Execute Session Command : exit
    > Subprocess stops at 20111209155027
    OK
    > Subprocess starts at 20111209155221
    Execute Command : C:\Program Files\sdb\programs\pgm\dbmcli.exe -n XXXXXXXXX db_enum
    Execute Session Command : exit
    > Subprocess stops at 20111209155221
    OK
    > Subprocess starts at 20111209155323
    Execute Command : C:\Program Files\sdb\programs\pgm\dbmcli.exe -n XXXXXXXXX inst_enum
    Execute Session Command : exit
    > Subprocess stops at 20111209155324
    OK
    7.5.00.31    f:\sapdb\liv\db
    7.6.06.10    f\sapdb\sdb\7606
    7.6.06.10    C:\Program Files\sdb\7606
    > Subprocess starts at 20111209155324
    Execute Command : C:\Program Files\sdb\programs\pgm\dbmcli.exe -n XXXXXXXXX inst_enum
    Execute Session Command : exit
    > Subprocess stops at 20111209155324
    OK
    7.5.00.31    f:\sapdb\liv\db
    7.6.06.10    f\sapdb\sdb\7606
    7.6.06.10    C:\Program Files\sdb\7606
    > Subprocess starts at 20111209161349
    Execute Command : C:\Program Files\sdb\programs\pgm\dbmcli.exe -n XXXXXXXXX inst_enum
    Execute Session Command : exit
    > Subprocess stops at 20111209161349
    OK
    7.5.00.31    f:\sapdb\liv\db
    7.6.06.10    f\sapdb\sdb\7606
    7.6.06.10    C:\Program Files\sdb\7606
    Regards,
    Ershad Ahmed.

  • Error during R/3 IDES installation -

    Dear All
    I am trying to install SAP R/3 4.7E IDES on Windows 2003 Enterprise with Oracle 10.2.0.4 version.
    During the database load phase, i am encountering a problem during creation of D010LINF view which is using T0001 table and mentions that the table doesnot exist. I am copying the relevant log here. Also i see a error mentioning that could not access SAPUSER table. Please help
    Log file - SAPVIEW.log
    F:\usr\sap\R47\SYS\exe\run/R3load.exe: START OF LOG: 20100302102935
    F:\usr\sap\R47\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#12 $ SAP
    F:\usr\sap\R47\SYS\exe\run/R3load.exe: version R6.40/V1.4
    Compiled Nov 30 2005 20:41:21
    F:\usr\sap\R47\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\NUC\DB/SAPVIEW.cmd -l C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\NUC\DB/SAPVIEW.log -stop_on_error
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
    (DB) ERROR: DDL statement failed
    (DROP VIEW "D010LINF")
    DbSlExecute: rc = 103
      (SQL error 942)
      error message returned by DbSl:
    ORA-00942: table or view does not exist
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) ERROR: DDL statement failed
    (CREATE VIEW "D010LINF" ( "PROG" , "R3STATE" , "MACH" , "UNAM" , "UDAT" , "UTIME" , "L_DATALG" , "Q_DATALG" , "SDAT" , "STIME" , "MINOR_VERS" , "MAJOR_VERS"  ) AS SELECT T0001."PROGNAME", T0001."R3STATE", T0001."MACH", T0001."UNAM", T0001."UDAT",  T0001."UTIME", T0001."L_DATALG", T0001."Q_DATALG", T0001."SDAT", T0001."STIME", T0001."MINOR_VERS", T0001."MAJOR_VERS" FROM "REPOLOAD" T0001)
    DbSlExecute: rc = 103
      (SQL error 942)
      error message returned by DbSl:
    ORA-00942: table or view does not exist
    (DB) INFO: disconnected from DB
    F:\usr\sap\R47\SYS\exe\run/R3load.exe: job finished with 1 error(s)
    F:\usr\sap\R47\SYS\exe\run/R3load.exe: END OF LOG: 20100302102937
    The line showing the SAPUSER error
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    Lokesh

    I am now not receiving the SAPUSER error. The only error i am receiving now is this as per SAPVIEW.log
    F:\usr\sap\R47\SYS\exe\run/R3load.exe: START OF LOG: 20100302121409
    F:\usr\sap\R47\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#12 $ SAP
    F:\usr\sap\R47\SYS\exe\run/R3load.exe: version R6.40/V1.4
    Compiled Nov 30 2005 20:41:21
    F:\usr\sap\R47\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\NUC\DB/SAPVIEW.cmd -l C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\NUC\DB/SAPVIEW.log -stop_on_error
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
    (DB) ERROR: DDL statement failed
    (DROP VIEW "D010LINF")
    DbSlExecute: rc = 103
      (SQL error 942)
      error message returned by DbSl:
    ORA-00942: table or view does not exist
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) ERROR: DDL statement failed
    (CREATE VIEW "D010LINF" ( "PROG" , "R3STATE" , "MACH" , "UNAM" , "UDAT" , "UTIME" , "L_DATALG" , "Q_DATALG" , "SDAT" , "STIME" , "MINOR_VERS" , "MAJOR_VERS"  ) AS SELECT T0001."PROGNAME", T0001."R3STATE", T0001."MACH", T0001."UNAM", T0001."UDAT",  T0001."UTIME", T0001."L_DATALG", T0001."Q_DATALG", T0001."SDAT", T0001."STIME", T0001."MINOR_VERS", T0001."MAJOR_VERS" FROM "REPOLOAD" T0001)
    DbSlExecute: rc = 103
      (SQL error 942)
      error message returned by DbSl:
    ORA-00942: table or view does not exist
    (DB) INFO: disconnected from DB
    F:\usr\sap\R47\SYS\exe\run/R3load.exe: job finished with 1 error(s)
    F:\usr\sap\R47\SYS\exe\run/R3load.exe: END OF LOG: 20100302121410
    Can i create teh T0001 table manually or suggest a solution guys
    Lokesh

  • Import ABAP error during ECC 6.0 installation on Win2003 with Oracle

    Dear friends,
    I am trying to install ECC 6.0 IDES version on Windows 2003 server with oracle 10g. In fact I had tried few days before and I was getting the same error message. I had posted a separate thread for this and after few suggestions I have moved the sorce data to internald HDD which was earlier on external HDD. Secondly the page file only 4096MB and now I have changed it to 24GB. But still it is giving errors. Only thing is that I have changed the page file size after istalling Oracle, will this effect installation? or is this because of any files corrupted source HDD?
    Kindly help me to solve this problem. I would be very much thankful to you. Here I am attaching DOKCLU.log; PCL2.log; sapinst.log; and import_monitor.java.log.
    Please let me know if you need any further information.
    - Ravinder.
    ============================================
    Error log from DOKCLU.log is as below:
    ++++++++++++++++++++++++++++++
    C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
    C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Apr  2 2006 23:26:45
    C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe -i DOKCLU.cmd -dbcodepage 4103 -l DOKCLU.log -stop_on_error
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (DB) INFO: DOKCLU created #20101202103735
    (RFF) ERROR: invalid checksum in data file "D:\SAPDVD\IDES-Exp 2\EXP2\DATA\DOKCLU.001"
                 current table was "DOKCLU"
    (DB) INFO: disconnected from DB
    C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    ============================================
    Error log from PCL2.log
    +++++++++++++++++
    C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
    C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Apr  2 2006 23:26:45
    C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe -i PCL2.cmd -dbcodepage 4103 -l PCL2.log -stop_on_error
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (DB) INFO: PCL2 created #20101202103740
    (RFF) ERROR: invalid checksum in data file "D:\SAPDVD\IDES-Exp 2\EXP2\DATA\PCL2.001"
                 current table was "PCL2"
    (DB) INFO: disconnected from DB
    C:\usr\sap\DEV\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
    ============================================
    log from import_monitor.java.log
    +++++++++++++++++++++++
    Loading of 'SAPDODS' import package: OK
    Import Monitor jobs: running 1, waiting 2, completed 40, failed 16, total 59.
    Import Monitor jobs: running 2, waiting 1, completed 40, failed 16, total 59.
    Loading of 'SAP0000' import package: OK
    Import Monitor jobs: running 1, waiting 1, completed 41, failed 16, total 59.
    Loading of 'SAPAPPL0_10' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 42, failed 16, total 59.
    ============================================
    log from sapinst.log
    +++++++++++++++
    Import Monitor jobs: running 2, waiting 9, completed 32, failed 16, total 59.
    Import Monitor jobs: running 3, waiting 8, completed 32, failed 16, total 59.
    Loading of 'SAPSSEXC_1' import package: OK
    Import Monitor jobs: running 2, waiting 8, completed 33, failed 16, total 59.
    Import Monitor jobs: running 3, waiting 7, completed 33, failed 16, total 59.
    Loading of 'SAPSLOAD' import package: OK
    Import Monitor jobs: running ...
    ERROR 2010-12-03 05:43:19
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    ERROR 2010-12-03 05:43:19
    FCO-00011  The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .

    Hi Rahul,
    Thanks for your valuable inputs, but when tried giving the below sqlplus command it is asking for user name and password and there I got stuck. Could you please let me know what is the default user and password or is there anyway we can skip it?
    Resolution
    stop the all oracle services.all r automatic mode.
    restart the system
    ==> When we restart system again all the automatic oracle services starts right, do we need to stop them again before executing the below command?
    login through
    goto command promt and type
    sqlplus "/as sysdba"
    ==> after this command it is asking for user name and password
    sql> startup
    exit
    c:---->lsnrctl (I do not understand this command, is it at C prompt or at SQL prompt?
    lsnrctl>status (also do not understand how to give this command)
    (look for the following message)
    The command completed successfully
    exit
    now u start the installation.
    Kindly help, it would be great if you could me your contact details, I will not disturb you but just in case of any help. Thanks once again. - Ravi.

  • Error during ECC 6.0 installation on Windows Server OS

    Hello Experts,
    I am having trouble installaint ECC 6.0 on windows server 2008 with MS SQL. I was half way through the installation and encountered an error. Hence i am trying a fresh installation however I get an error message " Cannot determine parameter SAPGLOBALHOST from default profile " . I have deleted registry entries for the previous installations, yet I am unable to proceed. Please help . Have cheked the forum bue haven found any inputs other than http://forums.sdn.sap.com/thread.jspa?threadID=1040931. This has not been of much help.

    Hi Venkata,
    Default profile.........
    SAPDBHOST = BR0137
    dbms/type = mss
    dbs/mss/server = BR0137
    dbs/mss/dbname = ERP
    dbs/mss/schema = erp
    j2ee/dbtype = mss
    j2ee/dbhost = BR0137
    j2ee/dbname = ERP
    SAPSYSTEMNAME = ERP
    SAPGLOBALHOST = BR0137
    rdisp/bufrefmode = sendoff,exeauto
    SAP Message Server for ABAP
    rdisp/mshost = br0137
    rdisp/msserv = sapmsERP
    rdisp/msserv_internal = 3903
    SAP Central Service Instance for J2EE
    j2ee/scs/host = br0137
    j2ee/scs/system = 02
    j2ee/ms/port = 3902
    SAP Message Server for ABAP
    SAP Central Service Instance for J2EE
    SAP Message Server for ABAP
    SAP Central Service Instance for J2EE
    SAP Message Server for ABAP
    SAP Central Service Instance for J2EE
    login/system_client = 001

Maybe you are looking for