I have recently encountered an error that is stopping me from saving my SAS EG project file to my company's shared drive. When I try to save, I get the error message "An unexpected error occurred while saving the project. Please review the application log for more details".
When I open the application log, the error message says "ERROR SAS.EG.ProjectElements.ElementManager [(null)] - Error saving project
System.IO.IOException: The process cannot access the file 'my project file path on the shared drive' because it is being used by another process."
I do not get the error if I try to save directly to my computer's C drive. In fact, I can save to my C drive, move the file from my C drive to the shared drive, open it from the shared drive and run some data, and still get an error when trying to re-save to the shared drive.
For extra context, I am using SAS EG version "8.4 Update 2 (8.4.2.22) (32-bit)".
I always had my project files on local drives, and would copy them to a share only for having them available on multiple computers. All actual work should be done with local files.
There were even incidents in our company where a network hickup would cause the destruction of a project.
This seems to be a long-time shortcoming in the .NET-based file handling routines of EG.
Good news: We've extended SAS Hackathon registration until Sept. 12, so you still have time to be part of our biggest event yet – our five-year anniversary!
Check out this tutorial series to learn how to build your own steps in SAS Studio.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.