MRI Commercial. MRI Residential. CRE Manager. Windows Version 4.0 Installation Guide

Transcription

1 MRI Commercial MRI Residential CRE Manager Windows Version 4.0 Installation Guide Stock Number: IG40WIN March 2007

2 2007 Intuit Inc. Any unauthorized use or reproduction of this documentation is strictly prohibited. All Rights Reserved. MRI, ForeSight, LeaseFlow, ViewPoint, and NetSource are trademarks of Intuit Inc. Microsoft, MS, and Windows are registered trademarks of Microsoft Corporation. Adobe and Acrobat are registered trademarks of Adobe Systems Incorporated. Novell is a trademark of Novell Corporation.

3 Table of Contents Chapter 1: Preparing Your System... 7 Verifying Your Current Database Version Database System Requirements Installing SQL Server 2005 Express Moving MRI Databases from MSDE 2000 to a New Instance of SQL Server 2005 Express Database Compatibility Levels MSDTC Options Setting Up MSDTC Services as a Windows Firewall Exception Setting MSDTC Options on Windows XP SP2 and Windows Server 2003 SP Setting MSDTC Options on Windows Vista Network Requirements File Server Requirements Database Server Requirements Network Workstation Requirements Terminal Server Requirements Additional Tools and Software Requirements Chapter 2: Installing MRI for Windows Overview Getting Started Step 1: MSDTC Options Step 2: Microsoft.NET Framework Step 3: Microsoft Windows Installer Step 4: Microsoft Data Access Components Step 5: Microsoft Core XML Services Step 6: Microsoft SQL Server Native Client Step 7: Microsoft SQL Server Management Objects Step 8: Utilities Step 9: MRILogin Step 10: System Database Maintenance Creating the MRI System Database Upgrading the MRI System Database Step 11: MRI License Step 12: MRI for Windows MRI for Windows Installation Guide 3

4 Table of Contents Chapter 3: Installing Additional Software Getting Started Installing Report Viewer Installing MRI External Web Services Step 1: Microsoft Windows Components Step 2:.NET Framework Step 3: Install External Web Service Relay Installing MRI API External Web Services Step 1: Microsoft Windows Components Step 2:.NET Framework Step 3: Install External Web Service Relay Chapter 4: Adding New Applications Overview Getting Started Upgrading Your System Database Applying Your New MRI License Installing New Applications Chapter 5: Setting Up Workstations Installing MRILogin on Network Workstations Running Workstation Setup Chapter 6: Creating Databases Creating New Databases Creating Links to Existing Databases

5 Table of Contents Chapter 7: Upgrading Databases Overview Understanding Upgrade Prompts Upgrading Databases from Version 3.0 to Moving Customizations from Version 3.0 to Upgrading Version 4.0 Databases Moving Customizations between Version 4.0 Databases Creating or Modifying Custom Cabinets Applying Custom Cabinets Foreign Key Warnings Locating Records with Foreign Key Warnings Resolving Foreign Key Warnings Timeout Errors Increasing Application Timeout Increasing Machine Timeout Logging Index

6

7 Preparing 1 Your System In This Chapter This chapter provides requirements and recommendations for preparing your network system to run MRI for Windows version 4.0. Caution Due to variable loads and uses on the server side, this documentation can recommend only minimum requirements. Contact Technical Support for recommendations specific to your organization and for all of the latest requirements and approved service packs. Verifying Your Current Database Version Database System Requirements Installing SQL Server 2005 Express. 11 Moving MRI Databases from MSDE 2000 to SQL Server 2005 Express Database Compatibility Levels MSDTC Options Setting Up MSDTC Services as a Windows Firewall Exception Setting MSDTC Options on Windows XP or Windows Server Setting MSDTC Options on Windows Vista Network Requirements File Server Requirements Database Server Requirements Network Workstation Requirements. 28 Terminal Server Requirements Additional Tools and Software Requirements MRI for Windows Installation Guide 7

8 Chapter 1: Preparing Your System Verifying Your Current Database Version Warning If you are currently running MRI for Windows, you must upgrade each database to version 3.0 Service Pack 4a (SP4a) prior to upgrading it to version 4.0. To verify if your current database is at version 3.0 SP4a: 1. Open the database in MRI for Windows. 2. On the Help menu, click About MRI to display the About MRI for Windows dialog box (Figure 1-1). Figure 1-1. About MRI for Windows Dialog Box 8 Verifying Your Current Database Version

9 Chapter 1: Preparing Your System 3. Click Application Info to display the Application Versions dialog box. Figure 1-2. Application Versions Dialog Box 4. Use the information in Table 1-1 to verify the version of each application in your database. The version in the DB Version column on the Application Database dialog box, must match the versions shown below. Table 1-1. Application Versions for MRI 3.0 SP4a Application ID Application Description Application Version for 3.0 SP4a ADVGL Enterprise Ledger AH Affordable Housing AM ViewPoint AP Accounts Payable AR Corporate AR AUDIT Audit Trail continued Verifying Your Current Database Version 9

10 Chapter 1: Preparing Your System Table 1-1. Application Versions for MRI 3.0 SP4a (Continued) Application ID Application Description Application Version for 3.0 SP4a BASE MRI Base Tables CM Commercial Management CRE Corporate Real Estate DHCR RM New York DHCR DP Distributive Processing FM Facility Management FS ForeSight GL General Ledger JC JobCost LF LeaseFlow MM Maintenance Management MRI MRI System Tables MRIWEB MRI for the Web PLATO Plato PO Purchase Order PR Project Management RM Residential Management RP Resident Portal RT Retail Module SM Space Manager TC Tax Credit WF Workflow Verifying Your Current Database Version

11 Chapter 1: Preparing Your System Database System Requirements Caution MRI no longer supports Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) or SQL Server 7.0. MRI version 4.0 only supports the following database systems: Microsoft SQL Server 2000 Standard or Enterprise Edition with all MRI databases hosted on the server set to compatibility level 80, as described in Database Compatibility Levels on page 16 Microsoft SQL Server 2005 Standard, Enterprise, Workgroup, or Express Edition with all MRI databases hosted on the server set to compatibility level 90, as described in Database Compatibility Levels on page 16 Notes: SQL Server 2005 Express Edition does not require a SQL Server license. IRES recommends you use SQL Server 2005 Express only if you have fewer than 20 users. Installing SQL Server 2005 Express You can install Microsoft SQL Server 2005 Express (SQL Server Express) and Microsoft SQL Server Management Studio Express (SSMSE) from the second MRI installation CD or the Microsoft Web site at Warning IRES does not provide a SQL administration tool for scheduling database backups. To schedule backups of SQL Server 2005 Express databases, you must use a third-party system, such as Express Agent from Vale Software. For assistance with scheduling regular backups of SQL Server 2005 Express databases, contact Technical Support. Database System Requirements 11

12 Chapter 1: Preparing Your System If you currently use Microsoft SQL Server 2000 Desktop Engine (MSDE 2000), you must install SQL Server 2005 Express Edition (SQL Server Express) as a replacement for MSDE Refer to the following table for installation guidelines. If you are currently using MSDE 2000 to host... MRI and non-mri databases MRI databases only Then IRES recommends you... install a new named instance of SQL Server Express alongside MSDE After installing a new instance of SQL Server 2005 Express, use the process described in Moving MRI Databases from MSDE 2000 to a New Instance of SQL Server 2005 Express on page 13 to move your MSDE 2000 databases to SQL Server 2005 Express. upgrade your current installation of MSDE 2000 to SQL Server Express. For detailed instructions from Microsoft on upgrading MSDE 2000 to SQL Server 2005 Express, refer to the documentation available at the following location: /msde2sqlexpress.mspx 12 Database System Requirements

13 Chapter 1: Preparing Your System Moving MRI Databases from MSDE 2000 to a New Instance of SQL Server 2005 Express If you installed a new named instance of SQL Server 2005 Express, use the following process to move your MRI system and application databases from MSDE 2000 to SQL Server 2005 Express: 1. In the MRI security console, delete your existing MSDE 2000 databases. For instructions on deleting databases in MRI, refer to the System Administration guide. Note: The Delete function in MRI only deletes the link to the database from MRI to the server; the database still remains on the server. 2. Using SQL Server Management Studio Express, back up your MRI system database (MRISystem) and all application databases on MSDE 2000 and restore them to the named instance of SQL Server 2005 Express. 3. Set the database compatibility level to 90 for each MRI database on SQL Server 2005 Express, as described in Database Compatibility Levels on page Use the System Database utility to redirect the link to the system database from MSDE 2000 to SQL Server 2005 Express: a. Open the \MRICMN\3.0.0\MRIWIN\BIN folder. b. Double-click SYSTEMDB.EXE to display the Enter SYSADM s Password dialog box (Figure 1-3). Figure 1-3. Enter SYSADM s Password Dialog Box Database System Requirements 13

14 Chapter 1: Preparing Your System c. Type the SYSADM password, and then click OK to display the Change System Database Connection String dialog box (Figure 1-4). Figure 1-4. Change System Database Connection String Dialog Box d. Type the server name, SQL login, and password for SQL Server 2005 Express, and then click Save. Note: The password is case-sensitive. e. When a message appears indicating the connection string for the system database was changed successfully, click OK. 5. If you use MRI for the Web, modify the MRI_Svr_Db.DBHelper constructor string to point to SQL Server 2005 Express: a. On the Windows Start menu, go to Settings > Control Panel > Administrative Tools > Component Services. b. In the left navigation pane, expand Component Services, Computers, My Computer, COM+ Applications, MRIServers, and then Components. c. Right-click MRI_Svr_Db.DBHelper, and then click Properties. d. On the MRI_Svr_Db.DBHelper Properties dialog box, click the Activation tab (Figure 1-5). 14 Database System Requirements

15 Chapter 1: Preparing Your System Figure 1-5. MRI_Svr_Db.DBHelper Properties Dialog Box e. In the Constructor String field, change the data source to the SQL Server 2005 instance (server_name\instance_name) and the password for the SQL Server 2005 login, if applicable. f. Click OK. 6. Install MRI 4.0. Note: The password is case-sensitive. 7. In the MRI, create a link to each MRI database on the new named instance of SQL Server 2005 Express. When you create the link to the database, the system automatically upgrades the database to version 4.0. For instructions on creating links to existing MRI databases, refer to Chapter 6, Creating Databases. Database System Requirements 15

16 Chapter 1: Preparing Your System Database Compatibility Levels Caution You must set the database compatibility level for each MRI database hosted on a SQL Server to 80 for SQL Server 2000 or 90 for SQL Server Otherwise, the system prevents you from upgrading the databases to version 4.0. To set the database compatibility level for a database on a SQL Server: 1. Open SQL Server Enterprise Manager, SQL Server Management Studio, or SQL Server Management Studio Express, depending on your version of SQL Server. 2. Expand the list of databases on the SQL Server. 3. Right-click an MRI database, and then click Properties. 4. Use the information in the following table to continue. If you are using... SQL Server Enterprise Manager for SQL Server 2000 SQL Server Management Studio or SQL Server Management Studio Express Then... a. On the [Database] Properties dialog box, click the Options tab. b. In the Level field under Compatibility, select Database compatibility level 80 a. On the left side of the Database Properties dialog box, click Options. b. In the Compatibility level field, select SQL Server 2000 (80) if you are using SQL Server 2000 SQL Server 2005 (90) if you are using SQL Server Repeat Steps 3 through 4 for each MRI database on the server. 16 Database System Requirements

17 Chapter 1: Preparing Your System MSDTC Options MRI requires specific Microsoft Distributed Transaction Coordinator (MSDTC) security options on your SQL Server and network workstations to ensure the integrity of database modifications during upgrades. Until you set the required MSDTC options, you cannot install MRI for Windows. You must set the following MSDTC security options on each SQL Server and workstation in your MRI network with the exception of Windows 2000 Service Pack 4 (SP4), Windows 2000 Server SP4, and Windows 2000 Advanced Server SP4, which do not provide MSDTC services: Allow DTC Access Allow Inbound Allow Outbound No Authentication Required or Mutual Authentication Caution The MSDTC options you set must be identical across your SQL Servers and workstations running MRI. If your environment includes a Windows 2000 operating system, you must set the No Authentication Required option on all SQL Servers and workstations running MRI does not include a Windows 2000 operating system, you can set the Mutual Authentication Required option as an added security measure If Windows Firewall is enabled for a SQL Server or workstation on which you set MSDTC options, you must set up MSDTC as an exception to prevent Windows Firewall from blocking MSDTC services, as described in Setting Up MSDTC Services as a Windows Firewall Exception on page 18. MSDTC Options 17

