We are a group of users of Blackbaud products and are not affiliated with Blackbaud. We'd love to have you join our community to help and be helped in getting the most from your Blackbaud software.
Register now to join us to get independant advice on your system, connect with 3rd party consultants to help you maximize your database and have a real alternative to the official Blackbaud website.
We recently installed the multi-user version of ICVerify (ICV), and we're in the middle of trying to resolve a security issue with the server. I'm not a tech person, but this is how I understand it: The multiuser version installed its own sql server. This led to a Windows security patch update. This update caused our Raiser's Edge sql server to stop working. Our tech guys 'rolled back' the update so we could get RE up and running, but this left our server vulnerable. We worked with ICV tech support Friday afternoon to resolve it. We tried a workaround of attaching the ICV multiuser database to the existing sql server (they said this has worked for other clients), but they were unsuccessful; the ICV software could not recognize the database. We also learned that ICV does not support these latest (??? May 95??) Windows updates. My tech guys and security guy are supposed to get with someone higher up at ICV today to see if they can resolve this. In the meantime, we can use Raiser's Edge, but we cannot use ICVerify.
I notified Blackbaud of this issue, but the person who responded said basically that it's not their problem and ICVerify needs to fix it. (They were much more diplomatic with the wording and tone of their response.)
If you need a more technical explanation than this, I can put in touch with my systems guy.
Thanks for the info. I am on sabbatical until mid-September and will be trying my install when I get back.
I remember setting up the single user version of IC Verify about 6-years ago and it was not an easy process then either.
I would have preferred IATS, but Gift Processing folks did not want to switch processing provider.
I would love to hear more after you get all the problems solved. I already bought the IC Verify software, so I will have to go with it, but hope I can be saved some problems by following after you folks have cleared the mine field.
I have very bad experience with ICVERIFY, up to the point I wouldn't like to touch the product even with barge pole. Constant corruptions of the database, terrible support from the vendor, every major upgrade of ICVERIFY causes some problems just to list few problems.
I advice anybody to look other way. I implemented very recently IATS and sofar I haven't got a single problem, reporting and reconciliation is sweet. You can maintain several coded streams of payments - equivalent of merchant accounts to allow for recognition of the separation of funds for reconciliation.
I wish I had something positive to tell you. We also have had a lot of problems with ICVerify. After the security issues on the server, we decided to install it on a workstation as the 'master' station with the other workstations acting as sub stations. We never got the sub stations to work. But now we're in the middle of migrating Raiser's Edge to a new server (we will have the database on a 'cluster' server and the BMC on the new server) and I hope to try installing ICV again on the new server.
Andrew, the reason we are not with IATS is because the cost for us is exhorbitant. I appreciate your comments, however, because I've had some very bad thoughts about ICVerify and the level of customer service that is provided .... or not provided. When you say 'database corruption' - which database? RE? or ICV?
Thanks for the feedback. I will forward all the responses to our Donor Services Dept, but they want me to try it and see what happens. I bought the software, but would love to dump it and go to IATS.
I'm just the techie and they expect me to take these bungee jumps and experience it for myself despite advice from others. I tried for 2-years to get them to move to IATS.
ICVerify 4.03 Multi-User and RE 7.82 Up and Running
I just finished my install of ICVerify and it all works fine. Since others warned about issues with running the Master Station on a Server which already had SQL databaes on it, I decided to install on a server which had no databases. Blackbaud told me that ICVerify version 4.03 is certified with RE 7.82 so I made sure to upgrade my RE first and then got the version 4.03 before starting.
My Server has ICVerify configured as the Master and I have installed on 5-workstations configured as sub-stations. To try and minimize install problems I decided to follow the steps below:
1. Install ICVerify and ICVerify User Manager on the Server. I then used a test CC# that was given to me by my processor (Nova) and verified that it worked.
2. I installed on a workstation and then ran the same CC test and it worked.
3. I then changed the Set file on the workstation and configured it as a sub-station.
4. I tested again using the test CC# and it worked
5. I then modified the configuration so that it could be used with RE.
6. I then created a batch in RE and made sure that it worked with RE.
The main problems I had were related to both ICVerify and Nova giving bad advice. I had to make many calls (at least a dozen) to both parties and each subsequent phone call would often result in directions which were vastly different than the previous call. The Blackbuad written instructions also did not make it clear which directory the ans files need to be placed.
Just a note here, ICVerify is just a software that transmits your transactions to your Processor. We use Nova. ICVerify is not a processor
I also found that if you follow the written directions for the ICVerify install (along with many screen shots) you might never get it running. There are areas where the screen shots have settings and paths which would not work if you are trying to do the Master and sub-stations.
Now that I understand it all and have it up and running I am going to record a screen cam video so that if needed I can watch the video and remember all the steps I did. I also made screen shots of the server and workstation settings and copied the Set file from both the workstations and the server and put it all in a PDF Binder.
just be aware of any upgrades to ICVERIFY and whatever support and maintenance desk on ICVERIFY would tell take it with a pinch o salt, especially you will never get anything from them in writing,
with upgrades and updates not only with full reinstall you are overwriting security encryption algorythm of the database = you are losing access to historical reporing and historical data and oppportunity although processing of the CC transaction is not affected,
I have been with this and recovery is a pretty long and nasty process
This was a main reason we moved to IATS which is smooth and doesnt require local installation, all reporting available on line, highly recommended
Thanks for the info. I actually have a very old version of ICVerify (single user with modem) up and running. I installed it about 5-years ago and have never upgraded it. It has and is still running without problems. I have never had to get any info from any files that are stored by ICVerify. We go to a web site and it list all our transactions, dates, etc.
I just install and support the software, so I never actually use it. What or why do you use the data from the ICVerify db?
I plan that as long as the new multi-user version is running fine I will not upgrade it. I tried to convince folks to move to IATS, but they were not interested.
Jeff, We were using ICVERIFY in the scenario when it was not integrated to RE, so this was our only way of reporting, ie. ICVERIFY reporting facility via reporting tool in client ICVERIFY menu hitting directly encryptrd database, once we integrated ICVERIFY with RE we had RE reporting on gifts processed through ICVERIFY, but native ICVERIFY reporting was still usefull for checking and reconciliation in case of discrepancies between ICVERIFY and RE reporting. They happen believe me. Also we wanted facility to do CC refunds to clients cards via ICVERIFY. IT is pretty useful even if used rarely.
IATS seem to me superior as it doesn't require any local installation and support is excellent, Best,
Jeff, thanks for posting this information on your ICVerify install. Believe it or not, we are still not using it. I think my IT guys have sent this to the bottom of their To Do list. Perhaps this information will be helpful in raising it up again.
Jeff, I'm curious to know how you have fared with ICVerify in the past 7 months. We finally decided to scrap it and use IATS, despite the cost, and our users are now in 7th heaven. The ease of implementation and use was unbelievable compared to the agony of getting ICVerify to work. If yours is working for you, I applaud your IT expertise and wish you well! - Judy
Jeff, I'm curious to know how you have fared with ICVerify in the past 7 months. We finally decided to scrap it and use IATS, despite the cost, and our users are now in 7th heaven. The ease of implementation and use was unbelievable compared to the agony of getting ICVerify to work. If yours is working for you, I applaud your IT expertise and wish you well! - Judy
Judy,
All is fine with ICVerify and RE. I had to install some new workstations and I've got it down to about 5-minutes for the install. The end-users love it and have reported no problems.
