Skip to Content
0

Need help with Solution Manager 7.2 installation error

Feb 27 at 08:25 AM

43

avatar image

deploycontrollerlog.txtHi,

I encountered ADS deployment error when installing Solution Manager 7.2. Below screen shot of deployinfo.html. I also attached deploycontroller.log for reference.

Can anyone advise how to resolve this problem?


Regards,

Lim

deployinfo.jpg (118.2 kB)
ads
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Wee Seng Lim Feb 28 at 09:20 AM
0

Problem resolved with SAP note 2451228. Thanks.

Share
10 |10000 characters needed characters left characters exceeded
Bartosz Jarkowski Feb 27 at 11:48 AM
0

I can see in the log files following errors:

[ Error ] Could not establish connection to AS Java on [sings1w12vsol:50304]. End of stream is reached unexpectedly during input from Socket[addr=/144.5.15.74,port=50304,localport=52478]. Check if the host and port specified are correct and AS Java is up and running.

[ Info ] +++ Wait for server response +++. Deploying offline [77] seconds. Will timeout in [14,322] seconds.

[ LOG EXCEPTION ]  :: Could not establish connection to AS Java on [sings1w12vsol:50304]. No alive connection. Check state of the server. 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.]

Can you please verify that the Java instance of the Solution Manager is up and running?

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hi Bartosz,

Yes, the Java instance is up, else the other Java components would not be able to be deployed successfully. I noticed that during installation, sapinst will deploy the Java components offline which will put the Java instance in yellow status in the SAPMMC. When the Java instance is in yellow status, port 50304 will not be available.

Rgds

0