Missing entity mappings in Meraki Service Graph Connector 1.5

Steelneck
Comes here often

Missing entity mappings in Meraki Service Graph Connector 1.5

Hi,

We have run into errors with the latest version of Meraki Service Graph Connector (1.5)

Both me, and a colleague of mine are running into issues with the 1.5 version which was released with support for Xanadu.

I have tried upgrading from an earlier version, and he has tried a clean install and we both get the same issues.

 

What we're encountering is that there appears to be missing references between fields in the robust transform map.

This leads to the import of data failing immediately without any actual write happening. This is one of the error messages from a failed import set:

 

java.lang.IllegalArgumentException: Invalid Entity class for field (name: location, sysid: 8d4ee2901b479610f5cf97d7b04bcb85)
at com.glide.robust_transform_engine.definition_provider.RteEntityBasedCoordinator.validateEntities(RteEntityBasedCoordinator.java:39)
at com.glide.robust_transform_engine.definition_provider.RteEntityBasedCoordinator.<init>(RteEntityBasedCoordinator.java:28)
at com.glide.robust_transform_engine.definition_provider.CmdbRobustTransformEngineDefinitionProvider.getRobustTransformEngineDefinition(CmdbRobustTransformEngineDefinitionProvider.java:99)
at com.glide.robust_transform_engine.RobustTransformEngineDefinitionLoader.getRobustTransformDefinition(RobustTransformEngineDefinitionLoader.java:42)
at com.glide.robust_transform_engine.RobustTransformEngine.getRTEDefinition(RobustTransformEngine.java:435)
at com.glide.robust_transform_engine.RobustTransformEngine.<init>(RobustTransformEngine.java:93)
at com.glide.robust_transform_engine.RobustTransformEngine$Builder.build(RobustTransformEngine.java:156)
at com.glide.db.impex.transformer.service.RobustImportSetProcessor.init(RobustImportSetProcessor.java:63)
at com.glide.db.impex.transformer.service.RobustImportSetProcessor.<init>(RobustImportSetProcessor.java:54)
at com.glide.system_import_set.ImportSetTransformerImpl.doRobustImportSetTransform(ImportSetTransformerImpl.java:164)
at com.glide.system_import_set.ImportSetTransformerImpl.transformAllMaps(ImportSetTransformerImpl.java:114)
at com.glide.system_import_set.ImportSetTransformer.transformAllMaps(ImportSetTransformer.java:91)
at com.snc.automation.ImportSetTransformerJob.runTransform(ImportSetTransformerJob.java:291)
at com.snc.automation.ImportSetTransformerJob.execute(ImportSetTransformerJob.java:103)
at com.glide.schedule.JobExecutor.lambda$executeJob$1(JobExecutor.java:195)
at com.snc.db.data_replicate.replicator.DataReplicationAdvisors.runInOriginatorContext(DataReplicationAdvisors.java:74)
at com.glide.schedule.JobExecutor.lambda$inDataReplicationContext$3(JobExecutor.java:225)
at com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:198)
at com.glide.schedule.JobExecutor.execute(JobExecutor.java:178)
at com.glide.schedule.JobExecutor.execute(JobExecutor.java:168)
at com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:609)
at com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$2(SchedulerWorkerThread.java:402)
at com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35)
at com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:402)
at com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:178)

Screenshot 2025-02-04 at 08.41.18.pngScreenshot 2025-02-04 at 08.40.38.png

 

Anyone else run into this issue? Anyone got a solution?

18 Replies 18
Ray1411
Conversationalist

I am running into the exact same issue when trying a clean install for Xanadu.

Seth_Bright
New here

We have also been experience this issue after upgrading our Meraki-SG connector to 1.5 in our test/dev environment.

SergeyT
Conversationalist

Having the same issue, updated on my DEV instance from 1.4.0 to 1.5.0 and getting these errors:

java.lang.IllegalArgumentException: Invalid Entity class for field (name: location, sysid: <removed sys id>)
at com.glide.robust_transform_engine.definition_provider.RteEntityBasedCoordinator.validateEntities(RteEntityBasedCoordinator.java:39)
at com.glide.robust_transform_engine.definition_provider.RteEntityBasedCoordinator.<init>(RteEntityBasedCoordinator.java:28)
at com.glide.robust_transform_engine.definition_provider.CmdbRobustTransformEngineDefinitionProvider.getRobustTransformEngineDefinition(CmdbRobustTransformEngineDefinitionProvider.java:99)
at com.glide.robust_transform_engine.RobustTransformEngineDefinitionLoader.getRobustTransformDefinition(RobustTransformEngineDefinitionLoader.java:42)
at com.glide.robust_transform_engine.RobustTransformEngine.getRTEDefinition(RobustTransformEngine.java:435)
at com.glide.robust_transform_engine.RobustTransformEngine.<init>(RobustTransformEngine.java:93)
at com.glide.robust_transform_engine.RobustTransformEngine$Builder.build(RobustTransformEngine.java:156)
at com.glide.db.impex.transformer.service.RobustImportSetProcessor.init(RobustImportSetProcessor.java:63)
at com.glide.db.impex.transformer.service.RobustImportSetProcessor.<init>(RobustImportSetProcessor.java:54)
at com.glide.system_import_set.ImportSetTransformerImpl.doRobustImportSetTransform(ImportSetTransformerImpl.java:164)
at com.glide.system_import_set.ImportSetTransformerImpl.transformAllMaps(ImportSetTransformerImpl.java:114)
at com.glide.system_import_set.ImportSetTransformer.transformAllMaps(ImportSetTransformer.java:91)
at com.snc.automation.ImportSetTransformerJob.runTransform(ImportSetTransformerJob.java:291)
at com.snc.automation.ImportSetTransformerJob.execute(ImportSetTransformerJob.java:103)
at com.glide.schedule.JobExecutor.lambda$executeJob$1(JobExecutor.java:194)
at com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:197)
at com.glide.schedule.JobExecutor.execute(JobExecutor.java:177)
at com.glide.schedule.JobExecutor.execute(JobExecutor.java:167)
at com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:577)
at com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$2(SchedulerWorkerThread.java:396)
at com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35)
at com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:396)
at com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:172)

