Maybe I do not have the JSON Engine?

[brookeewhite1]

Hi,

I am trying to import JSON files to SAS, which is a new endeavor for me.  I've been able to bring one in using a DATA step with INFILE statement, but not with the JSON engine.  I keep getting this error: "ERROR: The JSON engine cannot be found."  I'm using SAS Enterprise Guide Version 7.1 (7.100.0.1966) (64-bit) and For Base SAS Software ...Custom version information: 9.4_M4 Image version information: 9.04.01M4P110916.

So, I'm trying to find out if this means I just don't have that feature? Or if I should keep trying to debug my code?

The latest code I submitted was from a SAS blog: https://blogs.sas.com/content/sasdummy/2016/12/02/json-libname-engine-sas/

filename resp temp;
 
/* Neat service from Open Notify project */
proc http 
 url="http://api.open-notify.org/astros.json"
 method= "GET"
 out=resp;
run;
 
/* Assign a JSON library to the HTTP response */
libname space JSON fileref=resp;
 
/* Print result, dropping automatic ordinal metadata */
title "Who is in space right now? (as of &sysdate)";
proc print data=space.people (drop=ordinal:);
run;

However, I've also tried submitting various other code snippets with the JSON library engine, all with the same result.

Thanks in advance!

[Quentin · Accepted solution]

You get that error from the LIBNAME statement using the JSON engine?  

I would double check your SAS version is M4 with:  %put &sysvlong; and see what that writes to the log.  If that confirms that your are on 9.4M4 (or later), then I would submit a ticket to SAS tech support.

[brookeewhite1]

I ran that code and here is the log excerpt showing what I got back:

23 %put &sysvlong;
9.04.01M4P110916

[Sajid01]

Hello
Your issue has been addressed in this post on the forum.

https://communities.sas.com/t5/Administration-and-Deployment/ERROR-The-JSON-engine-cannot-be-found/t... .

Please revert back if this does not work.

[brookeewhite1]

Update: I have a ticket open with our local administrators and am waiting to see what the resolution will be!

[brookeewhite1]

Thank you for the suggestion to involve tech support!  After a bit of back and forth, our local tech support confirmed the issue was on their side by opening a JIRA ticket to resolve the problem.