Sunteți pe pagina 1din 26
PERVASIVE.SQL 7.0 SERVICE PACK INSTALLATION GUIDE For Novell NetWare ebix.com makes every effort to verify

PERVASIVE.SQL 7.0 SERVICE PACK INSTALLATION GUIDE

For Novell NetWare

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

TABLE OF CONTENTS

PRE-INSTALLATION CHECKLIST

4

PART I - PERVASIVE SERVICE PACK SERVER INSTALLATION

5

PRE-INSTALLATION PROCEDURE

5

STEP 1

5

STEP 2

5

STEP 3

5

STEP 4

5

STEP 5

5

STEP 6

6

STEP 7

6

STEP 8

7

STEP 9

8

STEP 10

8

PART II - UPDATING FOLDERS ON SERVER

9

STEP 1

9

STEP 2

9

STEP 3

10

STEP 4

10

PART III - PERVASIVE SERVICE PACK CLIENT REQUESTER INSTALLATION

11

STEP 1

11

STEP 2

11

STEP 3

11

STEP 4

11

STEP 5

12

STEP 6

12

STEP 7

13

STEP 8

13

APPENDIX A: REMOVING OUTDATED VERSIONS OF BTRIEVE (VERSION 6.15 AND 6.10)15

APPENDIX B: HOW TO DETERMINE THE VERSION (BUILD NUMBER) OF THE EXISTING PERVASIVE SERVICE PACK

16

PART 1 - CHECKING THE VERSION OF PERVASIVE SERVICE PACK ON THE FILE SERVER

16

STEP1

16

STEP2

16

STEP3

16

PART 2 - CHECKING THE VERSION OF PERVASIVE SERVICE PACK FOR THE CLIENT REQUESTER (WINDOWS 95/98 WORKSTATION)

17

STEP1

17

STEP2

17

STEP3

17

APPENDIX C: HOW TO STOP, RELOAD AND CHANGE FILE ATTRIBUTE OF PERVASIVE (BTRIEVE) AND SCALABLE SQL MODULES

18

PART 1 - STOPPING THE MODULES

18

STEP1

18

STEP2

18

PART 2 - RELOADING THE MODULES (AFTER APPLYING THE PATCHES)

18

STEP1

18

Page 2 of 26

STEP2

18

PART 3 VERIFYING AND CHANGING (IF NEEDED) THE FILE ATTRIBUTE OF THE BTRIEVE AND SQL MODULES

19

STEP 1

19

STEP 2

19

STEP 3

19

STEP 4

19

STEP 5

19

APPENDIX D: PERVASIVE SQL SERVICE PACK 3 SERVER INSTALLATION

20

STEP 1

20

STEP 2

20

STEP 3

20

STEP 4

21

STEP 5

21

STEP 6

22

STEP 7

23

STEP 8

23

APPENDIX E: PERVASIVE SERVICE PACK 3 CLIENT REQUESTER INSTALLATION

24

STEP 1

24

STEP 2

24

STEP 3

24

STEP 4

25

STEP 5

25

STEP 6

26

STEP 7

26

Page 3 of 26

PRE-INSTALLATION CHECKLIST

Important - Perform a complete backup of your server prior to installing the Pervasive Service Pack on the NetWare server.

Check if you have the latest NetWare Support Pack installed. You may download the

