Provides an overview of SAS 9.2 and links to other resources availalbe on the. The improvements include more widespread use of 64-bit computing, as well as.
Hi everyone, Does anyone have experience installing SAS 9.2 on a Mac? I have purchased and installed Windows 7 Professional (64-bit) and Parallels 6, both of which seem to be installed correctly. When I try to install SAS 9.2 (which states its platform is Microsoft Windows Workstation 32-bit), only select applications install, but the main SAS foundation file does not.
I checked the SAS requirements before purchasing the 64-bit Windows 7, and it is supposed to support SAS 9.2, however my installation is proving contrary. Does anyone have any suggestions? For more specifics, the 'System Requirements Wizard' says that my system meets the minimum requirements. However, it only installs 3 of 9 components, excluding the SAS Foundation, SAS Drivers, and other important ones!
Contents. Background As of October 2009, SAS for. However, SAS Foundation (9.2), SAS Enterprise Guide (4.2), and even the SAS metadata server with workspace and stored process servers can work on Windows 7 if you follow careful deployment steps. All of my advice here applies for both Windows 7 x86 (32-bit) and Windows 7 x64 (64-bit), and also covers SAS 9.2 for Windows x64, if that's what you've ordered. (Hey, it might even work for Microsoft Windows 2008 R2, a revision which is basically a server version of Windows 7.) I'm documenting the steps here so that folks who are taking an early look at Windows 7 may do so with some confidence.
SAS plans to officially support Windows 7 in early 2010. For the latest official information about SAS and Windows 7 support, refer to this SAS note:. The steps are derived from my own experience and 'inside' knowledge of How Things Work. It's not a result of an official regimen of testing on a wide variety of machines and scenarios, but I believe that these steps should be repeatable by most folks. Even though I work for SAS, this is not an official statement of support. Steps to follow Prerequisites All of these tests/steps are using and SAS Enterprise Guide 4.2 Maintenance 2, which were.
I don't advise trying this with the pre-maintenance-2 level of software. These steps should work with most flavors of Windows 7, 32-bit and 64-bit - Professional Business, Enterprise, Ultimate are usually the types that business customers use. Students might use Home Premium; I haven't tried it there, but I'm optimistic it would work.
Running as administrator You can 'stack the deck' towards success if you execute each deployment step 'as administrator'. Like Vista, Windows 7 reserves install/registration privileges for the admin role.
Every time you are presented with a step to double-click on an executable to run an install procedure (setup.exe, for example), you should right-click on the exe file and select ' Run as administrator'. Downloading a SAS software depot Most customers will use the to download a software order from SAS with electronic software download. I had two experiences when running this on Windows 7. Once I had the download complete but it failed, for some reason, to complete the software depot. In another test, the download and depot creation successfully completed, with no problems.
If for some reason you cannot use the SAS Download Manager on Windows 7, you can easily work around it by downloading to another machine (Windows XP or Server 2003, for example) and creating the initial depot there, and then copying to the Windows 7 machine or access it via a network share. Pre-emptive deployment steps There are some known problems that will prevent SAS software from correctly installing on Windows 7; these are mainly in the System Requirements Wizard. If the proper system requirements are not installed, then the SAS and SAS Enterprise Guide installation will fail and the software will not run. As a workaround, you can manually install the known required bundles before running the SAS Deployment Wizard.
Steps (where SSD: is the root of your SAS software depot):. Right-click and select Run as administrator on the following files: SSD: products sysreqwizard92280prtxxsp01 bundles vcredst7 setup.exe SSD: products sysreqwizard92280prtxxsp01 bundles vcredst71 setup.exe These are the Microsoft C runtime redistributables needed for SAS Integration Technologies client and other client components.
Right-click and select Install on this file: SSD: products sysreqwizard92280prtxxsp01 redist wse 3.0 wse30.msi This is the Microsoft WSE 3.0 bundle that enables SAS Enterprise Guide to talk to SAS web services. Important: after installing these components, you should reboot your Windows 7 system. I found that if you skip that step (even though you might not have been prompted to reboot), subsequent steps might not complete successfully.
![Sas 9.2 software for windows 7 32 bit windows 10 Sas 9.2 software for windows 7 32 bit windows 10](http://www.chip.de/ii/1/8/9/2/9/9/9/4/86a51e9ab2e8c769.jpg)
And another caveat: usually, navigating directly into the '. Products' area and installing pieces directly (circumventing the deployment wizard) is not a good idea. The SAS Deployment Wizard updates your SAS product registry as it works, which is important for successful maintenance via hotfixes and maintenance releases later on.
Because these are just third-party requirements and not software from SAS, it's okay in this case. Installing a non-planning order with SAS and SAS Enterprise Guide A 'non-planning' order is one that requires no configuration step. It usually means that you don't have a SAS Metadata Server, nor do you have SAS products that have a metadata component to be configured. If you are installing just SAS for Windows and SAS Enterprise Guide for use on your local PC, you typically don't need a planned configuration. With the above system requirements 'pre-emptively installed', you can follow these steps: Right-click on: SSD: setup.exe And select Run as administrator. This launches the SAS Software Deployment Wizard. Then select 'Install SAS Software', and click Next.
Select all of the software products that you want to install, and then continue through the wizard as normal. All of the software should install successfully, and when complete, SAS and SAS Enterprise Guide should Just Work. Installing a planned order: Server tier With the above system requirements in place, I right-clicked on: SSD: setup.exe And selected Run as administrator. This launched the SAS Software Deployment Wizard. Next, I selected 'Perform a planned deployment' with install and configuration. When prompted for a plan, I selected the 'Enterprise Guide, 2 machines' plan. I first installed the Server machine manifest.
I answered all of the configuration prompts in the usual way and allowed the installation to run. Installing a planned order: Client tier Launch the setup.exe again (as administrator), select the same plan, and this time follow the Client machine path. Everything (SAS Enterprise Guide and friends) should install successfully. If Everything is On One Machine: I made the mistake of answering 'Yes, please continue' when prompted about existing content in 'C: SAS EG Lev1'.
The deployment wizard overwrote levelenv.bat and sasv9meta.cfg, which broke my ability to connect to the SAS workspace with SAS Enterprise Guide. I restored those files using the copies in the. Backup folder and then all was well. If you are installing just the client software on Windows 7 (and not SAS Foundation or metadata or any of that configured stuff), then you shouldn't have to worry about the above conflict. Feedback If you have feedback about these instructions, please feel free to add to the Discussion portion of this page. You can also contact me through my blog,.