Cannot open SQL server

Problems printing non-datapiped reports in Accpac Advantage Series 5.2

The following error is returned:

Description: Cannot open SQL server

All databases in 5.2 use DSNs.  The problem occurs when multiple database types are used and the same database IDs' exist.

Example.  A Saminc and a Samsys DSN already exist on a machine from a DB2 install.  When the client accesses a Saminc database for Pervasive, a  Saminc and a Samsys DSN will be created for Pervasive on the same machine.  This creates duplicate DSNs on that machine and the above error will occur.

Remove the duplicate DSNs from Datasource (ODBC) setup.  If the database does exist with the same name for both types of databases, ie.  Pervasive and DB2, then use DBDump and DBLoad for one of them to a different database ID.

Error "A Strong SA Password is Required for Security Reasons" When Trying to Install MSDE

When trying to install MSDE included with Sage Accpac HRMS, the following error may occur:

"A strong SA password is required for security reasons. Please use SAPWD switch to supply the same. Refer to readme for more details. Setup will no exit."

The installation then terminates.This error normally occurs on Windows Server editions, but may also occur on Windows XP.

Follow the steps below to setup MSDE manually:

1. From the Start Menu, select Run...
2. In the Run dialog box, type in "cmd" and click OK.
3. Complete the following commands, pressing the Enter key after each command:

• "x:" (where x is the CD Drive where the HRMS CD is inserted)
• "cd\msde2000"
• "setup SAPWD="password" INSTANCENAME="name" SECURITYMODE=SQL (where password is the password you choose and name is the identifier which you choose to call the MSDE installation) (NOTE: the password must be a strong password, meaning it must contain both numbers and letters).

During the Accpac database setup, the login information will be as follows (unspecified fields can be left with their default values):

Server Name: \
User Name: sa
Password:

"Violation of PRIMARY KEY constraint 'ICUNIT_KEY_0'" when performing a DBload of data into MS-SQL

When importing data through DBLoad into a new Microsoft SQL database, the following error may  occur:

INSERT (error = 127, native code = 2627) message: [Microsoft][ODBC SQL Server Driver][SQL Server]Violation  of PRIMARY KEY constraint 'ICUNIT_KEY_0' Cannot insert duplicate key in object 'ICUNIT'

This  error is not evident performing the same procedure in an environment running another database engine such as Pervasive. This problem may be related to an incorrectly defined Sort Order or Collation Name in the setup of the Microsoft SQL database.

To correct this problem, do the following:

Set Sort order to Case Insensitive
Set collation name to Latin_general_bin