Missing entity mappings in Meraki Service Graph Connector 1.5

[Steelneck]

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)

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

[Ray1411]

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

[Seth_Bright]

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

[SergeyT]

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]

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

[Jhansi]

Did you get any response from ServiceNow?

[SergeyT]

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]

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

[SergeyT]

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]

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]

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]

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]

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 list: CMDB Integration Studio Entities)

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

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

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

[Ray1411]

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}}

[SergeyT]

After applying this fix, I no longer see a java error, but it doesn't import anything, so it is still not working

[SergeyT]

Also, these two didn't exist in 1.4.0, I just compared to my prod instance

[Picardo]

This fixed the initial error for me, but for some reason I'm not getting any affinity for Meraki ...

Error in MerakiGetOrganization - Organization Access: (instance number) No Record exists in Meraki Credential Affinity table. Execute Schedule Job- SG-Meraki Credential Affinity Sync

I've run the affinity job several times, but nothing happens and I'm not getting any valuable error messages from it.

[Misanab]

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]

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]

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

[FreshPaint503]

Our Instance is on Xanadu, and we updated Meraki from 1.3.0 to 1.5.0. We ran into this issue Meraki failing with the same Java error at the top of this Thread: java.lang.IllegalArgumentException: Invalid Entity class for field (name: location, sysid: 8d4ee2901b479610f5cf97d7b04bcb85)......... 

ServiceNow will tell you it's a 3rd Party App and they don't support it. Meraki support will point finger at ServiceNow. We went back to ServiceNow asking if they can't help us fix it, help us revert to earlier working version. They will tell you 1.3.0 or 1.4.0 can't be install on Xanadu, that isn't quite true.

Let me explain:
If you were on a previous working version of Meraki before you upgraded to Xanadu; and after Xanadu you updated Meraki to 1.5.0, you can Rollback the Plugin to the earlier working version. You only have 10 days from the time of the Meraki update to do so (unless you have retained version history set for a longer period of time). We were able to successfully Roll Back to 1.3 from the 'Rollback Contexts' Backups (see screenshot 1). If you run the Rollback for Meraki and it fails, look at the end of the message (see screenshot 2). You will then need to Rollback whatever it points to. Attempt to Rollback Meraki again. If it fails again Rollback what it points to this time.... You may have to keep doing this several times, like pealing back an onion. You have to Rollback each plugin the Backup touched until you can successfully Rollback Meraki. We are currently back to running 1.3.0 on Xanadu without issue. I refuse to update Meraki again until this issue is resolved. 

1.

2.

[geothomas]

I am new to this and I have been trying to integrate service graph connector with meraki. I am using Washington and Plugin is version 1.5 . I do not see any error in my logs. I am able to run the affinity sync and the device import without issues. But my Networks, Organization and Custom CI Fields are all empty. DO I have to make some additional configs or are they supposed to load automatically?

[SergeyT]

New version 1.5.1 was announced, which explicitly says it will fix the issue, but it won't! 

[shwetaP]

@SergeyT If you have made any changes to the entity mappings or robust transform you will get the above errors even after upgrading this connector. If any changes are made to these mappings, please uninstall and reinstall the connector. And ensure that you follow all the steps in the guided setup accurately after installing again.

[Misanab]

Hello shwetap, 

I've followed the instructions in our Dev instance, completely uninstalled the SGC connector (1.5.0) including deleting all tables and data, then installed 1.5.1 and ran thru the configs and still I'm having issues, The test connection works but the Robust Transform fails.. 

[Picardo]

Do you get any error messages?

On my end I just get squat.

	2025-03-18 09:47:47	Information	total: 0, inserts 0, updates 0, processed 0, ignored 0, skipped 0, errors 0		ScheduleImportJob
	2025-03-18 09:47:47	Information	Using import set: ISET0451610, table x_caci_sg_meraki_merakidevices		ScheduleImportJob
	2025-03-18 09:47:46	Information	Using import set: ISET0451610, table null		ScheduleImportJob
	2025-03-18 09:46:29	Information	Processed: 0, inserts 0, updates 0, errors 0, empty and ignored 0, ignored errors 0 (0:00:00.018)		Loader (SG-Meraki Devices)
	2025-03-18 09:46:29	Information	Loading import set table: x_caci_sg_meraki_merakidevices		ScheduleImportJob

Edit: ok, I found that I have affinity sync errors ... I ran affinity sync and it looks like it's working, but it doesn't appear to actually work ... 

I need to see if i've messed something up with the credentials / affinity.

[shwetaP]

I'm suspecting some missed configurations in the setup which can lead to the issue - Ensure that
1. "Execute Fix script" step is performed

2. Ensure that API Credentials are correct

3. organization IDs are passed

4. Affinity sync job is executed and validated properly