18 Chapter 1: Preparing Your System Setting Up MSDTC Services as a Windows Firewall Exception To set up MSDTC Services as a Windows Firewall Exception: 1. On the Windows Start menu, go to Settings > Control Panel > Windows Firewall. 2. On the Windows Firewall dialog box, click the Exceptions tab. 3. Click Add Program. 4. On the Add a Program dialog box, click Browse, and then select msdtc.exe in the C:\WINDOWS\system32 folder. 5. Click OK to display msdtc.exe in the list of Windows Firewall exceptions (Figure 1-6). Figure 1-6. Windows Firewall Exceptions 18 MSDTC Options

19 Chapter 1: Preparing Your System Setting MSDTC Options on Windows XP SP2 and Windows Server 2003 SP1 To set MSDTC options on Windows XP SP2 or Windows Server 2003 SP1: 1. On the Start menu, go to Settings > Control Panel > Administrative Tools > Component Services. 2. Expand Component Services, and then expand Computers. 3. Right-click My Computer, and then click Properties. 4. On the My Computer Properties dialog box, click the MSDTC tab. 5. Click Security Configuration to display the Security Configuration dialog box (Figure 1-7). Figure 1-7. Security Configuration Dialog Box MSDTC Options 19

20 Chapter 1: Preparing Your System 6. Select the Network DTC Access check box. 7. In the Transaction Manager Communication area, select the Allow Inbound and Allow Outbound check boxes. 8. Click either the No Authentication Required or Mutual Authentication Required option button. Caution The MSDTC options you set must be identical across your SQL Servers and workstations running MRI. If your environment includes a Windows 2000 operating system, you must set the No Authentication Required option on all SQL Servers and workstations running MRI does not include a Windows 2000 operating system, you can set the Mutual Authentication Required option as an added security measure 9. Click OK. 20 MSDTC Options

21 Chapter 1: Preparing Your System Setting MSDTC Options on Windows Vista To set MSDTC options on Windows Vista : 1. Click the Start button, and then type DCOMCNFG in the Search box. 2. On the Component Services view, expand Component Services > Computers > My Computers > Distributed Transaction Coordinator. 3. Right-click Local DTC, and then click Properties to display the Local DTC Properties dialog box (Figure 1-8). Figure 1-8. Local DTC Properties Dialog Box MSDTC Options 21

22 Chapter 1: Preparing Your System 4. Click the Security tab. 5. In the Transaction Manager Communication area, select the Allow Inbound and Allow Outbound check boxes. 6. Click either the No Authentication Required or Mutual Authentication Required option button. Caution The MSDTC options you set must be identical across your SQL Servers and workstations running MRI. If your environment includes a Windows 2000 operating system, you must set the No Authentication Required option on all SQL Servers and workstations running MRI does not include a Windows 2000 operating system, you can set the Mutual Authentication Required option as an added security measure 7. Click OK. 22 MSDTC Options

23 Chapter 1: Preparing Your System Network Requirements Your network system may consist of the following components: File Server Depending on whether you use SQL Server or SQL Server 2005 Express Edition, a file server may be dedicated to storing program files only or both program files and databases. For more information, refer to Table 1-2. Database Server A database server, or SQL Server, is dedicated to storing databases and processing database queries. Workstations A workstation, or client computer, is used for work by individuals. Table 1-2 describes the network components you need depending on whether you use SQL Server or SQL Server 2005 Express Edition. Warning SQL Server 2005 Express programs and databases must run on a Microsoft operating system. IRES does not support SQL Server on a domain controller or messaging system. Table 1-2. Network Component Requirements SQL Server If you use... SQL Server 2005 Express Edition You need... a file server to store program files a database server to store databases one or more workstations to run programs and applications a file server to store both program files and databases one or more workstations to run programs and applications Note: SQL Server 2005 Express Edition also functions on stand-alone workstation without any network connectivity or in a work group environment. Network Requirements 23

24 Chapter 1: Preparing Your System File Server Requirements The file server stores MRI for Windows program files. If you use SQL Server 2005 Express Edition, the file server can also store your databases. Use the information in Table 1-3 to determine file server requirements. Table 1-3. File Server Requirements Component Operating System (Optional) Database System CPU RAM Requirement MRI for Windows programs can run on the following operating systems: Windows 2000 Server Service Pack 4 Windows 2000 Advanced Server Service Pack 4 Windows Server 2003 Service Pack 1, Standard Edition Windows Server 2003 Service Pack 1, Enterprise Edition Note: IRES supports both 32-bit and 64-bit versions of Windows 2000 Server and Windows Server SQL Server 2005 Express Edition You must set the appropriate database compatibility level for each MRI database on the SQL Server. Otherwise, the system prevents you from upgrading the databases to version 4.0. For more information, refer to Database Compatibility Levels on page 16. Note: IRES supports both 32-bit and 64-bit versions of SQL Server database systems. 1 gigahertz (GHz) or industry standard Note: The number of processors may vary depending on the number of concurrent users. 1 gigabyte (GB) Note: Requirements increase as the number of concurrent users increases. continued 24 Network Requirements

25 Chapter 1: Preparing Your System Table 1-3. File Server Requirements Component Available Disk Space Drive Type CD-ROM Drive (Optional) SCSI Controller 600 megabytes (MB) for applications and processing, plus additional space for data if the file server hosts databases Note: Disk space requirements may vary based on other MRI for Windows applications installed or the amount of data and reports stored on the local hard disk. Using Real-Time General Ledger (GL) greatly increases the amount of disk space needed. SCSI, SATA, or industry standard Note: Disk subsystems can have dramatic impact on SQL Server 2005 Express performance and should be scaled to the number of users. Industry standard RAID 5 for data Requirement Network Requirements 25

26 Chapter 1: Preparing Your System Database Server Requirements The database server, also known as the SQL Server, stores the SQL database and log devices. Caution IRES recommends you use a dedicated computer as the database server. However, if you use SQL Server 2005 Express, you do not need a dedicated database server. Use the information in Table 1-4 to determine database server requirements. To set the required MSDTC options on a database server, refer to MSDTC Options on page 17 Table 1-4. Database Server Requirements Component Operating System Database System Requirement MRI for Windows databases can be hosted on the following operating systems: Windows 2000 Server Service Pack 4 Windows 2000 Advanced Server Service Pack 4 Windows Server 2003 Service Pack 1, Standard Edition Windows Server 2003 Service Pack 1, Enterprise Edition Note: IRES supports both 32-bit and 64-bit versions of Windows 2000 Server and Windows Server MRI for Windows supports the following database systems: SQL Server 2000 Service Pack 4, Standard Edition SQL Server 2000 Service Pack 4, Enterprise Edition SQL Server 2005 Express Edition SQL Server 2005 Service Pack 1, Workgroup Edition SQL Server 2005 Service Pack 1, Standard Edition SQL Server 2005 Service Pack 1, Enterprise Edition You must set the appropriate database compatibility level for each MRI database on the SQL Server. Otherwise, the system prevents you from upgrading the databases to version 4.0. For more information, refer to Database Compatibility Levels on page 16. Note: IRES supports both 32-bit and 64-bit versions of SQL Server database systems. continued 26 Network Requirements

27 Chapter 1: Preparing Your System Table 1-4. Database Server Requirements (Continued) Component Requirement CPU RAM Drive Type Available Disk Space CD-ROM Drive (Optional) SCSI Controller 1 GHz or industry standard Note: The number of processors may vary depending on the number of concurrent users. 2 GB Note: Requirements increase as the number of concurrent users increases. SCSI, SATA, or industry standard 600 MB for applications and processing, plus additional space for data Note: Disk space requirements may vary based on the amount of data and reports stored on the local hard disk. Using Real-Time General Ledger (GL) greatly increases the amount of disk space needed. Industry standard RAID 1 for OS and paging RAID 5 for data Network Requirements 27

28 Chapter 1: Preparing Your System Network Workstation Requirements A network workstation runs MRI for Windows programs and applications. Use the information in Table 1-5 to determine the requirements for a network workstation. To set the required MSDTC options on a workstation, refer to MSDTC Options on page 17. Table 1-5. Network Workstation Requirements Component Recommended Minimum Operating System Additional Components The following operating systems can be used for network workstations: Windows 2000 Service Pack 4 Windows XP Professional Service Pack 2 (SP2) Windows Vista Business Edition Windows Vista Enterprise Edition Windows Vista Ultimate Edition The following components are required on each network workstation, including the computer from which you perform the MRI installation. Workstations connecting to MRI through Citrix do not require these components; however, the components are required on the Citrix server. You cannot install MRI for Windows or run Workstation Setup unless the these components are installed. Microsoft.NET Framework 2.0 Microsoft Windows Installer 3.1 Microsoft Data Access Components (MDAC) 2.8 Microsoft Core XML Services (MSXML) 6.0 Microsoft SQL Server Native Client Microsoft SQL Server 2005 Management Objects Collection Note: If the components are not installed on the computer from which you perform the installation, you can install them during the MRI for Windows installation process. CPU 300 MHz for Windows XP Professional SP2 or 1 GHz for Windows Vista 233 MHz for Windows XP Professional SP2 or 800 MHz for Windows Vista continued 28 Network Requirements

29 Chapter 1: Preparing Your System Table 1-5. Network Workstation Requirements (Continued) Component Recommended Minimum RAM 256 MB for Windows XP Professional SP2 or 1 GB for Windows Vista 128 MB for Windows XP Professional SP2 or 512 MB for Windows Vista Note: Memory requirements vary based on other applications installed and the number of users connected. Increasing memory on the workstation provides the greatest performance gain. Color Monitor Available Disk Space Connection to SQL Server SVGA 1024x768, greater than 256 colors 1.5 GB for Windows XP Professional SP2 or 15 GB for Windows Vista Note: Disk space requirements may vary based on other applications installed or the amount of data and reports stored on the local hard disk. Using Real-Time General Ledger (GL) greatly increases the amount of disk space needed. SQL Server Client 32-bit net libraries running TCP/IP sockets Connection to SQL Server 2005 Express Edition 100 megabits per second (Mbps) Network Requirements 29

30 Chapter 1: Preparing Your System Terminal Server Requirements Microsoft Terminal Server is an optional server configuration used in conjunction with MRI for Windows for remote access. Use the information in Table 1-6 to determine the requirements for using a terminal server. Table 1-6. Terminal Server Requirements Component Server Operating System Client Operating System Requirement The following operating systems can be used for a server running Terminal Services: Windows 2000 Server Service Pack 4 Windows 2000 Advanced Server Service Pack 4 Windows Server 2003 Service Pack 1, Standard Edition Windows Server 2003 Service Pack 1, Enterprise Edition Notes: IIRES supports both 32-bit and 64-bit versions of Windows 2000 Server and Windows Server Citrix MetaFrame can be used for additional functionality. The following operating systems can be used for a client workstation running Terminal Services: Windows 2000 Service Pack 4 Windows XP Professional Service Pack 2 Windows Vista Business Edition Windows Vista Enterprise Edition Windows Vista Ultimate Edition Client Server Tools SQL Server 2000 or SQL Server 2005 Note: The version of Client Server Tools you use must match the version of SQL Server you use. CPU Dual 1 GHz or industry standard continued 30 Terminal Server Requirements

