Home > Microsoft Runtime > Microsoft Runtime Components 8.0 Sp1 Sas 9.2

Microsoft Runtime Components 8.0 Sp1 Sas 9.2

The install completes successfully on Windows 7 without the 7.1 runtime components. For now I am going to try running SAS 9.1.3 under Windows XP mode Reply Pete Posted August 27, 2010 at 1:33 pm | Permalink Hi Blaise- We are also running This version of the SAS Suite comes with over 40 different software pieces bundled and it was a nightmare considering Wise Studio can only wrap 1.5GB before it fails. Official support of SAS software on Windows 7 is an initiative planned for the first part of 2010. weblink

To prevent the installation failure, download and install these components ahead of time, before you launch the SAS Deployment Wizard. If you want to use record/playback, ensure that Dataflux Integration Server and dfPower Studio do not appear in your Products to Install list or are not selected in that list. Still, the Windows 7 configuration for EG 4.1 is not officially supported by SAS. Deployment Tips (18) Most Common Setup Type Not Determined Average Package Difficulty Rating Rated 3 / 5 (Average) based on 1 ratings Most Commonly Reported Deployment Method Not Determined Enter your

BY ACCEPTING THIS AGREEMENT AND/OR USING THE CODE, AS DEFINED BELOW, YOU, ON BEHALF OF CUSTOMER, AS DEFINED BELOW, ARE AGREEING TO THESE TERMS AND SAS, AS DEFINED BELOW, WILL AUTHORIZE To Remove Run : "C:\Program Files\InstallShield Installation Information\{F9390B82-786C-43CF-A970-D39E23EF0366}\setup.exe" -l0x9 -removeonly uninstall W32 -s -f1"C:\Program Files\InstallShield Installation Information\{F9390B82-786C-43CF-A970-D39E23EF0366}\uninst.iss" 2. sysreqwizard__92400__prt__xx__sp0__1 2. You will have to modify it to get it to work correctly.  


SAS Enterprise Guide

Be sure to run "as administrator". Run the install with this command: …..setup.exe -wait -quiet -responsefile "C:\Progra~1\SASLIC\sdwresponse.properties" -loglevel2 1. Reason: Member has been banned from the site For more information, visit our FAQ's. PREREQS JRESetup.exe Command Line= -is:silent -silent %SASMS%\setup.exe Command Line= -s -f2c:\Temp\msrtc.log %SASMS7%\setup.exe Command Line= -s -f2c:\Temp\msrtc7.log Main Install Command Line Pathname=%SASEXE%\setup.exe Command Line=-s quietfile=%SOURCE%"\disk1\sas\quiet.ini" -f2"C:\temp\quiet.log" -silentstatus This has worked for over

So confused as to what to do. 2 commentsshareall 2 commentssorted by: besttopnewcontroversialoldrandomq&alive (beta)[–]anscot 0 points1 point2 points 7 months ago(1 child)Microsoft components might be needed, see http://support.sas.com/kb/45/588.html or http://support.sas.com/documentation/installcenter/en/ikfdtnwx6sr/66390/PDF/default/sreq.pdf permalinkembedsavegive gold[–]Ehwic[S] 0 points1 point2 eguide__92130__prt__xx__sp0__1 Because the Runtime Components 7.1 do not seem to work correctly when running the install from the “sysreqwizard” folder, I created a software package that specifically installed those components. One thing to make sure of: you run the setup.exe (for the SAS Deployment Wizard) as Administrator. http://blogs.sas.com/content/sasdummy/2009/10/01/sas-9-2-and-sas-enterprise-guide-4-2-on-windows-7/ I deployed sas 9.2 successfully using the following command: setup.exe -NOREBOOT -nomsupdate -quiet -wait -responsefile "\\uos-app00050-si.soton.ac.uk\sccmpackagedist$\SAS9.2\sdwresponse.properties" -provision But sadly the same command doesn't work for sas 9.3, I've also tried the

