FIREHOUSE Software Enterprise Installation Guide

(1)

FIREHOUSE

Software

Enterprise Installation Guide

(2)

Urbandale, IA 50322

FIREHOUSE Software® is a registered trademark of Xerox Government Systems, LLC. All rights reserved. Microsoft, MS, MS-DOS, Microsoft Visual FoxPro, and Microsoft Access are registered trademarks. Windows is a trademark of Microsoft Corporation. CAMEO is a registered trademark. iPad is a registered trademark of Apple, Inc. All other products or services mentioned in this manual are identified by the trademarks or service marks of their respective companies or organizations. Xerox disclaims any responsibilities for specifying which marks are owned by which companies or organizations.

FIREHOUSE Software is protected by the copyright laws that pertain to computer software. It is illegal to make copies of the Software except for backups. It is illegal to rent, lease, sublicense, or otherwise transfer any of the materials. It is illegal to remove or obscure pro-prietary notices. It is illegal to duplicate and distribute the Software by any other means, including electronic transmission. To protect trade secrets contained in the Software, you may not decompile, reverse engineer, dissemble, or otherwise reduce the Software to human per-ceivable form. You may not modify, adapt, translate, rent, lease, or create derivative works based upon the Software or any part thereof. Xerox warrants the original media are free from defects in material and workmanship, assuming normal use, for ninety (90) days from the date of purchase. Except for express warranty of the original media set forth above, Xerox grants no other warranties, express or implied, by statute or otherwise, regarding the media related materials, their fitness for any purpose, their quality, their merchantability, or oth-erwise. The liability of Xerox, under the warranty set forth above, shall be limited to the amount paid by the customer for the product. In no event shall Xerox be liable for any special, consequential, or other damages for breach of warranty.

© 2014 Xerox Government Systems, LLC.- Printed in the United States. All rights reserved. No part of this work covered by copyright hereon may be reproduced in any form by any means -- graphic, electronic, or mechanical -- including photocopying, recording, taping, or storage in any information retrieval system, without the written permission of the copyright owner.

(3)

FIREHOUSE Software License Agreement

Carefully read the following terms and conditions before installing software fromFIREHOUSE Software. Only an Authorized Representative of the purchaser should install the software. Installing the software indicates acceptance of these terms and conditions specified in the License Agreement.

Xerox Government Systems, LLC and the party who installs this software (“you”) hereby agree as follows:

1. Licensed Software:“Licensed Software” means the software component and modules ordered and paid for by you, as listed in Xerox’s client database of licensed products, and as evidenced by your customer receipt. Licensed Software includes all documentation relating to our software. It also includes any upgrades, modi-fications, and customizations (collectively, “Improvements”) to our software, should such Improvements be delivered to you at a later time.

2. End Users:“End User(s)” means (i) your employees with a need to access the Licensed Software; and (ii) third party consultants engaged by you who have a need to access the Licensed Software, and who are fulfilling legitimate business functions for you on your behalf.

3. Materials:This document contains links to downloaded files and applicable manual(s) relating to the Licensed Software.

4. License Grant:Xerox hereby grants a revocable, non-exclusive, non-transferable license to use the Licensed Software on a single microcomputer, in the United States of America. The number of End Users authorized to access the Licensed Software concurrently is reflected on your invoice and in this License Agreement. You may increase the maximum number of concurrent End Users by procuring additional licenses from Xerox based upon the then-current license fee schedule. You may not make use of any object code for any component(s) or modules(s) for which you have not expressly obtained a license for use under this Agreement. Any rights not expressly granted in this Agreement are expressly reserved. You agree not to (a) rent, lease, sublicense, assign or otherwise transfer the Licensed Software, including any of the materials or your rights hereunder, (b) remove or obscure our proprietary notices, (c) translate, alter, decompile or disassemble any of the materials, (d) copy any of the materials without our prior written consent, (e) use the software for other agencies. You shall have no right to access, copy or otherwise use the source code for software licensed under this license. You are prohibited from causing or permitting the reverse engineering, disassembly or decompilation of the ware licensed under this license. You are prohibited from modifying, improving or otherwise enhancing the soft-ware licensed under this license.

5. Terms:This license is effective until terminated. You may terminate it at any time by destroying the materials and all copies of any material made from the original materials and notify Xerox immediately. This license ter-minates automatically upon breach of any of the conditions of this license. Upon termination, you agree to des-troy all copies of the materials. Use of the materials without a valid license of the materials is unauthorized and may subject you to monetary penalties.

6. Confidentiality:You receive the right to use the Licensed Software and materials as specified herein, but you do not become the owner of the Licensed Software and materials. The Licensed Software and materials are exclusive property of Xerox and are protected by trade secret, copyright, and trademark law. You acknowledge that the materials are Xerox property and contain valuable, confidential, unpublished information developed by Xerox at a great expense. You agree to protect the materials from unauthorized reproduction, distribution, dis-closure, or use of publication. You may not transfer any materials or software to anyone or entity without the writ-ten consent of Xerox authorized personnel.

7. U.S. Government Restricted Rights:The Licensed Software and documentation related thereto were developed at private expense and are provided with "RESTRICTED RIGHTS". Use, duplication, or disclosure by the Government is subject to restrictions as set forth in FAR 52.227-14 and DFAR 252.227-7013 et seq. or its successor.

(4)

8. Export Laws:You may not export the Licensed Software and agree to comply with all laws, regulations, orders or other restrictions of the U.S. Export Administration Regulations.

9. Warranty:We warrant the downloadable files to be free from material defect in normal use for 90 days from the date of receipt of materials. We do not warrant the error-free operation of the Licensed Software contained in the downloadable files, or that such Licensed Software will meet your requirements. The Licensed Software is licensed "as is". We will, however, attempt to correct or bypass any actual reproducible and significant error in the software, provided you notify us and describe it in writing within 90 days from the date of receipt of the mater-ials, and we will, within a reasonable time, at our option, provide either a corrected copy or work around instruc-tions. This does not cover altered software or require us to customize our software to meet your hardware or operating system requirements. Section 11 specifies your exclusive remedy for any breach by us of this section. No dealer, company, or person is authorized to expand, alter this section or any other provision of this agree-ment. Any such agreement will not bind Xerox. XEROX MAKES NO OTHER WARRANTIES WHATSOEVER, EXPRESS OR IMPLIED, WITH REGARD TO THE SOFTWARE LICENSED UNDER THIS LICENSE, IN WHOLE OR IN PART. XEROX EXPLICITLY DISCLAIMS ALL WARRANTIES OF MERCHANTABILITY AND OF FITNESS FOR A PARTICULAR PURPOSE. XEROX EXPRESSLY DOES NOT WARRANT THAT THE LICENSED