31 Chapter 1: Preparing Your System Table 1-6. Terminal Server Requirements (Continued) Component Requirement RAM Drive Type CD-ROM Drive 1 GB or more Note: Requirements increase as the number of concurrent users increases. SCSI, SATA, or industry standard Industry standard (Optional) SCSI Controller RAID 1 Additional Tools and Software Requirements Use the information in Table 1-7 to determine additional requirements and recommendations for tools and software. Contact Technical Support for specific recommendations based on the needs of your organization. Table 1-7. Additional Requirements and Recommendations Requirements Microsoft Enterprise Manager for SQL Server 2000 Microsoft Management Studio for SQL Server 2005 Microsoft Management Studio Express for SQL Server 2005 Express Edition SQL Server client tools dedicated for MRI Windows support Microsoft Internet Explorer 5.5, 6.0, or 7.0 Adobe Acrobat Reader Latest ODBC drivers (MDAC) Remote connectivity, such as, PCAnywhere 32, version 10 or Windows 2000 Terminal Services (a separate licensed function of Windows 2000 Server) with or without Citrix MetaFrame 2000 Recommendations Microsoft Excel 97, 2000, 2003, or 2007 Microsoft Word 97, 2000, 2003, or 2007 Microsoft Outlook Anti-virus software One external modem (56 KB) Backup solution Uninterruptible Power Supply (UPS) with accompanying software on all servers DVD-Writer Additional Tools and Software Requirements 31

32

33 Installing MRI 2 for Windows In This Chapter This chapter describes how to install MRI Windows 4.0. Before You Begin Make sure your system meets the requirements specified in Chapter 1, Preparing Your System Warning If you are currently running MRI for Windows, you must upgrade to version 3.0 Service Pack 4a prior to installing MRI 4.0. If you are currently using Microsoft SQL Server Desktop Engine (MSDE 2000) to host MRI databases, you must move the databases to SQL Server 2005 Express prior to installing MRI 4.0. For more information, refer to Chapter 1, Preparing Your System. Close any open applications Make sure all users are logged off of MRI Back up all databases, including the system database (MRISystem.mdb) Have your MRI license disk or license file (Sysinfo.lst) available Overview Getting Started Step 1: MSDTC Options Step 2: Microsoft.NET Framework Step 3: Microsoft Windows Installer Step 4: Microsoft Data Access Components Step 5: Microsoft Core XML Services Step 6: Microsoft SQL Server Native Client Step 7: Microsoft SQL Server Management Objects Step 8: Utilities Step 9: MRILogin Step 10: System Database Maintenance Creating the MRI System Database Upgrading the MRI System Database Step 11: MRI License Step 12: MRI for Windows MRI for Windows Installation Guide 33

34 Chapter 2: Installing MRI for Windows Overview With the purchase of MRI for Windows, you receive a license disk that contains the license file (Sysinfo.lst) and two installation CDs. The first installation CD contains MRI for Windows applications and programs. MRI for the Web applications and programs. For information about installing MRI for Windows, refer to the Installation Guide for MRI for the Web available on the first installation CD or the ClientSite The second installation CD contains user assistance for MRI for the Web, including online Help files, Adobe Flash demonstrations, and user guides. Caution To enable users to access online Help, Adobe Flash demonstrations, and user guides from the Help menu in MRI Web, you must complete the MRI Web User Assistance installation after you install MRI for the Web. the Report Viewer program for viewing MRI reports sent through . MRI external Web services. Microsoft SQL Server 2005 Express Edition (SQL Server Express) you can use as an alternative to Microsoft SQL Server databases. Note: MRI no longer supports Microsoft SQL Server Desktop Engine (MSDE 2000) databases. Microsoft SQL Server 2005 Management Studio Express for managing SQL Server 2005 Express Edition databases. For more information about installing user assistance for MRI for the Web, refer to the Installation Guide for MRI for the Web all other software provided on the second installation CD, refer to Chapter 3, Installing Additional Software 34 Overview

35 Chapter 2: Installing MRI for Windows Getting Started To begin the installation process: 1. Insert the first installation CD into your CD-ROM drive. If your system is... Set to autorun CDs Not set to autorun CDs Then... The Welcome screen (Figure 2-1) appears. Go to Step 2 to continue. a. Click the Windows Start menu, and then click Run. b. Type X:setup.exe where X is the letter of your CD-ROM drive, and then click OK. The Welcome screen (Figure 2-1) appears. c. Go to Step 2 to continue. Figure 2-1. Welcome Screen Getting Started 35

36 Chapter 2: Installing MRI for Windows 2. Click the Next button to the right of Install MRI for Windows 4.0 to display the installation screen (Figure 2-2), which will guide you through the installation process. The twelve numbered buttons on the left of the installation screen represent the steps required to install MRI for Windows. Caution While you can click any numbered step to review the installation requirements, you must perform each step in the order listed. A check mark indicates which steps have been completed. For example, in Figure 2-2, Steps 1 through 7 have been completed, and Step 8 is the next required step. Next required step Figure 2-2. Installation Steps 3. Proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. 36 Getting Started

37 Chapter 2: Installing MRI for Windows Step 1: MSDTC Options To complete Step 1 of the installation process: 1. Click the MSDTC Options button to display the Verify MSDTC Options screen (Figure 2-3). Figure 2-3. Verify MSDTC Options Screen 2. If the status indicates the required Microsoft Distributed Transaction Coordinator (MSDTC) options are not set, you must manually set the required MSDTC options on the computer from which you are performing the installation before you can proceed with the installation process. For instructions on how to set the required MSDTC options, refer to MSDTC Options on page Once the status indicates the required MSDTC options are set, proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. Step 1: MSDTC Options 37

38 Chapter 2: Installing MRI for Windows Step 2: Microsoft.NET Framework To complete Step 2 of the installation process: 1. Click the Microsoft.NET Framework button to display the Install.NET Framework 2.0 screen (Figure 2-4). Figure 2-4. Install.NET Framework 2.0 Screen 2. If the status indicates.net Framework 2.0 is not installed, you must install it on the computer from which you are installing MRI before you can proceed with the installation process. Click Install to launch the Microsoft installation program for.net Framework 2.0. For more information about installing.net Framework 2.0, refer to the Microsoft Web site. 3. Once the status indicates.net Framework 2.0 is installed, proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. 38 Step 2: Microsoft.NET Framework

39 Chapter 2: Installing MRI for Windows Step 3: Microsoft Windows Installer To complete Step 3 of the installation process: 1. Click the Microsoft Windows Installer button to display the Install Windows Installer 3.1 screen (Figure 2-5). Figure 2-5. Install Windows Installer 3.1 Screen 2. If the status indicates Microsoft Windows Installer 3.1 (MSI 3.1) is not installed, you must install it on the computer from which you are installing MRI before you can proceed with the installation process. Click Install to launch the Microsoft installation program for MSI 3.1. For more information about installing MSI 3.1, refer to the Microsoft Web site. 3. Once the status indicates MSI 3.1 is installed, proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. Step 3: Microsoft Windows Installer 39

40 Chapter 2: Installing MRI for Windows Step 4: Microsoft Data Access Components To complete Step 4 of the installation process: 1. Click the Microsoft Data Access Components button to display the Install Microsoft Data Access Components 2.8 screen (Figure 2-6). Figure 2-6. Install Microsoft Data Access Components 2.8 Screen 2. If the status indicates Microsoft Data Access Components (MDAC) 2.8 are not installed, you must install them on the computer from which you are installing MRI before you can proceed with the installation process. Click Install to launch the Microsoft installation program for MDAC 2.8. For more information about installing MDAC 2.8, refer to the Microsoft Web site. 3. Once the status indicates MDAC 2.8 is installed, proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. 40 Step 4: Microsoft Data Access Components

41 Chapter 2: Installing MRI for Windows Step 5: Microsoft Core XML Services To complete Step 5 of the installation process: 1. Click the Microsoft Core XML Services button to display the Install Microsoft Core XML Services (MSXML) 6.0 screen (Figure 2-7). Figure 2-7. Install Microsoft Core XML Services (MSXML) 6.0 Screen 2. If the status indicates MSXML 6.0 (MSXML6) is not installed, you must install it on the computer from which you are installing MRI before you can proceed with the installation process. Click Install to launch the Microsoft installation program for MSXML6. For more information about installing MSXML6, refer to the Microsoft Web site. 3. Once the status indicates MSXML6 is installed, proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. Step 5: Microsoft Core XML Services 41

42 Chapter 2: Installing MRI for Windows Step 6: Microsoft SQL Server Native Client To complete Step 6 of the installation process: 1. Click the Microsoft SQL Server Native Client button to display the Install Microsoft SQL Server Native Client screen (Figure 2-8). Figure 2-8. Install Microsoft SQL Server Native Client Screen 2. If the status indicates Microsoft SQL Server Native Client (SQL Native Client) is not installed, you must install it on the computer from which you are installing MRI before you can proceed with the installation process. Click Install to launch the Microsoft installation program for SQL Native Client. For more information about installing SQL Native Client, refer to the Microsoft Web site. 3. Once the status indicates SQL Native Client is installed, proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. 42 Step 6: Microsoft SQL Server Native Client

43 Chapter 2: Installing MRI for Windows Step 7: Microsoft SQL Server Management Objects To complete Step 7 of the installation process: 1. Click the SQL Server Management Objects button to display the Install SQL Server 2005 Management Objects Collection screen (Figure 2-9). Figure 2-9. Install SQL Server 2005 Management Objects Collection Screen 2. If the status indicates the objects are not installed, you must install them on the computer from which you are installing MRI before you can proceed with the installation process. Click Install to launch the Microsoft installation program for the objects. For more information about installing the SQL Server 2005 Management Objects Collection, refer to the Microsoft Web site. 3. Once the status indicates the objects are installed, proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. Step 7: Microsoft SQL Server Management Objects 43

44 Chapter 2: Installing MRI for Windows Step 8: Utilities Caution Due to enhanced security in Windows Vista, you cannot install MRI utilities if User Account Control (UAC) is turned on. If you are installing MRI from a computer running Windows Vista, you must temporarily turn off UAC from User Accounts in Control Panel. Once you complete the installation process, you can turn UAC back on. To complete Step 8 of the installation process: 1. Click the Utilities button to display the Install Utilities screen (Figure 2-10). Figure Install Utilities Screen 44 Step 8: Utilities

45 Chapter 2: Installing MRI for Windows 2. If the status indicates the required utilities are not installed, you must install them on the computer from which you are installing MRI before you can proceed with the installation process. Click Install to install the required utilities. 3. Once the status indicates the utilities are installed, proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. Step 9: MRILogin The MRILogin program is used to log on to MRI for Windows. To enable network workstations to register and install MRILogin, you must the install the network image of MRILogin on a network share path. Also, MRI requires the program to be installed in a folder named MRICMN. If you do not specify the folder name in your installation path, the system automatically appends it. For more information about installing MRILogin on network workstations, refer to Chapter 3, Setting Up Workstations. Note: MRI 4.0 can be installed as a stand-alone installation or side-by-side with any previous version of MRI. If you install MRI 4.0 side-by-side with a previous version, the system installs 4.0 in its own directory inside the existing MRICMN folder. To complete Step 9 of the installation process: 1. Click the MRILogin button to display the Install MRILogin Network Image screen (Figure 2-11). Note: Your installation CD contains the latest version of MRILogin, which might be a later version than the one shown in the following figures. Step 9: MRILogin 45

46 Chapter 2: Installing MRI for Windows Figure Install MRILogin Network Image Screen 2. If the status indicates the required version of MRILogin is not installed, use the information in the following table to specify an installation path. To ensure all workstations can access the network image of MRILogin, IRES recommends you specify a network share path using the format \\Server_name\Share_name. 46 Step 9: MRILogin

47 Chapter 2: Installing MRI for Windows Note: MRILogin must be installed in a folder named MRICMN. If you do not include the MRICMN folder at the end of your installation path, the system will automatically append it. To... install MRILogin for the first time or to specify a new location for the latest version of MRILogin update an existing version of MRILogin with the latest version Then... Click the Change link to browse to the location where you want to create the MRICMN folder in which MRILogin will be installed, and then proceed to Step 3 to continue. The system may detect your existing installation of MRILogin. If the path shown for the MRICMN location is correct, proceed to Step 3 to continue not correct or not shown, click the Change link to browse to the MRICMN folder in which to update the existing version of MRILogin. 3. Click Install to launch the MRILogin Setup Wizard. Step 9: MRILogin 47

