BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
Lukas852
Fluorite | Level 6

Hello,

 

we have old server running SAS Customer Intelligence Studio, and i need to move metadata to the new CI server.

 

I exported the SAS package(s) from old server and when i try to import the SAS package to new server, i get this warning trying to import Definiton folder:

"The current export path "EXP" is not valid. You must change the path or make it available to use the export definition."

EXP.JPG

 

The EXP library is present and working (imported from old server with no problem), so is connection to Oracle DB. Tables can be updated successfully.

lib.JPG

User used to import should have the permission for access. User is part of Customer Intelligence Advanced Campaign Designer group for example, which have all the rights.

 

What could be the problem here?

 

Best regards,

Lukas.

1 ACCEPTED SOLUTION

Accepted Solutions
Lukas852
Fluorite | Level 6

Hey James,

thanks for setting me on on the right track. I got this solved.

 

We never used mausrexp.sas file to define the library on old system.

Library should have been pre-assigned. Which it was according to SMC... But after trying everything i could think of, i did uncheck the "pre-assigned" option, checked it again and restarted whole sas.

And the warning no longer pop up.

 

Cheers.

View solution in original post

2 REPLIES 2
JamesAnderson
SAS Employee
Hi Lukas,
The library needs to be available to CI when importing the Export definition from the spk file. So this means the library is either pre-assigned or the library is defined in the mausrexp.sas macro file. If you choose to pre-assign the library you will need to refresh the object spawner and restart your session of SMC. Ive seen this error occur, and then when you get to CI Studio to run an export that uses the library it works, it just depends on users, permissions etc.
Regards
James
Lukas852
Fluorite | Level 6

Hey James,

thanks for setting me on on the right track. I got this solved.

 

We never used mausrexp.sas file to define the library on old system.

Library should have been pre-assigned. Which it was according to SMC... But after trying everything i could think of, i did uncheck the "pre-assigned" option, checked it again and restarted whole sas.

And the warning no longer pop up.

 

Cheers.

G2 Grid Leader Spring 2025.png

 

 

 

 

Want to review SAS Customer Intelligence 360? Gartner and G2 are offering a gift card or charitable donation for each accepted review. Use this link for G2 to opt out of receiving anything of value for your review.

 

Gartner.jpg

 

SAS Customer Intelligence 360

Get started with CI 360

Review CI 360 Release Notes

Open a Technical Support case

Suggest software enhancements

Assess your marketing efforts with a free tool

 

Training Resources

SAS Customer Intelligence Learning Subscription (login required)

Access free tutorials

Refer to documentation

Latest hot fixes

Compatibility notice re: SAS 9.4M8 (TS1M8) or later

How to improve email deliverability

SAS' Peter Ansbacher shows you how to use the dashboard in SAS Customer Intelligence 360 for better results.

Find more tutorials on the SAS Users YouTube channel.

G2 Grid Leader Spring 2025.png

 

 

 

 

Want to review SAS Customer Intelligence 360? Gartner and G2 are offering a gift card or charitable donation for each accepted review. Use this link for G2 to opt out of receiving anything of value for your review.

 

Gartner.jpg

 

SAS Customer Intelligence 360

Get started with CI 360

Review CI 360 Release Notes

Open a Technical Support case

Suggest software enhancements

Assess your marketing efforts with a free tool

 

Training Resources

SAS Customer Intelligence Learning Subscription (login required)

Access free tutorials

Refer to documentation

Latest hot fixes

Compatibility notice re: SAS 9.4M8 (TS1M8) or later

Discussion stats
  • 2 replies
  • 1628 views
  • 0 likes
  • 2 in conversation