Skip to main content
Question

error message integration process flow : rest dispatcher failed


Forum|alt.badge.img+11

Hello since today w ehave 3 process flow rest interfaces which are no more working with the following error : REST dispatcher failed. See Event Viewer for more information .

when we look at the event viewer we have the error : 

Unexpected error occurred in method Route( )
Original error: Cannot cast DBNull.Value to type 'System.Int32'. Please use a nullable type.
Stack trace:    at System.Data.DataRowExtensions.UnboxT`1.ValueField(Object value)
   at Astea.EO.EventBroker.DataHandler.Dispatcher.Implementation.FetchingPolicy.<>c__DisplayClass29.<FetchSequenceEntitiesFromDB>b__1f(DataRow m)
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
   at System.Linq.Enumerable.<TakeIterator>d__25`1.MoveNext()
   at Astea.EO.EventBroker.DataHandler.Dispatcher.Dispatcher.Route(Object data)

 

what we should look ? i have restart several times the astea data handler dispatcher with no sucess

thanks for your help

Rgds

Christophe

3 replies

Forum|alt.badge.img+11
  • Author
  • Sidekick (Partner)
  • 80 replies
  • December 7, 2021

It looks like there was an issue on the customer process flow endpoint , the error message was not clear and we didn’t know if the message was effectivly sent or not


Forum|alt.badge.img+12
  • Superhero (Employee)
  • 112 replies
  • December 7, 2021

Similar error was reported by a customer running 15.1.0.9 in the past.
It appeared after a windows update that was not installed successfully.
After reinstalled the windows update and the Util server was rebooted, the dispatcher started to send messages again.
Please check most reason windows update.
Server reboot may be worth to try if nothing helps.
Please also restart DefaultAppPool or custom Integration pool if any.


Forum|alt.badge.img+7
  • Sidekick (Customer)
  • 39 replies
  • December 8, 2021

last week we had an similar issue with a process flow. it was affecting only one server. after we restarted the server, it worked fine again. (assumed it was an issue with the workflow task executor service) 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings