Error on server request getMap. System error has occured, exception is: NullPointerException:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-12-2018 09:44 PM
Hi Team,
We're discovering the business services and all of a sudden after the discovery we started getting the following error:
Error on server request getMap. System error has occured, exception is: NullPointerException:
Any help will be appreciable.
Thanks in advance.
Regards
Ankit
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-12-2018 09:58 PM
Hi Ankit,
Any other error you see in logs.
Regards
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-12-2018 10:48 PM
Hi Ankur,
Thanks for the reply.
It is not showing any error as well as it is not loading the map which was discovered earlier.
Regards
Ankit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-13-2018 04:58 AM
There is a UI Action on the Business Service form view (not the map view) called "Recompute Business Service." Try clicking that and then re-running a full service discovery.
If that fails, look for a UI Action called "Sync with Service Model" on the cmdb_ci_service_discovered table which has a role required of "maint". Insert and Stay that UI Action and create a copy that doesn't have the requirement of the maint role, and then run it on that service.
The record is in your instance at /nav_to.do?uri=sys_ui_action.do?sys_id=35325d00ff020200ab8fffffffffffd3
This might be able to re-sync your service with its model data.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-13-2018 05:33 AM
Johnny approach is your best option. If this doesn't fix this then open up a HI ticket as it's probably something deeper that needs to be investigated.