" /> Reporting Server status displays as inititalized only in GA - Genesys CTI User Forum

Author Topic: Reporting Server status displays as inititalized only in GA  (Read 2887 times)

Offline mumtazalam2k

  • Jr. Member
  • **
  • Posts: 55
  • Karma: 0
Advertisement
I am installing RS in a single standalone setup.
I am able to start RS successfully, however its status always shows as Initialized only in GA with an exclamation.

Any clues what could be the reason.

I created the Oracle schema, modified the default language as well in Java Panel and the ini file.

22:17:47.171 Trace vpmum1gvp01 RS1 GCTI-153-04100 com.genesyslab.commons.log4j.LoggingManager Logging service started
22:17:47.187 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.service.StandAloneReportingService Successfully obtained configuration from configuration server.
22:17:47.281 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.service.StandAloneReportingService Creating HTTP connector on: 8080
22:17:47.343 Trace vpmum1gvp01 RS1 GCTI-153-04500 com.genesyslab.commons.lca.LCAManager Connecting to Local Control Agent 'LCA' at host 'localhost', port 4999
22:17:47.343 Standard vpmum1gvp01 RS1 GCTI-153-05061 com.gvp.rpt.service.StandAloneReportingService Initialization completed
22:17:47.359 Standard vpmum1gvp01 RS1 GCTI-153-04503 com.genesyslab.commons.lca.LCAManager Connected to Local Control Agent 'LCA' at host 'localhost', port 4999
22:17:47.359 Trace vpmum1gvp01 RS1 GCTI-153-20001 com.genesyslab.commons.lca.LCAManager  Reporting Server initializing in 'standalone' mode
22:17:47.359 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.service.StandAloneReportingService PARTITIONING_ENABLED is true. Using configuration - [Ljava.lang.String;@1ba1d9
22:17:48.968 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.dao.SessionFactoryBean Building new Hibernate SessionFactory
22:17:51.750 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.service.RSBrokerFactoryBean Supported JMS broker connections: UNENCRYPTED
22:17:51.750 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.service.RSBrokerFactoryBean JMS broker listening on: tcp://0.0.0.0:61616?transport.closeAsync=false
22:17:52.140 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.partitioning.PartitionMaintenanceJob Partitioning Job INIT STARTED 1274546872140
22:17:52.296 Interaction vpmum1gvp01 RS1 GCTI-153-30000 com.gvp.rpt.partitioning.dao.LastPartitionedDaoImpl Failed to locate partitioned data for RMCallDetailRecord
22:17:52.437 Interaction vpmum1gvp01 RS1 GCTI-153-30000 com.gvp.rpt.partitioning.dao.LastPartitionedDaoImpl Failed to locate partitioned data for RMCallDetailRecordExt
22:17:52.453 Interaction vpmum1gvp01 RS1 GCTI-153-30000 com.gvp.rpt.partitioning.dao.LastPartitionedDaoImpl Failed to locate partitioned data for MCPCallDetailRecord
22:17:52.468 Interaction vpmum1gvp01 RS1 GCTI-153-30000 com.gvp.rpt.partitioning.dao.LastPartitionedDaoImpl Failed to locate partitioned data for MCPCallDetailRecordExt
22:17:52.468 Interaction vpmum1gvp01 RS1 GCTI-153-30000 com.gvp.rpt.partitioning.dao.LastPartitionedDaoImpl Failed to locate partitioned data for CCPCallDetailRecord
22:17:52.484 Interaction vpmum1gvp01 RS1 GCTI-153-30000 com.gvp.rpt.partitioning.dao.LastPartitionedDaoImpl Failed to locate partitioned data for CCPCallDetailRecordExt
22:17:52.500 Interaction vpmum1gvp01 RS1 GCTI-153-30000 com.gvp.rpt.partitioning.dao.LastPartitionedDaoImpl Failed to locate partitioned data for VARCallDetailRecord
22:17:52.515 Interaction vpmum1gvp01 RS1 GCTI-153-30000 com.gvp.rpt.partitioning.dao.LastPartitionedDaoImpl Failed to locate partitioned data for CustomVarDTO
22:17:52.515 Interaction vpmum1gvp01 RS1 GCTI-153-30000 com.gvp.rpt.partitioning.dao.LastPartitionedDaoImpl Failed to locate partitioned data for GenericLog
22:17:52.546 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.partitioning.PartitionMaintenanceJob Partitioning Job INIT COMPLETEDs.
22:17:52.609 Trace vpmum1gvp01 RS1 GCTI-153-20007 com.gvp.rpt.service.DateComponentsPopulationJob DateComponents Population job run
22:17:52.625 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.service.DateComponentsPopulationJob Populating DateComponents from Fri May 01 00:00:00 GMT+05:30 2009 until Sun May 01 00:00:00 GMT+05:30 2011
22:17:52.625 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.dao.DateComponentsDao Populating date components from Fri May 01 00:00:00 GMT+05:30 2009 to Sun May 01 00:00:00 GMT+05:30 2011
22:17:53.031 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.dao.DateComponentsDao Added 730 records
22:17:53.078 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.service.DateComponentsPopulationJob Populating TimeComponents
22:17:53.156 Trace vpmum1gvp01 RS1 GCTI-153-20008 com.gvp.rpt.service.DateComponentsPopulationJob DateComponents Population job complete
22:17:55.078 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.var.service.VARStatsGenerator Shutting down VAR Stats Generator...
22:17:55.078 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.var.service.MetricSerialProcessor Shutting down MetricSerialProcessor...
22:17:55.078 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.var.service.VARStorageService Shutting down VAR Storage Service...
22:17:56.062 Trace vpmum1gvp01 RS1 GCTI-153-20000 com.gvp.rpt.dao.SessionFactoryBean Closing Hibernate SessionFactory
22:17:56.078 Standard vpmum1gvp01 RS1 GCTI-153-50000 com.gvp.rpt.service.StandAloneReportingService Unable to start RS application context, shutting down. org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'usageResetJob' defined in class path resource [quartz.config.xml]: Cannot resolve reference to bean 'usageResetService' while setting bean property 'targetObject'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'usageResetService' defined in class path resource [ems-rs.xml]: Cannot resolve reference to bean 'orUsageStorageService' while setting bean property 'service'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'orUsageStorageService' defined in class path resource [ems-rs.xml]: Invocation of init method failed; nested exception is org.hibernate.exception.SQLGrammarException: could not execute query
22:17:56.078 Standard vpmum1gvp01 RS1 GCTI-153-30001 com.genesyslab.commons.lca.LCAManager Reporting Server is unable to change its runtime mode
22:32:11.468 Debug vpmum1gvp01 RS1 GCTI-153-09900 com.genesyslab.commons.log4j.LoggingManager RS Logging configuration has being updated successfully

Offline mumtazalam2k

  • Jr. Member
  • **
  • Posts: 55
  • Karma: 0
Re: Reporting Server status displays as inititalized only in GA
« Reply #1 on: May 23, 2013, 06:12:15 AM »
Anyways it seems I have solved it,
I granted dba privileges to the report sql user and did a reinstall of the oracle schema, and now my RS shows as started.