48 Chapter 2: Installing MRI for Windows 4. On the Welcome dialog box (Figure 2-1) for the MRILogin Setup Wizard, click Next. Figure Welcome Dialog Box for the MRILogin Setup Wizard 48 Step 9: MRILogin

49 Chapter 2: Installing MRI for Windows 5. On the Network Location dialog box (Figure 2-13), verify the network share path for the network image of MRILogin. To change the path, click Browse, and then select a new location. When you are satisfied with the installation path, click Next. Figure Network Location Dialog Box Step 9: MRILogin 49

50 Chapter 2: Installing MRI for Windows 6. On the Ready to Install dialog box (Figure 2-14), click Install. Figure Ready to Install Dialog Box 50 Step 9: MRILogin

51 Chapter 2: Installing MRI for Windows The Installing MRILogin dialog box (Figure 2-15) displays the status of the installation process. Figure Installing MRILogin Dialog Box Step 9: MRILogin 51

52 Chapter 2: Installing MRI for Windows 7. On the Completing the MRILogin Setup Wizard dialog box (Figure 2-16), click Finish. Figure Completing the MRILogin Setup Wizard Dialog Box 8. Once the status on the Install MRILogin Network Image screen indicates the required version of MRILogin is installed, proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. 52 Step 9: MRILogin

53 Chapter 2: Installing MRI for Windows Step 10: System Database Maintenance The MRI system database (MRISystem) stores general information about your MRI installation, such as users, licensed applications, and security information. You must store the system database on a supported version of Microsoft SQL Server. Caution MRI no longer supports Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) or SQL Server 7.0. For more information about supported versions of SQL Server, refer to Chapter 1, Preparing Your System. The type of system database maintenance required to complete Step 10 of the installation process depends on whether or not you have an existing MRI installation. If you are installing MRI as... a new installation an update to an existing installation Then... You must create a new system database. The system creates the MRI system database in the MRICMN folder you specified when installing the MRILogin program. Proceed to Creating the MRI System Database on page 54. You must upgrade your system database. The system determines the location of your existing MRI system database using the MRICMN location you specified when installing the MRILogin program. Proceed to Upgrading the MRI System Database on page 56. Step 10: System Database Maintenance 53

54 Creating the MRI System Database Caution If you are not using the system administrator (sa) user name, you must assign the SQL login to the default MRISystem database with public/ db_owner permissions. To complete Step 10 of the installation process: 1. Click the System Database Maintenance button to display the Create the MRI System Database screen (Figure 2-17). Figure Create the MRI System Database Screen 2. If the status indicates the system database has not been created, click Create.

55 Chapter 2: Installing MRI for Windows 3. On the Create System Database dialog box (Figure 2-18), type the name, login, and password for the SQL Server on which you are hosting MRI databases, and then click OK. Note: Although you can change the name of the MRI system database, IRES recommends you use the default name MRISystem. Figure Create System Database Dialog Box 4. When a message appears indicating the system database structures have been refreshed, click OK. Note: If you are installing MRI for Windows from a network and you receive an ADO security warning, you can click OK. The warning appears because of a security setting in Microsoft Internet Explorer that requires prompting when you access data sources across domains. If you install MRI for Windows from the installation CD, the warning does not appear. 5. Once the status on the screen indicates the system database has been created, proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. Step 10: System Database Maintenance 55

56 Chapter 2: Installing MRI for Windows Upgrading the MRI System Database To complete Step 10 of the installation process: 1. Click the System Database Maintenance button to display the Upgrade the MRI System Database screen (Figure 2-19). Figure Upgrade the MRI System Database Screen 2. If the status indicates the system database requires an upgrade, click Upgrade. 3. When a message appears indicating the system database structures have been refreshed, click OK. 4. Once the status on the screen indicates the system database has been upgraded, proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. 56 Step 10: System Database Maintenance

57 Chapter 2: Installing MRI for Windows Step 11: MRI License Your MRI license (Sysinfo.lst) determines the MRI applications you can install. You must apply an MRI license file during the installation process if you are installing MRI for the first time adding a new application to an existing MRI installation To complete Step 11 of the installation process: 1. Click the MRI License button to display the Apply MRI License screen (Figure 2-20). Figure Apply MRI LIcense Screen Step 11: MRI License 57

58 Chapter 2: Installing MRI for Windows 2. Use the information in the following table to continue. If you are... installing MRI for the first time or adding a new application to an existing MRI installation you are updating an existing installation of MRI and your license has not changed Then... Click Apply License, and then go to Step 3 to continue. Click Skip, and then proceed to Step 12: MRI for Windows on page Verify where the license file (Sysinfo.lst) is located on your computer. or Insert the license disk into your disk drive. 4. Use the information in the following table to continue. If the license file is... stored in a folder on your computer or network on the disk in your disk drive Then the... Browse for Folder dialog box appears. a. Select the folder where the license file is stored, and then click OK to display the License Information dialog box (Figure 2-21). b. Go to Step 5 to continue. License Information dialog box appears (Figure 2-21). Go to Step 5 to continue. 58 Step 11: MRI License

59 Chapter 2: Installing MRI for Windows Figure License Information Dialog Box 5. Verify the license information. Caution If your current client ID does not match the client ID on the License Information dialog box, contact Order Fulfillment at (800) or before applying the license. 6. Click Apply Licenses to display the MRI Unlock dialog box (Figure 2-22). Step 11: MRI License 59

60 Chapter 2: Installing MRI for Windows Figure MRI Unlock Dialog Box 7. Use the information in the following table to obtain an unlock key. To obtain an unlock key via... You need to... phone Call PC Client Services at (800) fax Internet Fax the Key 1 code to PC Client Services at (888) a. Go to b. Log on to the ClientSite, as described in the System Administration manual. c. Under Support, click Product Unlock. d. Use the Product Unlock page to obtain an unlock key. 8. On the MRI Unlock dialog box, enter the unlock key in the Key 2 field, and then click OK. Caution If you exit the installation process before you enter the unlock key, the system will require you to obtain a new unlock key when you resume the installation process. 9. When a message appears confirming the license was successfully applied, click OK to return to the License Information dialog box. 60 Step 11: MRI License

61 Chapter 2: Installing MRI for Windows 10. To apply another license, click Read Another License, and then repeat Steps 3 through Click Close. 12. Once the status on the screen indicates the license has been applied, proceed to Step 12: MRI for Windows below. Step 12: MRI for Windows The final step of the MRI for Windows installation process is to create the network image of your MRI for Windows applications. The system stores the application files in a subdirectory under the MRICMN folder at the location you specified in Step 9: MRILogin on page 45. To complete Step 12 of the installation process: 1. Click the MRI for Windows button to display the Install Network Image of MRI for Windows screen (Figure 2-23). Figure Install Network Image of MRI for Windows Screen Step 12: MRI for Windows 61

62 2. Click Install to display the MRI for Windows License Agreement dialog box (Figure 2-24). Figure MRI for Windows License Agreement Dialog Box 3. Review the license agreement, and then click I Accept to display the Install Programs dialog box (Figure 2-25).

63 Chapter 2: Installing MRI for Windows Figure Install Programs Dialog Box 4. Review the installation path and the applications to be installed. To change the installation path of MRI programs, click the Browse button. By default, the system adds a new folder, 4.0.0, to the MRICMN folder or the folder you specified for the installation path. If you use the same installation path used for an existing installation of MRI 3.0, the system adds the folder next to the folder. exclude an application from being installed, clear the check box next to the application name. By default, all licensed applications are installed. However, some licensed submodules, such as CM LockBox, may not appear in the list of applications because the main application, Commercial Management, contains all of the necessary installation files. 5. Click Continue to display the Installation Progress dialog box (Figure 2-26). Step 12: MRI for Windows 63

64 Chapter 2: Installing MRI for Windows. Figure Installation Progress Dialog Box 6. When all the licensed applications are installed and a message appears indicating the network image of MRI for Windows was successfully installed, click OK. 7. Once the status on the screen indicates MRI for Windows has been installed, click the Back arrow in the upper-left corner of the screen to return to the Welcome screen. 8. To install MRI for the Web, refer to the Installation Guide for MRI for the Web 4.0 install additional supportive software, proceed to Chapter 3, Installing Additional Software set up network workstations to run MRI for Windows, proceed to Chapter 5, Setting Up Workstations 64 Step 12: MRI for Windows

65 Installing Additional Software 3 In This Chapter This chapter describes how to install additional software to be used with MRI. Before You Begin Close any open applications. Getting Started Installing Report Viewer Installing MRI External Web Services.. 71 Step 1: Microsoft Windows Components Step 2:.NET Framework Step 3: Install External Web Service Relay Installing MRI API External Web Services Step 1: Microsoft Windows Components Step 2:.NET Framework Step 3: Install External Web Service Relay MRI for Windows Installation Guide 65

66 Chapter 3: Installing Additional Software Getting Started To begin the installation process for additional supportive software: 1. Insert the second MRI installation CD into your CD-ROM drive. If your system is... Set to autorun CDs Not set to autorun CDs Then... The Additional Software and MRI Web User Assistance screen (Figure 3-1) appears. Go to Step 2 to continue. a. Click the Windows Start menu, and then click Run. b. Type X:setup.exe where X is the letter of your CD- ROM drive, and then click OK. The Additional Software and MRI Web User Assistance screen (Figure 3-1) appears. c. Go to Step 2 to continue. Figure 3-1. Additional Software and MRI Web User Assistance Screen 66 Getting Started

67 Chapter 3: Installing Additional Software 2. Use the information in the following table to continue. To install... MRI Web User Assistance Microsoft SQL Server 2005 Express (SQL Server Express) Microsoft SQL Server Management Studio Express (SSMSE) MRI Report Viewer MRI External Web Services MRI API External Web Services Then... Refer to the Installation Guide for MRI for the Web for instructions on installing MRI for the Web user assistance. To enable users to access online Help, Adobe Flash demonstrations, and user guides from the Help menu within MRI for the Web, you must complete the MRI Web User Assistance installation after you install MRI for the Web. If you are upgrading from Microsoft SQL Server Desktop Engine (MSDE 2000), refer to the requirements and recommendations in Chapter 1, Preparing Your System. To install SQL Server Express, click Install to launch the Microsoft installation program. For more information about installing SQL Server Express, refer to the Microsoft Web site. Note: SQL Server Express requires you to install Microsoft Windows Installer 3.1 on your database server. Click Install to launch the Microsoft installation program. For more information about installing SSMSE, refer to the Microsoft Web site. Proceed to Installing Report Viewer on page 68. Proceed to Installing MRI External Web Services on page 71. Proceed to Installing MRI API External Web Services on page 79. Getting Started 67

68 Chapter 3: Installing Additional Software Installing Report Viewer To view MRI reports sent through , you must use the Report Viewer program. Report Viewer can only display, not send, reports. For more information about how to use Report Viewer, refer to the Basics documentation. Because the Report Viewer program is part of the main MRI for Windows installation, you only need to install Report Viewer when you want to use it on a computer that does not have MRI for Windows installed. Before installing Report Viewer, use Add/Remove Programs in Control Panel to remove any existing installations of Report Viewer on your computer. To install the Report Viewer program: 1. On the Additional Software and MRI Web User Assistance screen (Figure 3-1), click Install to the right of MRI Report Viewer to launch the MRI Report Viewer Setup Wizard. 2. On the Welcome dialog box (Figure 3-2) for the MRI Report Viewer Setup Wizard, click Next. Figure 3-2. Welcome Dialog Box for the MRI Report Viewer Setup Wizard 68 Installing Report Viewer

69 Chapter 3: Installing Additional Software 3. On the Select Installation Folder dialog box, review the installation path. To change the installation path, click Browse and select a new path. When you are satisfied with the installation path, click Next. Tip To verify whether or not you have enough available disk space to install Report Viewer, click Disk Cost. Figure 3-3. Select Installation Folder Dialog Box Installing Report Viewer 69

70 Chapter 3: Installing Additional Software 4. On the Confirm Installation dialog box (Figure 3-4), click Next. Figure 3-4. Confirm Installation Dialog Box 5. When the installation is complete and the Installation Complete dialog box (Figure 3-5) appears, click Close. Figure 3-5. Installation Complete Dialog Box 70 Installing Report Viewer

