503   Service Unavailable,SAP J2EE Engine/7.00

Hi Experts,
I have upgraded J2EE Software Components from SP06 to sp22 successfully.
Components
JSPM
BASETABLES
CORE-TOOLS
JLOGVIEW
SAP-JEE
SAP-JEECOR
SAP_JTECHF
SAP_BUILDT
BI_MMR
KM-KW_JIKS
ADSSAP
CAF-UM
SAP_JTECHS
BI_UDI
Now here is the problem...
When I executed the URL: http://hostname:50100/index.html I'm getting the below error:
"503 Service Unavailable"
SAP J2EE Engine/7.00
Application Stopped
Details: you have requested an application that is currently stopped.
Please guide me on this.
Regards,
Sharath
Log :
IM_ERR_FAILED: SAP_SupportPackage.ElementTypeID="01200615321100062316",Name="SAPK-20011INTBYDSP",Vendor="sap.com",Version="0011" referenced by association SAP_SupportPackageSoftwareComponent.Antecedent=ref"SAP_SoftwareComponent.ElementTypeID=
"01200615320200016633
",Name=
"TBYDSP
",Vendor=
"sap.com
",Version=
"200
"",Dependent=ref"SAP_SupportPackage.ElementTypeID=
"01200615321100062316
",Name=
"SAPK-20011INTBYDSP
",Vendor=
"sap.com
",Version=
"0011
"" does not exist.: Instance of SAP_ExportInstCreation.
Embedded instance(s): Target instance = SAP_SupportPackageSoftwareComponent.Antecedent=ref"SAP_SoftwareComponent.ElementTypeID=
"01200615320200016633
",Name=
"TBYDSP
",Vendor=
"sap.com
",Version=
"200
"",Dependent=ref"SAP_SupportPackage.ElementTypeID=
"01200615321100062316
",Name=
"SAPK-20011INTBYDSP
",Vendor=
"sap.com
",Version=
"0011
CIM_ERR_FAILED: Can not create SAP_SupportPackage.ElementTypeID="01200615321100063170",Name="SP072",Vendor="sap.com",Version="072", instance defines an additional property Owner.: Instance of SAP_ExportInstModification.
Embedded instance(s): Target instance = SAP_SupportPackage.ElementTypeID="01200615321100063170",Name="SP072",Vendor="sap.com",Version="072"
CIM_ERR_FAILED: Can not create SAP_SupportPackage.ElementTypeID="01200615321100063169",Name="SP072",Vendor="sap.com",Version="072", instance defines an additional property Owner.: Instance of SAP_ExportInstModification.
Embedded instance(s): Target instance = SAP_SupportPackage.ElementTypeID="01200615321100063169",Name="SP072",Vendor="sap.com",Version="072"
CIM_ERR_FAILED: Can not create SAP_SupportPackage.ElementTypeID="01200615321100063245",Name="SP038",Vendor="sap.com",Version="038", instance defines an additional property Owner.: Instance of SAP_ExportInstModification.
Embedded instance(s): Target instance = SAP_SupportPackage.ElementTypeID="01200615321100063245",Name="SP038",Vendor="sap.com",Version="038"#
Edited by: sharathbabu gundu on Aug 29, 2011 9:42 PM

Sharath,
Check if your settings in the Visual Adminstrator for SLD are correct and also test the CIM Client Test there.
Secondly, ensure that the SLDDSUSER has all required roles to access SLD and it is not been locked.
Also, you might want to check this SAP NOTE:669669.
Good Luck!
Sandeep Tudumu

