Getting an error while bulk import EG projects in SAS Viya using CLI method

[devi001]

Hello everyone,

We are importing SAS 9.4 EG projects in SAS Viya using CLI method as we want to import multiple EGP files at a time (bulk import). We have installed latest CLI version(1.21.23), created profile, profile authenticated successfully (Trusted CA certificates validation) and installed all the plug-ins. For transfer plug-in, used force option to update the same. Used below reference links.

For CLI set up - https://documentation.sas.com/doc/en/sasadmincdc/v_046/calcli/n1e2dehluji7jon1gk69yggc6i28.htm

For import EG project - https://communities.sas.com/t5/SAS-Communities-Library/Go-with-the-flow-migrating-Enterprise-Guide-P...

We have executed below command (this is using folder path method as we have placed SAS 9.4 egp files at one location in Viya env and path is specified in --source-location option) in SAS Viya environment : -

./importEGProjects --sas-viya-path "/home/sasdemo/SASContentAssessment/sas-viya" --source-location "/home/sasdemo/SASContentAssessment/"

Getting an error as import FAILED.  The error that we are getting in the log is as follows :

---partial log start---

2023/11/22 06:56:14.660502 cli.go:54: Executing: /home/sasdemo/SASContentAssessment/sas-viya transfer
2023/11/22 06:56:14.853180 main.go:304: The required plugin, transfer, is installed.
2023/11/22 06:56:14.853220 cli.go:54: Executing: /home/sasdemo/SASContentAssessment/sas-viya transfer --version
2023/11/22 06:56:15.038999 semver.go:47: The version of sas-transfer is 1.22.41
2023/11/22 06:56:15.039034 main.go:355: Validating the specified settings: SUCCESS
2023/11/22 06:56:15.039046 main.go:358: Command-line options in use:
2023/11/22 06:56:15.039056 main.go:359:   Creating a profile for this SAS Enterprise Guide projects: false
2023/11/22 06:56:15.039066 main.go:360:   Root folder for this SAS Enterprise Guide projects import: ConvertedEGProjects
2023/11/22 06:56:15.039076 main.go:361:   Source file for this SAS Enterprise Guide projects import: 
2023/11/22 06:56:15.039085 main.go:362:   Source location for this SAS Enterprise Guide projects import: /home/sasdemo/SASContentAssessment/
2023/11/22 06:56:15.039099 main.go:560: Enumerating SAS Enterprise Guide projects to import.
2023/11/22 06:56:15.039116 main.go:598: Processing the source location /home/sasdemo/SASContentAssessment/ to determine which SAS Enterprise Guide projects to import
2023/11/22 06:56:15.041362 main.go:607: Processed 5 SAS Enterprise Projects
2023/11/22 06:56:15.041393 main.go:622: Importing the specified SAS Enterprise Guide projects.
2023/11/22 06:56:15.041412 main.go:637: Processing 1 of 5 SAS Enterprise Guide project(s): /home/sasdemo/SASContentAssessment/EGModels 1.egp
2023/11/22 06:56:15.041437 cli.go:54: Executing: /home/sasdemo/SASContentAssessment/sas-viya transfer --quiet upload --file /home/sasdemo/SASContentAssessment/EGModels 1.egp
2023/11/22 06:56:15.265145 main.go:723: The project was uploaded successfully with the ID: 
2023/11/22 06:56:15.265219 cli.go:54: Executing: /home/sasdemo/SASContentAssessment/sas-viya transfer --quiet import --id  --f :SKIP_VALIDATION:/ConvertedEGProjects/home/sasdemo/SASContentAssessment
2023/11/22 06:56:15.537759 main.go:738: The project failed to import
2023/11/22 06:56:15.537819 cli.go:54: Executing: /home/sasdemo/SASContentAssessment/sas-viya transfer --yes-to-all delete --id 
2023/11/22 06:56:15.898952 main.go:756: No package with the URI "/transfer/packages/" was found.

---partial log end---

Kindly assist in resolving this error.

Thanks in advance!

[SASKiwi]

This type of problem is best progressed with SAS Tech Support if you haven't already opened a track.

[Rutujak]

hi,

have nayone got the resolution for this please tell cause i am also facing the same error

[Patrick]

Do you get the exact same error?

Are your .egp files from a rather recent SAS EG version? 

Do you meet all that's define under: Command-Line Interface: Preliminary Instructions

It's likely something SAS Tech Support is best suited to help you with. Also with SAS Tech Support you will get to a resolution faster if you provide them with all the info from above questions as well as your Viya and CLI version, all the relavant log and the site number (for the site number: I normally run Proc Setinit and just share the "header" with TS that also includes the Viya version and the OS).

[devi001 · Accepted solution]

Yes, its resolved few months ago. Apologies couldn't post the solution in time.

Below steps worked in our case -

During CLI set-up, we need to create profile by executing "./sas-viya profile init".

In Service Endpoint option, we need to pass the value contains "https://...sas.com". Here we were passing incorrect values. 

(Although,  passing incorrect values, profile was created successfully and was accepting the token so please check this step while creating service endpoint profile. )

Thanks!!