SOFTWARE, IN WHOLE OR IN PART, WILL BE ERROR FREE, WILL OPERATE WITHOUT INTERRUPTION OR WILL BE COMPATIBLE WITH ANY HARDWARE OR SOFTWARE OTHER THAN THE EQUIPMENT. LICENSEE WAIVES ANY CLAIM THAT THE LIMITED WARRANTY SET FORTH IN THIS SECTION OR THE REMEDY FOR BREACH OF SUCH LIMITED WARRANTY FAILS OF ITS ESSENTIAL PURPOSE.

10. Limitation of Liability:XEROX’S LIABILITY IN CONNECTION WITH THE LICENSED SOFTWARE UNDER THIS LICENSE, OR ANY OTHER MATTER RELATING TO THIS LICENSE WILL NOT EXCEED THE FEE THAT YOU ACTUALLY PAID TO XEROX FOR THE SOFTWARE GIVING RISE TO THE LIABILITY. REGARDLESS

WHETHER ANY REMEDY SET FORTH HEREIN FAILS OF ITS ESSENTIAL PURPOSE OR OTHERWISE, IN NO EVENT WILL XEROX BE LIABLE TO YOU FOR ANY SPECIAL, INCIDENTAL, OR CONSEQUENTIAL

DAMAGES, WHETHER BASED ON BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY, INDEMNIFICATION, OR OTHERWISE, AND WHETHER OR NOT XEROX HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. YOU ACKNOWLEDGE THAT XEROX HAS SET ITS FEES AND ENTERED INTO THIS LICENSE IN RELIANCE UPON THE LIMITATIONS OF LIABILITY AND THE

DISCLAIMERS OF WARRANTIES AND DAMAGES SET FORTH IN THIS LICENSE, AND THAT THE SAME FORM AN ESSENTIAL BASIS OF THE BARGAIN BETWEEN THE PARTIES.

11. Remedy:In the event that Xerox breaches this agreement, your sole remedy is to notify us of such breach within the applicable warranty period and we will at our sole option, either cure the breach or refund the license fee paid to us for the materials. In no event will Xerox be responsible for any damage beyond the amount of the license fee or for any indirect, special, incidental, consequential or similar damages or profits to you or any other person, or entity, regardless of the legal basis, even if Xerox has been advised of the possibility of such dam-ages, except to the extent applicable state law specifically prohibits such exclusion.

12. General (System Only):This license shall be governed by laws of the State of Iowa. All prior correspondence oral or written including without limitation, all understandings with respect to the Licensed Software or materials relative thereto are hereby superseded. This license constitutes your and our entire agreement and under-standing regarding the Licensed Software and materials relative thereto.

General (Evaluation Only):This evaluation program is provided free of charge to the registered requestor of the evaluation software and is to be used solely as an evaluation copy.

13. Software Maintenance Agreement:90 days free phone support is provided with purchase of FIREHOUSE Soft-ware. A separate software maintenance contract is available for an additional charge. This software main-tenance contract is not mandatory but highly recommended. The annual mainmain-tenance contract includes phone support and program updates. The cost of the software maintenance contract is based on the type and number of modules installed. In the event that the 90 day free support period has expired and no software maintenance

(5)

Technical support

FH®_{Technical Support:}

Phone: 800-921-5300, option 2 [email protected]

Sales contacts

Jim Brandariz

Phone: 800-796-1614, 530-621-0981 Fax: 530-626-8582

[email protected] AZ, CA, NV, OR, WA

Peter Eleftherakis

Phone: 888-362-4446, 508-362-4446 Fax: 508-362-5932

[email protected] CT, MA, ME, NH, NY, RI, VT, Ontario Mike Rogers

Phone: 888-941-3473, 214-504-0242 Fax: 214-504-0244

[email protected] AR, KS, LA, MO, MS, OK, TX

Forest Nace

Phone: 800-285-8685 Fax: 724-283-9086

[email protected] DE, IN, KY, MD, NJ, OH, PA, VA, WV Brad Reineke

Roger DeDoncker Rebecca Sanger

Phone: 800-921-5300, ext. 1 Fax: 515-288-4825

[email protected]

AK, AL, CO, GA, FL, HI, ID, IA, IL, MI, MN, MT, NC, ND, NE, NM, SC, SD, TN, UT, WI, WY, International

(6)

Introduction

TheFIREHOUSE Software Enterprise Installation Guideis designed to help you install or update, launch, and configure new installations ofFIREHOUSE Software®_Enterprise.

Inform-ation on updating your existing installInform-ation of FH Enterprise to a newer version is available in the FIREHOUSE Software Enterprise Update Guide.

FH®_{Enterprise is a fire department records management software package that maintains a SQL}

database of information on a server where client computers can access it. You can install

FH Enterprise on any computer or network at your department. If there are no computers available at your department, you can install FH Enterprise on a personal computer.

Note:The free evaluation version of FH Enterprise, which creates a fully functional installation of FH Enterprise with all available modules, expires 90 days after installation.

FH®_{technical support staff is available to answer your questions by telephone or email. Technical}

support hours are from 7:00A.M. to 7:00P.M. Central time, Monday through Friday, and from 8:00 A.M. to 12:00P.M. on Saturday. Call 800-921-5300, option 2. You can also send an email to [email protected].

The server and client computer relationship

FH Enterprise establishes a SQL database on a computer designated as a "server." Any com-puter that connects to the FH Enterprise database on the server is a "client" comcom-puter.

Users on client computers view the normal FH interface, and their computers send and receive information from the SQL database on the server as users make changes. Because processing occurs on the server and only requested information is sent back to the client, traffic over the con-nection between the server and client is minimized and response times are adequate even with slower connection speeds.

The server should be a fast computer that can be assigned a unique address that all FH Enter-prise client computers can access. The server should not be a computer that is also used as a file server. Ideally, the server should be dedicated to hosting to the database engine and the FH Enter-prise database. If necessary, the server can also host other SQL databases.

(8)

Server system requirements

For servers, FH Enterprise is supported on the following operating systems:

l Windows 7 l Windows 8.1

l Windows Server 2008 l Windows Server 2012

Caution:FH Enterprise is compatible with most Windows 64-bit operating systems on new installations of Windows. Machines upgraded from 32-bit systems to 64-bit systems have demonstrated problems and are not recommended.

Note:Extended support for environments and products that have reached Microsoft's end of mainstream support is available if you subscribe to eitherFIREHOUSE Software's Gold or Plat-inum support program. Information on the FH Support Programs is available at http://www.fire-housesoftware.com/pdf/FH_Support_Program.pdf.

For networking, Microsoft .NET Framework 4.0 is required. For a Web browser, use Microsoft Internet Explorer 9.0 or later.

