Import sets not working

[Earl L]

I'm trying to run an import set on my instance and they are consistently failing with the following error.

2017-03-21 08:22:54 03-21 08:22 1m ago

Error

sysID cannot be null: java.lang.IllegalArgumentException: sysID cannot be null: com.glide.worker.ProgressMonitor.<init>(ProgressMonitor.java:21) com.glide.processors.ImportProcessor.waitForStartup(ImportProcessor.java:203) com.glide.processors.ImportProcessor.outputMessage(ImportProcessor.java:179) com.glide.processors.ImportProcessor.process(ImportProcessor.java:79) com.glide.processors.AProcessor.runProcessor(AProcessor.java:424) com.glide.processors.AProcessor.processTransaction(AProcessor.java:195) com.glide.processors.ProcessorRegistry.process0(ProcessorRegistry.java:178) com.glide.processors.ProcessorRegistry.process(ProcessorRegistry.java:167) com.glide.ui.GlideServletTransaction.process(GlideServletTransaction.java:49) com.glide.sys.Transaction.run(Transaction.java:1976) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) java.lang.Thread.run(Thread.java:745)

com.glide.ui.ServletErrorListener

This is a new import set and the underlying import set table has not been created yet (verified by searching in system tables). This is a very simple two record import and I've tried it in both Excel and CSV formats without any luck. I can attach a copy of the file I'm using for the import if that would be helpful.

My instance is dev17716.service-now.com and it's running Istanbul.

Is there any way that someone from SN can look at this to see if there are some kind of internal errors causing the instance to not be able to generate sys IDs? I really have no idea what's going on with this but it is getting pretty frustrating trying every combination of tricks I can come up with to try to make this work, only to have them all fail.

[sergiu_panaite]

Yes, they do. And I can see Progress Workers running for other things, so I believe there is no restriction indeed. Might be something related to the Istanbul Patch you have. I see instance is up, let me dig a bit further.

[sergiu_panaite]

Hey Earl,

Good news. It works now.

The problem was caused by:

glide.tiny_url_min_length=256

I've set it to 1024 and it works now. To figure out I compared the log transaction from my instance, this one:

------------

2017-03-22 06:55:38 (807) Default-thread-166 AE1B9753DBA536002F2DFA3BAF961937 #17892 /sys_import.do Parameters -------------------------

      sysparm_tablelabel=new test

      sysparm_data_source=7a4e6e03dba9f2002f2dfa3baf96192e

      sysparm_tablename=u_my_testing_import_table

      sysparm_recreate_table=false

      sysparm_extends=sys_import_set_row

      max_rows=20

      create_new_module=ON

      sysparm_default_state=test

      import_source=data_source

      selected_application=import_sets

------------

with the one generated initially on your instance, this one:

------------

2017-03-22 06:53:50 (345) Default-thread-8 7699DF134F213200FA7FEB118110C76E #360 /sys_import.do Parameters -------------------------

      sysparm_tiny=fe1f2e4b4f213200fa7feb118110c791

------------

That led me to that property.

Enjoy testing.

[Earl L]

This is great news Sergiu. Thanks so much for digging into it and getting it resolved.