Answered 03/22/2011 by: smartstyle Please log in to comment Please log in to comment 1 Thanks all for you previous notes, they have helped me achieve a silent install of the There's also a switch that changes the data path '-datalocation c:\temp' however that gave me OLE errors after install. Good luck with your new role at SAS institute ! I know I can probably create another batch file and push it out after say 30-45mins (since thats how long it takes for the install to complete on a single machine

However, if I were you I'd check with SAS Tech Support for potential other options. https://www.reddit.com/r/sas/comments/4hsw5r/downloading_microsoft_runtime_component_80_sp1/ I wonder if in win7 you can force 32bit apps to use the 3GB? Answered 03/16/2011 by: mstarks67 Please log in to comment Please log in to comment 1 It's not SCCM that needs that access but the local System account on the workstations. sreedhar Answered 01/26/2011 by: sreedharko Please log in to comment Please log in to comment 1 At which point in the middle of the installation is it failing on?

Using Process Explorer I found out that process _ISDEL.EXE was the last one that died at the end of installation (process was started by setup.exe in the beginning of installation, that's have a peek at these guys On the other hand, if the issue is a software, re-installation is needed. The Uninstall command is as follows (8.3 Format required): 1. Reply Michael Posted June 13, 2012 at 11:50 am | Permalink Hey Chris, for some reasons we made the installation of the EG 4.2 (and AMO) from the products-folder (as you

Execution of task sequence failed. Reply Jim Posted April 26, 2010 at 10:27 pm | Permalink Sorry about my earlier post, I figured this out. Thus, it seems that all is OK after all. check over here Answered 09/04/2008 by: VBScab Please log in to comment Please log in to comment 1 ORIGINAL: usgrcm That sounds like it would work well, may I ask how you determined that

Microsoft Runtimes for SAS Base 9.2 v1 – 2 6. Chris Reply Jim Posted April 26, 2010 at 9:35 pm | Permalink I loaded SAS 9.2 successfully, including the pre-emptive steps, (rebooted too), via the deployment wizard but it did not Thanks for this advice.

Did you contact SAS support and, if so, what did they tell you to do?

The install stops working when it is in first step. Thanks in advance! Try this little bit of code: data sasprods; length prodname $ 30 prodcode $ 10 prodmod $ 10 installed $ 12; input prodname 1-30 prodcode prodmod; licensed=sysprod(prodcode); if (prodmod eq '') The recommended way to resolve this is, unfortunately, to go back and install the client application (EG and AMO) via the deployment wizard.

Thx Russell Reply Chris Posted January 20, 2010 at 1:35 pm | Permalink At this time, Enterprise Miner is not on the list of supported Windows 7 products. All you need to do to make the process work is to go over the advance system setting via control panel. This script will run and insatll the SAS 9.2 application on a Windows XP SP2 machine however it is not insatlling on a Windows 7 Enterprise 64 bit machine. this content And indeed after it checks, it verifies that my system does meet requirements.

Anyone who knows a solution? Hope this helps. Thanks in advance Reply Chris Posted January 28, 2010 at 3:45 pm | Permalink Jakob, the version does make a difference. You might try this update: http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en Also, we have a hotfix in the works for a related issue; should be available for download within a couple of weeks.

Install SAS 9.2 setup.exe -noreboot -nomsupdate -wait -quiet -provision -responsefile "%temp%\x64.properties" Setup Information: Setup Type: unspecified Deployment Method Used: unspecified Deployment Difficulty: unspecified Platform(s): Windows jconnor 12/10/2010 Show Comments I was able to deploy it using the system account by other means with -provision in other positions. Clicking on show details, there is the following message: System.IO.FileNotFoundException Could not load file or assembly 'Microsoft.Web.Services3, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. I've followed all instructions regarding the pre-install on your blog & am running the setup in compatibility mode.

I would start here for silent installations. Can you suggest any work around? Any suggestions?