Skip to Content

This document tells how to resolve when SCC (Sybase control center) service fails with error code 1053.

 

Platform Requirement:

 

SUP 2.2.x

SCC 3.2.7

 

We all know that there are 4 different services exist related to Sybase unwired platform runtime.

 

 

3.PNG

 

But sometimes when starting SCC service it fails with Error 1053 but other 3 services are very well up and running in services.msc,

 

After checking Agent log, C:\Sybase\SCC-3_2\log\agent.log, we come to know about a particular error.

 

Failed to start MessageSender: javax.naming.NamingException:

Caused by: com.sybase.djc.SystemException: Error: Connecting to host: localhost, port: 2100.

 

 

Cause for this error message is: SCC uses EAServer as a messaging server. Messaging server is running on port 2100 but the listener doesn’t seems to be available.

 

Steps to resolve this issue:

 

1. first cross check if messaging server is listening on port 2100

 

    • Run this command in command prompt

 

   C:\Users\Administrator>netstat -aon | find “:2100”

 

    • If it messaging server is listening, you will get this kind of response.

112.PNG

    • Otherwise,

 

  C:\Users\Administrator>netstat -aon | find “:2100”

         

           C:\Users\Administrator>

 

This means files are inconsistent.

 

 

2. To check if files are incosistent and resolve them,

 

  • Open multihost_iiop1.properties file available at

 

C:\Sybase\SCC-3_2\services\Messaging\lib\eas\lib\Repository\Server\EmbeddedJMS\Instance\com\sybase\djc\server\SocketListener

 

    • If file is incosistent, it will look like this:

 

   #Instance Properties

              #Thu Sep 12 16:16:11 IST 2013

               port=2100

 

    • Modify this file with example below (Make sure all SUP related services have been stopped)

    

              

#Instance Properties

          #Thu Sep 12 16:16:11 IST 2013

          hosts=<SUP server ip>,127.0.0.1

          port=2100

          host=0.0.0.0

          securityProfile=default

          ant.project=sybase-jms

          protocol=iiop

 

 

  • Similarly open default.properties file available at

 

C:\Sybase\SCC-3_2\services\Messaging\lib\eas\lib\Repository\Server\EmbeddedJMS\Instance\com\sybase\djc\sql\DataSource

 

    • If file is incosistent, it will look like this:

 

 

  #Instance Properties

          #Thu Sep 12 16:16:11 IST 2013

          serverName=scc_repository

          databaseType=Sybase_ASA

          user=DBA

          databaseFile=

          password=*

          portNumber=3638

 

 

    • Modify this file with example below (Make sure all SUP related services have been stopped)

    

              

#Instance Properties

#Thu Sep 12 16:16:11 IST 2013

serverName=localhost

databaseType=Sybase_SCC

user=DBA

databaseStopCommand=”~/bin/asa-stop${.bat}” -y -c uid\=DBA;pwd\=${password};eng\=${dataSource}

ant.project=default-data-sources

databaseCreateCommand=”~/bin/asa-init${.bat}” -q -z UTF8 -zn UTF8 “${databaseFile}”

databaseFile=

password=*

portNumber=3638

authenticatedSQL=SET TEMPORARY OPTION CONNECTION_AUTHENTICATION\=’Company\=Sybase;Application\=Sybase Control           Center;Signature\=000fa55157edb8e14d818eb4fe3db41447146f1571g04cf0bfedc80ad0e47aa6c3df7a00c768ef89d61′

databaseStartCommand=”~/bin/asa-start${.bat}” -x tcpip(MyIP\=127.0.0.1;Host\=localhost;Port\=3638;DoBroadcast\=no;BroadcastListener\=no) -n           ${dataSource} “${databaseFile}” -qi -qw

 

 

3. Start all sup related services from Desktop icon.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply