Clarity Service Management

Expand all | Collapse all

Custom form is not able to submit in 17.1

Jump to Best Answer
  • 1.  Custom form is not able to submit in 17.1

    Posted 10-12-2018 08:42 AM

    Hello,

     

    We have one service in which we are using TABLE (System Component), After providing the required data in fields am trying to submit the request. But it not submitting. When i click on SUBMIT button its getting disabled. And i found some ERROR logs in system.

     

    Please help me in fixing this issue.

     

    2018/10/12 00.26.24.609 ERROR [SimpleAlarmMgr-Init] [DBSource] Error while saving object:{task_id=rm_reservation_status_task, name=Reservations Status Updater, comment=null, day_of_month=-1, day_of_week=-1, hour=-1, minute=-1, month=-1, status=1, task_to_exec=com.ca.usm.integration.reservationmgr.RMStatusUpdateTask, type=Minutely, year=-1, start_date=2018/09/10 11:12:19, end_date=null, requestor=general, runtime_component_id=Scheduler, action_type=0, data1=, data2=, data4=, data5=, interval=10, description=Updates reservation status when it is past it's end date, action_description=null, created_date=2018/09/10 11:12:19, last_exec_date=1752/12/31 18:18:00, missed_action=0, user_id=spadmin, modified_date=2018/10/11 13:56:46, guinode_id=, tenant_id=WiproDCS, time_zone_code=GMT-06:00 America/Chicago, comments=null, data3=}
    2018/10/12 00.26.24.609 ERROR [SimpleAlarmMgr-Init] [Task] Error creating ictask object.
    com.microsoft.sqlserver.jdbc.SQLServerException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.
    at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:217)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1635)
    at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:426)
    at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:372)
    at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:6276)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1794)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:184)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:159)
    at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate(SQLServerPreparedStatement.java:315)
    at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98)
    at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98)
    at com.ca.usm.datasource.DBJDBC.update(DBJDBC.java:1281)
    at com.ca.usm.datasource.DBSource.executeUpdate(DBSource.java:1527)
    at com.ca.usm.datasource.DBSource.save(DBSource.java:1714)
    at com.ca.usm.scheduler.Task.save(Task.java:109)
    at com.ca.usm.scheduler.AlarmEntry.saveAlarm(AlarmEntry.java:275)
    at com.ca.usm.scheduler.AlarmAction.run(AlarmAction.java:132)
    at com.ca.usm.scheduler.SimpleAlarmMgr.addAlarm(SimpleAlarmMgr.java:436)
    at com.ca.usm.scheduler.SimpleAlarmMgr.addAlarmAndProcessAllMissed(SimpleAlarmMgr.java:329)
    at com.ca.usm.scheduler.SimpleAlarmMgr.initialize(SimpleAlarmMgr.java:88)
    at com.ca.usm.scheduler.SimpleAlarmMgrInitializer$1.run(SimpleAlarmMgrInitializer.java:27)
    at java.lang.Thread.run(Unknown Source)



  • 2.  Re: Custom form is not able to submit in 17.1
    Best Answer

    Posted 10-12-2018 01:43 PM

    Akram,

     

    It needs to be looked into specifically .

     

    It has quite lots of defects with forms in catalog  17.1 .  At this point of time ,  you will need to have your catalog patched up with catalog 17.1 rollup1 and also several incremental patches .  

     

    I would suggest you open a support case  via support.ca.com to contact catalog support by providing the following :

     

    1.  CA_SLCM_<machine name>.HIS file on your catalog server so that we can check your catalog 17.1's patch level .  This file is located at the catalog installation home folder .

     

    2.  login the catalog GUI ,  go to Administration -> Tools -> Import Export Utility  to export that service offering ( by checking "Include Forms" checkbox  . Attach   the exported file to the support support case .

     

    With the files above ,  catalog support will be able to look into this problem specifically .

     

    Thanks, Jing