Might be a stretch, but if indeed this has a printer interaction, you might try adding -NOPRNGETLIST to your startup options. That prevents SAS from trying to "discover" available printers, and might prevent the initialization of this conflict. Of course, then you might not be able to print (to a printer) from within SAS...but think of all of the paper you'll save.
@Alphanumeric, @ChrisHemedinger, @TPGary -
@LethaChristian, @FredMayer, @David_wKing:
This is vaguely reminiscent of the time f(inger)print.d was enabled in a JBOSS Red HAT Linux 5.1 grid configuration and all hell broke loose well figuratively when the users tried to access the SAS platform more than 3 at a time.
Madly desiring a solution for this. Just installed 9.4 M5 on brand new HP laptop runing Win 10. I've explored hot-fixes; I've set the viewtable to show colnames; I've added SplWOW64TimeOutSeconds. After 6 weeks of fighting this still crashes (sometimes). Not able to reproduce but, when it happens it always happens when tinkering with size of an open viewtable view.
It's finally time to hack! Remember to visit the SAS Hacker's Hub regularly for news and updates.
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.