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, testing now.

[sergiu_panaite]

Strange, it doesn't work for me either, even if I create a new data source. Same works on my own instance which is also in Istanbul.

I would need more time on this. I can probably give you a better answer by tomorrow.

[Earl L]

Thank you so much for looking into this. I know this is a free resource and very much appreciate that it is, and that someone would be able to help with this. Looking forward to hearing back from you on your findings.

Earl

[sergiu_panaite]

Hey Earl,

Can't do testing today as your instance is in hibernate mode. I had a look thou in the source code and the error you're getting is because we're not able to start up a Progress Worker. This may be related to the fact that's it's a developer instance, but I am not 100% sure.

bradpsnc do you know if developer instances are restricted in running Progress Workers?

[Earl L]

It's starting up now. Give it 5-10 minutes.

Hmmm... not sure about the progress workers, but I've been able to run imports just fine in the past. Don't those require progress workers every time they run?