How To Upgrade Collect!
This topic discusses updating an existing Version 13 installation or upgrading from a prior releases
of Collect! to the latest release.
To download updates, please login to the Collect! Member Center and download the installer file.
If you are not currently a Member and would like to inquire about upgrading options, please
contact us.
It is recommended that you have a recent backup of your Collect! system prior to any upgrade
procedure.
Updating From Version 13 Or Higher
If you are running version 13, then the update is simply a patch.
On the computer that has the Collect! application installed (typically a server):
- Ensure you have an operator in your database at User Level 99 and you know their password
(user 99 exists by default)
- Ensure all users are logged out of Collect!
- Make sure that there are no open files (see below).
- Run the Collect-13.x.x.exe on your server or workstation that you are patching.
- On the Installation Type screen, select the applicable patch (Server/ Client) that you are
running and follow the prompts to direct it to your Collect! installation (for example,
C:\Collect). Do not run a server patch on a client install, and vice versa.
Installation Type
- On your SERVER, start Collect!, click SUBMIT on the splash screen to get to the
" Welcome to Collect!" screen.
- Select START to the update process.
- Click EXIT on the Signon Form. Do NOT sign into a database, yet.
- Repeat steps 7 and 8 for all remaining databases.
- Check the sections below starting here for any
troubleshooting that needs to be done.
Troubleshooting A Patch
Operating System Held on to Open Files
The installer makes an attempt to check for open files and will warn you if there is an issue.
Please ensure that all sessions and files are closed. To ensure that all sessions and files are close,
Reboot your actual server before continuing with patch instructions. Or, if you can:
- Right-click My Computer and select Manage or rights-click the Start button and select Computer
Management.
- Select Shared Folders and open it.
- Select Open Files and review for any files open in Collect. Collect!\bin folder.
- Highlight the files, then right-click and select Close Open File.
Reboot Your Server After Applying the Patch
Collect! Companion Server Didn't Shut Down Properly
If the patch gives an error indicating that you have to abort, this is also a sign of files are in
use. Please refer to the above instructions. This message may also indicate that the Collect! Companion
Service didn't shut down properly during the patch. Here are the instructions to manually shut it down.
- Navigate to the server's Services via the Control Panel or the Task Manager.
- Right-click the 'Collect! Companion Server' and select Stop.
- Apply the patch.
- Right-click the 'Collect! Companion Server' and select Start.
Click here for other troubleshooting topics.
Upgrading From Version 12
If you are on Version 12.11 or higher, then all you need to do is patch up. Please
see above for instructions on applying the patch.
If you are on Version 12.10 or lower, then download the latest Version 12 installer,
then follow the patching instructions above using the Collect-12.x.x.exe file. Once you have finished
opening each database, close everything, then repeat the process to patch to Version 13 with the
Collect-13.x.x.exe file.
Once the upgrade to Version 13 is complete, you may have to re-share Collect! on the Network.
Please refer to the Help topic How to Network Collect! for more information.
After Collect! is available on the network, you will have to update the Desktop shortcuts for
each user to point to \\server\Collect\bin\cv13.exe.
If you use Windows Scheduler to launch Collect! for automated processes like Scheduler
or Web Host, you will need to update your tasks with the new file path.
Upgrading From Version 11 Or Lower
Before you can upgrade to Version 13, you must first upgrade to Version 12 in order to convert
the database from Raima to Microsoft SQL.
Please refer to the Version 12 Upgrade documentation here:
How To Upgrade Collect! to
Version 12
WARNING: Pay special attention to the Troubleshooting section on the Version 12 documentation,
when upgrading from Version 11 or lower.
After you have upgraded to Version 12, and reviewed any troubleshooting issues, you can then upgrade
to Version 13.
Please refer to the section above on applying the patch to Version 13.
Once the upgrade to Version 13 is complete, you may have to re-share Collect! on the Network.
Please refer to the Help topic How to Network Collect! for more information.
After Collect! is available on the network, you will have to update the Desktop shortcuts for
each user to point to \\server\Collect\bin\cv13.exe.
If you use Windows Scheduler to launch Collect! for automated processes like Scheduler
or Web Host, you will need to update your tasks with the new file path.
Troubleshooting
Client Addresses
In Version 11 and newer, the Client form has fields for City, State, and ZIP. If your client
addresses are in the older format where all of this information was stored on one line, you
can run the Update Client Addresses utility to parse the address and put the pieces of the
address into the City, State and ZIP fields of the Client form.
Option 1: Run the Update Client Addresses utility from the Tools\ Utilities Menu in Version 12,
before updating to Version 13.
Option 2: If you already updated to Version 13, start Collect! with /claddress to access the
utility. It will automatically run when you sign in with user level 99.
By default, the upgrade does not upgrade your web host to the latest version of web host. This is
to preserve your customizations. If you wish to upgrade to the latest web host, please refer to the
Help topic How to Upgrade Web Host for more information.
The latest release of Web Host is optimized for the latest release of Collect!, so we recommend
upgrading web host to get the full benefit of the portal.
Collect! now allows only one 195 Judgment Interest transaction on a Judgment account. If you have
posted several 195 interest transactions, only the most recent will be used for the interest
calculations. To remedy this, it is necessary to change the Transaction Type of any additional
judgment interest transactions posted after the Judgment Date.
It is necessary to use a different type because the 195 is a special reserved transaction type for
the original Judgment Interest posted along with the Judgment Principal.
System Transaction Types
We have designated 1081 - 1085 as system types. If you were already using these types, the upgrade
process will re-code them to 1081O - 1085O and update any system references to them. If you have
reports that reference those transaction type codes, you will need to update them manually.
Areas To Test With Every Major Upgrade
Your upgrade should be tested thoroughly, especially in the following general areas,
before proceeding to use your upgraded database. We have a checklist that you can use as a guide for
testing an upgrade. Please Click here to obtain copy.
Reports and Letters
Collect! updates report codes during the upgrade, including address field codes, and creates the
cosigner loop in letters requiring this.
Run test printouts on ALL the reports you used in your previous version of Collect! to confirm that
they are still working properly and printing the way you expect.
You and your operators will see many new fields and forms in your new version. Sign in at various
User Levels and confirm that they still function as before. You may want to tighten up access
security rights to some of these new fields or forms.
By default, Collect! restricts access to new forms and menu items so that only Owner and
Administrator levels can access them (User Level 1, 10 and 99). There are some areas that
cannot be set this way, such as sub-tabs and you will need to set them.
Run all of the Contact Plans you were using in your previous version to make sure they function as
they did before.
Import Routines
If you used any import routines in your previous version, they will have to be carefully examined
in the new version. Do a Quick Print with all details in your previous version and then use this
printout to check your import specifications in the new version.
In Collect!'s Application Log, in the UPGRADE category, you can find the list of import
modifications naming fields no longer in Collect!.
Fields that no longer exist in the database, or that have been renamed, will appear as a blank
line in your import map. This must be corrected before you use the import.
|
Was this page helpful? Do you have any comments on this document? Can we make it better? If so how may we improve this page.
Please click this link to send us your comments: helpinfo@collect.org