chejunkie.

com

http://www.chejunkie.com/aspen-plus/installation-guide/

Installation Guide
by

Bellow is a step-by-step guide on how to install a standalone version of Aspen Engineering Suite onto your computer. In this case I will be installing Aspen ONE v7.3 (32-bit) onto a Windows 8 machine (64-bit), which resulted in some problems with the authentication mode used by the Aspen Properties Enterprise Database (APED), so the process is split-up into two different sections: 1. Installation of Aspen Engineering Suite 2. SQLEXPRESS Authentication Mode If you dont get warning messages during the setup about the authentication mode of the APED, then you can skip the last step. The problem likely arose because of the Visual Studio versions I already had prior to installation, but Im not too sure Note: For reference, additional information can be found here in the Aspen Engineering Suite v7.3 Installation Guide. Will multiple versions of Aspen Plus run on the same computer? Yes, all major version of Aspen Plus will run concurrently if the system supports all of them. For example, it is possible to run 11.1, 12.1, 2004, and 2004.1 on XP or 2000. Backup files for these versions are only upwardly compatible (i.e. they can only be opened in that version and higher and cannot be opened in any lower version.) Software Requirements? Some general software requirements that apply to all Aspen products: [--important!--] MS Office 2003 SP3 or higher Microsoft Excel is required on the client for the Datasheet Definer and the Excel Datasheet Generator. This can be installed after (or before) the install of Aspen Engineering products. (not really required) Internet Explorer 6 SP2 or higher You need a browser to display KB dialogs from their support website. You are not necessarily required to use Microsoft IE (Chrome, Firefox, etc. will work just fine too). (not really required) Adobe Reader Version 4 or higher All product documentation by AspenTech is in *.pdf format. You are not necessarily required to use Adobe (i.e. any program, like Foxit for instance, can equally be used instead). [--important!--] Microsoft .NET Framework 3.5

Aspen Engineering products are built on-top of this, and so it is fundamentally required for them to run You are responsible for installing this software BEFORE attempting to install the Aspen Engineering products. Download Microsoft .NET Framework 3.5 from Microsofts website. Make sure you have the latest service pack and critical updates for the version of Windows on the computer (i.e. check for Windows Updates). Microsoft .NET 3.5 SP1 is not typically enabled on Windows 8. Please review the Microsoft KB article on how to enable or install .NET 3.5 using command line function and enable the On Demand features. This requires Administrator access to install: Installing the .NET Framework on 3.5 on Windows 8 Error codes when you try to install the .NET Framework 3.5 in Windows 8 or in Windows Server 2012 [--important!--] Microsoft SQL Server 2005 SQL Server is required if Aspen Properties Enterprise Database is installed locally (must be configured to use SQL Server and Windows authentication mode). You are responsible for installing this software BEFORE attempting to install the Aspen Engineering products. Download Microsoft SQL Server 2005 Service Pack 3 from Microsofts website. Alternatively, the SQL Server installation package is also included on the AspenONE DVD. Is it possible to skip installation of the SQL Express Engine? There may be times when companies do not want individual copies of the Aspen Properties Enterprise Database (APED) to be installed on each client machine or when the installation media doesnt recognized that Microsoft SQL Server Express has already been installed. You need to change the registry to tell the installer to skip installation of the SQL Express engine on the client machine. Modify registry manually: For V7.X, create the following registry entry: Go to Start-> Run-> Type regedit Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\Setup for 32-bit Windows, or to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Aspentech\Setup for 64-bit Windows Right click the Setup folder and click New | DWORD from the context menu. Name the new DWORD key NOSQLExpress. Double click NOSQLExpress and assign a value of 1, then choose Hexadecimal. Click OK. Alternatively you can try something like this: MSDE Fool Installer.reg (you just need to change it from *.txt to *.reg before running)

