8.1 to 9.x upgrade
Response 8.1 to 9.0 Upgrade Instructions
VERY Important Notes before you begin:
Response 9.x is not compatible with Windows 98, due to the Crystal 10.x runtime
I. To qualify for free conversion support, CoLinear Systems requires that all customers perform a trial upgrade to 9.0 before upgrading their production system. This requires setting up a copy of Response (i.e. a new SQL database) on another Server or standalone PC. To set up a trial conversion machine use the instructions in step 1 below. You will perform the 9x upgrade on that copy and test all your routine and daily functions to be sure they are as you expect. This also allows you and your staff to see and work with any new and changed features.
II. After you have completed testing in your trial upgrade, please let CoLinear support know when you plan to convert your production system to 9.x. Please give us as much notice as you can. In order to give you the best service possible, we can’t allow more than 3 live conversions at any given time. We’ll let you know if the schedule is open for the date you choose. It’s rarely a problem, but we do appreciate your cooperation in this matter.
III. ATTN: MSDE Users!
The Response 9x tables after conversion require more table space than v8 (due primarily to the increased field sizes to support encrypted credit card data). Consequently, you may not have enough free space in your 2GB limited MSDE database to convert to v9, let alone continuing to process once you get there. Please check to be sure you're not using more than 1.25GB of space with MSDE prior to conversion. If you are over that limit it's imperative that you license the full MS SQL product to remove that space limitation prior to conversion. See information here for the files you need to look at: http://support.colinear.com/doc/Administrative+Upgrades+Utilities/MSDE_User_info&Tips.doc
Instructions for the Version 9 upgrade:
(If you previously installed the V9 upgrade, see appendix A for instructions to prepare your machine for REINSTALLING YOUR FROM SCRATCH) This is especially helpful if you’re installing the TRIAL over again.
1) Make a stand-alone copy of your current Response system as a “test” system. You’ll use this for performing your trial upgrade to 9.0. Details for creating a test environment can be found here. You create this so your production 8.x system is not interfered with while you “test” the upgrade. Perform the remaining steps on your test system, this is your trial upgrade. When you’re ready to upgrade your production system, you’ll perform the remaining steps on your production system.
2) Make sure you're running at least Build 3054 of Response 8.x.
3) Download and run on your separate TEST Response system: the v9upgrade.exe from our website. That link is provided upon receipt of your upgrade order; to place your order please call 1-800-COLINEAR (265-4632) or email
*NOTE: Because new builds are issued so frequently, we no longer distribute major upgrades on CD ROM. If, for some reason, you are unable to download this file, please contact to arrange for FedX shipment on CD ROM ($35.00 s&h applies).
!!!! The latest issues in the 9x upgrade executables and their resolutions can be found here:
http://support.colinear.com/doc/!-Deployment%20(new%20systems)/9xIssue&ResolutionList.htm
Executing the V9upgrade.exe file will display the following
Pressing next only unzips the files you’ll need to run the conversion, in the next screen it will ask for the destination of the extracted files, you should point it to the appropriate …\collinear\r4w folder (point to your 8x COPY if you’re running a trial conversion)
NOTE: if the folder you specify is not correct, you will see this error
If all is OK in the folder you specify, you’ll see this
Choose Install, next you’ll see this
4) After the Install Script above has completed, choose Start / Programs / CoLinear Systems / V9 Conversion. This is the part that actually executes the new r9_conversion.vd7 file and converts your data
You will see a screen like this showing progress
When it’s complete you will see this
IMPORTANT! Please email your conversion logs to . The filename is \r4w\data\r9_conversion.log (If you have a multi-company setup, an r9_conversion00x.log will be created in \r4w\data for each company).
Next, you must update the server (or workstation you used for the conversion) to 9.x by running \r4w\client\ v9Client.exe.
(hint, you should delete your OLD R4WClientSetup.exe file so it’s not confused with the new V9Client.exe)
TECH NOTES: Solutions for installing Response v9 for a user that is not an Admin on their local machine (admin = windows user setting)
Use # 1 OR #2 not both:
1. Install the Response client (v9client.exe) and login to Response for the first time while the user is in the local admin group.
Advantage-> You don't have to manipulate the registry! :)
Disadvantage-> this workaround must be completed for every install where the user is not an administrators for their local machine.
2. Set Full permissions to the HKEYLOCALMACHINE/SOFTWARE/DATA ACCESS CORPORATION registry key for Authenticated Users (then install the Response client v9client.exe).
Advantage-> You only have to do this once per machine
Disadvantage-> You have to manipulate the registry! :(
After updating the registry and links the following screen will display.
Press Next, you will see the progress indicator, then this
5) The first time you log into Response (after installing v9) you will be prompted to run the required credit card encryption routine. This part of the upgrade could take a long time to run (as much as 12+ hours on our largest systems). Be sure to allow sufficient time for this system-wide encryption of credit card data to complete.
When they are complete you must send us your credit card encryption code
Special notes section. VERY IMPORTANT PLEASE REVIEW EACH:
q Several new builds have been released since the 9x upgrade executable was created. You must apply new builds after your trial AND real upgrade is complete. Details here http://support.colinear.com/doc/Administrative+Upgrades+Utilities/New_Build_info.doc
q Special note for ICVERIFY and PCCHARGE Users:
Response 9x at build 4021 and greater do not support these two CC interfaces. While we’ve been telling you for years we not longer supported these, they have finally been removed. You can convert to 9x and apply up to builds 4020, but no further.
q MULTI-DIVISION SYSTEMS PLEASE NOTE!
We suggest that you log into each division from a separate workstation to run the encryption routines together, i.e. simultaneously. For example, log into division 001 on workstation #1 and start the encryption. Then log into division 002 on workstation #2 and, again, start the encryption. Repeat for all other divisions. By running these one-by-one the process will take much longer than if they're running in parallel.
Tech note: no encryption will run for R4W_primary. If a table that requires encrypting or masking is shared in r4w_primary, it will be encrypted/masked as part of each division's encryption process (but it won't happen more than once).
q See more information using the link below “for CISP-related information in v9”
If you must abort the CC Encryption for any reason, it will start again where it left off when you start Response 9.x the next time. The encryption must complete before you can use Response.
q Special note for RCK users: You MUST upgrade your RCK dll to version 80022, find information here
http://support.colinear.com/download/r8/RCK8022_forCISP.doc
And finally…… Here are some additional Links you will find useful.
Release notes for Version 9:
http://support.colinear.com/download/r9/relnotes/4011e_Release_Notes.htm
For CISP-related information in v9, see:
http://support.colinear.com/doc/Optional%20Modules/CC_Response_CISP.doc
For details on using the new features in Version 9, see:
http://support.colinear.com/download/r9/V9Highlights.doc
For a list of features in v9, see:
http://support.colinear.com/download/r9/V9Features.pdf
More V9 features explained from build 4018
http://support.colinear.com/download/r9/4018/4018Features.htm
!!!! The latest issues in the 9x upgrade executables and their resolutions can be found here:
http://support.colinear.com/doc/!-Deployment%20(new%20systems)/9xIssue&ResolutionList.htm
Please send any questions, comments, problems or concerns to .
Your 9.x upgrade is COMPLETE! See below for appendix A and Q&A
APPENDIX A: instructions to prepare your machine for REINSTALLING YOUR TRIAL UPGRADE FROM SCRATCH
To prepare your machine for “reinstalling” your trial conversion again:
1. You should uninstall everything related to v9 on the test server machine and get back to a working test copy of 8.x (ie. a mirror image of whatever you are running "live"). If you don't uninstall the v9 upgrade first, installshield may prompt them with a "repair" option, which will do nothing but confuse everyone (including support!).
2. You do not re-install the 9.x client on those clients that accessed your previous 9.x. When the v9upgrade and r9_conversion.vd7 have been run, the clients can still access the server assuming the paths haven't changed to the new copy of the 9x upgrade. If the paths DO change, just re-run the client - no need to uninstall the client first.
Q&A
The following information fixed the 9.x problem with the "..... # out of range" error in your custom Crystal reports :
Short-term fix is to download http://support.colinear.com/download/Crystal10.zip, extract all files into \r4w\bin, then run \r4w\bin\cr10.bat, then re-run the reports. The v9 update is currently being updated to fix this.
Q: can I look at my conversion logs to see if they are OK?
A: Yes, Check the log file [\r4w\data\R9_Conversion.log] for any error messages. Search for the word “fail”.
If you do see any errors [as in the example below] be sure to email the log file to for review.
>>missing example, sorry
Another User TIP: If your windows in Reponse 9.x looked cropped or truncated (where some of the buttons at the bottom of a view looked chopped off, see this document:
http://support.colinear.com/doc/Administrative%20+%20Upgrades%20+%20Utilities/ResponseWindowsCropped.doc
QUESTION:
I had one PC receive errors during the client install. It report is was unable to register 3 dll. I did move to the Crystal v10 run time this weekend.
It is a Win2K SP4. Any suggestions?
This is what the error looked like:
Response 9 client utility - installshield Wizard:
Self-registration error:
the following files did not self-register or unregister:
1. J:\r4w\bin\ExportModeller.dll class not registered
2. J:\r4w\bin\crqe.dll class not registered
1. J:\r4w\bin\crtslv.dll class not registered
ANSWER
You should manually register the DLLs on this client machine. Not sure why Installshield is complaining, but the following should do it at a command prompt:
regsvr32.exe r:\bin\exportmodeller.dll
regsvr32.exe r:\bin\crqe.dll
regsvr32.exe r:\bin\crtslv.dll
If you also see an error like this
regsvr32 ! D RegisterServer in J:\r4w\bin\crqe.dll failed Return code was 0x80040154
You may have problems manually registering the dll’s above until you also manually registered c:\WINNT\SYSTM32\atl.dll (the Unicode driver)
Page 8 of 13 10/17/2007