To manage your FH Enterprise database, use Microsoft SQL Server 2012.

Note:If you are using Windows 7 or later as the operating system for the SQL database server, you must use a 64-bit of SQL Server with FH Enterprise.

The hardware requirements for the server depend on the SQL software package you install to man-age your FH Enterprise database. Hardware requirements for SQL Server are available from Microsoft athttp://www.microsoft.com/sql/, or from your local Microsoft reseller. Your actual hard-ware requirements may be higher, based on the number of concurrent users or other applications running on the server, server configuration, and network configuration.

Tip:To qualify for U.S. General Services Administration (GSA) pricing, be sure to specify that you are a government entity when purchasing your SQL software package. You may save money by purchasing hardware and software as part of a package.

Note:If you use FH Enterprise to collect data from multiple departments, such as collecting state NFIRS transaction files or county EMS incident reports from area agencies, you should exceed the recommend hardware requirements if possible.

(9)

Client system requirements

On client computers, FH Enterprise is supported on the following operating systems:

l Windows 7 l Windows 8.1

l Windows Server 2008

Caution:FH Enterprise is compatible with most Windows 64-bit operating systems on new installations of Windows. Machines upgraded from 32-bit systems to 64-bit systems have demonstrated problems and are not recommended.

Note:Extended support for environments and products that have reached Microsoft's end of mainstream support is available if you subscribe to eitherFIREHOUSE Software's Gold or Platinum support program. Information on the FH Support Programs is available at

http://www.firehousesoftware.com/pdf/FH_Support_Program.pdf. The following network libraries are supported:

l Named Pipes l TCP/IP l Multi-Protocol l IPX/SPX

The FH Enterprise client must have the following hardware:*

Component Minimum Recommended

Processor Pentium 600 MHz Pentium III compatible

Faster processor

RAM 1 GB 2 GB or more

Hard disk space 2 GB available* 6 GB available

Video resolution 800 x 600 1024 x 768

* Your hardware requirements may be higher, based on the number of concurrent users or other applications running, server configuration, and network configuration. All requirements are subject to change.

Tip:Use an uninterruptible power supply (UPS) with client computers in case of power failure.

(10)

Checklist for a new installation of FH Enterprise

Caution: Below is a high-level checklist of the steps you need to install FH Enterprise for the first time. Detailed information for the steps below are available in the following pages of the FIREHOUSE Software Enterprise Installation Guide.

Tip:Print this page and check off the items below as you accomplish them.

(If you purchased your copy of FH Enterprise) Verify that you received an email from

FIREHOUSE Software technical support, containing a download link and a PDF file listing your serial number and an activation code.

Verify that you have adequate hardware to support FH Enterprise and MS SQL Server. (If you have an FH Standard database that you want to upsize to FH Enterprise) Prepare your FH Standard data for the upsizing process.

Information on preparing your FH Standard data for upsizing is available in the FIREHOUSE Software Enterprise Upsizing Guide.

Set up the database server. Install SQL Server.

(If you are not upsizing a database from FH Standard) Attach a demo database or attach the new blank FH Enterprise database.

On the first client computer, do the following. Install the FH Enterprise client.

Activate the new installation of FH Enterprise.

On the remaining client computers, install and activate the FH Enterprise client. (On any client computer) Configure FH Enterprise for your needs, and then log in.

(11)

Install SQL Server on the database server

WARNING:If you have been using an installation of FH Standard, and if you want to upsize your existing FH Standard database to work with FH Enterprise, you need to prepare your FH Standard data for the upsizing process before continuing with the steps below. Information on preparing your FH Standard data for upsizing is available in theFIREHOUSE Software Enter-prise Upsizing Guide.

Note:Microsoft SQL Server is purchased and configured separately from FH Enterprise, and provides full-featured database management to the qualified SQL Server administrator.

1. Log on to the computer you want to install SQL Server on as an administrator. 2. Install SQL Server according to its documentation.

