on 04-02-2013 9:21 PM
Hello,
We've noticed that our SCC (version 3.2.7) will not start on out
test
SUP
2.2.2 system. We've recently patched from 2.2.1 to 2.2.2 but we
are unsure if this is related, since it was fine before the upgrade. From the
logs. In the Agent.log We see these errors:
Messaging provider failed to fully start.
013-03-29 13:18:31,901 [ERROR] [plugin.PluginRegisterService ] [Agent Bootstrap Thread] - Failed to register plugin com.sybase.uep.admin.agent.plugin_2.0.0. Failed to start MessageSender. com.sybase.alert.message.api.ConnectionException: javax.naming.NamingException:
Caused by: com.sybase.djc.SystemException: Error: Connecting to host: localhost, port: 2100.
| at com.sybase.djc.rmi.iiop.client.Connection.init(Connection.java:624)
| at com.sybase.djc.rmi.iiop.client.Connection.getInstance(Connection.java:70)
We restarted all services and rebooted the servers several times but still it does not work.
I attached the SCC logs and the SUP logs for your analysis
thanks,
any help is appreciated
After our upgrade the SUP management Port was changed automatically from 2000 to 2001. After log in to SCC I could change it back to 2000 and I could connect again to the SUP Server.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I see this in the agent log, seems your messaging server did not start, Any info in the Windows Event viewer?
2013-06-17 12:08:03,684 [ERROR] [alert.AlertService ] [Agent Bootstrap Thread] - Failed to start MessageSender: javax.naming.NamingException:
Caused by: com.sybase.djc.SystemException: Error: Connecting to host: localhost, port: 2100.
RMI service | 9999 | TCP/IP |
Messaging service | 2100 | TCP/IP |
SCC repository database server | 3638 | TDS |
Web container | 8282 8283 | HTTP HTTPS |
User | Count |
---|---|
76 | |
9 | |
7 | |
6 | |
6 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.