We recently upgraded to Financial edge version 7.70.638. Since the upgrade, we are experiencing major performace issues. After certain actions ran by the user, such as posting, the data that the client workstation sees does not update in the module until the user exits the module and comes back in. Example, one AP staff enters and posts a few invoices; shortly after another AP staff enters an invoice and requests the first person to post again. That staff person cannot see the new inforation until she exits AP and goes back into it. (this is repeatetable in AR and payroll, but oddly not Fixed Assets) Other issues, which are more severe, for major actions, such as payroll, checks, and major reports, only the person running that task can be in Financial Edge for the task to complete. I have narrowed the cause down to the database server. These errors repeat on the client running on Citrix servers, dedicated workstations running XP SP1 and XP SP2. I am building a seperate test server to isolate the SQL potentionals. So far, on a seperate server; upgrading from 7.61 to 7.70 has resulted in the same issues. I am now going to try a rebuild of that test server, and a fresh install of 7.70 - no upgrade. Blackbaud reports they are not able to replicate the errors in their environement. Any ideas? If you need any info from logs, please let me know; i will be happy to post them. We are running the database on Windows 2003 SP1, SQL 2000 Standard SP4. No errors show in the event logs, all validation attempts report the data is OK. Indexes and Stats are updated nightly. Our FE environemnt consists of FE7 with Payroll 6. In efforts to rule out everything else: i have completely uninstalled anti-virus from the database server and client machines; enabled local admin rights to the client systems and database server for Finacial Edge users. [i]--- Edited at 6/14/2007 9:47:10 AM by Matt Miller[/i]

Our Director of Technology is anxious to upgrade to FE 7.70 and I was wondering if you are still experiencing the same issues. If so, is Blackbaud doing anything to help you? If not, what did you or Blackbaud do to correct them? Many thanks.

Blackbaud has confirmed there is a problem and has been working on it since my last post. However, no resolution has been found yet; must be something rather complicated. Do you use Payroll 6? On our systems, running the sample database (which has payroll 7), the problems do not show up. I have talked with others who do not have any payroll modules and have not had any issues. Don't know if this is coincidence or not. For us, the issue with reports and intensive processing forcing only that person to be in the system has not been 100% resolved, but was greatly improved after rollup patch 4. We still have a freezeup from time to time; which I think is associated with whatever is causing our other issues as noted in my first post. No matter what your setup is, I would recommend completely testing the system for a couple of weeks on sepererate machines (and have your accounting dept double enter most information). Give it a couple of weeks to fully test; including stress test by having everyone utilize it at once and running posts/reports/etc all at once. Our staff didnot report any issues for several days into it (as each thought there problem was isolated to them); until it was to late to roll back. This lack of testing on seperate systems is what bit me. In the past all upgrades and patches have gone so smoothly that as long as reports and balances were the same before and after the upgrade, we all new it was successful. Test, test, test, and good luck.

We need to update to version 7.7. We still have version 6 (and will still keep 6) in SB and payroll. I have talked to Blackbaud and they tell me these issues are occuring when SQL 2005 is being used. Is this the case with your set-up? We are still on SQL 2000 and they are assuring me it will not be an issue. What SQL version do you [Email Removed]