Support Pack from the Novell web site. (http://support.novell.com/misc/patlst.htm)

A qualified Novell administrator or engineer should do this.

The Pervasive Service pack installation will require a CD-ROM drive on the administrative workstation.

Determine where the Pervasive installation directories (BIN / Clients / Doc…etc) are currently located on the server drive. The Pervasive installation directories are installed under PVSW by default (Example F:\PVSW). You should have only one PVSW folder on the NetWare 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 server drive. It is recommended that you remove any duplicate PVSW folders on the same server. You may find PVSW on your local workstation (C:\PVSW). This is the default folder for the Pervasive client.

If you have a BTI folder on the server (Example F:\BTI), chances are you still have

Btrieve version 6.15 installed. It is recommended that you remove all the old Btrieve files from both the file server and the workstations. (See APPENDIX A)

Determine the version (build number) of Pervasive Service Pack currently installed on the server. (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.

Check and make sure the file attribute of the Pervasive modules (NLMs) is not read- only. (See Part 3 of APPENDIX C)

For ebix.com technical support, pcANYWHERE32 Version 8.0 or later is required. It must be installed and tested on the administrative workstation. A 56k modem is required on the administrative workstation.

Page 4 of 26

PART I - PERVASIVE SERVICE PACK SERVER INSTALLATION

Pre-installation procedure

Stop the Btrieve and Scalable SQL modules. (See Part 1 of APPENDIX C)

Note: The rest of the steps in PART I must be done at the administrative workstation.

If you have not already done so, check and make sure that the file attribute of the Pervasive modules is not read-only. (See Part 3 of APPENDIX C)

Step 1

Have all users log out of ebix.one (cd.one) completely.

Log onto the network as an Administrator or someone with Supervisor RIGHTS.

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 the Pervasive Service Packs folder. Expand the Novell folder. Double click on the Client folder.

Copy SP3CLIENT.EXE and SP5CLNT.EXE to the PVSW folder on the Server.

Step 3

Note: You should have already determined the Service Pack version (build number) installed on the file server. (See PRE-INSTALLATION CHECKLIST)

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 (See APPENDIX D) prior to installing Service Pack 5 for the server.

Step 4

Locate SP5NW_CI.EXE on the CD-ROM drive under Pervasive Service Packs \ Novell \ Server folder.

Double click on SP5NW_CI.EXE

Step 5

Click on Setup.

Pervasive Service Packs \ Novell \ Server folder. • Double click on SP5NW_CI.EXE Step 5 Click

Page 5 of 26

Step 6

Click on Next.

Step 6 Click on Next. Step 7 Check and verify if the Pervasive installation path (PVSW)

Step 7

Check and verify if the Pervasive installation path (PVSW) on the server is correct. It should be F:\PVSW. If not click on Browse to change it to the “Client Path”.

on the server is correct. It should be F:\PVSW. If not click on Browse to change

Page 6 of 26

Step 8

Click on next.

Step 8 Click on next. Note: This is a reminder to stop Pervasive modules. (See Part

Note: This is a reminder to stop Pervasive modules. (See Part 1 of APPENDIX C) Click on next to continue.

Note: This is a reminder to stop Pervasive modules. (See Part 1 of APPENDIX C )

Page 7 of 26

Step 9

Click on next.

Step 9 Click on next. Step 10 Click Finish. Viewing the Report is usually not required

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.

is a large number of Warnings (over five). Call ebix.one support if you do have a

Page 8 of 26

PART II - UPDATING FOLDERS ON SERVER

Note: The steps in PART II must be done at the administrative workstation.

Step 1

Open the Microsoft Explorer (Right click on My Computer. Select Explore).

Browse and expand the PVSW folder on the server (F:\PVSW).

Hold down the Ctrl key then highlight Demodata and Sample folders in the Contents window.

key then highlight Demodata and Sample folders in the Contents window. Step 2 Click on Edit

Step 2

Click on Edit and select Copy.

key then highlight Demodata and Sample folders in the Contents window. Step 2 Click on Edit

Page 9 of 26

Step 3

Expand the Clients folder under PVSW then double click the Win32 folder.

Step 4

Click on Edit and then select Paste. Click on View and select Refresh. You should now find Demodata and Samples folders under the Win32 folder.

Click on View and select Refresh. You should now find Demodata and Samples folders under the

Page 10 of 26

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 on Start. Select Run. Browse, locate and click the PVSW folder on the server (F:\PVSW).

Step 2

Determine the Pervasive Service Pack version (build number) on the workstation. (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 installing Service Pack 5 Client Requester. (See APPENDIX E)

Step 3

Double click on SP5CLNT.EXE found under the PVSW folder on the server. Click on Setup.

click on SP5CLNT.EXE found under the PVSW folder on the server. Click on Setup. Step 4

Step 4

Click on Next.

Page 11 of 26

Step 5 Click on Next. Step 6 Click on Next. Page 12 of 26

Step 5

Click on Next.

Step 5 Click on Next. Step 6 Click on Next. Page 12 of 26

Step 6

Click on Next.

Page 12 of 26

Step 7 Click on Next. Step 8 Click Finish. Viewing the Report is usually not

Step 7

Click on Next.

Step 7 Click on Next. Step 8 Click Finish. Viewing the Report is usually not required

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 13 of 26

Page 14 of 26

Page 14 of 26

APPENDIX A: REMOVING OUTDATED VERSIONS OF BTRIEVE (VERSION 6.15 AND 6.10)

Note: There is no uninstall program to uninstall Btrieve 6.10 or 6.15. The outdated files have to be removed manually.

From the workstation, locate and delete the BTI folder on the file server. (F:\BTI)

Use the Find utility to search for files listed below. (Click on Start. Select Find, then go to Files or Folders.)

Remove all the following files on the file server’s PUBLIC folder (F:\PUBLIC). Also find and remove any of those files found on the workstation’s C:\WINDOWS folder.

BREQNT.EXE

PBROLL.EXE

WBTICOMM.DLL

BREQUEST.EXE

W16NR.DLL

WBTRCALL.DLL

BREQUTIL.EXE

W32BTICM.DLL

WBTRTHNK.DLL

BROLLFWD.EXE

W32NR.DLL

WBTRV32.DLL

DBU_UI.DLL

W32RQCFG.EXE

WBTRVRES.DLL

NWIPXSPX.DLL

WBROLL.EXE

NWLOCALE.DLL

WBROLLRS.DLL

Note: Many, if not all, of these files are found in your C:\WINDOWS\SYSTEM folder. DO NOT REMOVE THEM from C:\WINDOWS\SYSTEM folder

If you are currently using Version 6.10 you will need to perform these additional steps:

a) Use Microsoft 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 26

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 the file Server

Step1

Go to the file server or use RCONSOLE to access the server’s System Console prompt.

Step2

At the System Console prompt, type the following then press Enter:

load butil –ver /s

Look for Build number to the right of BTUIL.NLM v7.0.0 You should see something similar to the following.

v7.0.0 You should see something similar to the following. Step3 Use the following guideline for interpreting

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 26

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 then press Enter.

BUTIL –VER

The build number is on the upper right. You should see something similar to the following:

right. You should see something similar to the following: Step3 Use the following guideline for interpreting

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 26

APPENDIX C: HOW TO STOP, RELOAD AND CHANGE FILE ATTRIBUTE OF PERVASIVE (BTRIEVE) AND SCALABLE SQL MODULES.

Part 1 - Stopping the modules

Step1

Go to the file server or use RCONSOLE to access the server’s System Console prompt.

Step2

At the System Console prompt type the following:

SQLSTOP (press Enter) BSTOP (press Enter) You should see something similar to the following.

Enter) You should see something similar to the following. Part 2 - Reloading the modules (after

Part 2 - Reloading the modules (after applying the patches)

Step1

Go to the file server or use RCONSOLE to access the server’s System Console prompt.

Step2

At the System Console prompt type the following:

SQLSTART (press Enter)

Note: You do not need to type BSTART, the BSTART command is included in SQLSTART command.

Page 18 of 26

Part 3 – Verifying and changing (if needed) the file attribute of the Btrieve and SQL modules

Step 1

At the workstation, log onto the network as an Administrator or someone with Supervisor RIGHTS.

Step 2

Click on Start. Select Programs. Select MS-DOS Prompt.

Step 3

At the DOS prompt, type F: (Press Enter) then type CD\SYSTEM (Press Enter)

Step 4

Type FLAG BTRIEVE.NLM (Press Enter) If you see “Ro” (readonly) in the square bracket [Ro], go to step 5. If you see “Rw” (readwrite) in the square bracket [Rw], skip step 5.

Step 5

Type FLAG BTRIEVE.NLM +RW SUB (Press Enter) Repeat step 5 with rest of the NLMs listed below – substitute BTRIEVE.NLM with the ones listed below. BREBUILD.NLM BROUTER.NLM BSPXCOM.NLM BSTART.NCF BSTOP.NCF BTCPCOM.NLM BTIMSG.NLM BUTIL.NLM NWBSRVCM.NLM NWINSEP.NLM NWINSIB.NLM

NWINSS2.NLM

NWMKDE.NLM

NWSSRVCM.NLM

NWUCINIT.NLM

NWUCMGR.NLM

NWUCUTIL.NLM

RIUTIL.NLM

SQLSTART.NCF

SQLSTOP.NCF

SQLUTIL.NLM

SSPXCOM.NLM

SSQL.NLM

STCPCOM.NLM

Page 19 of 26

APPENDIX D: PERVASIVE SQL SERVICE PACK 3 SERVER INSTALLATION

Step 1

Have all users log out of ebix.one (cd.one)

Stop the Pervasive (Btrieve) and Scalable SQL modules on the server . (See Part 1 of APPENDIX C)

If you have not already done so, check and make sure that the file attribute of the Pervasive modules is not read-only. (See Part 3 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 Novell folder.

Click on the Server folder.

Double click on SP3NW_CI.EXE

Step 3 Click on Setup.

Novell folder. • Click on the Server folder. • Double click on SP3NW_CI.EXE Step 3 Click

Page 20 of 26

Step 4

Click on Next.

Step 4 Click on Next. Step 5 Verify the Clients path for the existing Pervasive installation

Step 5

Verify the Clients path for the existing Pervasive installation on the Novell server is correct. It should be F:\PVSW. If not click on Browse to change it to the correct path. Click on Next.

is correct. It should be F:\PVSW. If not click on Browse to change it to the

Page 21 of 26

Step 6

Click on Next.

Step 6 Click on Next. Note: This is a reminder to stop Pervasive modules. (See Part

Note: This is a reminder to stop Pervasive modules. (See Part 1 of APPENDIX C) Click on next to continue.

Note: This is a reminder to stop Pervasive modules. (See Part 1 of APPENDIX C )

Page 22 of 26

Step 7

Click Next.

Step 7 Click Next. Step 8 Click Finish. Viewing the Report is usually not required unless

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.

is a large number of Warnings (over five). Call ebix.one support if you do have a

Page 23 of 26

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 (F:\PVSW).

Double click on SP3CLIENT.EXE under the PVSW folder on the server.

Step 2

Click on Setup.

click on SP3CLIENT.EXE under the PVSW folder on the server. Step 2 Click on Setup. Step

Step 3

Click on Next.

click on SP3CLIENT.EXE under the PVSW folder on the server. Step 2 Click on Setup. Step

Page 24 of 26

Step 4

Click on Next

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

Step 5

Click on Next

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

Page 25 of 26

Step 6

Click on Next

Step 6 Click on Next Step 7 Click Finish. Viewing the Report is usually not required

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.

is a large number of Warnings (over five). Call ebix.one support if you do have a

Page 26 of 26