- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- Error in Install instance SCS01 in SAP Netweaver 7...
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Error in Install instance SCS01 in SAP Netweaver 7.4 SR2
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-07-2015 3:09 PM
Hi everyone,
I'm installing the SAP Netweaver 7.4 SR2(as Application Server JAVA) for SAP Mobile Documents installation and the installation stopped in this point.
An error occurred while processing option SAP NetWeaver 7.4 Support Release 2 > MS SQL Server > SAP Systems > Application Server Java > Standard System > Standard System( Last error reported by the step: Instance SMD/SCS01 [PARTIAL] did not start after 5:00 minutes. Giving up.). You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and continue later.
Log files are written to C:\Program Files/sapinst_instdir/NW740SR2/MSS/INSTALL/STD/.
I have attached the screenshot for the same along with error logs.
Regards,
Suraj
- SAP Managed Tags:
- SAP NetWeaver,
- SAP NetWeaver Application Server
Accepted Solutions (1)
Accepted Solutions (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Guys,
After resolving the hostname to ip.
We are now able to move forward from that error.
But now the Java engine is not starting.
We are getting error:
Installation state did not persist. DIAGNOSIS: The last state of the installation was not saved by the persistency layer because at least one table container could not be written. SOLUTION: Check sapinst_dev.log to solve the problem and choose 'Retry'. If you cannot solve the problem, contact SAP Support. Do not cancel the installation with the kill command or task manager because you lose the current state of the installation.
Any ideas on this?
Regards,
Suraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Reagan
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Suraj,
You have to use configtool to reduce the heap assignment from 4096 to your personal settings.
Here you can find how to do this and the recomended parameter with differents resources:
Configuring JVM Parameters - Configuration of SAP NetWeaver CE - SAP Library
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
hemanth2
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Suraj,
Hope you are doing good.
Nice to hear from you again.
The issue is:
"
F [Thr 1964] Tue Jan 20 16:21:49 2015
F [Thr 1964] *** LOG => SfCJavaVm: exit hook is called. (rc = 335)
"
This is usually a SCS connection issue.
Please see note 1658385 - J2EE System fails with "exitcode = -334". Also have a look at the below notes and make sure that the network connection is fine. We have seen similar issues due to bad/ slow network connection. Please check the below notes with your network to ascertain the network health:
#124562 Hostname resolution problems (DNS timeouts)
#500235 Network Diagnosis with NIPING
#413330 Network timeout
Also add the below parameters to the SCS instance file: <sid>_SCS01_<host> in folder /usr/sap/<sid>/SYS/profile
ms/max_clients = 600
ms/max_open_requests = 2000
ms/audit=1
and
jstartup/keep_old_logfiles=3
The latter 2 parameters will prevent overwritting log files in case of restart.
Let me know how it goes
____________
Kind Regards,
Hemanth
SAP AGS
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
hemanth2
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
hemanth2
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Roman,
I would like to question that.
The exit code details are:
-334 server/dispatcher process is restarted because of error
getting confirmation during reattach to the message server.
Support component for this case is BC-CST-MS.
-335 server/dispatcher process is restarted because of timeout
for reconnecting to message server has reached. Support
component for this case is BC-CST-MS.
This is not a memory issue.
Regards,
Hemanth
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Hemanth,
I really appreciate your valuable comments. No one argues about the meaning of these exit codes. But the reasons for it appearance can be different. According to trace files provided it is clear that problems exists that relate to insufficient amount of memory installed that lead to bottlenecks at OS level (more likely related to high paging activity). Amount of memory that can be allocated by jvm is up to 3GB. 2.2GB installed is really not enough. Timeouts for reconnecting to message server can be related to performance issues on OS level. In any way (even if these problems have no relations to each other) it is desirable to perform proper sizing procedure to avoid problems with insufficient amount of memory.
Regards,
Roman
hemanth2
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Answers (7)
Answers (7)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
It has got installed !!
We allocated more RAM to the VM and continued the installation... and it worked.
It definitely was memory issue.
Thanks all for your help and valuable suggestions
To summarize, the hostname has to be resolved and adequate RAM size has to be allocated.
Will continue with further installation for SMD.
Regards,
Suraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
hemanth2
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Reagan
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Could you supply the latest std_server trace file?
If possible restart the Windows server and start the SAP system using the MMC and supply the latest std_server trace file.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
hemanth2
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Suraj,
Hope you are doing good. The server did not stop as per the std_server0 log. Was the engine hanging?
You do not need to manually start/restart just the SCS. This is counter productive.
When you run the startsap script/ or SAPMMC, it takes care of the start process of the entire server.
Regards,
Hemanth
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Reagan
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Suraj,
Can you attach your dev_icm and dev_ms log files?
Anyway if cant allocate memory you cannot work with message server or dispatcher.
In my last post I have posted a link to change your parameters acording with your resources (maybe must read it to check if all is ok).
I saw this in your log:
Suspiciously long running GC (turn this off via -XX:-DumpGCStatisticForLongGCs or change the time threshold via -XX:LongGCTime=<time in seconds>)
Sometimes when you cant resolve your alias or IPs in a good time, its helpful start separalety all components of system. You can too, add more time to the threshold indicated in the log.
I hope this can help you.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi friends,
I had stopped the server yesterday.
Today I restarted the server and straightaway continued installation.
We have moved ahead from the stuck situation.
One thing I did change before server shutdown is that I changed is the Processor scheduling to 'Programs' instead of Background services.
Currently I am at Deploy Java components stage. Maybe it was something to do with memory (no change in RAM has been made as yet)
Will let you all know how it turns out.
Regards,
Suraj
hemanth2
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
It still is at the same point.
We haven't got any errors as yet.
Not sure there has been any improvement.
We have seen messages such as :
Deployment: deployment triggered: tc~ep~epcftoolbox~api/sap.com
Deployment: Deployment of [name: 'tc~obn~migrator', vendor: 'sap.com' (sda)] finished.
etc.
And now when I check today I am seeing performing offline deployment. Elapsed time: 0:06 minutes...
Any ideas?
Regards,
Suraj
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Suraj,
Offline deployment is a part of the installation. You must be sure that the installation is running checking the activity of your server, the active process of SAP or the last entries of your sapinst.log (checking the date and time of the last entries).
Can you post the last entries of sapinst.log?
Regards,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Jose,
The last lines of the sapinst.log file:
21.01.2015 12:19:19
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
jstart.EXE, J2EE Server, GREEN, All processes running, 2015 01 21 12:09:31, 0:09:48, 3900
igswd.EXE, IGS Watchdog, GREEN, Running, 2015 01 21 12:09:32, 0:09:47, 1888
INFO 2015-01-21 12:19:19.878
Working directory changed to C:/Program Files/sapinst_instdir/NW740SR2/MSS/INSTALL/STD.
INFO 2015-01-21 12:19:20.161
Execute step createDeployList of component |NW_Java_OneHost|ind|ind|ind|ind|0|0|Prepare_Deployment_Using_Product_Version_Descriptor|ind|ind|ind|ind|deploy_pvd|0|Deployment_Using_Product_Version_Descriptor|ind|ind|ind|ind|deploy|0
INFO 2015-01-21 12:19:34.321
Creating file C:\Program Files\sapinst_instdir\NW740SR2\MSS\INSTALL\STD\componentsInLoad.lst.
INFO 2015-01-21 12:19:36.784
Creating file C:\Program Files\sapinst_instdir\NW740SR2\MSS\INSTALL\STD\deploy.lst.
INFO 2015-01-21 12:19:36.865
Working directory changed to C:/Program Files/sapinst_instdir/NW740SR2/MSS/INSTALL/STD.
INFO 2015-01-21 12:19:37.294
Execute step deploySoftwareComponents of component |NW_Java_OneHost|ind|ind|ind|ind|0|0|Prepare_Deployment_Using_Product_Version_Descriptor|ind|ind|ind|ind|deploy_pvd|0|Deployment_Using_Product_Version_Descriptor|ind|ind|ind|ind|deploy|0
INFO 2015-01-21 12:19:39.279
Creating file C:\Program Files\sapinst_instdir\NW740SR2\MSS\INSTALL\STD\deploycontroller.log.
INFO 2015-01-21 12:19:39.621
Output of "C:\Program Files\sapinst_instdir\NW740SR2\MSS\INSTALL\STD\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW740SR2/MSS/INSTALL/STD/install/lib;\\SMDTest/sapmnt/XYZ/SYS/global/security/lib/tools/iaik_jce.jar;\\SMDTest/sapmnt/XYZ/SYS/global/security/lib/tools/iaik_jsse.jar;\\SMDTest/sapmnt/XYZ/SYS/global/security/lib/tools/iaik_smime.jar;\\SMDTest/sapmnt/XYZ/SYS/global/security/lib/tools/iaik_ssl.jar;\\SMDTest/sapmnt/XYZ/SYS/global/security/lib/tools/w3c_http.jar;C:/usr/sap/XYZ/J00/j2ee/j2eeclient/sap.com~tc~exception~impl.jar;C:/usr/sap/XYZ/J00/j2ee/j2eeclient/sap.com~tc~je~clientlib~impl.jar;C:/usr/sap/XYZ/J00/j2ee/j2eeclient/sap.com~tc~logging~java~impl.jar;C:/Program Files/sapinst_instdir/NW740SR2/MSS/INSTALL/STD/install/lib/tc~je~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:\Program Files\sapinst_instdir\NW740SR2\MSS\INSTALL\STD\deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host SMDTest --port 50004 is written to the logfile deploycontroller.log.
Regards,
Suraj
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Well well,
It seems the process has got stuck.
Some of the entries in sapinst.log are
Error ] Could not establish connection to AS Java on [SMDTest:50004]. End of stream is reached unexpectedly during input from Socket[addr=/10.97.139.193,port=50004,localport=61599]. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [SMDTest:50004]. End of stream is reached unexpectedly during input from Socket[addr=/10.97.139.193,port=50004,localport=61600]. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/10.97.139.193,port=50004,localport=61600]
at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:501)
at java.lang.Thread.run(Thread.java:763)
[ Error ] Could not establish connection to AS Java on [SMDTest:50004]. End of stream is reached unexpectedly during input from Socket[addr=/10.97.139.193,port=50004,localport=61600]. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [SMDTest:50004]. End of stream is reached unexpectedly during input from Socket[addr=/10.97.139.193,port=50004,localport=61601]. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/10.97.139.193,port=50004,localport=61601]
at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:501)
at java.lang.Thread.run(Thread.java:763)
[ Error ] Could not establish connection to AS Java on [SMDTest:50004]. End of stream is reached unexpectedly during input from Socket[addr=/10.97.139.193,port=50004,localport=61601]. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [SMDTest:50004]. End of stream is reached unexpectedly during input from Socket[addr=/10.97.139.193,port=50004,localport=61603]. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/10.97.139.193,port=50004,localport=61603]
at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:501)
at java.lang.Thread.run(Thread.java:763)
[ Error ] Could not establish connection to AS Java on [SMDTest:50004]. End of stream is reached unexpectedly during input from Socket[addr=/10.97.139.193,port=50004,localport=61603]. Check if the host and port specified are correct and AS Java is up and running.
[ Info ] +++ Wait for server response +++. Deploying offline [6,407] seconds. Will timeout in [7,992] seconds.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [SMDTest:50004]. End of stream is reached unexpectedly during input from Socket[addr=/10.97.139.193,port=50004,localport=61604]. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
And latest entries include:
104
Component:EP-ADMIN ( sap.com)
Status:Aborted
Description:
1. Contains Aborted deployment component:
sap.com_com.sap.portal.appdesigner.pageeditor
Component:EP-RUNTIME ( sap.com)
Status:Skipped
Description:
Component:UWLJWF ( sap.com)
Status:Skipped
Description:
Component:EP-APPS-EXT ( sap.com)
Status:Skipped
Description:
Component:EP-WPC ( sap.com)
Status:Skipped
Description:
Component:NET-PDK ( sap.com)
Status:Skipped
Description:
Component:KMC-BC ( sap.com)
Status:Skipped
Description:
Component:KMC-COLL ( sap.com)
Status:Skipped
Description:
Component:KMC-CM ( sap.com)
Status:Skipped
Description:
Component:KMC-WPC ( sap.com)
Status:Skipped
Description:
Component:VC70RUNTIME ( sap.com)
Status:Skipped
Description:
Component:GROUPWARE ( sap.com)
Status:Skipped
Description:
Component:JWF ( sap.com)
Status:Skipped
Description:
[ Info ] Destroy command:[deploy]
ERROR 2015-01-22 12:54:50.607
CJS-30186 Execution of Deploy Controller Runner tool '"C:\Program Files\sapinst_instdir\NW740SR2\MSS\INSTALL\STD\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW740SR2/MSS/INSTALL/STD/install/lib;\\SMDTest/sapmnt/XYZ/SYS/global/security/lib/tools/iaik_jce.jar;\\SMDTest/sapmnt/XYZ/SYS/global/security/lib/tools/iaik_jsse.jar;\\SMDTest/sapmnt/XYZ/SYS/global/security/lib/tools/iaik_smime.jar;\\SMDTest/sapmnt/XYZ/SYS/global/security/lib/tools/iaik_ssl.jar;\\SMDTest/sapmnt/XYZ/SYS/global/security/lib/tools/w3c_http.jar;C:/usr/sap/XYZ/J00/j2ee/j2eeclient/sap.com~tc~exception~impl.jar;C:/usr/sap/XYZ/J00/j2ee/j2eeclient/sap.com~tc~je~clientlib~impl.jar;C:/usr/sap/XYZ/J00/j2ee/j2eeclient/sap.com~tc~logging~java~impl.jar;C:/Program Files/sapinst_instdir/NW740SR2/MSS/INSTALL/STD/install/lib/tc~je~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:\Program Files\sapinst_instdir\NW740SR2\MSS\INSTALL\STD\deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host SMDTest --port 50004' aborts with return code 104. Error message is <b>'Component:EP-ADMIN ( sap.com) Status:Aborted Description: 1. Contains Aborted deployment component: sap.com_com.sap.portal.appdesigner.pageeditor.</b> SOLUTION: Check 'C:\Program Files\sapinst_instdir\NW740SR2\MSS\INSTALL\STD\log\dc_log\deploy_api.0.log' and 'deploycontroller.log' for more information.
ERROR 2015-01-22 12:58:21.972
FCO-00011 The step deploySoftwareComponents with step key |NW_Java_OneHost|ind|ind|ind|ind|0|0|Prepare_Deployment_Using_Product_Version_Descriptor|ind|ind|ind|ind|deploy_pvd|0|Deployment_Using_Product_Version_Descriptor|ind|ind|ind|ind|deploy|0|deploySoftwareComponents was executed with status ERROR ( Last error reported by the step: Execution of Deploy Controller Runner tool '"C:\Program Files\sapinst_instdir\NW740SR2\MSS\INSTALL\STD\sapjvm\sapjvm_6\bin\java.exe" -classpath "C:/Program Files/sapinst_instdir/NW740SR2/MSS/INSTALL/STD/install/lib;\\SMDTest/sapmnt/XYZ/SYS/global/security/lib/tools/iaik_jce.jar;\\SMDTest/sapmnt/XYZ/SYS/global/security/lib/tools/iaik_jsse.jar;\\SMDTest/sapmnt/XYZ/SYS/global/security/lib/tools/iaik_smime.jar;\\SMDTest/sapmnt/XYZ/SYS/global/security/lib/tools/iaik_ssl.jar;\\SMDTest/sapmnt/XYZ/SYS/global/security/lib/tools/w3c_http.jar;C:/usr/sap/XYZ/J00/j2ee/j2eeclient/sap.com~tc~exception~impl.jar;C:/usr/sap/XYZ/J00/j2ee/j2eeclient/sap.com~tc~je~clientlib~impl.jar;C:/usr/sap/XYZ/J00/j2ee/j2eeclient/sap.com~tc~logging~java~impl.jar;C:/Program Files/sapinst_instdir/NW740SR2/MSS/INSTALL/STD/install/lib/tc~je~cl_deploy.jar" -Xmx256m -Ddc.api.verbose=false com.sap.engine.services.dc.api.cmd.Runner deploy -l "C:\Program Files\sapinst_instdir\NW740SR2\MSS\INSTALL\STD\deploy.lst" -e stop -u lower -w safety --lcm bulk -t 14400000 --host SMDTest --port 50004' aborts with return code 104. Error message is <b>'Component:EP-ADMIN ( sap.com) Status:Aborted Description: 1. Contains Aborted deployment component: sap.com_com.sap.portal.appdesigner.pageeditor.</b> SOLUTION: Check 'C:\Program Files\sapinst_instdir\NW740SR2\MSS\INSTALL\STD\log\dc_log\deploy_api.0.log' and 'deploycontroller.log' for more information.).
Regards,
Suraj
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Roman,
Attaching deploy_api.0.log and for reference
Below are entries of deploycontroler log :
[ Error ] Could not establish connection to AS Java on [SMDTest:50004]. End of stream is reached unexpectedly during input from Socket[addr=/10.97.139.193,port=50004,localport=61609]. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [SMDTest:50004]. End of stream is reached unexpectedly during input from Socket[addr=/10.97.139.193,port=50004,localport=61610]. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315)
... 14 more
Caused by: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/10.97.139.193,port=50004,localport=61610]
at com.sap.engine.services.rmi_p4.ClientConnection.run(ClientConnection.java:501)
at java.lang.Thread.run(Thread.java:763)
Regards,
Suraj
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Ok to sumarize it all make sure you have configuration like this:
1)SMDTest and SMDTest.ww930.my-it-solutions.net resolves to same IP and you can ping both of them
2) you have sapmsXYZ 3601/tcp #01 is instance number
sapgw01 3301/tcp
the error you getting is concering resolve of FQN of a server
*** ERROR => GwInitHostAdrs: GwHostToAddr(SMDTest.ww930.my-it-solutions.net) failed, rc=-2 [gwxxaddr.c 427]
that means it cant resolve the IP behind SMDTest.ww930.my-it-solutions.net
so make 100% sure you can ping SMDTest.ww930.my-it-solutions.net and the IP you get is the IP of a box where you install SCS instance
sapstartsrv service need to be stopped and shared memory cleanup (alternatively restart server)
delete the installation folder and repeat installation of SCS instance again
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
At the moment, we are unable to ping SMDTest.ww930.my-it-solutions.net (we are working on that)
Other than that, we have already done step for sapstartsrv.exe; i.e we had stopped the sapstartsrv and restarted the server.After that we tried the installation steps again, but we cannot move forward.
Thanks,
Suraj
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
I'm wondering how come you are able to install SAP on hostname with more than 13 characters.
Please refer 611361 - Hostnames of SAP servers
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Suraj ,
Did you disable the firewall ..
Thanks ,
Manu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi ,
We tried a fresh installation on a new 2012 R2 server which is a WorkGroup machine.
We are stuck on the same error again!
We have tried steps suggested above by Mr. Sriram,Mr. Yogesh and Mr. Reagan.
Below are the some errors found in
C:\Program Files\sapinst_instdir\NW740SR2\MSS\INSTALL\STD\sapinst_dev.log
WARNING 2015-01-15 12:09:58.170 [iaxxcmsclient.cpp:67]
CIaMsgClient::CIaMsgClient(SMDTest, 3901)
Connect to message server (SMDTest/3901) failed: MSENILAYER.
TRACE 2015-01-15 12:09:58.326 [jsextension.hpp:145]
JSExceptionHandler::setJSException()
Member function 'Installer.invokeModuleCall()' has thrown ESAPinstMsgException. Converting to JavaScript exception EJS::Exception.
NWException thrown: nw.msConnectException:
<html> <head> </head> <body> An exception occurred while connecting to the message server instance XYZ/SCS01 on host SMDTest, port 3901.<br>DIAGNOSIS: The original exception was: wapsmod.ms.MsAttachFailed:
Connect to message server (SMDTest/3901) failed: MSENILAYER..<br>SOLUTION: Make sure that the message server is started. </body></html>
Additionally we also tried to open sapstartsrv.exe which is working fine..(check screenshot attached)
Along with it we are attaching the dev_ms and dev_rd files from C:\usr\sap\XYZ\SCS01\work
UAC is disabled and internet is blocked on it..(only intranet)
Regards,
Suraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Reagan
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
*** ERROR => GwInitHostAdrs: GwHostToAddr(SMDTest.ww930.my-it-solutions.net) failed, rc=-2 [gwxxaddr.c 427]
***LOG S10=> GwInitReader, GwInitHostAdrs () [gwxxrd.c 2078]
Like I said before you have issues with the Gateway and the problem looks more likely with the hostname of the system? Check the hosts file and correct the entries if required.
Cheers
RB
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
yea I assumed that,
is it possible to put an alias to SMDTest also with full quilified domain name?
then it resolves
Other question is, during SWPM installation you did probably choose to uses FQN for SCS ? i remember it was possible to uncheck the possibility, then the shortname SMDTest will be used
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
you an assign to 1 IP address several hostnames
for example:
10.1.1.1 SMDTest SMDTest.ww930.my-it-solutions.net
you can set it localy under Windows folder System32/drivers/etc/hosts.txt
in this case both hostnames resolves to same IP address.
there is also a second solution you can try,but each time installation adjust profiles you gonna change them manually:
under /usr/sap/SMD/SYS/profile directory check for parameters
SAPLOCALHOSTFULL and change that to SMDTest
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Suraj,
You have to be sure that you can ping to SMDTest and SMDTest.ww930.my-it-solutions.net.
You can use traceroute for this hosts to ensure that all its ok.
Furthermore, you must check if sapgw##, sapmsSID have the correct ports on your services file too.
I hope this can help you.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Did you check the logs in the work folder of the SCS instance. You should be able to find something there. Usually I have seen this happens when the kernel is too old and it not matching the OS. You will find evidence in the logs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Thanks Yogesh,
We are using 2012 R2 server and Kernel version also seems to be the latest (51049350_10).
Which log file exactly do we have to check in the work folder?
I am attaching the logs of C:\Program Files\sapinst_instdir\NW740SR2\MSS\INSTALL\STD\sapinst_dev for reference.
Regards,
Suraj
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Check the following.
- check MMC, I am sure the SAP service is grey or orange. Check which service? message server etc.
- if it is the SCS service, check the following folder assuming your SID is XYZ and drive is K. K:\usr\sap\XYZ\SCS10\work. Sort files on time and check the first few files. They would have some error which is more accurate.
- as Sriram said, trey stopping sapinst. rebooting the system and start again, make sure to select to start from the point it stopped.
- One more thing you can try is double click on the sapstartsrv.exe file, see if the window pops up to install service. if it does not means ur kernel is definitely not correct. Check and let me know the error.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
We had gone through K:\usr\sap\XYZ\SCS10\work for logs ...
We found errors such as ;
WARNING 2015-01-08 11:44:57.377 [synxcpath.cpp:1010]
CSyPath::getOSNodeType(bool) lib=syslib module=syslib
Unable to get information about path \\LABEL.ASC\ using GetVolumeInformation. Operating system error message: The specified path is invalid.
ERROR 2015-01-08 11:50:53.797
CJSlibModule::writeError_impl()
CJS-30086 Instance SMD/SCS01 [PARTIAL] did not start after 5:10 minutes. Giving up.
Current access token
====================
Could not get thread token. Last error: 1008. I assume that no thread token exists.
Any idea on those?
We are planning to do a fresh installation on new OS.
BR
Suraj
Reagan
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
The problem is during the start of the instance so the SCS will be started first and it looks like the central services fails to start. You should supply the logs from the <Drive>:\usr\sap\SID\SCS<NN>\work directory to understand the reasons behind that.
Try starting the instance manually from the MMC and check the latest logs.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Reagan
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Reagan
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Suraj
>>
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
msg_server.EXE, MessageServer, GREEN, Running, 2015 01 08 11:45:43, 0:05:10, 3796
enserver.EXE, EnqueueServer, GREEN, Running, 2015 01 08 11:45:43, 0:05:10, 2384
gwrd.EXE, Gateway, GRAY, Stopped, 2015 01 08 11:45:45, 0:00:00, -1
<<
There is a problem with the gateway.
Check the gateway trace file (dev_rd) to know why the gateway fails to start.
Cheers
RB
- CF Deployment Error: Error getting tenant t0 in Technology Q&A
- It has never been easier to print from SAP with Microsoft Universal Print in Technology Blogs by Members
- SAP SABRIX UPGRADE in Technology Blogs by Members
- Create new system copyng existing system in Technology Q&A
- Develop a vue3 application on btp in Technology Q&A
| User | Count |
|---|---|
| 89 | |
| 10 | |
| 9 | |
| 9 | |
| 9 | |
| 6 | |
| 6 | |
| 5 | |
| 5 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.