Prizm 3.0 problem

[bucketboy]

We had a power failure the other day, and since then, prizm will not come up. Here is the log file. Does anyone see anything out of place??

09/05/07 07:11:52 INFO SYSTEM Build Version: 3.00.r1( 05.15.2007 10:27:59 )
09/05/07 07:11:52 INFO SYSTEM Java Version: 1.5.0_08
09/05/07 07:11:52 INFO SYSTEM Platform: x86
09/05/07 07:11:52 INFO SYSTEM Operating System: Windows 2003
09/05/07 07:11:52 INFO SYSTEM OS Version: 5.2
09/05/07 07:11:52 INFO SYSTEM System Log Severity Level: INFO
09/05/07 07:11:54 INFO SYSTEM Starting Prizm EMS Server…
09/05/07 07:11:54 INFO SYSTEM Build Version: 3.00.r1( 05.15.2007 10:27:59 )
09/05/07 07:11:54 INFO SYSTEM Java Version: 1.5.0_08
09/05/07 07:11:54 INFO SYSTEM Platform: x86
09/05/07 07:11:54 INFO SYSTEM Operating System: Windows 2003
09/05/07 07:11:54 INFO SYSTEM OS Version: 5.2
09/05/07 07:11:54 INFO SYSTEM Installing Security Manager
09/05/07 07:11:54 INFO SYSTEM Checking for Licenses at: D:/motorola/FLEXnet/license_files
09/05/07 07:11:54 INFO SYSTEM Utilizing Licensing Source: D:/motorola/FLEXnet/license_files
09/05/07 07:11:56 INFO SYSTEM Exported class com.mot.canopy.prizm.core.Server at port: 12801
09/05/07 07:11:56 INFO SYSTEM Exported class com.mot.canopy.prizm.core.Licensing at port: 12802
09/05/07 07:11:56 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.DatabaseManager
09/05/07 07:11:57 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.DatabaseManager
09/05/07 07:11:57 INFO SYSTEM DBManager Connecting to Database: Fred:1433
09/05/07 07:11:57 INFO SYSTEM DBManager using Driver Profile: SqlServer
09/05/07 07:11:57 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.LogEventManager
09/05/07 07:11:57 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.LogEventManager
09/05/07 07:11:57 INFO SYSTEM Checking for V1 Event Table Upgrade to V2
09/05/07 07:11:57 INFO SYSTEM Check for V1 Event Table Upgrade to V2 completed: 31 ms
09/05/07 07:11:57 INFO SYSTEM Checking for V2 Event Table Upgrade to 01_00_00
09/05/07 07:11:57 INFO SYSTEM Check for V2 Event Table Upgrade to 01_00_00 completed: 0 ms
09/05/07 07:11:57 INFO SYSTEM Checking for 01_00_00 Event Table Upgrade to 01_10_00
09/05/07 07:11:57 INFO SYSTEM Check for 01_00_00 Event Table Upgrade to 01_10_00 completed: 0 ms
09/05/07 07:11:57 INFO SYSTEM Log Event Table, loading Hash Cache:
09/05/07 07:11:57 INFO SYSTEM Log Event Table, loaded Hash Cache: Spawned a new Thread, hence 0 ms
09/05/07 07:11:57 INFO SYSTEM LogEvent Dispatcher: Thread started
09/05/07 07:11:58 INFO SYSTEM Exported class com.mot.canopy.prizm.services.logeventmanager.LogEventManager at port: 12803
09/05/07 07:11:58 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.UserManager
09/05/07 07:11:58 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.UserManager
09/05/07 07:11:58 INFO SYSTEM Checking for 01_00_00 Preferences Table Upgrade to 01_10_00
09/05/07 07:11:58 INFO SYSTEM Check for 01_00_00 Preferences Table Upgrade to 01_10_00 completed: 16 ms
09/05/07 07:11:59 INFO SYSTEM Get Remote Service: Canopy.Prizm.LogEventManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:11:59 INFO SYSTEM Exported class com.mot.canopy.prizm.services.usermanager.UserManager at port: 12804
09/05/07 07:11:59 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.OperationManager
09/05/07 07:11:59 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.OperationManager
09/05/07 07:11:59 INFO SYSTEM Exported class com.mot.canopy.prizm.services.operationsmanager.OperationManager at port: 12805
09/05/07 07:11:59 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.TaskScheduler
09/05/07 07:11:59 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.TaskScheduler
09/05/07 07:11:59 INFO SYSTEM Task scheduler started …
09/05/07 07:11:59 INFO SYSTEM Schedule Cleanup starts …
09/05/07 07:11:59 INFO SYSTEM Exported class com.mot.canopy.prizm.services.taskscheduler.TaskScheduler at port: 12806
09/05/07 07:11:59 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.NodeManager
09/05/07 07:11:59 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.NodeManager
09/05/07 07:12:00 WARN SYSTEM drop duplicate template with name:report.html.hsbhgeneral
09/05/07 07:12:00 WARN SYSTEM drop duplicate template with name:nat.port.mapping.config
09/05/07 07:12:00 WARN SYSTEM drop duplicate template with name:report.html.vlan
09/05/07 07:12:00 WARN SYSTEM drop duplicate template with name:report.sm.html.nat.port.mapping
09/05/07 07:12:01 WARN SYSTEM No data set found for performanceDataset
09/05/07 07:12:02 WARN SYSTEM No data set found for performanceDataset
09/05/07 07:12:02 WARN SYSTEM Missing report category
09/05/07 07:12:03 INFO SYSTEM Node Manager Compression Threshold: 50
09/05/07 07:12:03 INFO LICENSING POLICY file 'Data’cvsroot’BAM’authserver’api’businessrules’FlexLicenseManager.cpp, line 420: License Checked out for feature EMSPacksV3, version 3.0
09/05/07 07:12:03 INFO SYSTEM NodeManagerListenerManager: Dispatcher Thread started for listener com.mot.canopy.prizm.services.nodemanager.NodeStatusManager@1cbda0a
09/05/07 07:12:03 INFO SYSTEM Exported class com.mot.canopy.prizm.services.nodemanager.NodeManager at port: 12807
09/05/07 07:12:03 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.SNMPLib
09/05/07 07:12:03 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.SNMPLib
09/05/07 07:12:07 WARN SYSTEM Missing traps section in XML file for Generic.SNMP.Default.
09/05/07 07:12:07 WARN SYSTEM Missing traps section in XML file for Canopy.PLVMD.
09/05/07 07:12:07 INFO SYSTEM SNMP Session Manager pool size = 10
09/05/07 07:12:07 INFO SYSTEM Get Remote Service: Canopy.Prizm.LogEventManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:07 INFO SYSTEM Creating Trap Listener on Port:162
09/05/07 07:12:08 INFO SYSTEM SNMP Trap Listener Listening on 0.0.0.0/162
09/05/07 07:12:08 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.NetworkManager
09/05/07 07:12:08 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.NetworkManager
09/05/07 07:12:08 INFO SYSTEM System Auto-Refresh based on UpTime skips if UpTime > 0 (s)
09/05/07 07:12:08 INFO SYSTEM NodeManagerListenerManager: Dispatcher Thread started for listener com.mot.canopy.prizm.services.networkmanager.NetworkManager$1@12922f6
09/05/07 07:12:08 INFO SYSTEM Accepting registered element process started.
09/05/07 07:12:08 INFO SYSTEM Exported class com.mot.canopy.prizm.services.networkmanager.NetworkManager at port: 12808
09/05/07 07:12:08 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.PerfDB
09/05/07 07:12:08 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.PerfDB
09/05/07 07:12:08 INFO SYSTEM NodeManagerListenerManager: Dispatcher Thread started for listener com.mot.canopy.prizm.services.perfdb.PerformanceDB$1@11daa0e
09/05/07 07:12:08 INFO SYSTEM Exported class com.mot.canopy.prizm.services.perfdb.PerformanceDB at port: 12809
09/05/07 07:12:08 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.PerfChart
09/05/07 07:12:09 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.PerfChart
09/05/07 07:12:09 INFO SYSTEM Exported class com.mot.canopy.prizm.services.perfchart.RrdChartBuilder at port: 12810
09/05/07 07:12:09 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.ElementConfigManager
09/05/07 07:12:09 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.ElementConfigManager
09/05/07 07:12:09 INFO SYSTEM Checking for V1 Event Table Upgrade to V2
09/05/07 07:12:09 INFO SYSTEM Check for V1 Event Table Upgrade to V2 completed: 16 ms
09/05/07 07:12:09 INFO SYSTEM Config Manager: Default Alert = Warning
09/05/07 07:12:09 INFO SYSTEM Added element type specific value-display mapping for param Device Region Code. Added 32 mappings.
09/05/07 07:12:09 INFO SYSTEM Added element type specific value-display mapping for param Authentication Mode. Added 2 mappings.
09/05/07 07:12:09 INFO SYSTEM Added element type specific value-display mapping for param Device Region Code. Added 32 mappings.
09/05/07 07:12:09 INFO SYSTEM Added element type specific value-display mapping for param Device Region Code. Added 32 mappings.
09/05/07 07:12:09 INFO SYSTEM Added element type specific value-display mapping for param Device Region Code. Added 32 mappings.
09/05/07 07:12:09 INFO SYSTEM Element Configuration Manager: configApplyVerifyUpAll = false
09/05/07 07:12:09 INFO SYSTEM NodeManagerListenerManager: Dispatcher Thread started for listener com.mot.canopy.prizm.services.elementconfigmanager.ElementConfigManager$1@179f36b
09/05/07 07:12:09 INFO SYSTEM Configuration Manager: Updater Thread started
09/05/07 07:12:09 INFO SYSTEM Configuration Manager: CPLRelationshipChangeProcessor Thread started
09/05/07 07:12:09 INFO SYSTEM Exported class com.mot.canopy.prizm.services.elementconfigmanager.ElementConfigManager at port: 12811
09/05/07 07:12:09 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.PerfLoggingOperation
09/05/07 07:12:09 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.PerfLoggingOperation
09/05/07 07:12:09 INFO SYSTEM Performance Logging Operation Pool Size: 10
09/05/07 07:12:09 INFO SYSTEM Performance Logging Priority Delay 10; Priority Idle 50
09/05/07 07:12:09 INFO SYSTEM Get Remote Service: Canopy.Prizm.ElementConfigManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:09 INFO SYSTEM Scheduling Logging Poller for: 1 (5 Minute Interval)
09/05/07 07:12:09 WARN SYSTEM No performance data found for ElementType:Generic.Group
09/05/07 07:12:09 INFO SYSTEM Scheduling Logging Poller for: 2 (10 Minute Interval)
09/05/07 07:12:09 INFO SYSTEM Operation: Performance Logging Operation: 1 (5 Minute Interval) scheduled with Poll Interval: 1 (5 Minute Interval)
09/05/07 07:12:09 WARN SYSTEM No performance data found for ElementType:Generic.Group
09/05/07 07:12:09 INFO SYSTEM Operation: Performance Logging Operation: 2 (10 Minute Interval) scheduled with Poll Interval: 2 (10 Minute Interval)
09/05/07 07:12:09 INFO SYSTEM Scheduling Logging Poller for: 3 (15 Minute Interval)
09/05/07 07:12:09 WARN SYSTEM No performance data found for ElementType:Generic.Group
09/05/07 07:12:09 INFO SYSTEM Scheduling Logging Poller for: 4 (20 Minute Interval)
09/05/07 07:12:09 INFO SYSTEM Operation: Performance Logging Operation: 3 (15 Minute Interval) scheduled with Poll Interval: 3 (15 Minute Interval)
09/05/07 07:12:09 WARN SYSTEM No performance data found for ElementType:Generic.Group
09/05/07 07:12:09 INFO SYSTEM Scheduling Logging Poller for: 5 (25 Minute Interval)
09/05/07 07:12:09 INFO SYSTEM Operation: Performance Logging Operation: 4 (20 Minute Interval) scheduled with Poll Interval: 4 (20 Minute Interval)
09/05/07 07:12:09 WARN SYSTEM No performance data found for ElementType:Generic.Group
09/05/07 07:12:09 INFO SYSTEM Scheduling Logging Poller for: 6 (30 Minute Interval)
09/05/07 07:12:09 INFO SYSTEM Operation: Performance Logging Operation: 5 (25 Minute Interval) scheduled with Poll Interval: 5 (25 Minute Interval)
09/05/07 07:12:09 WARN SYSTEM No performance data found for ElementType:Generic.Group
09/05/07 07:12:09 INFO SYSTEM Scheduling Logging Poller for: 9 (45 Minute Interval)
09/05/07 07:12:09 INFO SYSTEM Operation: Performance Logging Operation: 6 (30 Minute Interval) scheduled with Poll Interval: 6 (30 Minute Interval)
09/05/07 07:12:09 WARN SYSTEM No performance data found for ElementType:Generic.Group
09/05/07 07:12:09 INFO SYSTEM Scheduling Logging Poller for: 12 (60 Minute Interval)
09/05/07 07:12:09 INFO SYSTEM Operation: Performance Logging Operation: 9 (45 Minute Interval) scheduled with Poll Interval: 9 (45 Minute Interval)
09/05/07 07:12:09 WARN SYSTEM No performance data found for ElementType:Generic.Group
09/05/07 07:12:09 INFO SYSTEM Scheduling Logging Poller for: 24 (2 Hour Interval)
09/05/07 07:12:09 WARN SYSTEM No performance data found for ElementType:Generic.Group
09/05/07 07:12:09 INFO SYSTEM Operation: Performance Logging Operation: 12 (60 Minute Interval) scheduled with Poll Interval: 12 (60 Minute Interval)
09/05/07 07:12:09 INFO SYSTEM Scheduling Logging Poller for: 36 (3 Hour Interval)
09/05/07 07:12:09 INFO SYSTEM Operation: Performance Logging Operation: 24 (2 Hour Interval) scheduled with Poll Interval: 24 (2 Hour Interval)
09/05/07 07:12:09 WARN SYSTEM No performance data found for ElementType:Generic.Group
09/05/07 07:12:09 INFO SYSTEM Scheduling Logging Poller for: 72 (6 Hour Interval)
09/05/07 07:12:09 INFO SYSTEM Operation: Performance Logging Operation: 36 (3 Hour Interval) scheduled with Poll Interval: 36 (3 Hour Interval)
09/05/07 07:12:09 WARN SYSTEM No performance data found for ElementType:Generic.Group
09/05/07 07:12:09 INFO SYSTEM Scheduling Logging Poller for: 144 (12 Hour Interval)
09/05/07 07:12:09 INFO SYSTEM Operation: Performance Logging Operation: 72 (6 Hour Interval) scheduled with Poll Interval: 72 (6 Hour Interval)
09/05/07 07:12:09 WARN SYSTEM No performance data found for ElementType:Generic.Group
09/05/07 07:12:09 INFO SYSTEM Scheduling Logging Poller for: 288 (24 Hour Interval)
09/05/07 07:12:09 INFO SYSTEM Operation: Performance Logging Operation: 144 (12 Hour Interval) scheduled with Poll Interval: 144 (12 Hour Interval)
09/05/07 07:12:09 WARN SYSTEM No performance data found for ElementType:Generic.Group
09/05/07 07:12:09 INFO SYSTEM PerformanceLogging: Registering NodeManager Listener
09/05/07 07:12:09 INFO SYSTEM Operation: Performance Logging Operation: 288 (24 Hour Interval) scheduled with Poll Interval: 288 (24 Hour Interval)
09/05/07 07:12:09 WARN SYSTEM No performance data found for ElementType:Generic.Group
09/05/07 07:12:09 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.SMTPService
09/05/07 07:12:09 INFO SYSTEM NodeManagerListenerManager: Dispatcher Thread started for listener com.mot.canopy.prizm.services.perflogging.PerformanceLogging2$1@129e5e9
09/05/07 07:12:09 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.SMTPService
09/05/07 07:12:09 INFO SYSTEM SMTP SERVICE: Setting SMTP server hostname to Fred
09/05/07 07:12:09 INFO SYSTEM SMTP SERVICE: Setting SMTP server port to 25
09/05/07 07:12:09 INFO SYSTEM SMTP SERVICE: Attempting to set authentication for the SMTP server.
09/05/07 07:12:09 WARN SYSTEM SMTP SERVICE: No login to SMTP server is specified!
09/05/07 07:12:09 INFO SYSTEM SMTP SERVICE: Setting Connection Timeout to 5000 ms
09/05/07 07:12:09 INFO SYSTEM SMTP SERVICE: Setting Timeout to 120000 ms
09/05/07 07:12:09 INFO SYSTEM Exported class com.mot.canopy.prizm.services.protocol.smtp.SMTPService at port: 12812
09/05/07 07:12:09 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.CustomerManager
09/05/07 07:12:09 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.CustomerManager
09/05/07 07:12:09 INFO SYSTEM Exported class com.mot.canopy.prizm.services.customer.CustomerManager at port: 12813
09/05/07 07:12:09 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.AlertManager
09/05/07 07:12:09 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.AlertManager
09/05/07 07:12:09 INFO SYSTEM Checking for 01_00_00 Alert Table Upgrade to 01_10_00
09/05/07 07:12:09 INFO SYSTEM Check for 01_00_00 Alert Table Upgrade to 01_10_00 completed: 0 ms
09/05/07 07:12:10 INFO SYSTEM Operation: Backhaul - Unpaired Master scheduled with 10 Minutes (From Start of the Hour) Recuring Schedule, days:!!!, hours:!!!,minutes:10
09/05/07 07:12:10 INFO SYSTEM Operation: Backhaul - Unpaired Slave scheduled with 10 Minutes (From Start of the Hour) Recuring Schedule, days:!!!, hours:!!!,minutes:10
09/05/07 07:12:10 INFO SYSTEM Operation: Element - Ethernet Down scheduled with 10 Minutes (From Start of the Hour) Recuring Schedule, days:!!!, hours:!!!,minutes:10
09/05/07 07:12:10 INFO SYSTEM Operation: Element - Poll Failed scheduled with 10 Minutes (From Start of the Hour) Recuring Schedule, days:!!!, hours:!!!,minutes:10
09/05/07 07:12:10 INFO SYSTEM Operation: RF - dBm Threshold Monitor scheduled with 10 Minutes (From Start of the Hour) Recuring Schedule, days:!!!, hours:!!!,minutes:10
09/05/07 07:12:10 INFO SYSTEM Operation: Hot RF Signal scheduled with 12 Hour (Starting Midnight) Recuring Schedule, days:!!!, hours:!..!..,minutes:0
09/05/07 07:12:10 INFO SYSTEM Operation: MIR Sustained Uplink > 500 scheduled with 12 Hour (Starting Midnight) Recuring Schedule, days:!!!, hours:!..!..,minutes:0
09/05/07 07:12:10 INFO SYSTEM Exported class com.mot.canopy.prizm.services.alertmanager.AlertManager at port: 12814
09/05/07 07:12:10 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.NotificationManager
09/05/07 07:12:10 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.NotificationManager
09/05/07 07:12:10 INFO SYSTEM Notification Dispatcher start …
09/05/07 07:12:10 INFO SYSTEM Checking for 01_00_00 Notification Table Upgrade to 01_10_00
09/05/07 07:12:10 INFO SYSTEM Check for 01_00_00 Notification Table Upgrade to 01_10_00 completed: 0 ms
09/05/07 07:12:10 INFO SYSTEM Exported class com.mot.canopy.prizm.services.notificationmanager.NotificationManager at port: 12815
09/05/07 07:12:10 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.NetworkDirectory
09/05/07 07:12:10 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.NetworkDirectory
09/05/07 07:12:10 INFO SYSTEM Operation: Bridge Operation scheduled with 20 Minutes (From Start of the Hour) Recuring Schedule, days:!!!, hours:!!!,minutes:20
09/05/07 07:12:10 INFO SYSTEM Exported class com.mot.canopy.prizm.services.networkdirectory.NetworkDirectory at port: 12816
09/05/07 07:12:10 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.MaintenaceService
09/05/07 07:12:10 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.MaintenaceService
09/05/07 07:12:10 INFO SYSTEM Get Remote Service: Canopy.Prizm.UserManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:10 INFO SYSTEM Get Remote Service: Canopy.Prizm.UserManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:10 INFO SYSTEM Operation: System Maintenance Operation scheduled with System Maintenance Schedule Recuring Schedule, days:!!!, hours:!!!,minutes:0
09/05/07 07:12:10 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.BAMManager
09/05/07 07:12:10 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.BAMManager
09/05/07 07:12:10 INFO SYSTEM Get Remote Service: Canopy.Prizm.LogEventManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:10 INFO SYSTEM Get Remote Service: Canopy.Prizm.NodeManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:10 INFO SYSTEM Get Remote Service: Canopy.Prizm.NodeManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:10 INFO SYSTEM Get Remote Service: Canopy.Prizm.NetworkManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:10 INFO SYSTEM Get Remote Service: Canopy.Prizm.UserManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:10 WARN SYSTEM Utilizing bamconfigfile: D:/Motorola/Prizm/config/bamconfig.xml
09/05/07 07:12:10 INFO SYSTEM BAM Radius Mode is Disabled
09/05/07 07:12:10 INFO SYSTEM NodeManagerListenerManager: Dispatcher Thread started for listener com.mot.canopy.prizm.services.bammanager.BAMManager$1@15b123b
09/05/07 07:12:10 INFO SYSTEM Get Remote Service: Canopy.Prizm.ElementConfigManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:10 INFO SYSTEM Get Remote Service: Canopy.Prizm.ElementConfigManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:16 INFO SYSTEM Exported class com.mot.canopy.prizm.services.bammanager.BAMManager at port: 12817
09/05/07 07:12:16 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.CoverageService
09/05/07 07:12:16 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.CoverageService
09/05/07 07:12:16 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.SWUpdateManager
09/05/07 07:12:16 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.SWUpdateManager
09/05/07 07:12:16 INFO SYSTEM Get Remote Service: Canopy.Prizm.NetworkManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:21 INFO SYSTEM Exported class com.mot.canopy.prizm.services.swupdater.SWUpdateManager at port: 12818
09/05/07 07:12:21 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.SupportTool
09/05/07 07:12:21 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.SupportTool
09/05/07 07:12:21 INFO SYSTEM Get Remote Service: Canopy.Prizm.NodeManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:21 INFO SYSTEM Get Remote Service: Canopy.Prizm.SMTPService Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:21 INFO SYSTEM Get Remote Service: Canopy.Prizm.LogEventManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:21 INFO SYSTEM Get Remote Service: Canopy.Prizm.ElementConfigManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:21 INFO SYSTEM Get Remote Service: Canopy.Prizm.PerfChart Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:21 INFO SYSTEM Get Remote Service: Canopy.Prizm.TaskScheduler Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:21 INFO SYSTEM Exported class com.mot.canopy.prizm.services.custsupptool.SupportToolService at port: 12819
09/05/07 07:12:21 INFO SYSTEM LOADING ENABLED SERVICE: Canopy.Prizm.CustomMenu
09/05/07 07:12:21 INFO SYSTEM STARTING SUPPORTED SERVICE: Canopy.Prizm.CustomMenu
09/05/07 07:12:21 INFO SYSTEM Exported class com.mot.canopy.prizm.services.custommenu.CustomMenuManager at port: 12820
09/05/07 07:12:21 INFO SYSTEM Log Event Table : Joining the thread which loads the hash.
09/05/07 07:12:21 INFO SYSTEM Get Remote Service: Canopy.Prizm.OperationManager Internal/Unknown Requester: java.rmi.server.ServerNotActiveException: not in a remote call
09/05/07 07:12:21 INFO SYSTEM Coverage service Shutdown ok
09/05/07 07:12:25 INFO SYSTEM NodeManagerListenerManager: Dispatcher Thread completed for listener com.mot.canopy.prizm.services.bammanager.BAMManager$1@15b123b
09/05/07 07:12:25 INFO SYSTEM Operation: System Maintenance Operation for schedule:System Maintenance Schedule done.
09/05/07 07:12:25 INFO SYSTEM Operation: Bridge Operation for schedule:20 Minutes (From Start of the Hour) done.
09/05/07 07:12:25 INFO SYSTEM Notification Dispatcher exit
09/05/07 07:12:25 INFO SYSTEM Operation: Backhaul - Unpaired Master for schedule:10 Minutes (From Start of the Hour) done.
09/05/07 07:12:25 INFO SYSTEM Operation: Element - Ethernet Down for schedule:10 Minutes (From Start of the Hour) done.
09/05/07 07:12:25 INFO SYSTEM Operation: Hot RF Signal for schedule:12 Hour (Starting Midnight) done.
09/05/07 07:12:25 INFO SYSTEM Operation: RF - dBm Threshold Monitor for schedule:10 Minutes (From Start of the Hour) done.
09/05/07 07:12:25 INFO SYSTEM Operation: MIR Sustained Uplink > 500 for schedule:12 Hour (Starting Midnight) done.
09/05/07 07:12:25 INFO SYSTEM Operation: Backhaul - Unpaired Slave for schedule:10 Minutes (From Start of the Hour) done.
09/05/07 07:12:25 INFO SYSTEM Operation: Element - Poll Failed for schedule:10 Minutes (From Start of the Hour) done.
09/05/07 07:12:25 INFO SYSTEM PerformanceLogging: Unregistering NodeManager Listener
09/05/07 07:12:25 INFO SYSTEM NodeManagerListenerManager: Dispatcher Thread completed for listener com.mot.canopy.prizm.services.perflogging.PerformanceLogging2$1@129e5e9
09/05/07 07:12:25 INFO SYSTEM PerformanceLogging: Unregistered NodeManager Listener
09/05/07 07:12:25 INFO SYSTEM Shutting Down Performance Loggers
09/05/07 07:12:25 INFO SYSTEM Shutting down Logger: Performance Logging: 1 (5 Minute Interval)
09/05/07 07:12:25 INFO SYSTEM Operation: Performance Logging Operation: 1 (5 Minute Interval) for schedule:Performance Logging: 1 (5 Minute Interval) done.
09/05/07 07:12:25 INFO SYSTEM Shutting down Logger: Performance Logging: 2 (10 Minute Interval)
09/05/07 07:12:25 INFO SYSTEM Operation: Performance Logging Operation: 2 (10 Minute Interval) for schedule:Performance Logging: 2 (10 Minute Interval) done.
09/05/07 07:12:25 INFO SYSTEM Shutting down Logger: Performance Logging: 3 (15 Minute Interval)
09/05/07 07:12:25 INFO SYSTEM Operation: Performance Logging Operation: 3 (15 Minute Interval) for schedule:Performance Logging: 3 (15 Minute Interval) done.
09/05/07 07:12:25 INFO SYSTEM Shutting down Logger: Performance Logging: 4 (20 Minute Interval)
09/05/07 07:12:25 INFO SYSTEM Operation: Performance Logging Operation: 4 (20 Minute Interval) for schedule:Performance Logging: 4 (20 Minute Interval) done.
09/05/07 07:12:25 INFO SYSTEM Shutting down Logger: Performance Logging: 5 (25 Minute Interval)
09/05/07 07:12:25 INFO SYSTEM Operation: Performance Logging Operation: 5 (25 Minute Interval) for schedule:Performance Logging: 5 (25 Minute Interval) done.
09/05/07 07:12:25 INFO SYSTEM Shutting down Logger: Performance Logging: 6 (30 Minute Interval)
09/05/07 07:12:25 INFO SYSTEM Operation: Performance Logging Operation: 6 (30 Minute Interval) for schedule:Performance Logging: 6 (30 Minute Interval) done.
09/05/07 07:12:25 INFO SYSTEM Shutting down Logger: Performance Logging: 9 (45 Minute Interval)
09/05/07 07:12:25 INFO SYSTEM Operation: Performance Logging Operation: 9 (45 Minute Interval) for schedule:Performance Logging: 9 (45 Minute Interval) done.
09/05/07 07:12:25 INFO SYSTEM Shutting down Logger: Performance Logging: 12 (60 Minute Interval)
09/05/07 07:12:25 INFO SYSTEM Operation: Performance Logging Operation: 12 (60 Minute Interval) for schedule:Performance Logging: 12 (60 Minute Interval) done.
09/05/07 07:12:25 INFO SYSTEM Shutting down Logger: Performance Logging: 24 (2 Hour Interval)
09/05/07 07:12:25 INFO SYSTEM Operation: Performance Logging Operation: 24 (2 Hour Interval) for schedule:Performance Logging: 24 (2 Hour Interval) done.
09/05/07 07:12:25 INFO SYSTEM Shutting down Logger: Performance Logging: 36 (3 Hour Interval)
09/05/07 07:12:25 INFO SYSTEM Operation: Performance Logging Operation: 36 (3 Hour Interval) for schedule:Performance Logging: 36 (3 Hour Interval) done.
09/05/07 07:12:25 INFO SYSTEM Shutting down Logger: Performance Logging: 72 (6 Hour Interval)
09/05/07 07:12:25 INFO SYSTEM Operation: Performance Logging Operation: 72 (6 Hour Interval) for schedule:Performance Logging: 72 (6 Hour Interval) done.
09/05/07 07:12:25 INFO SYSTEM Shutting down Logger: Performance Logging: 144 (12 Hour Interval)
09/05/07 07:12:25 INFO SYSTEM Operation: Performance Logging Operation: 144 (12 Hour Interval) for schedule:Performance Logging: 144 (12 Hour Interval) done.
09/05/07 07:12:25 INFO SYSTEM Shutting down Logger: Performance Logging: 288 (24 Hour Interval)
09/05/07 07:12:25 INFO SYSTEM Operation: Performance Logging Operation: 288 (24 Hour Interval) for schedule:Performance Logging: 288 (24 Hour Interval) done.
09/05/07 07:12:25 INFO SYSTEM All Loggers Shut Down
09/05/07 07:12:25 INFO SYSTEM PerformanceLogging: Service Shutdown ok
09/05/07 07:12:25 INFO SYSTEM NodeManagerListenerManager: Dispatcher Thread completed for listener com.mot.canopy.prizm.services.elementconfigmanager.ElementConfigManager$1@179f36b
09/05/07 07:12:25 INFO SYSTEM Configuration Manager: Updater Thread exited
09/05/07 07:12:25 INFO SYSTEM Configuration Manager: CPLRelationshipChangeProcessor Thread completed
09/05/07 07:12:25 INFO SYSTEM NodeManagerListenerManager: Dispatcher Thread completed for listener com.mot.canopy.prizm.services.perfdb.PerformanceDB$1@11daa0e
09/05/07 07:12:25 INFO SYSTEM NodeManagerListenerManager: Dispatcher Thread completed for listener com.mot.canopy.prizm.services.networkmanager.NetworkManager$1@12922f6
09/05/07 07:12:26 INFO SYSTEM destroying SNMP Trap Receiver
09/05/07 07:12:26 INFO SYSTEM SNMP Trap Listener on 0.0.0.0/162 exit.
09/05/07 07:12:26 INFO SYSTEM NodeManagerListenerManager: Dispatcher Thread completed for listener com.mot.canopy.prizm.services.nodemanager.NodeStatusManager@1cbda0a
09/05/07 07:12:26 INFO SYSTEM Task scheduler exit
09/05/07 07:12:26 INFO SYSTEM Schedule Cleanup exits
09/05/07 07:12:26 INFO SYSTEM LogEvent Dispatcher: Thread completed
09/05/07 07:12:26 SEVERE SYSTEM Start Server failed: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can not re-read row data for column 1.
09/05/07 07:12:26 SEVERE SYSTEM EXCEPTION: com.mot.canopy.prizm.core.InvalidConfigurationException: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can not re-read row data for column 1.
com.mot.canopy.prizm.services.operationsmanager.OperationManager.postStartup(OperationManager.java:83)
com.mot.canopy.prizm.core.Server.loadServices(Server.java:1105)
com.mot.canopy.prizm.core.Server.startup(Server.java:793)
com.mot.canopy.prizm.core.Server.startServer(Server.java:616)
com.mot.canopy.prizm.core.Server.main(Server.java:325)
09/05/07 07:12:26 SEVERE SYSTEM Prizm Server Failed to Start. See above errors.