Similar Messages

  • Problem: 503 Service Unavailable  SAP WebAS Engine is starting...

    Problem: 503 Service Unavailable
    SAP WebAS Engine is starting...
    If this state does not change within a few minutes,
    please contact your system administrator.
    Check the recommendations in SAP Notes: 943498, 764417
    Message: Dispatcher running but no server connected!
    Details: No details available
    This problem occurs suddenly after a time interval when working on Sap Enterprise Portal. Please Suggest me Number of possible solutions for this type of problem.....
    Thank's in Advance
    Regards-
    Sumeet Sharma

    Hi,
    The issue here is that the JAVA engine has not ye started completely. Check the status of the SAP instance in SAP MMC. You need to have the SDM, dipatcher, Server0 in green(started completely). If the server0 is in yellow/grey, then u will not be able to launch the portal URL.
    Check and post us the dev_server0 log for more information.
    Regards,
    Varadharajan M

  • Com.sap.security.core.ume.service failed. J2EE Engine cannot be started

    Hi,
    I have configured SNC on NetWeaver 7.0 (ABAP+JAVA) System on Windows 2003 Server with MS-SQL 2005 Database.
    After the SNC configuration restarted the Server but the JAVA Server process is going down with EXIT Code -11113. The SNC Configuration is working fine but JAVA is not running. SDM and dispatcher are in green but server process is going gray.
    I have checked the log files under C:\usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log
    The following is the part of log file.
    #1.5#005056BA6C3F001D0000000F000008D8000489ACAFC86070#1277274683393#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_71##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    [EXCEPTION]
    #1#com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    #1.5#005056BA6C3F001D00000011000008D8000489ACAFC8628E#1277274683393#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_71##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
    Please help me to solve the issue.
    Thanks,
    Ajay.

    Hi Tim,
    I have configured using Kerberos library for 32 bit on Net Weaver 7.0 with MS SQL 2005 Server on Windows 2003 Server. I didnt change any thing on JAVA side. I have configured as per the Kerberos configuration steps  as per below URL
    http://help.sap.com/saphelp_nw70ehp2/helpdata/en/44/0ebf6c9b2b0d1ae10000000a114a6b/frameset.htm
    The configuration was successful and I am able to login with out asking password, but After the configuration when I have restarted every thing on ABAP side works well but JAVA server process going down with EXIT code -11113. One of the log file contains follows error message.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Jun 25, 2010 3:05:24 AM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_69] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    One of the line says "SNC required for this connection". What does this mean? What else need to be done for JAVA to communicate with ABAP?
    Thanks,
    Ajay.

  • Error when starting SAP J2EE Engine Log Viewer Service

    Hi,
    I'm running SAP EP6 SP14.
    I need to make the default trace log file on the WAS Server (Windows) available to the developer's. For this goal, I am attempting to install and start the SAP J2EE Engine LogViewer Service on the WAS. I think I have configured the service.ini file appropropriately. When I register the service, I get a successful message that the service has been registed. The service even shows up in the Windows Service Manager.
    However, when I attempt to start the service, the process fails after a 4-minute attempt. I eventually get an error popup saying
    "Could not start the SAP J2EE Engine Logviewer service on the Local Computer"
    "Error 1053: The service did not respond to the start or control request in a timely fashion".
    The service shows as "starting" until I reboot the WAS.
    The logviewer.bat runs fine on the WAS itself.
    I can also connect from the client to the WAS thru the J2EE connection, but that requires the admin password. I'd rather get this approach to work.
    Regards,
    Kevin

    Hi,
    I have the same error during starting the service. How did you resolve that error?
    Regards
    Sabine

  • HTTP 503 Service Unavailable Error in SAP XI 3.0

    Hi All,
       I am doing a simple File -> File scenario which picks up a .txt file from a folder and post it to the same folder .My file is getting picked up.But I am getting an error
    <SAP:Stack>HTTP response contains status code 503 with the description Service Unavailable Error when sending by HTTP (error code: 503, error text: Service Unavailable)</SAP:Stack>
    I have done a cache refresh to resolve this error. But then my error is MAPPING PROGRAM NOT FOUND.When I retry I am getting the HTTP 503 error.
      Please suggest any solution for the same .
    Thanks,
    Tiny

    Look similar thread to resolve your problem
    Error in Call Adapter (IDOC->XI->FILE)
    XI Server Malfunction:Error in Receiver Adapter
    Http* Errors in XI
    Please can you look at note: 803145
    Error : HTTP_RESP_STATUS_CODE_NOT_OK - 503 Service Unavailable
    HTTP_RES_STATUS_CODE_NOT_OK,503 error

  • J2EE server not running. 503 service unavailable

    Hi ,
    J2EE Server is not starting. Rest all are running in mmc console.The contents of the file std_server0.out is as below.
    stdout/stderr redirect
    node name : server0
    pid : 584
    system name : J2E
    system nr. : 00
    started at : Tue Feb 15 10:12:46 2005
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude iaik/security/md/SHA a
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    SAP J2EE Engine Version 6.40 PatchLevel 87289.311 is starting...
    Loading: LogManager ... 1656 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 282 ms.
    Loading: ThreadManager ... 1360 ms.
    Loading: IpVerificationManager ... 47 ms.
    Loading: ClassLoaderManager ... 31 ms.
    Loading: ClusterManager ... 1047 ms.
    Loading: LockingManager ... 719 ms.
    Loading: ConfigurationManager ... 2093 ms.
    Loading: LicensingManager ... 125 ms.
    Loading: ServiceManager ...
    0.000: [GC 0.000: [ParNew: 43517K->2681K(65280K), 0.1899077 secs] 43517K->2681K(502528K), 0.1900163 secs]
    Loading services.:
    Service memory started. (125 ms).
    Service cross started. (125 ms).
    Service jmx_notification started. (110 ms).
    Service trex.service started. (140 ms).
    Service file started. (47 ms).
    Service runtimeinfo started. (0 ms).
    Service timeout started. (188 ms).
    Service userstore started. (16 ms).
    7.557: [GC 7.557: [ParNew: 46201K->4641K(65280K), 0.0511883 secs] 46201K->4641K(502528K), 0.0513121 secs]
    Service tcsecvsi~service started. (953 ms).
    Service tcsecwssec~service started. (1016 ms).
    Service p4 started. (578 ms).
    Service classpath_resolver started. (32 ms).
    Service deploy started. (5922 ms).
    14.157: [GC 14.157: [ParNew: 48161K->7636K(65280K), 0.0653829 secs] 48161K->7636K(502528K), 0.0655197 secs]
    Service apptracing started. (390 ms).
    Service log_configurator started. (11172 ms).
    Service locking started. (0 ms).
    Service http started. (563 ms).
    Service naming started. (765 ms).
    Service failover started. (94 ms).
    Service appclient started. (250 ms).
    Service ts started. (234 ms).
    Service javamail started. (282 ms).
    Service jmsconnector started. (282 ms).
    Service licensing started. (47 ms).
    Service connector started. (547 ms).
    Service configuration started. (250 ms).
    Service webservices started. (1234 ms).
    19.873: [GC 19.873: [ParNew: 51143K->8276K(65280K), 0.0746933 secs] 51143K->8276K(502528K), 0.0748063 secs]
    25.284: [GC 25.284: [ParNew: 51796K->8763K(65280K), 0.0613457 secs] 51796K->8763K(502528K), 0.0614361 secs]
    Service dbpool started. (6796 ms).
    Timed out services:
    Service ssl.
    Service tc.monitoring.logviewer.
    Service keystore.
    Service shell.
    Service prtbridge.
    Service webdynpro.
    Service com.sap.security.core.ume.service.
    Service pmi.
    Service tcsecsaml~service.
    Service sld.
    Service com.sap.portal.prt.sapj2ee.
    Service jms_provider.
    Service basicadmin.
    Service classload.
    Service adminadapter.
    Service telnet.
    Service servlet_jsp.
    Service ejb.
    Service dsr.
    Service monitor.
    Service tcsecdestinations~service.
    Service tcsecsecurestorage~service.
    Service security.
    Service applocking.
    Service jmx.
    Service DQE.
    Service tceCATTPingservice.
    Service rfcengine.
    ServiceManager started for 315217 ms.
    Framework started for 323623 ms.
    SAP J2EE Engine Version 6.40 PatchLevel 87289.311 is running!
    PatchLevel 87289.311 November 18, 2004 20:31 GMT
    608.267: [GC 608.268: [ParNew: 52274K->10357K(65280K), 0.1024975 secs] 52274K->10357K(502528K), 0.1026132 secs]
    Excluding compile: iaik.security.md.SHA::a
    The Developer Trace of J2EE Server is as below.
    trc file: "D:\usr\sap\J2E\JC00\work\dev_server0", trc level: 1, release: "640"
    node name : ID3718450
    pid : 3964
    system name : J2E
    system nr. : 00
    started at : Tue Feb 15 10:12:46 2005
    arguments :
    arg[00] : D:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
    arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC00_igtehydsapweb
    arg[02] : -DSAPINFO=J2E_00_server
    arg[03] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC00_igtehydsapweb
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties]
    -> ms host : igtehydsapweb
    -> ms port : 3601
    -> OS libs : D:\usr\sap\J2E\JC00\j2ee\os_libs
    -> Admin URL :
    -> run mode : NORMAL
    -> run action : NONE
    -> enabled : yes
    Used property files
    -> files [00] : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host : igtehydsapweb
    -> ms port : 3601
    -> os libs : D:\usr\sap\J2E\JC00\j2ee\os_libs
    -> admin URL :
    -> run mode : NORMAL
    -> run action : NONE
    -> enabled : yes
    Bootstrap nodes
    -> [00] bootstrap : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID3718400 : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID3718450 : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID3718400 : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    -> [01] ID3718450 : D:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
    [Thr 4256] Tue Feb 15 10:12:46 2005
    [Thr 4256] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 4256] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 3328] JLaunchRequestFunc: Thread 3328 started as listener thread for np messages.
    [Thr 1800] WaitSyncSemThread: Thread 1800 started as semaphore monitor thread.
    [Thr 4256] Tue Feb 15 10:12:47 2005
    [Thr 4256] INFO: Invalid property value [JLaunchParameters/]
    [Thr 4256] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx512M [jstartxx.c 2282]
    [Thr 4256] [Node: server0] java home is set by profile parameter
    Java Home: D:\j2sdk1.4.2_07
    JStartupIReadSection: read node properties [ID3718450]
    -> node name : server0
    -> node type : server
    -> java path : D:\j2sdk1.4.2_07
    -> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -XX:MaxNewSize=85M -XX:NewSize=85M -XX:DisableExplicitGC -XX:MaxPermSize=192M -XX:PermSize=192M -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Drdbms.driverLocation=D:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=D:/usr/sap/J2E/SYS/global/
    -> java vm version : 1.4.2_07-b05
    -> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type : server
    -> java vm cpu : x86
    -> heap size : 512M
    -> init heap size : 512M
    -> root path : D:\usr\sap\J2E\JC00\j2ee\cluster\server0
    -> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path : D:\usr\sap\J2E\JC00\j2ee\os_libs
    -> main class : com.sap.engine.boot.Start
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path : D:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
    -> shutdown class : com.sap.engine.boot.Start
    -> parameters :
    -> debuggable : no
    -> debug mode : no
    -> debug port : 50021
    -> shutdown timeout: 120000
    [Thr 4256] JLaunchISetDebugMode: set debug mode [no]
    [Thr 1784] JLaunchIStartFunc: Thread 1784 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack : 262144 Bytes
    -> arg[ 0]: exit
    -> arg[ 1]: abort
    -> arg[ 2]: -Denv.class.path=D:\j2sdk1.4.2_07\%JAVA_HOME%\lib;
    -> arg[ 3]: -Djava.security.policy=./java.policy
    -> arg[ 4]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 8]: -Djco.jarm=1
    -> arg[ 9]: -Dsun.io.useCanonCaches=false
    -> arg[ 10]: -Djava.awt.headless=true
    -> arg[ 11]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 12]: -verbose:gc
    -> arg[ 13]: -XX:+PrintGCDetails
    -> arg[ 14]: -XX:+PrintGCTimeStamps
    -> arg[ 15]: -XX:+UseParNewGC
    -> arg[ 16]: -XX:MaxNewSize=85M
    -> arg[ 17]: -XX:NewSize=85M
    -> arg[ 18]: -XX:+DisableExplicitGC
    -> arg[ 19]: -XX:MaxPermSize=192M
    -> arg[ 20]: -XX:PermSize=192M
    -> arg[ 21]: -XX:SurvivorRatio=2
    -> arg[ 22]: -XX:TargetSurvivorRatio=90
    -> arg[ 23]: -Drdbms.driverLocation=D:/sapdb/programs/runtime/jar/sapdbc.jar
    -> arg[ 24]: -Dsys.global.dir=D:/usr/sap/J2E/SYS/global/
    -> arg[ 25]: -Dsys.global.dir=D:\usr\sap\J2E\SYS\global
    -> arg[ 26]: -Dapplication.home=D:\usr\sap\J2E\JC00\j2ee\os_libs
    -> arg[ 27]: -Djava.class.path=D:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=D:\j2sdk1.4.2_07\jre\bin\server;D:\j2sdk1.4.2_07\jre\bin;D:\j2sdk1.4.2_07\bin;D:\usr\sap\J2E\JC00\j2ee\os_libs;D:\usr\sap\Python\.;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;D:\j2sdk1.4.2_07\bin;;D:\usr\sap\J2E\SCS01\exe;D:\usr\sap\J2E\JC00\exe;D:\usr\sap\J2E\SYS\exe\run
    -> arg[ 29]: -Dmemory.manager=512M
    -> arg[ 30]: -Xmx512M
    -> arg[ 31]: -Xms512M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=3964
    -> arg[ 35]: -Djstartup.ownHardwareId=W0450436801
    -> arg[ 36]: -Djstartup.whoami=server
    -> arg[ 37]: -Djstartup.debuggable=no
    -> arg[ 38]: -DSAPINFO=J2E_00_server
    -> arg[ 39]: -DSAPSTARTUP=1
    -> arg[ 40]: -DSAPSYSTEM=00
    -> arg[ 41]: -DSAPSYSTEMNAME=J2E
    -> arg[ 42]: -DSAPMYNAME=igtehydsapweb_J2E_00
    -> arg[ 43]: -DSAPDBHOST=
    -> arg[ 44]: -Dj2ee.dbhost=igtehydsapweb
    [Thr 1784] Tue Feb 15 10:12:48 2005
    [Thr 1784] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 3104] Tue Feb 15 10:12:56 2005
    [Thr 3104] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 3104] JLaunchISetClusterId: set cluster id 3718450
    [Thr 3104] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 3104] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 3104] Tue Feb 15 10:18:15 2005
    [Thr 3104] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    please do the needful.
    regards,
    sreeram

    Hi Sreeram,
    The reasons for this issue can be numerous and most of them will be present in the default trace in
    /usr/sap/<SID>/JC<instance-nr>/j2ee/cluster/server<0..N>/log
    It would be best to report an OSS message and let the support find the problem for you.
    Best Regards: Iavor

  • 503 Service Unavailable? unable open irj/portal and NWA for SAP CE 7.3 trial version

    Hi Experts,
    I am not able to open irj/portal and nwa for my recently installed SAP CE 7.3 trail version.
    Only start page is opening.
    SAP J2EE engine and data base is up and runing.
    1.
    Time
    2014 07 03 10:18:04:932
    Severity
    Error
    Filename
    defaultTrace_00.3.trc
    Details
    SourceName: com.sap.engine.services.deploy.server.TransactionManager Location: com.sap.engine.services.deploy.server.TransactionManager DCComponent: servlet_jsp CSNComponent: BC-JAS-WEB User: Guest Session: 0 CorrelationID: 4699250000000003 DSRTransaction: f0452ed0026911e48a26000c29f14d18 DSRRootContextID: F0452ED0026911E48A26000C29F14D18 DSRConnection: f0452ed0026911e48a26000c29f14d18 DSRCounter: 0 ThreadName: Thread[HTTP Worker [@1380566121],5,Dedicated_Application_Thread] TimeZone: +0530
    Text
    Global [startApp] operation of application [sap.com/tc~lm~itsam~co~ui~nwa~localnavigation~wd] failed with errors on server process [4699250].
    Thanks,
    Amith.

    Hi Mayank,
    I am not able to access index.html page it shows 404 error,
    Main page is opening.
    please provide path for dev_server0 and stdout_server0 logs i will update.
    Thanks,
    Amith.

  • SAP J2EE engine for configuring Java mail Service.

    Hi
    I am experiencing following exception when trying to use JAVA mail API.
    javax.mail.SendFailedException: Invalid Addresses;
    nested exception is:
    javax.mail.SendFailedException: 554 <email@ddress>: Recipient address rejected:
    Relay access denied
    email address above is valid..
    I have to use SAP J2EE engine for configuring Java mail Service.
    But is does not hav any such access permissions to check....!!

    Relay access denied
    To send mails from SAP system through the mail server which you have configured, SAP server should be permitted to relay through the mailserver. Then only you will be able to send mail to external email address. Otherwise, you will get the above message.
    You must contact the mail server administrator and ask him to add the ip of SAP server into the allowed relay list.
    If you are using MS exchange server as your mail server and if you have administrative access to the Exchange box, you can do it yourself by following the below steps:
    1.Verify that your Exchange computer is not an open mail relay. To do this, follow these steps:
    a.      Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
    b.      In Exchange System Manager, expand the following object:
    Servers\Your_Exchange_Server_Name\Protocols\SMTP
    c.      Right-click the virtual SMTP server where you want to prevent mail relay, and then click Properties.
    d.      Click the Access tab, and then click Relay.
    e.      By default, open relay is blocked. The default settings are as follows:
    u2022     The Only the list below check box is selected.
    u2022     The Allow all computers which successfully authenticate to relay, regardless of the list above check box is selected.
    f.      If you must permit a single computer, a group of computers, or a domain to relay through the server, click Add. In the Computer dialog box, click the appropriate selection for the computers you want to relay through the server. Then, type the required information.
    Note Enabling access by IP address or by domain name is helpful for users who do not authenticate with the Exchange computer.
    g.      In the Relay Restrictions dialog box, click OK.
    h.      Click Apply, and then click OK in the Default SMTP Virtual Server Properties dialog box.
    hope this helps you out...
    Cheers,
    Jazz

  • 503  Service Unavailable Error: Application cannot be started!

    Hi Experts,
       I have NWE 7.11 SP 01 installed . While try to update to SP04, the server restarted automatically & when i try to access the portal link http:<host>:<port>/irj/portal am getting err as 503 service unavailable. I am able to see irj, JMS_Provider,tcjewebservice_srv,tcwddispwda  services in failed state. Please help me out.
       I got the log file in dev_server0 as follows
    [Thr 1122040128] *** ERROR => NiHsLGetNodeAddr: NiPGetHostByName failed (rc=-1) [nixxhsl.cpp  308]
    [Thr 1122040128] *** ERROR => NiHsLGetHostName: NiPGetHostByAddr failed (rc=-1) [nixxhsl.cpp  507]
    M [Thr 1211640128] Mon Jul  4 11:44:31 2011
    M  [Thr 1211640128] ***LOG Q0I=> NiPConnect2: 172.20.50.242:3300: connect (111: Connection refused) [nixxi.cpp 3150]
    M  [Thr 1211640128] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 31/sock 92
        (SI_ECONN_REFUSE/111; I4; ST; 172.20.50.242:3300) [nixxi.cpp    3150]
    2.#2011 07 04 15:02:37:289#+0530#Error#/System/Server#
    #BC-JAS-JMS#jms#001A6406631A001F0000001800002B3A#4513750000000005##com.sap.jms.server.JMSServerFrame####4083D980A61D11E0842E001A6406631A#4083d980a61d11e0842e001a6406631a#4083d980a61d11e0842e001a6406631a#0#Services Start Processor#Plain##
    An error occurred starting the jms_provider service. The applications using JMS resources may not work as expected. For more details, refer to the trace file.#
    #2.#2011 07 04 15:02:37:290#+0530#Error#/System/Server#
    com.sap.ASJ.krn_srv.000059#BC-JAS-JMS#sap.com/jms_provider#001A6406631A001F0000001B00002B3A#4513750000000005##com.sap.engine.core.service630.container.ServiceRunner####4083D980A61D11E0842E001A6406631A#4083d980a61d11e0842e001a6406631a#4083d980a61d11e0842e001a6406631a#0#Services Start Processor#Java#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle#
    Service [{0}] error. Nested exception is: [{1}]#2#jms_provider#java.lang.NoClassDefFoundError: com/sap/engine/services/rmi_p4/interfaces/LocalRemoteByRef
    ------------------------- Loader Info -------------------------
    ClassLoader name: [service:jms_provider]
    Living status: alive
    Direct parent loaders:
       [system:Frame]
       [library:core_lib]
       [library:j2eeca]
       [service:timeout]
       [service:naming]
       [service:cross]
       [service:dbpool]
       [service:jmx]
       [service:security]
    Resources:
       /usr/sap/CEP/J00/j2ee/cluster/bin/services/jms_provider/lib/private/sap.com~tc~je~jms_provider~impl.jar
    Error occurred while trying to load com.sap.jms.server.remote.JMSRemoteServerImpl#
    #2.#2011 07 04 15:02:37:296#+0530#Error#/System/Server/Services/Deploy#
    com.sap.ASJ.dpl_ds.002038#EP-PIN-PRT#sap.com/irj#001A6406631A00520000000300002B3A#4513750000000003##com.sap.engine.services.deploy#Guest#0##4083D980A61D11E0842E001A6406631A#4083d980a61d11e0842e001a6406631a#4083d980a61d11e0842e001a6406631a#0#Thread[HTTP Worker [@1593095773],5,Dedicated_Application_Thread]#Java#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle#
    Global operation [{0}] over [{1}] [{2}] finished with errors for [{3}]ms on server [{4}]#2#500#true#
    #2.#2011 07 04 15:02:37:298#+0530#Warning#/System/Server/WebRequests#
    com.sap.ASJ.web.000132#BC-JAS-WEB#servlet_jsp#001A6406631A00520000000500002B3A#4513750000000003##com.sap.engine.services.servlets_jsp.server.DeployContext#Guest#0##4083D980A61D11E0842E001A6406631A#4083d980a61d11e0842e001a6406631a#4083d980a61d11e0842e001a6406631a#0#Thread[HTTP Worker [@1593095773],5,Dedicated_Application_Thread]#Java#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle#
    Error occurred during retrieving web module context needed for 'Lazy' startup of [irj] web module.
    For more details on the problem please check traces searching by logId: null#
    Thanks,
    Arun

    Hi,
    NiPGetHostByName failed
    NiPGetHostByAddr failed
    Looks like network related issue. Make sure the server is in the network and has proper hostname to IP address mapping maintained.
    SiPeekPendConn failed 172.20.50.242:3300
    Next check if the port 3300 is free using the netstat command.
    Regards,
    Srikishan

  • XIServer error raised: 503 Service Unavailable with SOAP Adapter

    Hi,
    We are getting a very strange error from a process that is working fine in 2 other environments.
    We are sending a message into the SOAP receiver adapter and are getting the following error at the Call Adapter part of the process :
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
      <SAP:P1>503</SAP:P1>
      <SAP:P2>Service Unavailable</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>&lt;!DOCTYPE HTML PUBLIC &quot;-//W3C//DTD HTML 4.0 Transitional//EN&quot;&gt; &lt;html&gt; &lt;head&gt; &lt;title&gt;Error Report&lt;/title&gt; &lt;style&gt; td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active &lt;/style&gt; &lt;/head&gt; &lt;body marginwidth=&quot;0&quot; marginheight=&quot;0&quot; leftmargin=&quot;0&quot; topmargin=&quot;0&quot; rightmargin=&quot;0&quot;&gt; &lt;table width=&quot;100%&quot; cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; align=&quot;left&quot; height=&quot;75&quot;&gt; &lt;tr bgcolor=&quot;#FFFFFF&quot;&gt; &lt;td align=&quot;left&quot; colspan=&quot;2&quot; height=&quot;48&quot;&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;4&quot; color=&quot;#666666&quot;&gt;&lt;b&gt;&amp;nbsp;&amp;nbsp;503 &amp;nbsp Service Unavailable&lt;/b&gt;&lt;/font&gt;&lt;/td&gt; &lt;/tr&gt; &lt;tr bgcolor=&quot;#3F73A3&quot;&gt; &lt;td height=&quot;23&quot; width=&quot;84&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt; &lt;td height=&quot;23&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt; &lt;td align=&quot;right&quot; height=&quot;23&quot;&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;2&quot; color=&quot;#FFFFFF&quot;&gt;&lt;b&gt;SAP J2EE Engine/6.40&amp;nbsp;&lt;/b&gt;&lt;/font&gt;&lt;/td&gt; &lt;/tr&gt; &lt;tr bgcolor=&quot;#9DCDFD&quot;&gt; &lt;td height=&quot;4&quot; colspan=&quot;3&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt; &lt;/tr&gt; &lt;/table&gt; &lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt; &lt;p&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;3&quot; color=&quot;#000000&quot;&gt;&lt;b&gt;&amp;nbsp;&amp;nbsp;The requested application, AFW, is currently unavailable.&lt;/b&gt;&lt;/font&gt;&lt;/p&gt; &lt;p&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;2&quot; color=&quot;#000000&quot;&gt;&lt;table&gt;&lt;tr&gt;&lt;td valign=&quot;top&quot;&gt;&lt;b&gt;&amp;nbsp;Details:&lt;/b&gt;&lt;/td&gt;&lt;td valign=&quot;top&quot;&gt;&lt;PRE&gt;No details available&lt;/PRE&gt;&lt;/font&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;/font&gt;&lt;/p&gt; &lt;/body&gt; &lt;/html&gt;</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP response contains status code 503 with the description Service Unavailable XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    We are on XI 3.0 SP13.
    Any suggestions ?
    Kind regards
    Colin.

    Hi Colin,
    Quick look into these-
    1) Are you able to test the WebService, because the error tells about unavailable...
    For more-
    /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
       /people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
    2) Is your SOAP Receiver COnfiguration is correct
       ~ http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
    3) Check the  wsdl is correct and try look into the input message for the Webservice(SOAP Adapter)
    Have a look into this thread-
    503 service unavailable
    Hope this helps,
    Regards,
    Moorthy

  • Status code 503--Service Unavailable

    Hi everyone.
    A little time ago I 've faced status code 503 -- service unavailable on XI 3.0, so I found Sap Note 803145 and applied it.
    The note says to change the PollAttempts parameter from 60 to 100 and that's supposed to solve the problem.
    Actually it seems that problem is solved, but occasionally it keeps apearing the same error (status code 503  -- service unavailable).
    I've checked all PollAttempts parameters and they are in 100 like the note says.
    Before the Note application the error was appearing in some messages that use SOAP and JDBC Adapters, but now this error is only appearing in JDBC adapter.
    Not all messages that use JDBC adapter are erroneous, the tricky thing here is that some messages that appear with this error can be restarted and processed succesfully but others can not be restarted.
    Can someone give me some light in this??
    Thanks in advanced.
    Emmanuel Rebolledo

    Hi Emmanuel,
    The "pollIntervall" and "pollAttempts" properties define how often and in what
    interval the messaging system tries to access the Listener Beans
    during startup (using JNDI Lookup). In the default system, this is a maximum
    of 10 attempts every 60 seconds. This is necessary because the Messaging
    System (MS) is implemented as a J2EE service, whereas EJBs are part of a
    J2EE application. During server startup, applications are always in a second
    phase after the services; therefore they are unavailable during the MS
    initialization. If your system starts very slowly (if it takes more than 10
    minutes), you may therefore need to increase "pollIntervall" and
    "pollAttempts".
    Default: pollInterval=60000 [ms], pollAttempts=10
    Regards
    joel

  • Error : HTTP_RESP_STATUS_CODE_NOT_OK - 503 Service Unavailable

    Hi experts!!
    We are getting the error "HTTP_RESP_STATUS_CODE_NOT_OK - 503 Service Unavailable" can you please let me know what are my options to resolve it.
    Any help would be highly appreciated.
    Thanks
    - Ravi

    Hi Ravi,
    Reward points if this helps
    The J2EE server might be overburdened and cannot accept the call. The 'Receive'servlet is not called. You will find further details on the HTTP status code definitions under "http://www.w3.org". Check the accessibility of the server by calling: http://<hostname>:<port>/MessagingSystem/receive/AFW/XI.
    The Listener Beans of the affected connection (AFW, Marketplace, BC,see above) were not registered or the log-specific Event Handler was not found.
    Check out this trouble shooting guide for SAP XI...Section 7.4.4.4 talks about exactly the same problem:-
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283
    Reward points if this helps
    Regards
    Pragathi.

  • Interactive Form Error:  Invalid Response Code: (503) Service Unavailable

    Hi,
    Here i am Facing a Problem while i try to develop a sample application using Interactive Forms.
    When i tried to Deploy it.
    the Error i am getting is
       com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (503) Service Unavailable. The requested URL was:"http://localhost:50000/AdobeDocumentServices/Config?style=document"
        at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:976)
        at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1423)
        at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
        at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
        at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:279)
        ... 27 more
    i will be very thankful if anyone solve my problem ...
    Thank you
    Srikanth

    Hi,
    you seem to be pointing to a Java stack that either hasn't got the Adobe document services installed or has them incorrectly configured. Check the ADS Configuration Guide again against the settings of the Engine on which you have the ADS running. Without ADS, you won't get a PDF. The URL with http://localhost:50000/AdobeDocumentServices/Config?style=document in it is a good start, but the config is more than just that.
    Best regards,
    Markus Meisl
    SAP NetWeaver Product Management

  • SAP j2ee engine is not running error while applying patches.

    Hi all,
    Iam in the process of aplpying patches using JSPM tool , for some of them iam getting the error messages , when i checked the log file for this tool it says:
    SAP J2ee engine is not running , unable to login to  <HOST name> with id <Login id>.
    Iam very new to this activity ,can anybody help me in this regard , i wil be very thankful.
    Thanks and Regards.
    Niyati.

    Hi,
    What exactly do you see when you say that the status in the MMC is OK? I don't think it can be green if you say that you get a message saying "Service Unavailable" when you try to login. If you get that message, it means that the service hasn't either been started or could not be started in case of an error. In this case the server status in the MMC should be yellow (or gray in case none of the services could be started)...
    Could you perhaps check it again? Another point to check would be if the connection to the database is OK. If you are using MySQL MaxDB, you could use the Database Manager tool to check this. Sometimes the log files fill up the database and the server cannot start because the database is full. In such cases you will need to clear the logs and then restart the entire cluster.
    Sameer

  • SAP J2E Engine Terminates on Portal Application Servers.

    Short Text 
    SAP J2EE Engine Terminates 
    Long Text 
    we are experencing a problem with SAP Enterprise Portal Server 5.0,where SAPJ2E Engine service failing almost once in a week on either of the two servers.
    Server details
    Os: Window 2000 Service pack 4
    SAP J2EE verison : 6.20 Path 19
    SAP Enterprise Portal SP5
    EP5 SP5 Hot fix 3.
    Oracle 8i Enterprise Edition Release 8.1.7.4.1
    Java 2 Standard Environment 1.3.1_10
    Error from Event Viewer for SAPJ2E engine
    "The Description for Event ID (0) in source (SAP J2E Engine Alone) cannot be found.The Local computer may not have the necessary registry information or message DLL files to display messages from a remote computer.The following information is part of the event SAP J2EE Engine Alone error
    6.SetServiceStatus.
    Error from SAP J2E engine logs:
    "Socket receive failed."
    Error from console.log
    "Integrity token expired"
    Actions done at our end.
    1) Got the confirmation from the backup team that no backups are being run at that time of SAP J2EE engine failure.
    2) Checked the service market place.
    Note 578554 - SAP J2EE ISAPI module: Release notes and known issues
    Note 581599 - EP5.0 SP4 : SAPJ2EE engine crashes after a while
    Need your help ..its bit Urgent.

    Hi,
    I have check the License under port/system config/License.
    Please find the below details which tell the license is valid.
    This Portal is: Licensed
    Portal Release: 5.0
    System ID: EP5
    Hardware Key: X0135695037
    Installation No.: 0020117479
    System No.: 000000000310150667
    Software Product: Portal_ORA
    EP5 X0135695037 Portal_ORA Unlimited 31/Dec/9999 Permanent 0020117479 000000000310150667 Valid
    EP5 X0135695037 Portal Unlimited 31/Dec/9999 Permanent 0020117479 000000000310150667 Valid
    Thanks,
    Deepu

Maybe you are looking for