WARNING:When you reach theDatabase Engine Configurationscreen of the SQL Server installation wizard, be sure to selectMixed Mode (SQL Server authen-tication and Windows authenauthen-ticationto prevent problems with logging into the SQL Server database later during configuration.

3. Depending on whether or not you are upsizing from FH Standard to FH Enterprise, do one of the following.

Upsizing? Do this

No l Continue withAttach a database to SQL Server, on page 6.

Yes l Continue withInstall FH Enterprise on a client computer, on page

10.

(12)

Attach a database to SQL Server

If you want to create a new blank database to enter your data into, or if you are planning to use the demonstration database provided with FH Enterprise for evaluation purposes, you need to attach the appropriate database to your installation of SQL Server.

1. (If you have not done so already) Log on to the SQL Server database server as an admin-istrator.

2. (If the FH Enterprise installation or update dialog box is not already open) Do the fol-lowing.

a. Navigate into the folder of installation contents you unzipped earlier. b. Double-clickAutoRun.exe.

(13)

3. In the FH Enterprise installation or update dialog box, clickAttach a FIREHOUSE Software Database to a running Microsoft SQL Server.

Either theSQL Server Loginor theSelect Database to Attachdialog box appears.

4. (If theSQL Server Logindialog box appears) Enter the SQL Server administrator's user name and password, and then clickOK.

TheSelect Database to Attachdialog box appears.

5. At the top of the dialog box, from the list of available FH databases, click the database you want to attach to SQL Server.

fhis a blank database for "live" systems, andfh_demois a database with sample data for evaluations.

6. InCopy the selected database to the following path on the server, type the path to the location where you want the FH Enterprise database to exist.

(14)

7. (If the server is a different machine on a network) Do the following.

a. SelectServer is a remote computer, and then type the server name/address and instance name of the SQL Server database on the server.

Example:fhserver\sqlexpress

b. InPath to database file relative to the server, type the path on the server to the database files.

Note:The default path is normally the best choice. If you need to change this path, contact FH technical support for assistance.

8. InSpecify the name to give to the new database, type a name for the database. WARNING:The name of the database must begin withFH.

Example:FH_AFD orFH_ACME.

9. Select or clearMake this the default startup database on this computerto indicate whether this is FH Enterprise's default database to use on startup.

10. ClickOK.

TheSQL Server Logindialog box appears.

11. Enter the SQL Server administrator's user name and password, and then clickOK. TheAttach Database Resultsdialog box appears, displaying what at first glance is an error message.

(15)

Note:This error message references a log file that was not found, not a failure for the database to attach to your installation of SQL Server. A new log file was created, and your database has successfully attached to your installation of SQL Server.

12. ClickContinue.

The FH Enterprise installation and update dialog box reappears.

Caution:If the FH Enterprise client will be installed on the SQL database server, do not clickExitor close the FH Enterprise installation or update dialog box, as you will need it later to install the client software.

13. (If the FH Enterprise client will be installed on a different computer) ClickExit. 14. Continue withInstall FH Enterprise on a client computer, on page 10.

(16)

Install FH Enterprise on a client computer

You must install FH Enterprise on each client computer that will run FH Enterprise. If a computer does not have enough free disk space, the installation will not complete.

Caution:

l Close all open applications and disable anti-virus software before installing FH Enterprise

or updating an existing installation of FH Enterprise.

l For the server and client computers to communicate, you must have the proper network

pro-tocol enabled on the server for your environment. If it is not already enabled, consult the Windows documentation for the server’s operating system for the steps to add your pre-ferred network protocol.

1. (If you have not done so already) Log on to the computer you want to install the FH Enter-prise client onto as an administrator.

2. (Windows Server 2008 or later, if Citrix or Terminal Services are installed) Place the com-puter in installation mode.

a. ChooseStart → Run. TheRundialog box appears.

b. InOpen, typecmd.

A Windows system dialog box appears with a command prompt.

c. At the prompt, typechange user /install.

A message appears confirming that the server is now set to installation mode. d. Close the Windows system dialog box.

(17)

3. Depending on where you are installing the FH Enterprise client, do one of the following.

l (On the SQL database server, and if the FH Enterprise installation or update dialog

box is still open) Go to step 4.

l (On a different computer, or if you closed the FH Enterprise installation or update

dia-log box on the database server) Do the following.

a. (If you have not done so already) Follow the directions in the email to download and unzip the necessary files and folders.

b. Navigate into the folder of unzipped contents. c. Double-clickAutoRun.exe.

The FH Enterprise installation or update dialog box dialog box appears. 4. In the FH Enterprise installation or update dialog box, clickInstall or Update the

FIREHOUSE Software Enterprise Client (Workstation).

(18)

TheWelcomescreen of the wizard appears.

5. SelectNew Installation, and then clickNext >. TheSetup screen of the wizard appears.

(19)

6. Read the information on the screen, and then clickNext >. TheSelect Installation Locationscreen of the wizard appears.

7. (Optional) InInstall to Folder, clickBrowseand use the file browser that appears to nav-igate to the directory where you want to install FH.

WARNING:For Windows 7, Windows 8, Windows 2008, and higher computers, this location must be outside theC:\Program FilesandC:\WINDOWSdirectories.

8. SelectInstall Shortcuts and icons in Windows NT common foldersso that all users logging into this computer can see the FH Enterprise icons.

9. ClickNext >.

(20)

TheRegistration Informationscreen of the wizard appears.

10. Fill in this screen as appropriate to your company and location, and then clickNext >. TheConfirm Registration Informationscreen of the wizard appears.

(21)

TheBackup Replaced Files screen of the wizard appears.

12. For a new installation, selectNo, because there are no files to back up yet.

13. (Optional) ClickBrowseand then navigate to the directory where you want to place files. 14. ClickNext >.

TheAdditional Installation Optionsscreen of the wizard appears.

(22)

Caution:The additional options are for administrators, and should not be installed unless an administrator will be using these tools at this client computer.

15. (If necessary) Select the options for an administrator to use at this client computer. Select this For an administrator to do this Install Remote Backup Create database backups.

Caution:Not recommended for computers used by non-administrative personnel, and only recommended for the SQL database server.

Install Database Tools Perform database maintenance. Recommended for all com-puters.

Install Enterprise Database Administrator

Administer SQL Server databases.

Caution:Not recommended for workstations used by non-administrative personnel, and only recommended for the SQL database server.

Install Local Database Upsizer

Upsize a standard FH database.

Caution:Only recommended for installation on the SQL database server.

WARNING:If you want to upsize an existing

FH Standard database to a SQL database that works with FH Enterprise, you must select this option on the first computer you install the FH Enterprise client on. You do not need to install it on other client computers. Install Database

Archiver

Create database archives.

Caution:Recommended for the server only. Install System

Activation Utility

Activate an evaluation system. Recommended for all com-puters.

Install Internet

(23)

16. ClickNext >.

TheConnect to Database screen of the wizard appears.

17. Depending on the location of the database, select the appropriate option, and then click Next >.

If FH Enterprise is located on Select this A server on your network, not on the

computer you are currently on.

Connect to a remote database on your network

This computer. Connect to a database on this computer

(24)

TheConfiguration Location screen of the wizard appears.

18. Verify thatINI Fileis selected.

Configuration will be saved in the program installation directory.

WARNING:Do not selectRegistryfor Windows 7,Windows 8.1, Windows Server 2008, or Windows Server 2008 R2.

(25)

TheStart Installationscreen of the installation wizard appears.

20. ClickInstall.

TheInstallingscreen appears, and progress bars appear in the wizard.

When the installation completes, the installation wizard disappears and theRemote Con-figurationdialog box appears, set to theConnectiontab.

When a user logs into FH Enterprise with their FH username and password, the client computer automatically tries to connect to the SQL database for FH on the

SQL database server. You need to specify the network protocol, the location of the FH database, and the SQL Server administrator username and password, and other para-meters for this connection to be successful.

Tip:If necessary, you can access this dialog box after installing FH Enterprise on a cli-ent computer by choosingStart → FIREHOUSE Software → FIREHOUSE Software Enterprise Edition Tools → Remote Connection Configuration.

(26)

21. Do one of the following.

To do this Do this

(New installation or addi-tional client computers) Connect to a SQL database

l Continue with step 22 below.

Upsize from FH Standard to FH Enterprise

If this is the first client computer you have installed the FH Enterprise on, then your FH Standard database is still in its FoxPro format, and cannot be connected yet to FH Enterprise. Later, after you run the Local Database Upsizer utility you selected for installation earlier in step 15, you will connect the upsized database to

FH Enterprise.

WARNING:You only want to upsize the FH Standard

database once. If you have already run the Local Data-base Upsizer utility on the first client computer, do not run it again on other client computers. Instead, con-nect to the SQL database that was creatad when the utility was run on the first client computer.

1. ClickCancel.

TheRemote Configurationdialog box disappears, and the installation wizard reappears, displaying the Installation Completescreen.

2. Skip step 22 and continue with step 23 below. 22. In theRemote Configurationdialog box, do the following.

a. UnderConnect Using, select a method to connect the client computer to the server. Custom Connectionis the default method for connecting an FH Enterprise client to the server.ODBC Data Sourceis useful if you encounter connection errors and if you have the ability to set up an ODBC (Open Database Connectivity) user data source that contains details about the client connection to the server.

Note:ODBC data sources are set up outside FH Enterprise.

If you select this Do this

Custom Connection

1. FromNetwork Protocol, selectWinsock Netlib. Named Pipesis not recommended for low-bandwidth connections.

Note: TCP/IPis a common network protocol for wide area networks, but is not available with the newest Microsoft Data Access Components (MDAC). It is, however, supported in Winsock Netlib.

(27)

If you select this Do this

Caution:Both the server and client need to have the selected network protocol enabled for the connection to be valid.

2. Depending on the location of the FH Enterprise data-base, do one of the following.

Database

loc-ation Do this

On a server on the network

l InServer Name or Network

Address, server name/address of the database server.

Also on the cli-ent computer

l SelectUse Local Server.

Note:This option should only be used if SQL is using the default instance name. If a named instance of SQL is used, you must specify that. ODBC Data

Source Note:_{interface in the}When you select_{Remote Configuration}ODBC Data Source_{dialog box}, the user changes on theConnectiontab.

l FromODBC Data Source Name, select an ODBC data

source.

b. InDefault Database, type the name of the database you selected earlier (fh,fh_ demo, or the database name you specified earlier).

(28)

c. (If you have multiple SQL databases for FH Enterprise on the database server) Select Rebuild the list of FH databasesto include all FH Enterprise databases in the list of databases you can connect to when logging into FH Enterprise.

d. Click theLogintab.

e. Define your SQL Server login credentials in one of the following ways. To use these

login credentials Do this

The current or act-ive Windows user account

l SelectUse Windows NT Authentication.

Note:This option is only available for Windows net-works, and the logged-in user must have an SQL secur-ity login added for their Windows login.

Example:advsetup@sqlserv

Unique SQL Server login credentials

1. (If it is selected) ClearUse Windows NT Authentication.

2. InServer Login User NameandServer Login Pass-word, enter the user name and password for

SQL Server.

3. SelectRemember Passwordto indicate that you want to automatically use the specified server user name and password.

If this option is not selected, you are prompted to supply this information each time you connect to SQL Server.

(29)

f. Click theAdvancedtab.

g. InNetwork Packet Size, enter the size of data segments sent through your network between the client and database server.

The packet size 4096 is the default, but most networks can support a larger size. h. InConnect Timeout, enter the number of seconds the client attempts to connect to

the database server.

If the client computer is a longer distance from the database server, a longer timeout value may be needed.

i. SelectAll data sessions share a single connectionto consolidate multiple con-nections to SQL Server to a single connection.

Note:Using a dedicated connection to SQL Server databases can increase per-formance for FH Enterprise.

j. ClearInclude memo fields when checking for data conflictsto prevent FH Enterprise from comparing updated text in theNotestab of dialog boxes to the text which had existed before.

k. At the bottom of the dialog box, clickTest.

A dialog box indicating confirmation or failure of the client's success at connecting with the FH Enterprise server appears.

l. ClickOK.

(30)

m. In theRemote Configurationdialog box, clickOK.

TheRemote Configurationdialog box disappears, and the installation wizard reappears, displaying theInstallation Completescreen.

23. ClickFinish.

(31)

24. ClickNext >.

The location where the documentation will be installed appears.

25. (Optional) ClickBrowseand use the file browser that appears to navigate to the directory you want to install the documentation in.

26. ClickNext >.

A list of the documentation you can install appears.

(32)

27. (Optional) Clear any documents you do not want to install, and then clickNext >. A confirmation screen appears.

28. Read the information on the screen, and then clickNext >. Another confirmation screen appears.

(33)

TheFIREHOUSE Software installation or update dialog box reappears.

Caution:If this is the first computer you have installed the FH Enterprise client on, do not close the FH Enterprise installation or update dialog box. You will need it to activ-ate FH Enterprise or upsize an FH Standard database.

30. (Windows Server 2008 or later, if Citrix or Terminal Services are installed) Return the computer to application mode.

a. ChooseStart → Run. TheRundialog box appears.

b. InOpen, typecmd.

A Windows system dialog box appears with a command prompt.

(34)

c. At the prompt, typechange user /execute.

A message appears confirming that the server is now set to user mode. d. Close the Windows system dialog box.

31. Do one of the following.

If this is the case Do this This is the first computer

you have installed the FH Enterprise client on

l Do one of the following.

If you are Do this

Upsizing from FH Standard to FH Enter-prise

Continue withUpsize the FH Standard database, on page 29.

Installing a new installation of FH Enterprise

Continue withActivate a new FH Enterprise installation, on page 36.

You are adding another client computer

l Begin using FH Enterprise on the client computer as

nor-mal.

The licensing necessary for this client computer is auto-matically applied.

Tip:If the license is not applied automatically, copy the

fh.licfile in theRemotefolder from the first computer you installed the FH Enterprise client on, and paste it into theRemotefolder the computer you added.

(35)

Upsize the FH Standard database

When you upsize from FH Standard to FH Enterprise, the process attaches a new SQL database to SQL Server on the database server, and then populates the new database with the records from the FH Standard database.

Note:If you are not upsizing from FH Standard to FH Enterprise, skip the steps below and con-tinue withActivate a new FH Enterprise installation, on page 36.

WARNING: Before doing the steps below:

l Read theFIREHOUSE Software Enterprise Upsizing Guide, at

http://www.fire-housesoftware.com/pdf/FH7StdEntUpsize.pdfand prepare your FH Standard database according to the instructions in it.

l Verify that all FH users are logged out, and that FH is not running.

Caution:To be able to run the upsizing process, you must have selected theInstall Local Database Upsizeroption on theAdditional Installation Optionsscreen when you installed the FH Enterprise client. For faster performance, do the steps below on the SQL Server data-base server.

1. ChooseStart → Programs → FIREHOUSE Software → FIREHOUSE Software Enterprise Edition Tools → Upsize Local Database.

TheUpsize Local Foldersdialog box appears.

(36)

2. Verify that the paths inDatabase,Lookup,System,Queries, andReportsare correct for their corresponding FH Standard folders.

Note:The path forLookupis usually the same as the path forDatabase.

3. (If necessary) For any paths that are not correct, click the lookup button and use the file browser to navigate to and select the correct corresponding folder.

4. ClickConfigure Remote Connection.

TheRemote Configurationdialog box appears.

5. On theConnectiontab, do the following.

a. FromNetwork Protocol, selectWinsock Netlib.

Named Pipesis not recommended for low-bandwidth connections.

Note: TCP/IPis a common network protocol for wide area networks. but is not available with the newest Microsoft Data Access Components (MDAC). It is, how-ever, supported in Winsock Netlib.

Caution:Both the server and client need to have the selected network protocol enabled for the connection to be valid.

(37)

b. Depending on the location of the FH Enterprise database, do one of the following.

Database location Do this

On a server on the network

l InServer Name or Network Address, server

name/ad-dress of the database server. Also on the client

computer

l SelectUse Local Server.

Note:This option should only be used if SQL is using the default instance name. If a named instance of SQL is used, you must specify that.

Tip:If your FH database is on a different computer than the SQL server, you should manually copy theData, Sys-tem,Queries, andReportsfolders in the

FH installation directory to the SQL server before upsiz-ing. This prevents users from accessing the FH database during the upsize process, and significantly improves the speed of the upsize.

c. InDefault Database, type the name of the SQL database that will contain the FH Standard data after it is upsized.

WARNING:The name of the database must start withFH. Example:FH_afdorFH_ACME.

d. Click theLogintab.

(38)

e. Define your SQL Server login credentials in one of the following ways. To use these

login credentials Do this

Windows user account active at the workstation

l SelectUse Windows NT Authentication.

Note:This option is only available for Windows net-works, and the logged-in user either must have network administrator rights and/or have a SQL login added for the Windows login.

Unique SQL Server login credentials

1. InServer Login User NameandServer Login Pass-word, enter the user name and password for

SQL Server.

2. SelectRemember Passwordto indicate whether you want to automatically use the specified server user name and password.

You must havesarights to create a new database through the SQL login or Windows NT authentication. f. Click theAdvancedtab.

g. InNetwork Packet Size, enter the size of data segments sent through your network between the client and database server.

h. InConnect Timeout, enter the number of seconds the client attempts to connect to the database server.

i. SelectAll data sessions share a single connectionto consolidate multiple con-nections to SQL Server to a single connection.

Note:Using a dedicated connection to SQL Server databases can increase per-formance for FH Enterprise.

(39)

j. ClearInclude memo fields when checking for data conflictsto prevent FH Enterprise from comparing updated text in theNotestab of dialog boxes to the text which had existed before.

k. At the bottom of the dialog box, clickTest.

A dialog box indicating confirmation or failure of the client's success at connecting with the FH Enterprise server appears.

l. ClickOK.

m. In theRemote Configurationdialog box, clickOK. 6. In theUpsize Local Foldersdialog box, clickOK.

A warning that all users need to be logged out of FH appears.

7. ClickYes.

TheExpanderandUpsizingdialog boxes appear with progress bars as the FH Standard database upsizes.

(40)

When the database has finished upsizing, a confirmation dialog box appears.

8. ClickOK.

Another confirmation dialog box appears, prompting you to view the upsize log file.

9. ClickYes.

(41)

10. Carefully review the file to see if any errors occurred during the upsizing process. 11. Close the log file window.

12. Follow the instructions inInstall FH Enterprise on a client computer, on page 10 to install the FH Enterprise client on any other client computers that need to access the upsized database.

Note:Because the upsizing process converts the FH Standard database to an SQL database that FH Enterprise can connect with, when you reach step 21 inInstall FH Enterprise on a client computer, on page 10, you do not have to clickCancel when theRemote Configurationdialog box appears. You can specify the database server connection information.

13. Uninstall FH Standard from all computers.

Caution:Be sure to uninstall FH Standard before installing the FH Enterprise client that accesses the upsized FH database.

(42)

Activate a new FH Enterprise installation

Note:If you are upsizing an FH Standard installation to FH Enterprise, you have already activ-ated the FH Enterprise following the steps in theFIREHOUSE Software Enterprise Upsizing Guide. You can skip the steps below and continue withConfigure a purchased copy of FH Enterprise, on page 42.

FH Enterprise always installs as an "evaluation" copy, even when you are purchasing your install-ation. If you purchased FH Enterprise, you need to activate the license for FH Enterprise to change it from an evaluation installation to a purchased installation. You were a PDF file con-taining a serial number and an activation code FH Enterprise.

Caution:Activate the license for FH Enterprise right away, as the activation code expires 45 days after it is created.

Note:The FH Enterprise installation or update dialog box should still be open from installing the FH Enterprise client.

1. (If you closed the FH Enterprise installation or update dialog box) Reopen the dialog box as described in step 3 ofInstall FH Enterprise on a client computer, on page 10.

(43)

The FH Enterprise activation wizard appears.

3. (If you are certain you only have one installation of FH) SelectSkip automatic search for existing installations.

Note:If you do not know if other copies of FH are installed, let the installation search and list all FH installations (the process may take several minutes).

4. Read the information on this screen of the wizard, and then clickNext >.

If no other installations are found, or if you selectedSkip automatic search for existing installations, the wizard displays the path to the folder where the license will be

installed.

(44)

If multiple installations ofFIREHOUSE Software were detected, the wizard lists the loc-ations where FH installloc-ations exist.

5. Depending on which screen appeared in the wizard, do one of the following.

If this screen appears Do this

Installation Location l ClickBrowse, and then use the file browser that appears

to navigate to the location of the FH installation.

Select Location l Select the FH installation you want the FH license to be

(45)

6. ClickNext >.

The activation wizard reappears, prompting you for the serial number of your FH installation, and the activation code associated with it.

7. Depending on how many days have passed since you installed FH, do one of the fol-lowing.

Days since

installation Then do this

45 days or less

l InSerial NumberandActivation Code, type the serial number and

activation code that was sent to you when you purchased FH. More than

45 days

1. (If you have not done so already) Contact an FH representative and ask for a new activation code.

2. InSerial NumberandActivation Code, type the serial number and activation code that was sent to you when you purchased FH. Caution:The activation code is case-sensitive. Copy and paste the code into Activ-ation Code, or enter it exactly as it appears.

8. ClickNext >.

(46)

The wizard displays the path to theRemotefolder.

9. (Optional) ClickBrowseand use the file browser that appears to navigate to a different location for live data directory.

10. ClickNext >.

(47)

11. ClickNext >.

When the activation completes, the wizard displays another confirmation screen.

12. ClickFinish.

The FH Enterprise installation or update dialog box reappears.

13. ClickExit.

14. Continue withConfigure a purchased copy of FH Enterprise, on page 42.

(48)

Configure a purchased copy of FH Enterprise

Once you have installed and activated the license for your purchased copy of FH Enterprise, you are ready to log in and configure FH Enterprise with caching information and specify database server options.

Log into a purchased copy of FH Enterprise

1. ChooseStart → Programs → FIREHOUSE Software 7 → FIREHOUSE Software 7. The first time you start FH Enterprise, an informational dialog box appears, stating that the license file has been uploaded to the server.

2. ClickOK.

TheLogindialog box for FH Enterprise appears.

3. InUser Name, typeguest. 4. InPassword, typedemo.

5. InDatabase, verify that the name of your FH Enterprise database is correct. 6. (If necessary) FromDatabase, choose a different database to connect to. 7. (If the message dialog box appears) ClickOK.

(49)

TheTry Additional Modules or Featuresdialog box appears, informing you of features you may want to explore in FH.

8. SelectDon't show this message again, and then clickOK.

The FH Enterprise window appears, with the menus and the main toolbar across the top.

9. Continue withEnable local caching, on page 44.

(50)

Enable local caching

If a client computer encounters slow response times when using lookup-driven fields, you can enable local caching to improve response times. When local caching is enabled, the most up-to-date lookup codes and system database are copied from the server to the client computer and are used locally on the client computer.

Caution:Enabling local caching is optional. If you enable it, you will not be able to modify the lookup codes or system rules from the client computer.

1. ChooseTools → Workstation Options. TheWorkstation Optionsdialog box appears. 2. Click theLocal Data & Filestab.

3. SelectEnable local caching of system and lookup tables. TheCachebutton and field beside it activate.

4. (If necessary) ClickCacheand use the file browser that appears to change the location of the files that are cached on the client computer.

Caution:Do not cache files on the client computer in the\FIREHOUSE Software\

installation folder. The defaulted sub-folder \Cache\ is usually acceptable. 5. ClickOK.

(51)

A confirmation dialog box appears, indicating that you must exit and restart FH Enter-prise.

6. ClickOK.

A second confirmation dialog box appears, directing you to exit and restart FH Enterprise.

7. ClickOK.

8. Exit FH Enterprise, and then restart it.

9. Continue withSpecify remote options, on page 46.

(52)

Specify remote options

There are a number of parameters you can set to control how the FH Enterprise client connects to the database server.

1. ChooseTools → Workstation Options. TheWorkstation Optionsdialog box appears. 2. Click theRemote Datatab.

3. (Optional) InRemote Access, type the path to the Remote folder.

The Remote folder stores the database field structure, the user field definitions, and the license file for FH Enterprise.

4. (Optional) UnderOn Startup, select the option that indicates which database the client should connect to when FH Enterprise starts.

Select this To connect to this Allow login to remote

database only

The SQL database located on the server. Note:This is the recommended option. User can select remote

or local database

(53)

Select this To connect to this Allow login to local

data-base only

The FH Standard database used before changing to FH Enterprise.

Caution:This option is only available if you have upsized an FH Standard database to an SQL database for FH Enterprise.

WARNING:Records added to the FH Standard data-base are not written to the SQL datadata-base server. Do not provide the opportunity to access the local data-base unless you have specific reasons for doing so, such as using the client computer for temporary train-ing purposes.

5. (If you experience delays displaying queries to large result sets) Do the following. a. SelectEnable Incremental fetching of query results.

The field belowEnable Incremental fetching of query resultsactivates. The FH Enterprise tables can potentially include millions of records. When records are accessed, specific tables are queried and matching records are returned to the cli-ent. If millions of records match the request, it may take some time for the complete list to be displayed.

b. In the field, type the number of records to include in results lists.

Tip:If there are more records in a query result than specified in incremental fetching, they are not displayed in the results list. To display remaining result list items, right-click with the query displayed and selectFetch All RecordsorFetchnumberof Records.

6. (Optional) Create new remote access folder files at startup.

In certain instances, remote access folder files can become corrupt, resulting in program errors for the FH Enterprise client when the corrupt remote access files are accessed.

Caution:Slower computers need several minutes to recreate remote folder files. Do not enable this option unless you have specific reasons for doing so.

a. SelectRe-Initialize the remote access folder prior to login.

The options belowRe-Initialize the remote access folder prior to loginactivate. b. Select the option that indicates the extent of the re-initialization in the remote access

folder at login.

To rebuild this Select this

All files in theRemotefolder Re-initialize all files in the remote folder Only FH system and user files Re-initialize system and user files only

(54)

7. SelectAutomatically download client program updates from the server on startup. Updates to the server are automatically downloaded to the client computer when the ver-sion of FH Enterprise on the client computer is older than the verver-sion of the FH SQL data-base on the datadata-base server.

8. (Optional) Change the connection information the client computer uses to connect to the database server.

a. ClickRemote Connection.

TheRemote Configurationdialog box appears, set to theConnectiontab.

b. Fill out the parameters in this dialog box, as directed inInstall FH Enterprise on a client computer, in step 22.

9. ClickOK.

A confirmation dialog box appears, indicating that you may need to exit and restart FH Enterprise.

10. ClickOK.

A second confirmation dialog box appears, directing you to exit and restart FH Enterprise.

11. ClickOK.

(55)

Check custom reports after upsizing

Note:If you did not upsize from FH Standard to FH Enterprise, you can skip the steps below. Standard FH and FH Enterprise support ANSI standard Structured Query Language (SQL) com-mands. While SQL is an ANSI standard, some products have their own versions of SQL imple-mentation, which translate and process SQL statements in different ways. Visual FoxPro uses a different version of SQL than SQL Server (used with FH Enterprise).

Queries used by reports to gather data are converted into SQL statements. The differences in SQL implementations between FH Standard and FH Enterprise can cause problems in custom reports after upsizing to FH Enterprise.

A list of FH Standard expressions and how they are converted for FH Enterprise is available in the Appendix of theFIREHOUSE Software Enterprise Upsizing Guide.

Note:Hand-coded queries that worked in FH Standard may not work at all in FH Enterprise. 1. Run your custom reports and verify whether or not they still function as expected. 2. (If they do not still function as expected) Contact FH technical support for assistance.

Update an existing installation of FH Enterprise

TheFIREHOUSE Software Enterprise Installation Guideis designed to help you install or update, launch, and configure new installations ofFIREHOUSE Software Enterprise. Inform-ation on updating your existing installInform-ation of FH Enterprise to a newer version is available in the FIREHOUSE Software Enterprise Update Guide, at

http://www.fire-housesoftware.com/pdf/FH7EnterpriseUpdate.pdf.

(56)

Backup and restore the FH Enterprise database

You must havesysadminaccess in SQL Server and administrator access in FH Enterprise to create and restore backups. You must also have an understanding of the SQL Server con-figuration, including a complete and accurate path to the device that will store the backup file.

Note:

l If you are using a Microsoft SQL Server Data Engine (MSDE), you can only restore the

backup to an MSDE server. You cannot backup the database on a Microsoft SQL Server 7 server and restore the database to an MSDE server.

l You cannot backup or restore from a network drive. The file must be located on the local

server drive itself for backup or restore to proceed correctly.

l If you backup repeatedly to the same file, the information appends to the existing file by

default, and the file size grows extremely quickly. In this case, you should backup to a tape drive.

1. ChooseStart → Programs → FIREHOUSE Software → FIREHOUSE Software Backup Utility.

TheLogin Required - FIREHOUSE Softwaredialog box appears.

2. Enter the administrative username and password for FH Enterprise in theLogin Required - FIREHOUSE Softwaredialog box, and then clickOK.

(57)

TheBackup/Restore - FIREHOUSE Softwaredialog box appears, displaying the Remote Backup/Restoretab.

3. Continue with one of the following.

l Backup your FH Enterprise database, on page 52. l Restore an FH Enterprise database, on page 53.

(58)

Backup your FH Enterprise database

1. (If you have not done so already) Open theBackup/Restore - FIREHOUSE Software dialog box, as described inBackup and restore the FH Enterprise database, on page 50.

2. UnderBackup To, check the backup device listed.

3. (If the displayed listing isNo Backup Devices Found, or if the backup device is not lis-ted in the drop-down menu) Do the following.

a. Click Manage Backup Devices.

TheRemote Backup Devicesdialog box appears.

b. ClickAdd Backup Device.

TheAdd Remote Backup Devicedialog box appears.

c. InDevice Name, type the name of the device to back up the SQL Server database to.

Note:Spaces are not allowed in the device name.

d. InDevice Path and Filename, type the complete path and file name relative to the SQL Server database.

(59)

The new device appears in theRemote Backup Devicesdialog box.

Note:If you remove a backup device later, the file is not physically removed. If you add the same backup device back again, and if the file has not been deleted in the interim, they will be available again.

f. In theRemote Backup Devicesdialog box, clickOK.

The new device appears in theBackup Tomenu, and is selected by default. Caution:If your only backups are located on a hard drive and that hard drive crashes, you will lose access to the backup.

4. UnderBackup To, inName of Backup, type a name for the backup you are creating. 5. InDescription of Backup, type a description for the backup.

6. ClickOK.

Progress updates appear on your screen. This process may take some time if you have many records or a large database.

Restore an FH Enterprise database

1. (If you have not done so already) Open theBackup/Restore - FIREHOUSE Software dialog box, as described inBackup and restore the FH Enterprise database, on page 50.

2. SelectRestore From, and then select the backup device to pull the SQL Server data-base for FH Enterprise from.

3. UnderBackup to Restore, select a name for the backup you want to restore. 4. ClickOK.

Progress updates appear on your screen. This process may take some time if you have many records or a large database.

(60)

Troubleshooting your installation

If you encounter the following issues during your installation of FH Enterprise, you may be able to troubleshoot and correct them with this information.

Citrix and Terminal Services connection issues to FH Enterprise

Issue Citrix and Terminal Services allow multiple sessions of FH to share a

single Windows registry. Problems may occur when multiple FH Enterprise sessions attempt to use a single Windows registry.

Example:The station defaults to the same station, because all workstations appear to be the same to FH Enterprise.

Explanation FH.INFand a\Remotedirectory needs to be created and placed in the Windows directory for each user who uses FH Enterprise. CITRIX creates a unique Windows folder for each user session. When anFH.INFfile is available and located in the Windows folder for the user session, FH reads data paths (database, system, reports, queries, lookup) from theFH.INFfile. This lets multiple workstations use one configuration file while using different data paths.

Workaround Detailed setup instructions for Citrix and Terminal Services install-ations are available athttp://www.firehousesoftware.com/pdf/citrix_ setup.pdf.

Note:Information in theFH.INFfile supercedes registry or.INI

installation settings.

Connection issues between client computers and the database server

Issue You are having trouble connecting a client computer with the

data-base server.

Explanation A number of things outside of FH Enterprise can prevent a client com-puter from connecting with the database server. The following issues are the most common, and you can easily check for and correct them on your own.

Workaround If you have tried each of the solutions below and your client computer is still unable to connect to the database server, you should contact FH technical support for more assistance.

l Check network protocols, on page 55.

l Open a static port in the Windows firewall for TCP access,

on page 58.

l Open access to SQL Server when using dynamic ports, on

(61)

69.

Check network protocols

1. Log into the database server as an administrator.

2. ChooseStart → Programs → Microsoft SQL Server → Configuration Tools → SQL Server Configuration Manager.

TheSQL Server Configuration Managerdialog box appears.

3. In the left pane, expandSQL Server Network Configuration. 4. In the left pane, clickProtocols forSQL instance name.

The right pane updates with protocol information.

5. Right-clickTCP/IP, and then chooseProperties.

(62)

TheTCP/IP Propertiesdialog box appears.

6. (IfEnabledis set toNo) ClickNo, and then selectYesfrom the menu that appears. 7. Click theIP Addressestab.

8. For the section containing the IP address of the database server, verify thatActiveand Enabledare both set toYes.

(63)

9. (IfActiveand/orEnabledis set toNo) ClickNo, and selectYesfrom the menu that appears, so that both are set toYes.

10. InTCP Port, check the port number, and note it if it is anything other than1433. 11. Scroll down until you see theIPAllsection, and note the value inTCP Port.

Caution:The values in theIPAllsection override the port settings for all IP addresses in the dialog box. IfTPC Portin this section contains a port number that does not match the TCP port number from step 10, the database server and the client computer cannot communicate.TPC Portin this section is blank, the TCP port number from step 10 is used.

12. (If necessary) Change the port number in this section or in the IP section for the database server.

13. ClickOK.

A confirmation dialog box appears.

14. ClickOK.

15. In the left pane, clickSQL Server Services.

(64)

The right pane updates to list all the SQL server services.

16. Right-click the name of your SQL Server service (instance), and then chooseRestart. A dialog box with a progress bar appears as the service is stopped and then started again, and then closes.

17. Close theSQL Server Configuration Managerdialog box.

Open a static port in the Windows firewall for TCP access

1. On the database server, chooseStart → Control Panel. TheControl Panelwindow appears.

(65)

TheWindows Firewalldialog box appears.

3. In the left pane, clickAdvanced settings.

The window refreshes to display a left, center, and right pane of advanced options.

4. In the left pane, clickInbound Rules.

(66)

The center and right panes refresh to display different options.

5. In the right pane, clickNew Rule.

TheNew Inbound Rule Wizardappears, set to theRule Typescreen.

(67)

TheProtocol and Portsscreen of the wizard appears.

7. Verify thatTCPandSpecific local portsare selected. 8. InSpecific local ports, type a port number.

Note:Port 1433 is used in most cases, and is the default port for SQL Server. 9. ClickNext >.

(68)

TheActionscreen of the wizard appears.

10. Verify thatAllow the connection is selected, and then clickNext >. TheProfilescreen of the wizard appears.

(69)

TheNamescreen of the wizard appears.

12. InName, type a name for the rule. Example:SQL1433Port

13. (Optional) InDescription, type additional information describing the rule you have set up. 14. ClickFinish.

15. Close theWindows Firewallwindow. 16. Close theControl Panelwindow.

(70)

Open access to SQL Server when using dynamic ports