[Johnp]

"09/05/07 07:12:26 SEVERE SYSTEM Start Server failed: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can not re-read row data for column 1.
09/05/07 07:12:26 SEVERE SYSTEM EXCEPTION: com.mot.canopy.prizm.core.InvalidConfigurationException: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can not re-read row data for column 1."

Here is the interesting part, “can not re-read row data for column 1.”

Looks like either the database is corrupt now or it’s complaining about the JDBC driver. I would try changing the JDBC driver, unless it was Canopy that instructed you on which one to use in the first place.

We have had databases get corrupted because of power outages. If you have a back up of the database you might want to revert back to it.

Hope that points you in the right direction.

[Dave_Wilson]

Johnp wrote:

"09/05/07 07:12:26 SEVERE SYSTEM Start Server failed: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can not re-read row data for column 1. 09/05/07 07:12:26 SEVERE SYSTEM EXCEPTION: com.mot.canopy.prizm.core.InvalidConfigurationException: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can not re-read row data for column 1." Here is the interesting part, “can not re-read row data for column 1.” Looks like either the database is corrupt now or it’s complaining about the JDBC driver. I would try changing the JDBC driver, unless it was Canopy that instructed you on which one to use in the first place. We have had databases get corrupted because of power outages. If you have a back up of the database you might want to revert back to it. Hope that points you in the right direction.

We had a problem with exactly the same symptoms as described. The solution was this KB article.

Hope this helps,
Dave.