71 Chapter 3: Installing Additional Software Installing MRI External Web Services MRI external Web services enables your organization to safely relay information to and from a Web server outside your system s firewall to one or more Web servers inside the firewall. This allows your organization to take advantage of applications that use and update your secure system s information. Example Intuit Real Estate Solutions offers Resident Portal to its MRI Residential Clients. The application can update resident information, allow residents to make service requests, and interact with your secure system in many ways. Installing external Web services on a Web server outside your organization s firewall makes that possible. To install MRI external Web services: 1. On the Additional Software and MRI Web User Assistance screen (Figure 3-1), click Install to the right of MRI External Web Services to display the installation interface (Figure 3-6), which will guide you through the installation process. The three numbered buttons on the left of the installation interface represent the steps required to install MRI external Web services. While you can click any numbered step to review the installation requirements, you must perform each step in the order listed. A check mark indicates which steps have been completed. For example, in Figure 3-6, Steps 1 and 2 have been completed, and Step 3 is the next required step. Installing MRI External Web Services 71

72 Chapter 3: Installing Additional Software Next required step Figure 3-6. Installation Steps 2. Proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. 72 Installing MRI External Web Services

73 Chapter 3: Installing Additional Software Step 1: Microsoft Windows Components To complete Step 1 one of the installation process: 1. Click the Microsoft Windows Components button to display the Microsoft Windows Components screen. 2. If the status indicates you need to install Microsoft Windows Components, on the Windows Start menu, go to Settings > Control Panel > Add/Remove Programs. 3. Click Add/Remove Windows Components and use the Windows Components Wizard to select and install IIS. You may need the installation CD for your operating system to complete the installation. 4. Once the status indicates the required components are installed, proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. Step 2:.NET Framework Microsoft.NET Framework configures your server to run the software necessary for it to use MRI for the Web. Warning You must install Microsoft Internet Information Services (IIS) before you install Microsoft.NET Framework. If you have installed.net Framework before installing IIS, you will need to uninstall.net Framework, install IIS, and reinstall.net Framework. To complete Step 2 of the installation process: 1. Click the.net Framework button to display the.net Framework 2.0 screen. 2. If the status indicates.net Framework 2.0 is not installed, click Install to launch the Microsoft installation program. For more information about installing.net Framework 2.0, refer to the Microsoft Web site. 3. Once the status indicates.net Framework 2.0 is installed, proceed to Step 3: Install External Web Service Relay on page 74. Installing MRI External Web Services 73

74 Chapter 3: Installing Additional Software Step 3: Install External Web Service Relay To complete Step 3 of the installation process: 1. Click the Install External Web Service Relay button to display the Install MRI External Web Service Relay screen. 2. On the installation screen click Install to display the Welcome dialog box. Figure 3-7. Welcome Dialog Box 3. Click Next to display the License Agreement dialog box (Figure 3-8). 74 Installing MRI External Web Services

75 Chapter 3: Installing Additional Software Figure 3-8. License Agreement Dialog Box 4. After reviewing the license agreement, click the I Accept the terms of the license agreement option button, and then click Next to display the Customer Information dialog box (Figure 3-9). Figure 3-9. Customer Information Dialog Box Installing MRI External Web Services 75

76 Chapter 3: Installing Additional Software 5. Complete the fields on the Customer Information dialog box, and then click Next to display the Setup Type dialog box (Figure 3-10). Figure Setup Type Dialog Box 6. To change the default installation path or check the disk space requirements, click the Custom option button. Otherwise, click the Complete option button. 7. Click Next to display the IIS Configuration Settings dialog box (Figure 3-11). 76 Installing MRI External Web Services

77 Chapter 3: Installing Additional Software Figure IIS Configuration Settings Dialog Box 8. Select the Web site where the virtual directory for the external Web services will be created and accessed. 9. Type the URL to the MRI internal Web server used for Web services. If the page wsmriops.asmx is not listed as a default page, then you must include it at the end of the URL. Example Name/MRIWeb/MRIWebService/wsMRIOps.asmx 10. Type the number of the port through which the communication will take place. 11. Click Next to display the Ready to Install dialog box (Figure 3-12). Installing MRI External Web Services 77

78 Chapter 3: Installing Additional Software Figure Ready to Install Dialog Box 12. Click Install. 13. When the InstallShield Wizard Completed dialog box (Figure 3-13) appears, click Finish. Figure InstallShield Wizard Completed Dialog Box 78 Installing MRI External Web Services

79 Chapter 3: Installing Additional Software Installing MRI API External Web Services MRI API External Web Services enables your organization to safely relay information to and from a Web server outside your system s firewall to one or more Web servers inside the firewall. This allows your organization to take advantage of applications that use and update your secure system s information. Example Intuit Real Estate Solutions offers application interfaces for key processes in Accounts Payable and General Ledger to enable you to integrate MRI with third-party financial vendors. Installing MRI API external Web services on a Web server outside your organization s firewall makes that possible. To install MRI API external Web services: 1. On the Additional Software and MRI Web User Assistance screen (Figure 3-1), click Install to the right of MRI API External Web Services to display the installation interface (Figure 3-14), which will guide you through the installation process. The three numbered buttons on the left of the installation interface represent the steps required to install MRI external Web services. While you can click any numbered step to review the installation requirements, you must perform each step in the order listed. A check mark indicates which steps have been completed. For example, in Figure 3-14, Steps 1 and 2 have been completed, and Step 3 is the next required step. Installing MRI API External Web Services 79

80 Chapter 3: Installing Additional Software Next required step Figure Installation Steps 2. Proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. 80 Installing MRI API External Web Services

81 Chapter 3: Installing Additional Software Step 1: Microsoft Windows Components To complete Step 1 one of the installation process: 1. Click the Microsoft Windows Components button to display the Microsoft Windows Components screen. 2. If the status indicates you need to install Microsoft Windows Components, on the Windows Start menu, go to Settings > Control Panel > Add/Remove Programs. 3. Click Add/Remove Windows Components and use the Windows Components Wizard to select and install IIS. You may need the installation CD for your operating system to complete the installation. 4. Once the status indicates the required components are installed, proceed to the next required installation step, as indicated by the check marks on the left side of your installation screen. Step 2:.NET Framework Microsoft.NET Framework configures your server to run the software necessary for it to use MRI for the Web. Warning You must install Microsoft Internet Information Services (IIS) before you install Microsoft.NET Framework. If you have installed.net Framework before installing IIS, you will need to uninstall.net Framework, install IIS, and reinstall.net Framework. To complete Step 2 of the installation process: 1. Click the.net Framework button to display the.net Framework 2.0 screen. 2. If the status indicates.net Framework 2.0 is not installed, click Install to launch the Microsoft installation program. For more information about installing.net Framework 2.0, refer to the Microsoft Web site. 3. Once the status indicates.net Framework 2.0 is installed, proceed to Step 3: Install External Web Service Relay on page 82. Installing MRI API External Web Services 81

82 Chapter 3: Installing Additional Software Step 3: Install External Web Service Relay To complete Step 3 of the installation process: 1. Click the Install External Web Service Relay button to display the Install MRI External Web Service Relay screen. 2. On the installation screen click Install to display the Welcome dialog box (Figure 3-15). Figure Welcome Dialog Box 3. Click Next to display the License Agreement dialog box (Figure 3-16). 82 Installing MRI API External Web Services

83 Chapter 3: Installing Additional Software Figure License Agreement Dialog Box 4. After reviewing the license agreement, click the I Accept the terms of the license agreement option button, and then click Next to display the Customer Information dialog box (Figure 3-17). Figure Customer Information Dialog Box Installing MRI API External Web Services 83

84 Chapter 3: Installing Additional Software 5. Complete the fields on the Customer Information dialog box, and then click Next to display the Setup Type dialog box (Figure 3-18). Figure Setup Type Dialog Box 6. To change the default installation path or check the disk space requirements, click the Custom option button. Otherwise, click the Complete option button. 7. Click Next to display the IIS Configuration Settings dialog box (Figure 3-19). 84 Installing MRI API External Web Services

85 Chapter 3: Installing Additional Software Figure IIS Configuration Settings Dialog Box 8. Select the Web site where the virtual directory for the external Web services will be created and accessed. 9. Type the URL to the MRI internal Web server used for API Web services. If the page APIService.asmx is not listed as a default page, then you must include it at the end of the URL. Example Name/MRIWeb/IRESAPIServices/APIService.asmx 10. Type the number of the port through which the communication will take place. 11. Click Next to display the Ready to Install dialog box (Figure 3-20). Installing MRI API External Web Services 85

86 Chapter 3: Installing Additional Software 12. Click Install. Figure Ready to Install Dialog Box 13. When the InstallShield Wizard Completed dialog box (Figure 3-21) appears, click Finish. Figure InstallShield Wizard Completed Dialog Box 86 Installing MRI API External Web Services

87 Adding New 4 Applications In This Chapter This chapter describes how to add new applications to your existing installation of MRI. Before You Begin Close any open applications Make sure all users are logged off of MRI Back up your databases, including all application databases and the system database (MRISystem) Have your MRI license disk or license file (Sysinfo.lst) available Overview Getting Started Upgrading Your System Database Applying Your New MRI License Installing New Applications MRI for Windows Installation Guide 87

88 Chapter 4: Adding New Applications Overview When you purchase a new application to add to your existing installation of MRI, you receive a new license file from Intuit Real Estate Solutions (IRES) to enable you to install the new application from your installation CD. The process of adding a new application to an existing installation of MRI typically consists of the following steps. However, if the installation program does not detect the required components on your system, you may be required to complete additional installation steps. 1. Upgrade your MRI system database, as described in Upgrading Your System Database on page Apply the new MRI license file you received from IRES, as described in Applying Your New MRI License on page 92. Note: You can apply a new license file from the MRI installation CD or from within the security console, as described in the System Administration manual. This chapter documents how to apply a license from the MRI installation CD. 3. Install the new licensed applications from the MRI installation CD, as described in Installing New Applications on page Log on to MRI for Windows and run Workstation Setup, as described in Chapter 5, Setting Up Workstations. 5. Upgrade each database in which to include the new application, as described Chapter 7, Upgrading Databases. 88 Overview

89 Chapter 4: Adding New Applications Getting Started To begin the installation process: 1. Insert the installation CD into your CD-ROM drive. If your system is... Set to autorun CDs Not set to autorun CDs Then... The Welcome screen (Figure 4-1) appears. Go to Step 2 to continue. a. Click the Windows Start menu, and then click Run. b. Type X:setup.exe where X is the letter of your CD-ROM drive, and then click OK. The Welcome screen (Figure 4-1) appears. c. Go to Step 2 to continue. Figure 4-1. Welcome Screen Getting Started 89

90 Chapter 4: Adding New Applications 2. Click the Next button to the right of Install MRI for Windows 4.0 to display the installation screen (Figure 4-2), which will guide you through the installation process. Because you are adding applications to an existing installation of MRI, the first nine steps of the installation process are typically complete with Step 10 being the next required step, as shown in Figure 4-2. However, if the installation program does not detect the required components on your system, you may be required to complete additional installation steps. Next required step Figure 4-2. Installation Steps 3. Review the check marks on the left side of your installation screen to determine the steps you are required to complete. If Steps 1 through 9 are complete, proceed to Upgrading Your System Database on page 91 to continue are not complete, refer to Chapter 2, Installing MRI for Windows to complete the required steps 90 Getting Started

91 Chapter 4: Adding New Applications Upgrading Your System Database To upgrade your system database: 1. Click the System Database Maintenance button to display the Upgrade the MRI System Database screen (Figure 4-3). Figure 4-3. Upgrade the MRI System Database Screen 2. Click Upgrade. 3. When a message appears indicating the system database structures have been refreshed, click OK. 4. Once the status on the screen indicates the system database has been upgraded, proceed to Applying Your New MRI License on page 92. Upgrading Your System Database 91

92 Chapter 4: Adding New Applications Applying Your New MRI License To apply your new MRI license: 1. On the installation screen, click the MRI License button to display the Apply MRI License screen (Figure 4-4). Figure 4-4. Apply MRI LIcense Screen 2. Click Apply License. 3. Verify where the license file (Sysinfo.lst) is located on your computer. or Insert the license disk into your disk drive. 92 Applying Your New MRI License

