Getting Data In

Your entry was not saved. The following error was reported: SyntaxError: Unexpected token < in JSON at position 0.?

russell120
Communicator

Reproduce the error:
1. Export the results of a previous search job (a table with 22 fields and 32k+ rows) as a CSV.
2. Attempt to upload CSV as a new lookup file with CSV filetype selected.

Why do I get this error? I've seen error messages similar to this for other peoples' questions but I have not seen any where the issue comes from trying to upload a CSV as a lookup file.

Labels (1)
0 Karma

Ne_phil
Loves-to-Learn Lots

Did you ever figure out how to resolve this error? I'm currently having the same issue. @russell120 

0 Karma

burwell
SplunkTrust
SplunkTrust

I have seen this error when my authentication to Splunk has expired.

When I reauthenticate, the error has gone away.

0 Karma

DalJeanis
Legend

It sounds like it's trying to ingest the file as a json rather than as a csv. Perhaps somebody touched the file with Excel and Microsoft converted it?

First, verify that the file is, in fact, a plain csv down on the box, by attempting to edit it with a vanilla editor (notepad++ or something like that).

Second, step through the upload one item at a time and read every instruction or message. This sounds vaguely familiar, and I'm pretty sure it's just either the file has been altered or an option that went wonky.

0 Karma
Get Updates on the Splunk Community!

Enter the Dashboard Challenge and Watch the .conf24 Global Broadcast!

The Splunk Community Dashboard Challenge is still happening, and it's not too late to enter for the week of ...

Join Us at the Builder Bar at .conf24 – Empowering Innovation and Collaboration

What is the Builder Bar? The Builder Bar is more than just a place; it's a hub of creativity, collaboration, ...

Combine Multiline Logs into a Single Event with SOCK - a Guide for Advanced Users

This article is the continuation of the “Combine multiline logs into a single event with SOCK - a step-by-step ...