schemaRevisionDate issue

[gzhao888]

In IncidentManagement.wsdl, there is an attribute schemaRevisionDate. On SC 6.2.4, the attribute returns a value of "00:00:00" as a SOAP response, which causes Axis 1.4 throws a NumberFormatException: Invalid Date. From sc.log the schemaRevisionDate value is from SOA revision time as shown in the following log entries

23242(5949967) 02/27/2009 21:06:51 RTE D Operation will be carried out on file probsummary
23242(5949967) 02/27/2009 21:06:51 RTE D doQuery using query string number="4000002179"
23242(5949967) 02/27/2009 21:06:51 RTE D doGet query returned 1
23242(5949967) 02/27/2009 21:06:51 RTE D SOA revision time is 00:00:00
23242(5949967) 02/27/2009 21:06:51 RTE D SOA revision level is 2
23242(5949967) 02/27/2009 21:06:51 JRTE D buildSoapResp(): cAttachments size = 0
23242(5949967) 02/27/2009 21:06:51 JRTE D sendResponse() Retrieve completed
23242(5949967) 02/27/2009 21:06:51 JRTE I doShutdown -- iTermination Signal: 0

SOA revision time should return a date string such as 2009-02-10 but it returns 00:00:00. Apparently the log entries were generated from run time environment. Does this mean I need to fix this in C code or a RAD application? The information on where to look into to fix this is needed.

Thanks.

[glg]

you can't update either the C code or the RAD applications. Most likely, you're going to need to open a ticket with HP.

[tommy]

Yes if its in binary only HP can correct that. If it is in RAD, HP or a HP Partner with a RAD license can correct that.

Though RTE in the log file suggests to me that it is binary so you need to report this to HP to get it fixed.

[fid509]

Hello,

Did you got an solution on this problem? I use 6.2.7.3 and when I retrieve info from an incident in VB I got the same issue.

thx,
Geert

[fid509]

I found where that date is coming from. Inside the system Information record there is field called soa.revision.time that was set to '00:00:00' in our TEST environment. I changed it to a valid datetime and the problem is solved.

[nobody13]

This is an issue known to HP, I don't have the SCR number handy and of course I can't find it on the HP site.
This soa revision time is reset back to 00:00:00 when ever an extaccess record is updated. To work around it, we added a trigger to the "info" table to revert it back. And, I think it might only happen on systems pushed to Oracle.... or something particular such as that.

I hope that helps.
Happy Thursday,
--- Travis