Video Screencast Help

Proper use of "SearchIncident" Component for SD7

Created: 16 Mar 2011 | 8 comments

I'd like to look up an incident based on the incident number with the "SearchIncident" component. I fill out all of the criteria, but I'm not sure what to put in the "input" for "Exchange Connection String". I get the below error. Anyone out there used this before?

Error Details

Error Message:
Input string was not in a correct format.

Message Stack:
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at LogicBase.Core.Messaging.MessageExchangeFactory.CreateRemoteTarget(String name)
at LogicBase.Core.Messaging.MessageExchangeFactory.GetExchangeTarget(String name, Boolean internalRequest)
at LogicBase.Core.Messaging.MessageExchangeFactory.GetExchange(String name, Boolean internalRequest)
at LogicBase.Core.Messaging.MessageExchangeFactory.GetExchange(String name)
at SD.Components.DB.SearchIncident.Run(IData data)
at LogicBase.Core.ExecutionEngine.MultiPathProcessComponentExecutionDelegate.Execute(IData data, IOrchestrationComponent comp, String& outputPath, IExecutionEngine engine, TLExecutionContext context)
at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.DoRunComp(IOrchestrationComponent comp, IData data, TLExecutionContext context)

Comments 8 CommentsJump to latest comment

reecardo's picture

Try using "local.orm"... the object relational mapper local to the machine.

Jimbaland's picture

Error Details

Error Message:
Invalid object name 'ObjectStructureCheck'.

Message Stack:
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at LogicBase.Core.Messaging.Implementations.InsertStatement.Execute(SqlConnection conn, SqlTransaction tr)
at LogicBase.Core.Messaging.Implementations.InsertOrUpdateStatement.RunInsertStatement(SqlConnection conn, SqlTransaction tr)
at LogicBase.Core.Messaging.Implementations.InsertOrUpdateStatement.Execute(SqlConnection conn, SqlTransaction tr)

reecardo's picture

Just checking here:

Do you have a SQL backend? If so, do you have ServiceDesk installed?

jvenuto's picture

Just in case, check this tech article or

I got this error before.  Apprently something renamed the table in the database for my issues

reecardo's picture

I think (maybe) what you have to do is add a type to the Storage Preferences tab of Project Properties to represent an Incident perhaps (XML Serialization preference)

The IncidentManagement process has this set up if you have access to the .package.

Jimbaland's picture

The storage preferences tab had logicbase.core.datatypes.filedatatype with Binary as the serialization. I added with XML seriaization and got the same results as last time (ObjectStructureCheck).

coloup's picture


Did you by any chance get to the bottom of this? I am having exactly the same problem.