EAM Map Workbench Fails With Error 404--Not Found .....
(Doc ID 2390552.1)
Last updated on AUGUST 19, 2022
Applies to:
Oracle Enterprise Asset Management - Version 12.2.5 and laterInformation in this document applies to any platform.
Symptoms
When attempting to 'Map All' using the map workbench the following error occurs.
ERROR
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be
used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
STEPS
The issue can be reproduced at will with the following steps:
Asset Number must have entered geocode:
To check this go to:
1. (N) Assets > Capital > Query Asset Number = “CT” > View: Details > Go, longitude and latitude are shown
2. Click 'Map All' button to locate the asset in the Google Map Viewer.
3. Error 404--.....
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |