PERVASIVE.SQL 7.0 Service Pack Installation Guide. For Windows NT

Transcription

1 PERVASIVE.SQL 7.0 Service Pack Installation Guide For Windows NT ebix.com makes every effort to verify that the information published in this guide is accurate. ebix.com reserves the right to modify or change the contents of this guide at any time, without any obligation to notify any person or entity of such changes. Revised 01/12/00

2 TABLE OF CONTENTS PRE-INSTALLATION CHECKLIST... 4 PART I - PERVASIVE SERVICE PACK SERVER INSTALLATION. 5 STEP STEP STEP STEP STEP STEP STEP STEP STEP STEP PART II - UPDATING FOLDERS ON SERVER... 9 STEP STEP STEP STEP PART III - PERVASIVE SERVICE PACK CLIENT REQUESTER INSTALLATION STEP STEP STEP STEP STEP STEP STEP STEP APPENDIX A: REMOVING OUTDATED VERSIONS OF BTRIEVE (VERSION 6.15 AND 6.10) FROM THE WORKSTATION APPENDIX B: HOW TO DETERMINE THE VERSION (BUILD NUMBER) OF THE EXISTING PERVASIVE SERVICE PACK PART 1 - CHECKING THE VERSION OF PERVASIVE SERVICE PACK ON A NT SERVER 16 STEP STEP STEP PART 2 - CHECKING THE VERSION OF PERVASIVE SERVICE PACK FOR THE CLIENT REQUESTER (WINDOWS 95/98 WORKSTATION) STEP STEP STEP APPENDIX C: HOW TO STOP AND START PERVASIVE (BTRIEVE) MICROKERNEL AND SCALABLE SQL ENGINES Page 2 of 27

3 PART 1 - STOPPING THE ENGINES STEP STEP STEP STEP STEP PART 2 - STARTING THE ENGINES STEP STEP APPENDIX D: PERVASIVE SQL SERVICE PACK 3 SERVER INSTALLATION STEP STEP STEP STEP STEP STEP STEP STEP APPENDIX E: PERVASIVE SERVICE PACK 3 CLIENT REQUESTER INSTALLATION STEP STEP STEP STEP STEP STEP STEP Page 3 of 27

4 PRE-INSTALLATION CHECKLIST Important - Perform a complete backup of your server prior to installing the Pervasive Service Pack. You should have at least NT Service Pack 3 for Windows NT 4.0 installed. To determine the version of NT Service Pack Double click on My Computer. Click on Help and select About Windows NT. The Pervasive Service pack installation will require a CD-ROM drive on the NT server. Determine where the Pervasive installation directories (BIN / Clients / Doc etc) are currently located on the NT server. The Pervasive installation directories are installed under PVSW by default (Example D:\PVSW). You should have only one PVSW folder on the NT file server. If you have installed Pervasive SQL 7 to the server more than once, you may have a duplicate PVSW folder perhaps on a different drive. It is recommended that you remove any duplicate PVSW folders. If you have a BTI folder on the NT server (Example D:\BTI), chances are you still have Btrieve version 6.15 installed. It is recommended that you delete the BTI folder from the server hard drive. Also it is recommended that you remove outdated Btrieve files from the workstations. (See APPENDIX A) Note: You may find the PVSW folder on your local workstations (C:\PVSW). This is the default folder for the Pervasive Client. Determine the version of Pervasive Service Pack installed. (See Part 1 of APPENDIX B) Note: If the current Pervasive Service Pack build number is 152, you have the final Pervasive Service Pack for SQL 7 installed. You do not need to apply any Pervasive Service Packs on the file server. However, you may still need to apply the Pervasive Client Service Pack on the workstations. (See Part 2 of APPENDIX B) Note: Pervasive Service Pack 3 includes Pervasive Service Pack 1 and Service Pack 2. Pervasive Service Pack 5 includes Pervasive Service Pack 4. For ebix.com technical support, pcanywhere32 Version 8.0 or later is required. It must be installed and tested on the server and on the administrative workstation. A 56k modem is required on the administrative workstation. No modem is required on the server though it is recommended. Page 4 of 27

5 PART I - PERVASIVE SERVICE PACK SERVER INSTALLATION Note: The procedure in PART I must be done at the NT server. Step 1 Have all users log out of ebix.one (cd.one) completely. Log onto your NT server as an Administrator. Stop the Btrieve Microkernel Engine and Scalable SQL on your server via Services in Control Panel. (See Part 1 of APPENDIX C) Place the ebix.com QMR Q4-99 disc in CD-ROM drive. Step 2 Click on Start and select Run. Click on the BROWSE button to locate the CD-ROM drive. Expand Pervasive Service Packs folder. Expand the NT folder. Double click on the Client folder. Copy SP3CLIENT.EXE and SP5CLNT.EXE to the PVSW folder on the Server. Step 3 Determine the Service Pack version (build number) if you have not already done so. (See Part 1 of APPENDIX B) If the current Service Pack build number is 112 or 132 go to Step 4 now. If the current Service Pack build number is less than 112, you must install Pervasive Service Pack 3 for the server prior to installing Service Pack 5 for the server. (See APPENDIX D) Step 4 Go back to the CD-ROM drive. Locate SP5NT_CI.EXE which is under Pervasive Service Packs \ NT \ Server folder. Double click on SP5NT_CI.EXE Step 5 Click on Setup. Page 5 of 27

6 Step 6 Click on Next. Step 7 Check and verify if the Pervasive installation path for the client components (PVSW) on the server is correct. If not click on Browse to change the Client path. Page 6 of 27

7 Step 8 Click on next. Note: If you forgot to stop Pervasive SQL (on Step 1), you may see the following window. Click on next to continue. Page 7 of 27

8 Step 9 Click on next. Step 10 Click Finish. Viewing the Report is usually not required unless there is a large number of Warnings (over five). Call ebix.one support if you do have a large number of Warnings. Page 8 of 27

9 PART II - UPDATING FOLDERS ON SERVER Step 1 Open the Microsoft Explorer (Right click on My Computer, Select Explore). Browse and expand the PVSW folder on the server drive. Hold down the Ctrl key then highlight Demodata and Sample folders in the Contents window. Step 2 Click on Edit and select Copy. Page 9 of 27

10 Step 3 Expand the Clients folder under PVSW then double click the Win32 folder. Step 4 Click on Edit and then select Paste Page 10 of 27

11 PART III - PERVASIVE SERVICE PACK CLIENT REQUESTER INSTALLATION Note: PART III must be done at EACH workstation. Step 1 Exit all Window programs before applying Pervasive Service Pack. At the workstation, click Start. Select Run. Browse and locate the PVSW folder on the server drive. Step 2 Determine the Service Pack version (build number) if you have not already done so. (See Part 2 of APPENDIX B) If the current Service Pack build number is 112 or 132 go to Step 3 now. If the current Service Pack build number is less than 112, you must install Pervasive Service Pack 3 Client Requester prior to installing Service Pack 5 Client Requester. (See APPENDIX E) Step 3 Double click on SP5CLNT.EXE found under the PVSW folder on the server. Page 11 of 27

12 Step 4 Click on Next. Step 5 Click on Next. Page 12 of 27

13 Step 6 Click on Next. Step 7 Click on Next. Page 13 of 27

14 Step 8 Click Finish. Viewing the Report is usually not required unless there is a large number of Warnings (over five). Call ebix.one support if you do have a large number of Warnings. Page 14 of 27

15 APPENDIX A: REMOVING OUTDATED VERSIONS OF BTRIEVE (VERSION 6.15 AND 6.10) FROM THE WORKSTATION Remove the following files from your workstation s C:\WINDOWS folder. BREQUEST.EXE MKDELINK.DLL WBTRTHNK.DLL W16NR.DLL BREQNT.EXE MKDESVCS.DLL WBTRVES.DLL W32BTICM.DLL OS2NWBRQ.DLL WBTRV32.DLL W32MKDE.EXE WBTRLOCL.DLL BTICOMM.DLL WBTRCALL.DLL WBTR32.EXE W32MKRC.DLL BTRCALLS.DLL WBTICOMM.DLL WBT32RES.DLL W32NR.DLL Note: Many, if not all, of these files are found in your C:\WINDOWS\SYSTEM folder. DO NOT REMOVE THEM. It is unlikely that you are currently using Btrieve Version But if you are, you will need to perform these additional steps: a) Use the Explorer to browse your C:\WINDOWS folder. b) Locate WINSTART.BAT. Highlight this file. c) Right click on WINSTART.BAT and choose edit. d) Delete the line(s) containing BREQUEST.EXE. e) From the File menu select Save. f) From the File menu select Exit. Page 15 of 27

