Question

PSO : Unable to cast object of type 'System.DBNull' to type 'System.Int32'

  • 19 February 2022
  • 9 replies
  • 445 views

Userlevel 1
Badge +4

Hi,

 

We are observing the below error while restarting “PSO : Input Manager” service.

It keeps erroring with the below message, can you please assist with the same.

 

“Unable to cast object of type 'System.DBNull' to type 'System.Int32'. at ThreeSixty.Schema.DsModelling.RAM_UpdateRow.get_organisation_id() at ThreeSixty.BOL.ArchiveDataHandler.InsertAuditData(IDbCommand command, DataSet auditData, Nullable`1 nExternalDatabaseId, Int32 nInternalId, Int32 nPlanId, String strAuditDescription, Boolean updateSuccessful, EResult result) at ThreeSixty.BOL.ArchiveDataHandler.<>c__DisplayClass45_0.<InsertAuditData>b__0(IDbCommand cmd) at ThreeSixty.DAL.DbInternalBase.Command(Func`2 func, Action onRetry, Boolean withRetry)”


This topic has been closed for comments

9 replies

Userlevel 7
Badge +17

Hi,

It sounds like organisation_id has not been set on the RAM_Update row

Thanks

Phil

Badge +4

Hi,

It sounds like organisation_id has not been set on the RAM_Update row

Thanks

Phil

Hi Phil, where is this RAM_Update row setup?

Userlevel 7
Badge +17

Hi,

It sounds like organisation_id has not been set on the RAM_Update row

Thanks

Phil

Hi Phil, where is this RAM_Update row setup?

Hi,

It is in the input data and defined in the integration

Thanks

Phil

Badge +4

Hi,

It sounds like organisation_id has not been set on the RAM_Update row

Thanks

Phil

Hi Phil, where is this RAM_Update row setup?

Hi,

It is in the input data and defined in the integration

Thanks

Phil

Hi Phil,
Thank you for your quick response. Could you please guide me to where it is in the application. Kindly point me to the screen on FSM or PSO.

Thanks.
Kind regards.
 

Userlevel 7
Badge +17

@Lee Pinchbeck can you help on the FSM side please

Userlevel 7
Badge +24

Hi @CalvinAM,

The RAM tables for PSO integration are system tables not directly exposed in FSM. The data is collated from several screens in FSM that control the setup of the PSO datasets, resources etc.

The guide here:

Goes through the setup so should cover the locations that need checking in case something is missing for it not to pull in the organisation ID. 

Is there any more information from the input and error as to what the rest of the line containing the null ID contains? If we know the rest of the record information it would be easier to point to where this has come from.

Kind regards,

Lee Pinchbeck 

Badge +4

Hi @Lee Pinchbeck ,
Thank you for your feedback,

However, there is no reference to the organization ID in the integration Guide shared, that points to this error.

We basically get this error while trying to initialize a any Dataset on FSM from the Scheduling Manager window. We are also getting an error related to an INVALID_REMOTING_STRING.

Our FSM version: 6U15.8040
PSO Version: 6.8.0.26

There is really not much more to provide regarding the information from the input. It happens when we initiate the initialize action from the Schedule manager.

Kind Regards
Calvin Atwongyeire.

Userlevel 1
Badge +2

HI ,

      We are also facing the same issue,How were you able to resolve this,Can you please let us know,It would help us with our issue as well

Badge +4

Solution for this issue was to check delete all the files in the “Input Folder”, then restart the SIM service. Once this was done the Input service started to respond fine and this error cleared.