93 Chapter 4: Adding New Applications 4. Use the information in the following table to continue. If the license file is... stored in a folder on your computer or network on the disk in your disk drive Then the... Browse for Folder dialog box appears. a. Select the folder where the license file is stored, and then click OK to display the License Information dialog box (Figure 4-5). b. Go to Step 5 to continue. License Information dialog box appears (Figure 4-5). Go to Step 5 to continue. Figure 4-5. License Information Dialog Box Applying Your New MRI License 93

94 Chapter 4: Adding New Applications 5. Verify the license information. Caution If your current client ID does not match the client ID on the License Information dialog box, contact Order Fulfillment at (800) or before applying the license. 6. Click Apply Licenses to display the MRI Unlock dialog box (Figure 4-6). Figure 4-6. MRI Unlock Dialog Box 7. Use the information in the following table to obtain an unlock key. To obtain an unlock key via... You need to... phone Call PC Client Services at (800) fax Internet Fax the Key 1 code to PC Client Services at (888) a. Go to b. Log on to the ClientSite, as described in the System Administration manual. c. Under Support, click Product Unlock. d. Use the Product Unlock page to obtain an unlock key. 94 Applying Your New MRI License

95 Chapter 4: Adding New Applications 8. On the MRI Unlock dialog box, enter the unlock key in the Key 2 field, and then click OK. Caution If you exit the installation process before you enter the unlock key, the system will require you to obtain a new unlock key when you resume the installation process. 9. When a message appears confirming the license was successfully applied, click OK to return to the License Information dialog box. 10. To apply another license, click Read Another License, and then repeat Steps 3 through Click Close. 12. Once the status on the screen indicates the license has been applied, proceed to Installing New Applications below. Applying Your New MRI License 95

96 Chapter 4: Adding New Applications Installing New Applications To install a new application: 1. On the installation screen, click the MRI for Windows button to display the Install Network Image of MRI for Windows screen (Figure 4-7). Figure 4-7. Install Network Image of MRI for Windows Screen 2. Click Install to display the MRI for Windows License Agreement dialog box (Figure 4-8). 96 Installing New Applications

97 Chapter 4: Adding New Applications Figure 4-8. MRI for Windows License Agreement Dialog Box 3. Review the license agreement, and then click I Accept to display the Install Programs dialog box (Figure 4-9). Installing New Applications 97

98 Chapter 4: Adding New Applications Figure 4-9. Install Programs Dialog Box 4. Verify the Location to Install MRI for Windows field displays the path of your existing installation. To select the path of your existing installation, click the Ellipse button. 5. In the list of applications to install, clear the check box next to your currently installed applications and select the check box next to each new application to install. By default, the system selects all licensed applications, including the applications you already have installed. 6. Click Continue to display the Installation Progress dialog box (Figure 4-10). 98 Installing New Applications

99 Chapter 4: Adding New Applications. Figure Installation Progress Dialog Box 7. When the new applications are installed and a message appears indicating the network image of MRI for Windows was successfully installed, click OK. 8. To complete the process of adding the new application, you must run Workstation Setup on each network workstation, as described in Chapter 5, Setting Up Workstations upgrade each database in which to include the application, as described in Chapter 7, Upgrading Databases Installing New Applications 99

100

101 Setting Up 5 Workstations In This Chapter This chapter describes how to install the MRILogin program and run Workstation Setup on network workstations. Installing MRILogin on Network Workstations Running Workstation Setup Before You Begin Know the network share path where the MRICMN folder was created during the MRI for Windows installation process. Make sure each workstation meets the system requirements specified in Chapter 1, Preparing Your System MRI for Windows Installation Guide 101

102 Chapter 5: Setting Up Workstations Installing MRILogin on Network Workstations To enable network workstations to log on to MRI for Windows, you must install the MRILogin program locally on each workstation by accessing the MRILogin network image from each workstation. The MRILogin network image is stored in the MRICMN folder on the network share path you specified during the installation process. To install the MRILogin program on a network workstation: 1. From the network workstation, open the MRICMN folder on the network share path, and then double-click Setup.exe to launch the MRILogin Setup Wizard. or If you are on a terminal server, browse to the MRICMN folder and double-click Setup.exe from within Add or Remove Programs in Control Panel. Note: To install MRILogin on a terminal server, you must be logged on as an administrator. 2. On the Welcome dialog box (Figure 5-1), click Next. 102 Installing MRILogin on Network Workstations

103 Chapter 5: Setting Up Workstations Figure 5-1. MRILogin Setup Wizard Dialog Box 3. On the MRILogin License Agreement dialog box, read the terms of the license agreement, and then click the I accept the terms in the License Agreement option button. Installing MRILogin on Network Workstations 103

104 Chapter 5: Setting Up Workstations Figure 5-2. MRILogin License Agreement Dialog Box 4. Click Next. 104 Installing MRILogin on Network Workstations

105 Chapter 5: Setting Up Workstations 5. On the Select Installation Folder dialog box (Figure 5-3), review the installation path for the local installation of MRILogin. To change the installation path, click Browse. When you are satisfied with the installation path, click Next. Tip To verify whether or not you have enough available disk space to install MRILogin, click Disk Cost. Figure 5-3. Select Installation Folder Dialog Box Installing MRILogin on Network Workstations 105

106 Chapter 5: Setting Up Workstations 6. On the Ready to Install dialog box (Figure 5-4), click Install. Figure 5-4. Ready to Install Dialog Box 106 Installing MRILogin on Network Workstations

107 Chapter 5: Setting Up Workstations The Installing MRILogin dialog box (Figure 5-5) displays the status of the installation process. Figure 5-5. Installing MRILogin Dialog Box Installing MRILogin on Network Workstations 107

108 Chapter 5: Setting Up Workstations 7. On the Completing the MRILogin Setup Wizard dialog box (Figure 5-6), click Finish. Figure 5-6. Completing the MRILogin Setup Wizard Dialog Box 108 Installing MRILogin on Network Workstations

109 Chapter 5: Setting Up Workstations Running Workstation Setup When you log on to MRI for Windows from any network workstation for the first time after installing MRI, upgrading MRI, adding a new application, or installing a hotfix, the system prompts you to run Workstation Setup. Before running, the Workstation Setup program checks to ensure the required software components are installed on the workstation and the correct Microsoft Distributed Transaction Coordinator (MSDTC) options are set. If any of the workstation requirements are not met, the program notifies you, and you must complete the required steps on the workstation before you can proceed. For more information about workstation requirements, refer to Chapter 1, Preparing Your System. Caution Due to enhanced security in Windows Vista, Workstation Setup will not run if User Account Control (UAC) is turned on. To run Workstation Setup on workstations running Windows Vista, you must temporarily turn off UAC from User Accounts in Control Panel before running Workstation Setup. Once you complete the Workstation Setup process, you can turn UAC back on. To run Workstation Setup on a network workstation: 1. On the Windows Start menu, go to Programs > MRI Real Estate Solutions > MRILogin to display the MRI for Windows Login dialog box (Figure 5-7). Note: The fields shown on the MRI for Windows Login dialog box depend on whether or not you have multiple client licenses. Single Client License Figure 5-7. MRI for Windows Login Dialog Box Multiple Client Licenses Running Workstation Setup 109

110 2. In the User Name field, type SYSADM. Note: This field is not case sensitive. 3. Use the information in the following table to complete the Password field. If you... have not yet established a password for the SYSADM user name have established a password for the SYSADM user name Note: If you installed MRI 4.0 next to a previous installation of MRI, you do not need to reestablish the SYSADM password unless you are using a new system database. Then... Leave the password blank. Type the password for the SYSADM user name. 4. If the Use Default DB check box appears on the MRI for Windows Login dialog box, clear the check box, so you can log on to MRI without opening a database. Note: For detailed information about logging on and selecting, creating, or upgrading databases, refer to the System Administration manual. 5. Click Login. If you typed a password in the Password field, the Database field appears on the MRI for Windows Login dialog box. Go to Step 9 to continue. left the Password field blank, a message indicating you must change your password appears. Click OK. 6. Click Change Password to display the Change Password dialog box (Figure 5-8).

111 Chapter 5: Setting Up Workstations Figure 5-8. Change Password Dialog Box 7. Use the information in the following table to complete the fields. Field Old Password New Password Confirm New Password Action Leave the old password blank. Type a password for the SYSADM user name. Retype the password for the SYSADM user name. 8. Click Save to return to the MRI for Windows Login dialog box. 9. In the Database field, select Executable Version as shown in Figure 5-9. Figure 5-9. MRI Login Dialog Box With Database Field 10. Click Go MRI. Running Workstation Setup 111

112 Chapter 5: Setting Up Workstations 11. When a message prompting you to run Workstation Setup appears (Figure 5-10), click OK. Figure Workstation Setup Message Caution Due to enhanced security in Windows Vista, Workstation Setup will not run if User Account Control (UAC) is turned on. To run Workstation Setup on workstations running Windows Vista, you must temporarily turn off UAC from User Accounts in Control Panel before running Workstation Setup. Once you complete the Workstation Setup process, you can turn UAC back on. 12. When the MRI for Windows dialog box (Figure 5-11) appears, click Continue. Figure MRI for Windows Dialog Box 13. If you receive a prompt requiring you to restart your computer, restart your computer. 14. When a message indicating the Workstation Setup process is complete appears, click OK. 112 Running Workstation Setup

113 Creating 6 Databases In This Chapter This chapter describes how to create an MRI database or create a link to an existing MRI database on a SQL Server. Creating New Databases Creating Links to Existing Databases Before You Begin Make sure you meet the system requirements specified in Chapter 1, Preparing Your System. know the system administrator (sa) login or login with system administrator rights for the SQL Server to host the new databases can log on to MRI as a system administrator or user with administrator rights with permission to create new databases. For more information, about assigning user rights, refer to the System Administration guide. MRI for Windows Installation Guide 113

114 Chapter 6: Creating Databases Creating New Databases Caution Before you create a new database, make sure you meet the system requirements specified Chapter 1, Preparing Your System. When you create an MRI database, the system creates the database on the SQL Server a link to access the database in MRI Note: To create the database on the SQL Server, MRI requires you specify a system administrator (sa) login or a login with system administrator rights for the SQL Server on the New Database dialog box (Figure ). During the database creation process, you determine the database name to appear in MRI and the database file name on the SQL Server initial size of the database and where to store database files By default, the system stores databases in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL folder. However, you can override the default location in either SQL Server Enterprise Manager Studio, SQL Server Management Studio Express, or during the database creation process on the New Database Options dialog box. whether or not the database will be Unicode, which enables the database to accommodate languages with more than 256 characters the licensed applications to include in the database The process of creating either a SQL Server 2000, SQL Server 2005, or SQL Server 2005 Express Edition database is the same. The type of database the system creates depends on the server name and instance you specify on the New Database dialog box. 114 Creating New Databases

115 Chapter 6: Creating Databases To create a new version 4.0 database: 1. On the Windows Start menu, go to Programs > MRI Real Estate Solutions > MRILogin. 2. On the MRI for Windows Login dialog box (Figure 6-1), log on with the SYSADM user name or as a system administrator with database creation rights, and then click Security Console. Figure 6-1. Security Console Button 3. On the File menu in the security console, click New Database. Note: You can also create a database from the File menu on the main view. However, if you maintain multiple database versions, make sure you are logged on to the 4.0 executable version. Creating New Databases 115

116 Chapter 6: Creating Databases 4. On the Select Database Version dialog box (Figure 6-2), click the 4.0 option button, and then click OK. Note: For information about creating new version 3.0 databases, refer to the System Administration guide for version 3.0. Figure 6-2. Select Database Version Dialog Box 5. Use the information in Table 6 1 to complete the fields on the New Database dialog box (Figure ). Figure 6 3. New Database Dialog Box 116 Creating New Databases