16 APPENDIX B: HOW TO DETERMINE THE VERSION (BUILD NUMBER) OF THE EXISTING PERVASIVE SERVICE PACK Part 1 - Checking the version of Pervasive Service Pack on a NT Server Step1 At the NT server, click on Start. Select Programs. Select Command Prompt. Step2 At any DOS prompt type the following: BUTIL -VER (press Enter) You should see something similar to the following: The build number appears on the upper right. Step3 Use the following guideline for interpreting the most recent service pack installed Build 76 means the original install - No Service Pack installed. Build 92 means Service Pack 1 is installed (on the server). Build104 means Service Pack 2 is installed (on the server). Build 112 means Service Pack 3 is installed (on the server). Build 132 means Service Pack 4 is installed (on the server). Build 152 means Service Pack 5 is installed (on the server). Note: If the build number is 152, you do not need to apply any Pervasive Service Pack for the server. Page 16 of 27

17 Part 2 - Checking the version of Pervasive Service Pack for the Client Requester (Windows 95/98 workstation) Step1 At the workstation, click on Start. Select Programs. Select MS-DOS Prompt. Step2 At the DOS prompt type the following: BUTIL -VER (press Enter) You should see something similar to the following: Step3 Use the following guideline for interpreting the most recent service pack installed Build 76 means the original install - No Service Pack installed. Build 92 means Service Pack 1 is installed (on the workstation). Build104 means Service Pack 2 is installed (on the workstation). Build 112 means Service Pack 3 is installed (on the workstation). Build 132 means Service Pack 4 is installed (on the workstation). Build 152 means Service Pack 5 is installed (on the workstation). Note: If the build number is 152, you do not need to apply any Pervasive Service Pack for this workstation. Page 17 of 27

18 APPENDIX C: HOW TO STOP AND START PERVASIVE (BTRIEVE) MICROKERNEL AND SCALABLE SQL ENGINES. Note: The following steps must be done at the NT server. Part 1 - Stopping the engines Step 1 Click on Start. Select Settings. Select Control Panel. Double click on Services. Step 2 Highlight Btrieve 7.0 for Windows NT (Server Edition) then click on Stop. Step 3 Click on Yes. Page 18 of 27

19 The following message will appear briefly. Step 4 Scroll down and highlight Scalable SQL v4.0 for NT (Server Edition) then click on Stop. Step 5 Click on Yes. The following message will appear briefly. Page 19 of 27

20 Part 2 - Starting the engines Step 1 Highlight Btrieve 7.0 for Windows NT (Server Edition). Click on Start. The following message will appear briefly. Click on Close when the message disappears. Step 2 Scroll down and highlight Scalable SQL v4.0 for NT (Server Edition). Click on Start. The following message will appear briefly. Page 20 of 27

21 APPENDIX D: PERVASIVE SQL SERVICE PACK 3 SERVER INSTALLATION Note: The procedure in APPENDIX D must be done at the NT server. Step 1 Have all users log out of ebix.one (cd.one) completely Stop the Btrieve Microkernel Engine and Scalable SQL on your server via Services in Control Panel if you have not already done so. (See Part 1 of APPENDIX C) Step 2 Place the ebix.com QMR Q4-99 disc in CD-ROM drive. Click on Start and select Run. Click on the BROWSE button to locate the CD-ROM drive. Expand Pervasive Service Packs folder. Expand the NT folder. Double click on the Server folder. Double click on SP3NT_CI.EXE Step 3 Click on Setup. Page 21 of 27

22 Step 4 Click on Next. Step 5 Verify the Clients path for the existing Pervasive installation on the NT server is correct. Click on Next. Page 22 of 27

23 Step 6 Click on Next. Note: If you have not stopped the Btrieve Microkernel and Scalable SQL Engines (See Part I of APPENDIX C), you will see the following Window. Click Next to continue Page 23 of 27

24 Step 7 Click Next. Step 8 Click Finish. Viewing the Report is usually not required unless there is a large number of Warnings (over five). Call ebix.one support if you do have a large number of Warnings. Page 24 of 27

25 APPENDIX E: PERVASIVE SERVICE PACK 3 CLIENT REQUESTER INSTALLATION Note: Apply the Pervasive Service Pack 3 client requester only if the current Service Pack build number on the workstation is less than 112. (See Part 2 of APPENDIX B) If you have not installed the Pervasive Service Pack 3 for the server, you must install it prior to installing the Pervasive Service Pack 3 client requester. Step 1 Exit all Window programs prior to applying Pervasive Service Pack. At the workstation, click Start. Select Run. Browse and locate the PVSW folder on the server drive. Double click on SP3CLIENT.EXE under the PVSW folder on the server. Step 2 Click on Setup. Step 3 Click on Next. Page 25 of 27

26 Step 4 Click on Next Step 5 Click on Next Page 26 of 27

27 Step 6 Click on Next Step 7 Click Finish. Viewing the Report is usually not required unless there is a large number of Warnings (over five). Call ebix.one support if you do have a large number of Warnings. Page 27 of 27