03-07-2009 06:26 PM
We've this problem since day one: every instance of ACT!, no matter what computer it's running on, causes a crash when you close the application (and Microsoft loves hearing about it, but never offers a solution.)
Today I applied the 10.0.3 update to all of the machines (all of them running WinXP, SP3) and much to my surprise, it's still doing the same thing. We can launch Act, use it, but the moment you close the application, we get the same windows again 'ACT! By Sage has encontered a problem and needs to close. We are sorry for the inconvenience.' Um yeah, not as sorry as I will be for the next person that dials my extention in this office.
We've tried this on a brand new WinXP system, with nothing on it, fresh installation of ACT! 10.0 (whatever came in the box), and it crashes. Then we upgraded to the 10.0.3 one (I downloaded the update and applied it) and it does the same thing.
So, now what? Mind you, with the previous version of ACT! this was never an issue. It only became an issue when we started using ACT! V10.x ...
03-08-2009 09:33 PM
Adding to this. I downloaded the full 10.0.3 installation file (URL from this post from ghollister). Decided to use my system as the guinea pig and uninstalled ACT! (from Add/Remove Programs...). I've rebooted the computer, and proceeded to install the newly downloaded 10.0.3 version. When all was said and done, it's still causing a crash when I exit ACT!.
I've even tried opening the Demo database, thinking maybe it's my database. No luck, same crash.
This is becoming ridiculous. No previous version of ACT! ever did this. It only started with version 10. And it's crashing across all the systems in our office. This is UNACCEPTABLE. Considering how many others are complaining about this same crashing issue, you'd think Sage would actually fix the problem
Between this, and the stupid fixed port 25 for e-mail, I have no choice but to start looking for a completley different solution. If anyone has any suggestions for something else, let me know please.
03-09-2009 08:56 AM
03-09-2009 04:50 PM
03-10-2009 06:29 AM
You probably have .Net vers 2 SP1, if your on XP you can remove it and reinstall it minus the service pack and it should get rid of your error. If this has been done in the past it likely reoccured b/c of windows updates.
There is even a KB article published 8/12 of 2008 that dealt with this issue specifically. KB 22381
03-10-2009 09:03 AM
Ok, so question then. Those machines were, at some point, running .NET 2.0 (possible with or without SP2 - not SP1). However, they have all been upgraded to .NET 3.5 SP1 now. And the problem still persists. The old .NET 2.0 hasn't been removed yet (neither has .NET 3.0 SP2).
So my question is, if I remove .NET 2.0 completely, and leave .NET 3.5 (possibly also .NET 3.0), will this error get resolved? Or do I have to uninstall all the .NET versions, ACT!, reinstall only .NET 3.5 then ACT! again?
Considering how many systems I'd have to do this on, this is not a task I'm looking forward to.