117 Chapter 6: Creating Databases Table 6 1. New Database Dialog Box Fields Field MRI Database Name Database Description Server Name (\Instance) Server Database Name Unicode Action Type the name to use for the database in MRI. The database name must be limited to 12 characters and cannot include spaces. Note: MRI Windows displays the name at the bottom of the main menu view, and MRI Web displays the name in the upper-right corner of the window. Type a description that enables you to locate the database easily in a list of multiple databases. Note: In MRI Windows, the database description appears on the title bar of most application views. Type the name and instance of the SQL Server on which to create the database using the following format: computer_name\instance_name Type the name to use for the database on the SQL Server. The database name must be limited to 12 characters and cannot include spaces. Otherwise, you will not be able to link to the database in MRI. Select to create a Unicode database rather than an ANSI database. A(n) Unicode database can accommodate languages with more than the standard ASCII 256-character set, such as Japanese and Arabic. ANSI database can only accommodate languages with up to 256 characters. Once you create a database in Unicode, you cannot convert the database to ANSI and vise versa. continued Creating New Databases 117

118 Chapter 6: Creating Databases Table 6 1. New Database Dialog Box Fields (Continued) Field Use Trusted Connection Database User ID Password Action Select to use Windows authentication instead of SQL Server authentication. Using SQL Server authentication requires you to use a SQL Server user ID and password to connect to the SQL Server Windows authentication, or a trusted connection, enables you to set access rights to SQL databases at the domain user level Type the system administrator (sa) login or a login with system administrator rights for the SQL Server. Type the password associated with the SQL Server login. 6. To change the default database file location or initial database size: a. Click Options to display the New Database Options dialog box (Figure 6-4). b. In the Location of database files field, type or browse to the path to store.mdf and.ldf database files. The path in this field overrides the default SQL Server path or any path you specified in SQL Server Enterprise Manager Studio or SQL Server Management Studio Express. Note: You can only browse to a location on your local machine. Otherwise, you must type the location. c. To set the initial size for your database to 200 MB, click the Large (200MB) option button. IRES recommends you use this option for large databases to optimize performance. d. Click OK. 118 Creating New Databases

119 Chapter 6: Creating Databases Figure 6-4. New Database Options Dialog Box 7. On the New Database dialog box, click Next. 8. On the New Database Applications dialog box (Figure 6-5), clear the check box next to any applications you do not want to install. By default, the system installs all applications for which you are licensed. Figure 6-5. New Database Applications Dialog Box Creating New Databases 119

120 Chapter 6: Creating Databases 9. To create the database, click Process. A status view (Figure 6-6) appears, which displays the status of the upgrade process. Figure 6-6. New Database Status View 10. When a message appears indicating whether the process was successful or unsuccessful, click OK. 120 Creating New Databases

121 Chapter 6: Creating Databases 11. To view the details of a message on the status view, double-click the message in the Message grid. clear or display the list of success, warning, or error messages, click the corresponding button at the top of the view. When a message button is active, as indicated by a white background, the system displays the corresponding messages in the grid inactive, as indicated by a gray background, the system clears the corresponding messages from the grid copy the messages appearing in the grid to your clipboard, click Report, and then click Copy Messages to Clipboard. 12. Click OK to close the status view. Creating New Databases 121

122 Chapter 6: Creating Databases Creating Links to Existing Databases If you have an existing MRI database on a SQL Server that you want to add to the database list in MRI, you must create a link from MRI to the database on the SQL Server. To create a link to an existing MRI database: 1. On the Windows Start menu, go to Programs > MRI Real Estate Solutions > MRILogin. 2. On the MRI for Windows Login dialog box (Figure 6-7), log on with the SYSADM user name or as a system administrator with database creation rights, and then click Security Console. Figure 6-7. Security Console Button 3. On the File menu in the security console, click New Database. Note: You can also create a link to an existing database from the File menu on the main view. However, if you maintain multiple database versions, make sure you are logged on to the 4.0 executable version of MRI. 122 Creating Links to Existing Databases

123 Chapter 6: Creating Databases 4. On the Select Database Version dialog box (Figure 6-8), click the 4.0 option button, and then click OK. Note: For information about creating links to version 3.0 databases, refer to the System Administration guide for version 3.0. Figure 6-8. Select Database Version Dialog Box 5. Use the information in Table 6 2 to complete the fields on the New Database dialog box (Figure 6-9). Figure 6-9. New Database Dialog Box Creating Links to Existing Databases 123

124 Chapter 6: Creating Databases Table 6 2. New Database Dialog Box Fields Field MRI Database Name Database Description Server Name (\Instance) Server Database Name Unicode Use Trusted Connection Database User ID Password Action Type the name to use for the database in MRI. The database name must be limited to 12 characters and cannot include spaces. Note: MRI Windows displays the name at the bottom of the main menu view, and MRI Web displays the name in the upper-right corner of the window. Type a description that enables you to locate the database easily in a list of multiple databases. Note: In MRI Windows, the database description appears on the title bar of most application views. Type the name and instance of the SQL Server on which the existing database is located using the following format: computer_name\instance_name Type the name of the database as it exists on the SQL Server. For the system to recognize the database on the SQL Server, the database name you specify in this field must be identical to the database name on the SQL Server. (Not applicable). Once a database has been created, you cannot convert the database from ANSI to Unicode or vice versa. Select to use Windows authentication instead of SQL Server authentication. Using SQL Server authentication requires you to use a SQL Server user ID and password to connect to the SQL Server Windows authentication, or a trusted connection, enables you to set access rights to SQL databases at the user level. Type a login for the SQL Server on which the database is located. Type the password associated with the SQL Server login. 124 Creating Links to Existing Databases

125 Chapter 6: Creating Databases 6. Click Next. 7. When a message appears prompting you to create a link to the database in MRI, click OK. The system creates the link and refreshes the database structures. Caution If the version of the database on the SQL Server is not already 4.0, the system automatically upgrades the database to 4.0. Before allowing the system to upgrade the database, you must ensure the database version is at 3.0 Service Pack 4a. A status view (Figure 6-10) appears, which displays the status of the process. Figure New Database Status View Creating Links to Existing Databases 125

126 Chapter 6: Creating Databases 8. When a message appears indicating whether the process was successful or unsuccessful, click OK. 9. To view the details of a message on the status view, double-click the message in the Message grid. clear or display the list of success, warning, or error messages, click the corresponding button at the top of the view. When a message button is active, as indicated by a white background, the system displays the corresponding messages in the grid inactive, as indicated by a gray background, the system clears the corresponding messages from the grid copy the messages appearing in the grid to your clipboard, click Report, and then click Copy Messages to Clipboard. 10. Click OK to close the status view. 126 Creating Links to Existing Databases

127 Upgrading 7 Databases In This Chapter This chapter describes how to upgrade databases to apply standard updates, new applications, or database customizations. Before You Begin Make sure you meet the system requirements specified in Chapter 1, Preparing Your System. Back up each database you plan to upgrade, including all application databases and the system database (MRISystem). If you use Audit Trail, back up field-level settings and disable Audit Trail. After you complete the database upgrade, restore the field-level settings. For more information, refer to the Audit Trail documentation. Make sure you can log on with the SYSADM user name and password or as a system administrator with upgrade database rights. For more information about assigning user rights, refer to the System Administration guide. Overview Understanding Upgrade Prompts Upgrading Databases from Version 3.0 to Moving Customizations from Version 3.0 to Upgrading Version 4.0 Databases Moving Customizations between Version 4.0 Databases Foreign Key Warnings Locating Records with Foreign Key Warnings Resolving Foreign Key Warnings Timeout Errors Increasing Application Timeout Increasing Machine Timeout Logging MRI for Windows Installation Guide 127

128 Chapter 7: Upgrading Databases Overview Upgrading a database is the process of changing the structure and content of a database to apply standard updates, new applications, or database customizations. During an upgrade, the system only upgrades database objects if they have changed since the last upgrade. However, you can refresh database objects that have not changed since the last upgrade or reapply an upgrade as needed. You can upgrade a database by selecting the Upgrade Database command on the File menu from either the main view or the security console view. The instructions in this chapter document how to perform an upgrade from within the security console. If you use multiple versions of MRI concurrently, keep the following considerations in mind: If you initiate the upgrade process from within the security console, you can select a version 3.0 database, and then choose whether to refresh or upgrade the 3.0 version of the database or upgrade the database to version 4.0. If you initiate the upgrade process from the main view, the system automatically detects the database or executable version you selected when you logged on and upgrades the database in the current version. For example, if you log on to the 4.0 executable version, and then select a 3.0 database to upgrade, the system prompts you to upgrade the database to version 4.0. The process of upgrading a 3.0 database is different than upgrading a 4.0 database. For information about upgrading 3.0 databases, refer to the System Administration guide for version Overview

129 Chapter 7: Upgrading Databases Understanding Upgrade Prompts Whenever you select a database that needs to be upgraded from either the MRI for Windows Login dialog box or the Select Database dialog box, an upgrade prompt appears. Depending on the extent of the changes, the prompt indicates whether an upgrade is recommended or required, as shown in Figure 7-1, and enables you to either proceed with the upgrade or cancel the upgrade. Upgrade Required Upgrade Recommended Figure 7-1. Upgrade Messages The information in the following table can help you determine how to proceed when an upgrade prompt appears. If you click... Upgrade Cancel Version Info Then... the system begins the upgrade process, as described in Upgrading Version 4.0 Databases on page 136. if the upgrade is required, the system prevents access to the database until you upgrade the database recommended, the system enables you to open the database without upgrading the database the system provides information about the MRI version. Overview 129

130 Chapter 7: Upgrading Databases Upgrading Databases from Version 3.0 to 4.0 Caution Before upgrading a database to version 4.0, you must ensure the current database version is 3.0 Service Pack 4a (SP4a). To verify the current database version, refer to Verifying Your Current Database Version on page 8. Back up each database you plan to upgrade, including all application databases and the system database (MRISystem). To upgrade a database from version 3.0 to 4.0: 1. On the Windows Start menu, go to Programs > MRI Real Estate Solutions > MRILogin. 2. On the MRI for Windows Login dialog box (Figure 7-2), log on with the SYSADM user name or as a system administrator with database upgrade rights, and then click Security Console. Figure 7-2. Security Console Button 3. On the left side of the security console view, click the Database tab, and then select a version 3.0 database to upgrade to version 4.0 in the drop-down list. 130 Upgrading Databases from Version 3.0 to 4.0

131 Chapter 7: Upgrading Databases 4. On the File menu, click Upgrade Database. 5. On the Select Database Version dialog box (Figure 7-3), click the Upgrade database to version 4.0 option button, and then click OK. Figure 7-3. Select Database Version Dialog Box 6. On the Confirm Current Database Version dialog box (Figure 7-4), select the check box to confirm the database is at version 3.0 SP4a and you have a current backup of the database. Note: For information about verifying the current version of the database, refer to Verifying Your Current Database Version on page 8. Figure 7-4. Confirm Current Database Version 7. When a message appears prompting you to indicate whether to upgrade to version 4.0 (Figure 7-5), click Yes to upgrade the database core and framework. Caution Once you click Yes, you cannot cancel the core and framework upgrade process. Upgrading Databases from Version 3.0 to

132 Chapter 7: Upgrading Databases Figure 7-5. Database Upgrade Required Message 8. When a message appears listing the applications to be upgraded to version 4.0 (Figure 7-6), review the list, and then click Yes to upgrade the applications. Caution IRES recommends you do not cancel the upgrade process. Figure 7-6. Upgrade Applications Message 132 Upgrading Databases from Version 3.0 to 4.0

133 Chapter 7: Upgrading Databases 9. When a message appears indicating whether the upgrade was successful or unsuccessful, click OK. Note: If the system returns any errors, the upgrade will fail. If the system returns any warnings, the upgrade is still successful, but there may be data-related issues to resolve. Caution If the system cannot recreate or apply a foreign key, warning messages occur. As of version 4.0, foreign key warnings do not cause an upgrade to fail. However, in subsequent versions of MRI, foreign key messages will be errors that will cause an upgrade to fail. Therefore, IRES recommends you resolve any foreign key warnings, as described in Foreign Key Warnings on page To view the details of a message on the status view, double-click the message in the Message grid. clear or display the list of success, warning, or error messages, click the corresponding button at the top of the view. When a message button is active, as indicated by a white background, the system displays the corresponding messages in the grid inactive, as indicated by a gray background, the system clears the corresponding messages from the grid copy the messages appearing in the grid to your clipboard, click Report, and then click Copy Messages to Clipboard. For more information about foreign key warnings, refer to Foreign Key Warnings on page Click OK to close the status view. Upgrading Databases from Version 3.0 to

