SalesLogix Technical Support Knowledge Base

Error Messages & What They Mean

System Level

Error:
Can not run a Windows 16 bit application.
Resolution:
This error pertains to installing SalesLogix on a Windows NT 4.0 server that does not have NT Service Pack 2.0 installed. Therefore, the registry does not support 32-bit long file names which is required for any true 32-bit application such as SalesLogix. At least Service Pack 2.0 for Windows NT needs to be installed on the server (Service Pack 3.0 for Windows NT would also suffice). This upgrades the registry on the Windows NT server to 32-bit, allowing SalesLogix to be successfully installed.

Error: 
A Database error occurred. Unexpected end of command. Token line #2
Resolution:
The executable that was being used when this error came up is corrupt and needs to be re-placed.

Error:
A Database error occurred. Can not find table TABLENAME. (Where TABLENAME is the name of a table such as SYNCSITEOPTS or SECPROFILE.)
Resolution #1:
There is a version mismatch between the database schema and the executables. Namely, the executables are lower than Version 2.10 and the database has already been upgraded to Version 2.1x. Upgrading the executable to Version 2.10 or higher should resolve this issue.
Resolution #2:
If this error message appears when attempting to log onto a Remote User's Local Database, it is possible that the table mentioned does not exist in this database's schema. This occurs when an entry for this table does not exist in the SECTABLEDEFS or RESYNCTABLEDEFS tables of the Main Host Database. First, use DB Explorer against the Remote User's Local Database to see if the mentioned table exists. After confirming that it does not, use DB Explorer against the Main Host Database to check for the entries in the SECTABLEDEFS and RESYNCTABLEDEFS tables. If they do not exist, call SalesLogix Technical Support or your SalesLogix Certified Business Partner for guidance on inserting them.

Error: 
Error opening Database: This is not a SalesLogix Database...
Resolution: 
The Workgroup Administrator is open and changes are being made to the USERINFO table. Closing the Workgroup Administrator will resolve this issue.

Error:
A Database error occurred. Unable to connect. GDS32.dll error.
Resolution:
This error indicates that the SalesLogix component is having problems locating InterBase on the server containing the database. Make sure that InterBase is running (as an application or a service) on the database server. Double check the Borland Database Engine (BDE) configuration utility alias to make sure that the SERVER NAME parameter is configured correctly. See the section on Troubleshooting Network Communications for more details.

Error:
Database error: Concurrent update detected. Check you driver flags parameter.
Resolution:
For an InterBase database, open the Borland Database Engine (BDE) configuration utility and click the Drivers Tab. Select InterBase from the list of Driver Names and scroll through the list of Parameters until you see the Driver Flags parameter. Make sure that this is set to 512. 
If this is already set to 512 or if the database platform is something other than InterBase and you are still seeing the error above, it means that there is a deadlock. These deadlocks usually occur if the Architect is open at the same time as one of the other SalesLogix components with the same UserID. Closing one of the other applications should resolve the issue.

The Full Copy utility

Error:
Table not found...
Resolution:
The MS SQL Server is configured to use NT Integrated security which causes it to bypass the local MS SQL Server security and use the Windows NT network level security. This means that the BDE is unable to find the tables pertaining to SalesLogix when it tries to connect to MS SQL Server since SYSDBA, the owner of these tables, is not a valid Windows NT network account. Therefore, the MS SQL Server security configuration needs to be changed to either Standard security or Mixed Security. This is done in the SQL Enterprise Manager in the Security tab of the Configure SQL Server dialog box.

Component Level

The Workgroup Administrator

Error: 
TSYSINFO exception in module Admin.exe at Address 00. Error creating data dictionary. No tables processed.
Resolution: 
This error only appears when using MS SQL Server as the database platform and implies that the SYSDBA user has not been correctly registered within the MS SQL Server system tables (ex: SYSUSER, SYSINFO). It could also point to other problems within MS SQL Server. Therefore, the only known resolution to this issue is to re-install MS SQL Server.

The SalesLogix Database Manager

Error:
General SQL error: Alter table only allows columns to be added...
Resolution:
This error pertains to adding fields in the SalesLogix Database Manager when using MS SQL Server as the database platform. Open the SQL Enterprise Manager and select the database set up for SalesLogix. Click the right mouse button and select Edit from the shortcut menu. Go to the Options tab and make sure that the Columns null by default option is selected.

The Synchronization Server

