Cashbook for Windows Technical Training Notes and Trouble Shooting

Installation: 

Windows 2000/NT 

When you install as administrator it creates the keys but keeps the ownership and permission’s of administrator. You can use the regmon util to show you which keys have problems with permission’s. (www.sysinternals.com)

You then need to run Regedt32, find the keys and select the Security tab at the top of the screen which will give you the option to select permissions.

Assign the user full rights to the PereSoft keys. The user has to have read/write rights to these keys as we write the last open, etc. to the registry each time they log in.

Also give the user rights to any of the keys off HKEY_CLASSES_ROOT\INTERFACE

When installing on Windows 2000/NT:

1.      You must have NT Service Pack 6 or later loaded.

2.      Assign the users Domain Admin rights to the program files directory on the server during workstation installation.

3.      After installation you can set the users back to Power Users.

Citrix

1. Login as Administrator and use the Control Panel, Add/Remove Programs to install Cashbook.

2. In some instances DAO only installs in SAFE mode, you can install DAO in SAFE mode by running SETUPD.EXE from the CD in \winacct\support.

3. Use the following start command from the Cashbook icon: ...\winacct\bin\walogin.exe cbbankrx

Installation Procedure

Program files on the server

1.      Install Cashbook on the server.

2.      Install the latest Cashbook PTF on the server. (The PTF will update workstation setup on the server)

3.      Install ER (Enhancement Release) if there is one available on the server.

4.      Run workstation setup on each workstation from the server directory WKSSETUP.

5.      Start the Cashbook DataManager on each workstation, if the DataManager can not find the Profile and User directories you will be able to enter the relevant server/network drive and directory where the Profile and User files reside.

New Cashbook PTF’s and ER’s need only be installed on the server. Both these installs update the program files only.

Program files locally on the workstations

1.      Run a full Cashbook install on every workstation.

2.      Install the latest Cashbook PTF on every workstation.

3.      Install ER (Enhancement Release) if there is one available on every workstation.

4.      Copy the Profile and User directories (including sub-directories) to the server/network drive.

5.      Remove the Profile and User directories from the workstations local drives.

6.      Start the Cashbook DataManager on each workstation, you will be able to enter the relevant server/network drive and directory you have copied the Profile and User files to. (All workstations must share the same User and Profile directories)

New Cashbook PTF’s and ER’s must be installed on every workstation. Both these installs update the program files.

Note: Installing the ER can be done at any stage as all it does is create a lic file that Cashbook for Windows looks for. It does not change any files all Cashbook needs is the activation code for the ER.

Placing the data on the Network

1. If you have not created any data, DataManager can be run and you can put the data straight onto the Network, else copy your data files onto the network.

Example:  Copy C:\WINACCT\DATA to K:\WINACCT\DATA and, C:\WINACCT\SYSTEM K:\WINACCT\SYSTEM. Copy both DATA and SYSTEM directories.

2. When complete, remove or rename the data files on C:\WINACCT.

3. Start PereSoft Cashbook and you will be able to specify the drive and path where you have placed your data files.

Note: The paths of the data in DataManager are stored in the WINACCT.INI file in your windows directory on your local machine. To change the data paths, you can use the Cashbook User Maintenance function.

 Lanpac Installation

The Lanpac’s can be installed as soon as you have completed your Cashbook installation.

The lanpac installation will update the file profile.ndb that resides in the profile directory.

 Microsoft SQL Installation

Create a database for Cashbook on SQL Server.

This is recommended as you can then keep the Cashbook data separate from ACCPAC's (for backups etc.), and then link to that database.

Please make sure that when you create this database you are logged into the SQL Server as sa, as this will give all the rights to the database.

Once you have installed the Cashbook for Windows MS SQL Lanpac you are able to change the Database Type field to Microsoft SQL Server in DataManager and the following additional fields will appear: DSN/Server Name, Login ID and Database, as well as the Test Data Source facility.

Do the following in DataManager when you create the Cashbook databases:

