Posting this, in the hope that it helps someone else, and if it happens to me again in a year's time, I don't go on the same wild goose chase trying to fix it.
In SAS 9.4, I lost the ability to launch a .SAS file in the editor window by double-clicking on it in Windows Explorer. Whilst there are lots of potential solutions online, most of them cater for issues on 9.2 or 9.3 which tell you to run the SAS File Type Management Tool, which no longer exists in 9.4.
For 9.4 you can now fix the issue using the Manage File Types Utility in the SAS Deployment Manager. However, this didn't work for me, as the Deployment Manager was just hanging when running. Apparently, this is due to the issue described in Problem Note 57391: The Manage SAS File Types utility in the SAS® Deployment Manager fails to associ.... The fix in the KB article didn't work for me either, as the reinstall BASE SAS option wasn't available in my setup.
By far the most useful information to help me find the solution was in Double-Clicking a SAS® File: What Happens Next? (although again, it is aimed at 9.2 / 9.3 rather than 9.4.)
What fixed it for me was the following. (This assumes that you have access to, and are comfortable with modifying your Windows registry):
Maybe I am misunderstanding your point here, however SAS Base - i.e. a locally installed SAS to the machine should be easily able to open SAS files just by associating the file type with the application - much the same as you would do with any other application. If it does not do this automatically, or you want to change it, right click on a .sas file, select Open With. Then find the SAS application and make sure that set as default is checked. Should work fine from there. Really wouldn't go editing registry and such like for something so simple?
This does not always work, and is not the recommended method. Please see the Gibbs paper.
Thanks for posting. I had a similar problem and was able to use this information to fix it. My solution was a little different, but the steps I followed were:
1. Deleted the UserChoice registry key as discussed in the Double-clicking paper.
2. Running the SASFileTypeRegFix.reg registry fix as discussed in the paper.
3. Using the windows registry editor. (Modify at your own risk, take a back-up before modifying):
Here is one other method of resolution that has worked for me in stubborn situations before (you may need I.T. assistance), but doesn't require quite so many edits to the registry. Again, always back up the registry before, just in case!
Now - if the issue is with any other file type other than .sas - note the folder name underneath each file type on the left (expand the node) - there is a pattern in which the folder name equates to that Data Value for the "(Default)" Key.
So, for example instead of 'SAS.Program.701', for a .sas7bdat file, you would specify 'SAS.DataSet.701'.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.