JoeG1
Just browsing

Same issue here after upgrading in PROD. Has anyone found a fix? We have also opened a call with ServiceNow.

Jhansi
Here to help

Did you get any response from ServiceNow?

SergeyT
Conversationalist

Hi, I also raised a ticket with SNOW, only automatic reply so far that they are looking into issue and will get back to me once they have anything.

Jhansi
Here to help

Hi we are also facing the same issue. Did you get any resolution so far?

SergeyT
Conversationalist

I checked my records with Empty Entity Mapping and they weren't changed since early January this year, and I did update version Yesterday, so I don't think this is the cause.

SergeyT
Conversationalist

Here's an answer I got from SNOW support. As I expected SNOW support points to Meraki support:

I am marking this case as "Solution Proposed" with the below information.


Solution Proposed:
Please note that this is a 3rd party application, which is developed and supported by Meraki. 3rd party apps are out of scope for Technical Support as we only deal with OOTB integrations and break fixes.

We recommend you reach out to Meraki support for the issue you are facing currently.

Store link
https://store.servicenow.com/sn_appstore_store.do#!/store/application/dc27a74a80421010f8772cdfe9d5f8...

Support Contacts mentioned in above link,
Meraki Support
+1 4159376671

Kindly let me know in case of any queries.

SergeyT
Conversationalist

I called Meraki support number indicated on connector page a few minutes and they told me that this is inappropriate channel for customers to reach out, and that ServiceNow team should reach out to Meraki team and work on the issue.

Jhansi
Here to help

I have a Meraki support case open by my colleague. We are trying to follow up and see if they have any resolution. I will update here.

SatyaUndrakunta
New here

Do the below updates on Transformer Definition "SG-Meraki Devices" to fix this issue.

 

Step 1: Add IP Address 1 to the Serial Number  and Network Adapter rows where there is Lookup for Entity field value is empty (Related listCMDB Integration Studio Entities)

SatyaUndrakunta_0-1739575858357.png

Step 2: Add Add IP Address 1 to all the rows where Entity field value is empty. (Related list: RTE Entity Fields)

SatyaUndrakunta_1-1739576297031.png

 

Step 3: Make sure IP Address 1 is associated with tempToIP Address 1 (Related list: RTE Entity Mappings)

SatyaUndrakunta_2-1739576601798.png

 

Step 4: Update Entity Mapping field with tempToIP Address 1 (Related list: RTE Field Mappings)

SatyaUndrakunta_3-1739576797922.png

 

 

Ray1411
Conversationalist

Thanks, this really helped, robust transform map is working after implementing your solution.
However, I am getting the following error.
Error:

{"x_caci_sg_meraki_meraki_organization":{"unchanged":1},"cmdb_ci_wap_network":{"updated":2},"x_caci_sg_meraki_meraki_network":{"unchanged":1},"x_caci_sg_meraki_meraki_custom_ci_fields":{"inserted":1},"cmdb_ci_network_adapter":{"unchanged":1},"cmdb_serial_number":{"unchanged":1},"cmdb_rel_ci":{"incomplete":1,"inserted":1,"unchanged":2,"errors":1},"cmdb_ci_ip_address":{"mergedPartialPayloads":1,"updated":1}}

 

Ray1411_1-1739880285981.png

 

SergeyT
Conversationalist

After applying this fix, I no longer see a java error, but it doesn't import anything, so it is still not workingScreenshot 2025-02-18 at 7.49.24 AM.png

SergeyT
Conversationalist

Also, these two didn't exist in 1.4.0, I just compared to my prod instanceScreenshot 2025-02-18 at 8.14.35 AM.png

Misanab
New here

We too are actively having this issue and we've updated all our servicenow instances with this newer 1.5 version. In speaking with Meraki support today, they've indicated that they have no control over how ServiceNow presents the SGC Connector and the different versions that might be available, but that they (Meraki) have provided ServiceNow with all the versions and their corresponding related install files.. 

 

Separately I too had a ServiceNow ticket open which originally they did the default pass along and pointed us to Meraki Support, I've since escalated and challenged this indicating that although Meraki support and their developers are aware of the issues and are working to fixing the issues, we should at least have the ability to downgrade to a lower working version. So that the ServiceNow technician is taking back to his internal team to provide a fix or methodology for. 

Misanab
New here

Further Update from ServiceNow Support, which really puts a wrench in all this. I'm told the older version of the Meraki SGC Connector (1.4) supports only Vancouver and Washington - NOT Xanadu. So anyone running Xanadu if they've already installed the 1.5 version cannot go back to the older version. Which is the case for us, So my platform architect will take a look at some of those potential fixes provided above to see if maybe he can get it to work with some tweaks, if so, I will most certainly update this thread for everyone's benefit. 

 

And Meraki support in speaking with them yesterday did acknowledge that the developers of this app are aware of the issues and are working towards a fix, when that fix might be available is a whole other question.. So I guess we'll see, right now  for us, our Meraki Integration remains down and unusable. 

KILLTROUT
New here

We have the same issue after upgrading to the latest version of the SG for Meraki in ServiceNow.

Get notified when there are additional replies to this discussion.