Frequently Asked Questions -
HealthOffice® Installation And Setup

Why is my MS-SQL/MSDE not installing correctly?
My client software is installed. Why am I unable to log in successfully?
I've installed an MS-SQL service pack. Why can't I login successfully from the client software?
I'm having problems with the data import process. What can I do to help the process?
Are there any conflicts between HealthOffice and Microsoft XP Service Pack 2?

Additional Questions or concerns: 1-800-732-7317 or email us at info@healthmaster.com

The Answers

Why is my MS-SQL/MSDE not installing correctly?

[A.] Verify on WinNT/2K/XP that an administrator level login is used to install the MS-SQL/MSDE program.

[B.] Verify the computer name. The MS-SQL/MSDE program takes its name from the computer. Characters following the first character can include letters, numbers, or the symbols #, $, or _. No embedded spaces are allowed

[C.] Verify that the HealthOffice Enterprise installation CD is readable. If it is not, call Healthmaster Customer Support for a new CD.

[D.] Verify that there is enough disk space on the system for the installation. (Approx. 60MB)

[E.] Verify that the TCP/IP network protocol is installed. If there is no network adapter installed on the system, then install either the dial-up adapter or the Microsoft Loop back adapter - which is just a dummy driver, no hardware involved.

[F.] Microsoft Client for Networks must be installed on Windows 9x/ME.

[G.] Because a named-pipe, used by the set-up routine, is effectively a file as far as the operating system is concerned, real-time Virus scanners can cause problems. Most of these have been fixed so they don't interfere with SQL's named-pipes, but make sure you're running the latest version of whichever virus package you use. But if in doubt, then disable the virus software for the duration of the install.

[H.] Verify the computer chipset. Older Cyrix/IBM chips that do not support the full Pentium instruction set will not work.

[I.] Verify the system has the latest Microsoft Scripting Engine (except WinXP). (As of 10/18/2001, Version 5.6)

My client software is installed. Why am I unable to log in successfully?

[A.] Verify that the MS-SQL/MSDE service is running. The client login component does not have the ability to start SQL in all operating systems. If MS-SQL/MSDE is not running, then the service can be started by using the Service Manager.

[B.] A general rule with the login is if the message from the login appears immediately after selecting the OK button, then the system is communicating with the server. This leaves either the login/password combination as being incorrect, or the system is not being authenticated to the MS-SQL Server. If the message takes more than 20 seconds to appear, then the client is not communicating with the MS-SQL Server correctly. Use the remaining checks in this section for a resolution.

[C.] Verify that the client machine is able to successfully ping the server system. This can be accomplished with the DOS command line utility or with the Healthmaster SQL Port Scan Utility:
http://www.healthmaster.com/downloads.cfm

[D.] Verify that the SQL Server has been registered on the client system by using the Healthmaster Server Register Utility.

[E.] Reinstall MDAC 2.6 SP1. This can be found on the HealthOffice Enterprise installation CD or by downloading it from microsoft.com at: http://www.microsoft.com/data

[F.] Verify whether the MS-SQL server machine is registered in the client system HOSTS file. On Win9X/ME system, the HOSTS file is located in the \Windows folder. On WinNT/2K/XP systems, the HOSTS file is located in the \Windows\System32\Drivers\etc folder. The format of the file is: {IP Address}space{Machine Name}. Most existing systems have a HOSTS file already created or a sample HOSTS file name hosts.sam.
****************************************************************************************************
IMPORTANT:
It is important to note that HealthOffice Enterprise will no longer query any DNS servers for information about a server or domain if it appears in the hosts file. If the IP address of the MS-SQL server changes, HealthOffice Enterprise will continue to attempt connection to the IP address listed in the HOSTS file
****************************************************************************************************

[G.] HealthOffice Enterprise was set up to use the TCP/IP protocol in conjunction with MS-SQL Server on port 1433. Verify all network devices are blocking or rerouting traffic on this port. These devices would include router, gateways, managed switches, etc.