134 Chapter 7: Upgrading Databases Moving Customizations from Version 3.0 to 4.0 You can use the following procedure to move customizations from a version 3.0 database to a version 4.0 database. To move customizations, you apply a Master Program Database (MPD) file created using the Update MPD program in version 3.0 to a version 4.0 database. For more information about creating an MPD file with customizations created in version 3.0, refer to the System Administration guide for version 3.0. Note: You can no longer create MPD files in version 4.0. Instead, you must create a custom cabinet to store database customizations, as described in Creating or Modifying Custom Cabinets on page 142. To apply a custom MPD file to a version 4.0 database: 1. On the Windows Start menu, go to Programs > MRI Real Estate Solutions > MRILogin. 2. On the MRI for Windows Login dialog box (Figure 7-7), log on with the SYSADM user name or as a system administrator with database upgrade rights, and then click Security Console. Figure 7-7. Security Console Button 3. On the left side of the security console view, click the Database tab, and then select the version 4.0 database to which to apply the custom MPD in the drop-down list. 134 Upgrading Databases from Version 3.0 to 4.0

135 Chapter 7: Upgrading Databases 4. On the File menu, click Apply Custom MPD. Note: You can also access the Apply Custom MPD command from the File menu on the main view in MRI for Windows after you select a database. 5. On the Custom MPD Upgrade dialog box (Figure 7-8), click the browse button to select the MPD file to apply. Figure 7-8. Custom MPD Upgrade Dialog Box 6. Click OK. 7. When a message appears indicating the database upgraded successfully, click OK. Upgrading Databases from Version 3.0 to

136 Chapter 7: Upgrading Databases Upgrading Version 4.0 Databases Caution Back up each database you plan to upgrade, including all application databases and the system database (MRISystem). If you are upgrading a database to apply a new application, you must first refresh your license to include the new application, as described in Chapter 4, Adding New Applications. Upgrading a database is required to apply service packs or hotfixes new applications To upgrade a version 4.0 database: 1. On the Windows Start menu, go to Programs > MRI Real Estate Solutions > MRILogin. 2. On the MRI for Windows Login dialog box (Figure 7-9), log on with the SYSADM user name or as a system administrator with database upgrade rights, and then click Security Console. Figure 7-9. Security Console Button 136 Upgrading Version 4.0 Databases

137 Chapter 7: Upgrading Databases 3. On the left side of the security console view, click the Database tab, and then select the version 4.0 database to upgrade in the drop-down list. 4. On the File menu, click Upgrade Database. 5. On the Upgrade Database Options dialog box (Figure 7-10), click the Upgrade Application Database option button. Figure Upgrade Database Options Dialog Box 6. Click OK. 7. On the Upgrade Database dialog box (Figure 7-11), select the applications to upgrade or any new applications to include in the database. The system automatically selects and places an asterisk (*) next to each application for which it detects an update. Caution The system does not automatically select newly installed applications. If you are upgrading a database after installing a new application, you must select the application on the Upgrade Database dialog box to include the application in the database. Upgrading Version 4.0 Databases 137

138 Chapter 7: Upgrading Databases Figure Upgrade Database Dialog Box 138 Upgrading Version 4.0 Databases

139 Chapter 7: Upgrading Databases 8. Click Process. A status view (Figure 7-12) appears, which displays the status of the upgrade process. Caution IRES recommends you do not cancel the upgrade process. Figure Upgrade Database Status View Upgrading Version 4.0 Databases 139

140 Chapter 7: Upgrading Databases 9. When a message appears indicating whether the upgrade was successful or unsuccessful, click OK. Note: If the system returns any errors, the upgrade will fail. If the system returns any warnings, the ugprade is still successful, but there may be data-related issues to resolve. Caution If the system cannot recreate or apply a foreign key, warning messages occur. As of version 4.0, foreign key warnings do not cause an upgrade to fail. However, in subsequent versions of MRI, foreign key messages will be errors and will cause an upgrade to fail. Therefore, IRES recommends you resolve any foreign key warnings, as described in Foreign Key Warnings on page To view the details of a message on the status view, double-click the message in the Message grid. clear or display the list of success, warning, or error messages, click the corresponding button at the top of the view. When a message button is active, as indicated by a white background, the system displays the corresponding messages in the grid inactive, as indicated by a gray background, the system clears the corresponding messages from the grid copy the messages appearing in the grid to your clipboard, click Report, and then click Copy Messages to Clipboard. For more information about foreign key warnings, refer to Foreign Key Warnings on page Click OK to close the status view. 140 Upgrading Version 4.0 Databases

141 Chapter 7: Upgrading Databases Moving Customizations between Version 4.0 Databases To move customizations from one version 4.0 database to another, you can use the Cabinet Maker utility. The Cabinet Maker utility packages MRI objects, such as data, reports, and other customizations, in a zipped cabinet file with an.izc file name extension, such as CMRPTS.izc. After creating a cabinet file with the Cabinet Maker utility, you can apply the cabinet to another version 4.0 database through the database upgrade process. You can also modify and reapply the cabinet file, as needed. Note: The Cabinet Maker utility is a replacement for the Update MPD program used in MRI version 3.0 and earlier. If your customizations are currently in an MPD file, you can apply the MPD to a version 4.0 database, as described in Moving Customizations from Version 3.0 to 4.0 on page 134. To... add customizations from a source database to a custom cabinet apply the custom cabinet to a destination database Proceed to... Creating or Modifying Custom Cabinets on page 142 Applying Custom Cabinets on page 147 Upgrading Version 4.0 Databases 141

142 Chapter 7: Upgrading Databases Creating or Modifying Custom Cabinets To create or modify a custom cabinet: 1. Log on to MRI for Windows and select the database that contains the customizations to include in the cabinet. 2. On the main view, click MRI Utilities, and then click Cabinet Maker. 3. On the Cabinet Location dialog box (Figure 7-13), type or select a full path and file name, including the.izc extension, for the custom cabinet, and then click OK. Caution Do not type or select an MRI-supplied cabinet name. Refer to the the \MRICMN\4.0.0\MRIWIN\Cabinet folder for a list of existing cabinet names. Figure Cabinet Location Dialog Box 4. On the left side of the Create/Modify Cabinet view (Figure 7-14), click an object type to display the associated objects in the Database grid. 5. To filter the list of database objects, select an application in the Application Filter list box. 142 Upgrading Version 4.0 Databases

143 Chapter 7: Upgrading Databases 6. To add objects to the cabinet, select the objects in the Database grid, and then click Copy to Cabinet or drag the objects from the Database grid to the Cabinet grid remove objects from the cabinet, select the objects in the Cabinet grid, and then click Remove from Cabinet or drag the objects from the Cabinet grid to the Database grid Notes: You can SHIFT-click to select a range of objects or CTRLclick to select multiple objects. When you select a report, the system also selects the Windows subview or Web activity group containing the associated report options. Figure Create/Modify Cabinet View Upgrading Version 4.0 Databases 143

144 Chapter 7: Upgrading Databases 7. To preview the objects in the new cabinet, click Preview Cabinet. 8. On the left side of the Preview Cabinet view (Figure 7-15), select an object type to display the associated objects in the Cabinet Objects grid. Figure Preview Cabinet View 9. Click OK to return to the Create/Modify Cabinet view, and repeat Step 4 through Step 8 as needed until you are ready to create the cabinet. 144 Upgrading Version 4.0 Databases

145 Chapter 7: Upgrading Databases 10. To create the cabinet, click Process. A status view (Figure 7-16) appears, which displays the status of the process. Figure Create/Modify Cabinet Status View 11. When a message appears indicating whether the cabinet creation was successful or unsuccessful, click OK. Upgrading Version 4.0 Databases 145

146 Chapter 7: Upgrading Databases 12. To view the details of a message on the status view, double-click the message in the Message grid. clear or display the list of success, warning, or error messages, click the corresponding button at the top of the view. When a message button is active, as indicated by a white background, the system displays the corresponding messages in the grid inactive, as indicated by a gray background, the system clears the corresponding messages from the grid copy the messages appearing in the grid to your clipboard, click Report, and then click Copy Messages to Clipboard. 13. Click OK to close the status view. 146 Upgrading Version 4.0 Databases

147 Chapter 7: Upgrading Databases Applying Custom Cabinets When you apply a custom cabinet to a database, you can specify objects in the cabinet to exclude from the upgrade. By default, the system applies all objects in the cabinet to the database. Caution Back up each database you plan to upgrade, including all application databases and the system database (MRISystem). To apply a custom cabinet to a database: 1. On the Windows Start menu, go to Programs > MRI Real Estate Solutions > MRILogin. 2. On the MRI for Windows Login dialog box (Figure 7-17), log on with the SYSADM user name or as a system administrator with database upgrade rights, and then click Security Console. Figure Security Console Button 3. On the left side of the security console view, click the Database tab, and then select the version 4.0 database to upgrade in the drop-down list. 4. On the File menu, click Upgrade Database. Upgrading Version 4.0 Databases 147

148 Chapter 7: Upgrading Databases 5. On the Upgrade Database Options dialog box (Figure 7-18), click the Apply Custom Cabinet to Application Database option button, and then browse to or enter the path and file name of the custom cabinet to apply. Figure Upgrade Database Options Dialog Box 6. Click OK. 148 Upgrading Version 4.0 Databases

149 Chapter 7: Upgrading Databases 7. Use the information in the following table to specify which objects to include in the database on the Custom Upgrade view (Figure 7-19). To include... all objects only specific objects Then... Ensure the All Object Types check box is selected, and then click Process. a. Clear the check box next to an object type. b. Select the name of the object type to display all the associated objects on the right side of the view. c. Clear the check box next to each object you do not want to include in the database upgrade. d. Click Process. Figure Custom Upgrade View Upgrading Version 4.0 Databases 149

150 Chapter 7: Upgrading Databases A status view (Figure 7-20) appears, which displays the status of the upgrade process. Figure Custom Upgrade Status View 150 Upgrading Version 4.0 Databases

151 Chapter 7: Upgrading Databases 8. When a message appears indicating whether the upgrade was successful or unsuccessful, click OK. Note: If the system returns any errors, the upgrade will fail. If the system returns any warnings, the ugprade is still successful, but there may be data-related issues to resolve. Caution If the system cannot recreate or apply a foreign key, warning messages occur. As of version 4.0, foreign key warnings do not cause an upgrade to fail. However, in subsequent versions of MRI, foreign key messages will be errors and will cause an upgrade to fail. Therefore, IRES recommends you resolve any foreign key warnings, as described in Foreign Key Warnings on page To view the details of a message on the status view, double-click the message in the Message grid. clear or display the list of success, warning, or error messages, click the corresponding button at the top of the view. When a message button is active, as indicated by a white background, the system displays the corresponding messages in the grid inactive, as indicated by a gray background, the system clears the corresponding messages from the grid copy the messages appearing in the grid to your clipboard, click Report, and then click Copy Messages to Clipboard. For more information about foreign key warnings, refer to Foreign Key Warnings on page Click OK to close the status view. Upgrading Version 4.0 Databases 151

152 Chapter 7: Upgrading Databases Foreign Key Warnings Caution As of version 4.0, foreign key warnings do not cause an upgrade to fail. However, in subsequent versions of MRI, foreign key messages will be errors and will cause an upgrade to fail. Therefore, IRES recommends you resolve any foreign key warnings, as described below. When you upgrade a database, there may be occasions when the system displays foreign key warnings (Figure 7-21). Foreign keys enforce data integrity between tables and may be the result of differences in column structure between two tables a missing primary key a field in a foreign table that contains an invalid value When a foreign key warning occurs, the system writes the message to the Events log, which you can view and print later when you want to resolve the error. Figure Foreign Key Warnings 152 Foreign Key Warnings