1. Enter the SQL Server name in the DSN/Server Name field.

2. Enter the SQL database User ID in the Login ID field. e.g. sa.

3. Enter the SQL password you have setup (in SQL for sa) in the Password field.

4. Enter the database name on the SQL Server for the Cashbook SQL Database you have created, e.g. CBWSQL in the Database field.

You can the run the Test Data Source function to verify that your database connection is established successfully.

Cashbook Set Up

ACCPAC Security for Cashbook

Cashbook verifies the User Name and Password set up in Cashbook, to the User Name and Password that has been set up in ACCPAC for Windows.

When you add new users in Cashbook, the password from ACCPAC is automatically read and stored in Cashbook.

The users need to be given the correct rights in ACCPAC.

The minimum security authorizations required in ACCPAC for Cashbook to function correctly are:

Common Services

Modify Company Profile - For Cashbook Posting only.

Bank Services

Reconcile - for Retrieving from Other Systems and Cheque Reversals.

Reverse Customer Cheques - for Customer Deposit Reversals.

General Ledger

Journal Entry - for Transfer to General Ledger

Setup Maintenance - if all ACCPAC G/L Source Codes are not correctly added to General Ledger. These source codes are entered in the Bank Maintenance Bank tab in Cashbook and must be added to the General Ledger Source Codes in G/L Setup.

Accounts Payable and Accounts Receivable

Batch Entry - for Posting to AP and AR

Trouble Shooting:

"Activation code is not correct for Cashbook."

Check the following:

a) You have the correct info in the Peresoft.ini file in \profile.

b) In the registry under Software|PereSoft|Company Information that the Company name is correct for the server’s registry.

If the above does not resolve the issue please send us your sver.dll file residing in ..\Winacct.

We will also need to know which product you installed E.g. Cashbook Full Product/Cashbook Dos Upgrade/ Cashbook Version Upgrade etc.  

"Unable to get object information from ROTO" 

Although NT/W2K/XP do not use the autoexec.bat file, Cashbook still looks in there to make sure the path has been entered correctly.

It is very important that the paths in the registry for ACCPAC and the environment paths are identical. This can go wrong when

1. The Autoexec.bat files are wrong (Win 95, 98)

2. The Environment configuration is wrong (Win NT, 2000, ME)

3. The Novell search paths have overwritten your Autoexec.bat files.

1 and 2 can be addressed by checking the environment path settings. This can be done by typing PATH at the DOS prompt.

The Novell issue can be addressed by using the MAP INSERT S* command and not just the MAP command when creating the search drives. The INSERT parameter prevents the search path from overwriting what is in your Autoexec.bat path.

The ACCPAC key to the registry settings are at: HKEY_LOCAL_MACHINE/Software/ACCPAC INTERNATIONAL,INC./ACCPAC/Configuration/Programs

This error is only caused by the path used by ACCPAC and the path used by Cashbook not being the same. If they are not the same for ACCPAC as well as Cashbook, ACCPAC returns the ROTO error message.

The program Listdlls.exe, found on our download page, will let you see exactly where the ACCPAC runtime files are loaded from.

Listdlls.exe is a utility provided by AI for situations like this. All it does is list what is loaded in memory and where the files were loaded from. It does not change, remove or delete anything.

Run the Listdll's utility by going into DOS and typing the command Listdlls >filename.prn to place this information into a log format.

"Active X component cannot create object"

Download the PereSoft MUDIAG 4.2 Utility and run the Connect Test to check that all the objects required by Cashbook 4.2A have been registered correctly.

If necessary run the Register Objects function to register the objects.

"Error on startup" (when trying to login to Cashbook)

Run walogin.exe from the bin directory and the component will re-register itself, then login to Cashbook.
 

Top Of Page | Home

Copyright © (2004) PereSoft Software & Support (Pty) Ltd.
All product names referenced herein are trademarks of their respective companies.

Web comments can be directed to the webmaster@peresoft.co.za