05-20-2012 08:13 AM
Please hope to get help for my enquiry,
I have project containing data created by sas enterprise guide 4.2 on local PC, the project saved there locally and now we have sas server and enterprise guide 5,1, I want to transfer and run the project to the new version (on server), when I open the project and click run, I get errors , I need please details and instructions for what I must do to run on new version
Appreciated for your support
Thanks and Best Regards,
05-20-2012 10:18 PM
There are so many moving parts to your question that I suspect that we can't answer it here. A couple of thoughts.
05-21-2012 04:55 AM
I had no problems to open EG project created with EG4.2 with 5.1 and then run it. The projects got right away converted. BUT: I didn't change the environment (from local SAS to server SAS).
I assume that's where you face issues. So for example your input and output files must now be in a directory which can be accessed by the SAS server (that's where your code gets executed - EG is only a "code generator").
Let's say you had your files somewhere on your c-drive. That worked with a local SAS installation (the SAS server on the same machine than the EG client). Doesn't work now anymore!
First thing: Move all your data to folders which the SAS Server can access, then change all the pathnames in the libraries so that they point to the new locations.
There is a EG migration wizard which can help you mapping old paths to new ones. Mine is under C:\Program Files\SASHome\x86\SASEnterpriseGuide\5.1\MigrationWizard.exe.
What you also can do is "hack". EG projects ".egp" are zip files. You can open it with WinZip or the like and then change paths directly in project.xml (work on a copy of the project! - it's "hacking" and you could destroy your project if you're doing something wrong).
The best thing of course would be - now that you're on a server - to use pre-defined libraries (in metadata) which already point to a location the server can access. Not sure how you can replace your old librefs with the new ones. I believe the migration wizard would support you there. For librefs in the code: you would need to change them.
One lazy way exists: libname <old libref> (<new libref in metadata>); would point your old librefs to the new locations as well.
02-12-2013 10:38 PM
Thanks Patrick. This is useful. I was also facing similar situation. MigrationWizard.exe allowed me to change Local server Paths to server paths for a project and helped me.