[H.] If there are still problems with the login after this point, then a call to Healthmaster Technical Support may be necessary.

I've installed an MS-SQL service pack. Why can't I login successfully from the client software?

[A.] The #1 cause this problem is due to the wrong authentication mode being selected during the service pack installation. Only SQL Authentication or Mixed Mode Authentication should be picked. By selecting any other authentication mode, the HealthOffice Enterprise software will be unable to gain sufficient server permissions for a database connection.

[B.] There are two ways to change the authentication mode.
(1)The first is to backup all HealthOffice Enterprise databases and uninstall the MS-SQL/MSDE software. The reinstallation of the MS-SQL/MSDE will reset the authentication mode.
(2)The second is to change the registry settings of MS-SQL Server. Navigate the registry editor to the key HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode\ A value of 1 will set the system for NT/Windows authentication and a value of 2 will set the system for SQL/Mixed Mode authentication. The value of 2 is desired.

I'm having problems with the data import process. What can I do to help the process?

[A.] The data import process can import delimited and fixed width ASCII files. Each row in the file is equivalent to a single student record. Each row needs to be properly ended with a CRLF (Carriage Return/Line Feed). Without the CRLF, the program will usually give an error that relates to the records exceeding the length limit. The common file format is comma delimited. It seems to be the easiest to work with. The file can be easily opened in Microsoft Excel for easy data editing. *Note*: Watch out for the zip code field. Excel will strip any leading zeros in the zip code.

[B.] The data import process is two steps. The first step defines which fields in the ASCII data file relates to a particular field in the HealthOffice database. The second step does the actual processing of the records into the system.

[C.] The import process makes an attempt to match-up student records based upon the following criteria:
·Student SSN
·Student ID
·Student First Name, Last Name, Middle Name,Birthdate

If these criteria do not match successfully, then the process generates a new student record.

[D.] The import process makes an attempt to match-up contact records based upon the following criteria:
·Contact SSN
·Contact ID
·Contact First Name, Last Name, Phone Number

If these criteria do not match successfully, then the process will generate a new contact record and connect it to the student record.

[E.] The import process allows for a student to be matched with a particular school in the system by matching the student import field called “SchoolID” to the school ID field that can be managed by accessing the school information from the Manage Schools screen.

[F.] The data import process requires the following fields in order to import or update a student record:
·First Name
·Last Name
·Grade
·Birth date

[G.] The grade fields are matched up by either number or by the first letter of the grade, i.e. HealthOffice grade “4” would match to a grade field in the data file of either “04” or “4”. HealthOffice grade “Preschool” would match to a grade field in the data file of either “Preschool” or “P”.
****************************************************************************************************
Note: The only exception is when dealing with Kindergarten1 and Kindergarten2. A grade data field that starts with just “K” would match to HealthOffice grade field “Kindergarten1”. A data field grade field that starts with a “K” but includes a “2”, will match to the HealthOffice grade field “Kindergarten2”.
****************************************************************************************************

Are there any conflicts between HealthOffice and Microsoft XP Service Pack 2?

Yes.

We are aware of an issue relating to the new Security Center - Windows Firewall. By default, the firewall is installed and active. This firewall will block the networking required to run the HealthOffice program and SQL/MSDE.

If you would like to keep the firewall active on the system, you only need to create an exception for Port 1433. The other option is to disable the firewall all together.

**NOTE**
Port 1433 is the default port during the installation of SQL Server and MSDE. If another port is being used for SQL/MSDE, please substitute 1433 for your active port in the following instructions.

------------------------------------------
Add Port Instruction Overview
------------------------------------------
1. Open Windows Firewall. (Start Button\Control Panel\Windows Firewall) 2. Click on the Exceptions tab at the top of the window.
3. Click on the Add Port button.
4. Type in “MSSQLSERVER” as the Name and “1433” for the Port Number.
5. Click OK.