MWM/ORS Reports 'No such stop' After SMAuto Restart Due To Differing Geocodes For Similiar SiteIDs
(Doc ID 1605055.1)
Last updated on APRIL 17, 2017
Applies to:Oracle Utilities Mobile Workforce Management - Version 2.0 and later
Oracle Real-Time Scheduler - Version 2.1.0 and later
Information in this document applies to any platform.
In a production system, several activities could not be dispatched. The Scheduler reports that the activity does not exist with a "No such stop" error. This incident has been reported a number of times.
SMAuto logs show:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!