Reference: How to add, modify, or delete registry subkeys and values by using a .reg file After that, if the prompt comes when starting Aspen Hysys or Aspen Plus looking for APED databases, switch to Legacy databases under Aspen Properties Database Selection Application >> Programs >> Aspentech >> Process Modeling V7.X >> Aspen Properties. How do I resolve the Configuration failed error when attempting to install the SQL Server? This installation issue can happen to you if you have MSXML 6 already installed on your machine and then try to install MS SQL Server 2005 SP3. Microsoft created a patch called MSXMLFix.exe to fix the installation conflict. Certain functionality may require you to install additional 3rd party programs such as Intel Fortran, or Visual Studio Compiler, and so on. Details of such 3rd party program prerequisites are covered in individual product installation sections of the Aspen Engineering Suite v7.3 Installation Guide.

Installation of Products
Run setup.exe from the installation disc:

This will open the following dialog: Note: Here it looks slightly distorted because I am installing onto a Windows 8 machine, but you should see something in-kind.

Select the [Products] tab, which brings up the following dialog:

Click [OK]:

Click [Next >]:

Select Standalone License File and click [Next >] to continue. Note: If you also have to work off a server (e.g. work or school) then you can choose Both, but I only show the standalone installation here. The only addition when adding a license server is that you need the name during the installation. You can always add a license server at a later time too.

Click [Add License ] to browse and add your *.lic file. Click [Next >] to continue:

A dialog box will now appear and determine which products you have the license to install. After the Licenses list is populated with all licenses found, click [Next >]:

Select Aspen Engineering and click the [Install] button. The Windows Installer view appears briefly as it prepares for installation. When no AspenONE products are installed the following dialog appears:

Click [Next >]: Note: When one or more AspenONE products are already installed a slightly different dialog will appear (from above), but you still only have to click [Next >].

Accept the terms and click [Next >] to continue:

Click the Standard Install icon to the left of the dialog (this will automatically jump you to the [Next >] dialog]:

Set This feature, and all subfeatures, option from the drop-down menu of each product you wish to install. Afterwards, click [Next >]: Note: Although you may choose differently, here I only install Process Modelling for Aspen Plus and Hysys, Process Development, and Aspen Plus Based Refinery Reactors.

If you are installing onto a 64-bit machine you will likely receive a warning message (above). It tells you to view Solution #131130, which basically tells you that it should work on a 64-bit machine but AspenTech is not responsible if it does not (blah-blah-blah) So click [OK] on the warning message to continue:

This information dialog now informs us that we will have to use the Aspen Properties Database Configuration Tester to change the authentication mode of the SQL database Aspen uses for properties. For now just click [OK] to continue with the installation:

Note: AspenTech requires Mixed Mode Authentication (SQL Server Authentication), but this information dialog only appears if SQLEXPRESS is incorrectly setup for Windows Authentication. If you dont see this dialog then you will not have to follow the step-by-step on how to change this setting after installation.

Click [Next >]:

Click [Next >]:

Enter your [Username ], [Password ], and [Domain ] (which is typically just your computer name). Click [Next >]:

Click [Install]:

Click [Finish ] .

Now [Restart] your computer before continuing to the next section below.

SQLEXPRESS Authentication Mode

During the installation I was provided with some information regarding Aspen Properties Enterprise Database (APED):

So it told us to use the Aspen Properties Database Configuration Tester (which was installed during the installation) to fix the problem; however, long story short, this did not fix the problem :/ The configuration tester falsely tells you that the problem is fixed:

But when you run the Tester again you receive the same error message:

So if this didnt work (like it didnt here) then the only way I found to change it is in the Registry.

Changing LoginMode via Registry

You need to find the LoginMode registry value for the SQLEXPRESS server, located within the registrykey MSSQLServer under HKEY_LOCAL_MACHINE (HKLM). For me this was the following path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQLServer Note: There are a couple of places in the registry that you will find LoginMode under different key-paths (but under the same key-name of MSSQLServer). Changing one of these values should automatically change the other values too. You can verify this, for instance, by searching for values named LoginMode. [Ctrl] + [F] brings up the find-form.

In the MSSQLServer registry-key (above) there will be a value called LoginMode, which will need to be set to the value of number 2. After making this change you should be good to go after restarting your computer again cheers! Note: LoginMode:= 1 is for Windows authentication, and 2 is for mixed mode authentication (required by AspenTech).