Some PDIs are currently unavailable, and PDI actions are paused. View the latest updates here. Read More

SCCM Error for Computer Identity

Ashish48
Tera Contributor

Hi All,

 

We are getting this error while running SCCM for computer identity.

 

java.lang.NullPointerException: Cannot invoke "String.startsWith(String)" because "name" is null
at com.glide.db.TableDescriptorProviderFactory.get(TableDescriptorProviderFactory.java:14)
at com.glide.db.TableDescriptor.getProvider(TableDescriptor.java:903)
at com.glide.db.TableDescriptor.getSchema(TableDescriptor.java:235)
at com.glide.db.TableDescriptor.get(TableDescriptor.java:91)
at com.snc.cmdb.identify_reconcile.Util.getElementDescriptor(Util.java:116)
at com.snc.cmdb.identify_reconcile.RecordWithState.normalizeIPAddress(RecordWithState.java:1800)
at com.snc.cmdb.identify_reconcile.RecordWithState.processAttributes(RecordWithState.java:1774)
at com.snc.cmdb.identify_reconcile.RecordWithState.<init>(RecordWithState.java:227)
at com.snc.cmdb.identify_reconcile.APIPayloadWithState.loadData(APIPayloadWithState.java:61)
at com.snc.cmdb.identify_reconcile.EnhancedPayloadManager.loadData(EnhancedPayloadManager.java:47)
at com.snc.cmdb.identify_reconcile.IdentificationEngine.importData(IdentificationEngine.java:754)
at com.snc.cmdb.identify_reconcile.IdentificationEngine.execute(IdentificationEngine.java:674)
at com.snc.cmdb.identify_reconcile.IdentificationEngine.executeAndGenerateOutput(IdentificationEngine.java:613)
at com.snc.cmdb.identify_reconcile.IdentificationEngine.execute(IdentificationEngine.java:570)
at com.snc.cmdb.identify_reconcile.IdentificationEngine.createOrUpdateCI(IdentificationEngine.java:416)
at com.snc.cmdb.identify_reconcile.PayloadMerger.execute(PayloadMerger.java:256)
at com.snc.cmdb.identify_reconcile.PayloadMerger.mergeAndExecute0(PayloadMerger.java:324)
at com.snc.cmdb.identify_reconcile.PayloadMerger.mergeAndExecute(PayloadMerger.java:66)
at com.snc.cmdb.identify_reconcile.IdentificationEngine.createOrUpdateCI(IdentificationEngine.java:391)
at com.snc.cmdb.identify_reconcile.listener.IREMessageListener.invokeIre(IREMessageListener.java:336)
at com.snc.cmdb.identify_reconcile.listener.IREMessageListener.onMessages(IREMessageListener.java:154)
at com.glide.db.impex.transformer.service.RobustImportSetTransformerDAO$ThrottlingListener.onMessages(RobustImportSetTransformerDAO.java:156)
at com.glide.db.impex.transformer.service.RobustImportSetProcessor.processBatch(RobustImportSetProcessor.java:125)
at com.glide.db.impex.transformer.service.RobustImportSetProcessor.transform(RobustImportSetProcessor.java:83)
at com.glide.system_import_set.ImportSetTransformerImpl.doRobustImportSetTransform(ImportSetTransformerImpl.java:166)
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:271)
at com.snc.automation.ImportSetTransformerJob.execute(ImportSetTransformerJob.java:100)
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)

2 REPLIES 2

Ashok Sasidhara
Tera Sage

Check if the issue and solution mentioned in the following URL is relevant:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1584760

 

shivani42
Tera Contributor

Hi Ashish,

did you get solution for the issue. We are also facing the same issue while running SCCM computer identity schedule import.

Regards,

Shivani