Error:
Unknown UserName or Password. Alias: dbSyncLog.db
Resolution #1:
InterBase is not running on the Sync Server. 
If InterBase is running as an application: check the Windows system tray for the InterBase  icon. The InterBase executable is located in Program Files\Borland\InterBase\Bin on your hard drive. Double-click the  icon to manually launch InterBase.
If InterBase is running as a service: check Services in the Control Panel for the status of InterBase Server. If it is stopped, re-start the service manually.
Resolution #2: 
The Sync Server executables have been physically moved from their originally installed location. All traces of the SalesLogix Sync Server must be removed (including the registry) and the product then needs to be re-installed.

Error:
This database does not contain a valid SyncServer license number. Please properly configure before use.
Resolution #1:
You have not entered the license number for the Synchronization Server into the database through the Workgroup Administrator. This needs to be in place before the Sync Server can be launched. To check this, open the Workgroup Administrator while making sure that the Database Alias listed in the Login Dialog is SalesLogix. Once the Workgroup Administrator is open, click the System icon on the navigation bar and select the License Tab. If no Sync Server license is present, click the right mouse button (RMB) and select Add from the short cut menu. Then enter the license number for the Sync Server and click Okay.
Resolution #2:
If you have already entered a valid Sync Server license number into the database with an alias of SalesLogix but the error still appears, the site code for the Sync Server machine may not be correct. To resolve this, open the directory where SalesLogix is installed and look for the SalesLogix.key file. This is a hidden system file so if you don't see it, select Options from the View menu of Explorer and make sure that the Show all files option is selected. Open the SalesLogix.key file with Notepad and look at the line denoted by Site Code. Delete the value that appears after the equals sign - this will enable the Sync Server to re-set the site code correctly. Save these changes and close the key file. You should no longer see the error message displayed and Sync Server should launch successfully.

Error:
A Database error occurred. Unable to connect to DB.
Resolution #1:
Ensure that there are no connectivity issues between the machine with the Sync Server and the Database Server. See the section on Troubleshooting Network Communications for more details on this. 
Resolution #2:
This error may also occur if the sysdba system user password has been changed to something other than the default value of masterkey which is used by the Sync Server. If this has been done, the same change needs to be made in the Connect to Other Database dialog that appears off the Login dialog for SalesLogix. If Sync Server is the only SalesLogix component that is currently installed on this machine, install either the SalesLogix Client or Workgroup Administrator on this machine as well. Then, launching either of these applications will provide access to the Connect to Other Database Dialog.

The SalesLogix Client

Error:
The site code on this machine is not valid for the database that you are trying to log onto. Please contact your system administrator.
Resolution:
Log onto the Workgroup Administrator and double-click the user that is getting the site code error. This will open that user's profile. Click on the Synchronization Tab and verify that the User's Site Code matches the Site Code in the SalesLogix.key file of the Workgroup/Remote Client machine. If the site code does not match, change the value in the Saleslogix.key file to match the site code specified in the Workgroup Administrator. See the SalesLogix.key file section under Troubleshooting for more details.

Error: 
This program has performed an illegal operation and will be shut down.
Resolution: 
If the following conditions are met, then there are some corrupted system views contained in the database: 
1) The machine's operating system is Windows 95
2) All other SalesLogix components can be opened against the same database.
3) The SalesLogix Client can be successfully launched against a different database.
To isolate which system view is corrupted, it is possible to try opening them in the SalesLogix Architect. The other option to isolate which system view is corrupted is to use SQL Monitor. Once the corrupted system view has been isolated, open the Plugin Manager from the SalesLogix Architect and delete the corrupted system view from the database. Then use the system views contained within the demonstration database to copy over a non-corrupted replacement for the deleted system view. Close the Plugin Manager and the SalesLogix Architect. You should now be able to successfully launch the SalesLogix Client.

Error:
SECPROFILE table does not exist.
Resolution:
This error only pertains to the SalesLogix Remote Client and means that the Create Database process was not completely successful. From the SalesLogix Workgroup Administrator, make sure that the Remote Database is being created locally, instead of on a different machine over the network and re-create the Remote Database for the particular Remote user.

Error:
A Database error occurred. Invalid use of key word. Token = line #2
Resolution:
This error can also occurs in the SalesLogix Architect and relates to the properties of a datagrid object. In Design mode in the SalesLogix Client or in the SalesLogix Architect, open the properties for the datagrid object and check the edit key field. This field is probably blank. Once the value is keyed in and the properties saved, the error should not appear. See the section on Datagrids for more details on the edit key field.

The SalesLogix Mail Client

Error:
Unable to Retrieve Headers...
Resolution:
This error results from corrupted messages when using POP3 e-mail. The SalesLogix Mail Client executable that accompanies Version 2.11 handles these corrupted messages. Therefore, the current SalesLogix Mail executable should be replaced with the newer version.