Google Maps API Issue stating "Oops! Something went wrong"
If OpManager 12100 is installed after 22nd July,
Issue - While clicking on Google Maps, We'll get the below error:
On Jun 22nd, 2016 onward the Google has restricted the access to "Google Map API" only by valid API key, hence the issue.
Note :The issue will occur only if the installation done on or after June 22nd, 2016,The access restriction is applicable for domain specific only. Which is 25000 loads per day.Please check the below google document for more information.
How to solve this issue?
We can solve this issue by providing valid API key during the Google MAP API access.1. How to get the API Key:Please refer the below document to generate API Key.2. Where to place the API key in Opmanager.1. Go to the OpManager Instillation folder.2. Open map.html from <OpManager_home>apiclient luidicv2 directory.3. Append the API key in the Google map URL as a parameter like (&key=<Your_API_Key>), In the script tag's src attribute.Example:If your API kay is xxxxxxxxxxxxxxxx. The script tag will be.<script type="text/javascript" src="//maps.googleapis.com/maps/api/js?sensor=false&language=en&key=xxxxxxxxxxxxxxxx"></script>4. Save the map.html file.5. Wait for 5 mins to API Key reflect in Opmanager.
New to ADSelfService Plus?
Related Articles
Firewall Logs time stamp issue for Sonicwall Devices in ManageEngine Firewall Analyzer V12
Issue: Not able to see any Syslog traffic in Firewall Log analyzer. Solution : When checked the raw Logs received from the Firewall , the time stamp are based on UTC time where as the server time and the Firewall device time was with EST time. ...How to work with unknown devices in OpManager?
There are 2 reasons for devices to go in to "Unknown" Category in OpManager: 1)Device credentials (SNMP/WMI/CLI) are not added or discovered with wrong credentials in OpManager. 2)Credentials are correct but OpManager does not have built-in Device ...Device/Interface Name not populating in Traffic (NFA) Module for SNMP V3 - OpManager v12
Issue: Device/Interface Name not getting populated for N/w Devices monitored using SNMP V3 protocol OpManager v12. Analysis: When the device takes longer time to respond for the SNMP V3 requests, then the device name will not get populated in the ...OpManagerv12 -SDP MSP (build 9005 and above) integration
Opmanager integrates with SDP MSP via API using login details for sending the emails to ServiceDesk. This integration allows Technicians to log critical alarms raised in OPM as tickets in ServiceDesk and track those tickets. For integration configure ...