05-22-2008 07:40 AM
Last month MS updates to the .net framework caused Act to fail. After talking to Act support, they helped me resolve the problem, however, they also advised me to turn off XP automatic updates until this problem has been resolved.
My Question: has this issue been resolved, either by MS or Sage, so that I can turn on automatic updates once again?
Also, I see XP SP3 has been released.. does anyone know if there are any conflicts with SP3 and Act 2007 (Version 9)?
I rely heavily on Act for my business, and just cannot afford to be down again for any length of time.
05-23-2008 02:51 PM
The issue has not yet been resolved by either parties.
However you might want to set up your automatic updates to:
'Download updates for me, but let me choose when to install them'.
Go to 'Start -> Control Panel -> Automatic Updates' to do this
That way you can get windows to ignore the update 'Microsoft .NET Framework 2.0 Service Pack 1', but continue with other updates.
05-23-2008 05:05 PM
I'd really like to hear something from Sage on these... are they (.Net 2.0 sp1 or XP sp3) MS issues or something Sage can do for 10.03?
Especially as both of these don't happen to every user, it makes me think there is a resolution somehow?
06-16-2008 02:41 AM
I have spent a lot of hours with our clients in the last couple of weeks uninstalling .net 2.0 sp1. I'm wondering when will ACT have a fix for this. This is a huge pain to deal with.
06-16-2008 04:38 PM
Actually, i believe that it's Microsoft that will need to have a fix for it...
In fact ACT! isn't the only application that suffers from these, as QuickBooks has issues too, as would any other .NET application.
The reason some work and some don't is due to the order in which the udpates may have been applied. If you had a virgin XP install, updated to ALL availbale updates, THEN installed ACT!, you wouldn't have an issue (most likely), but if you installed ACT!, then applied post updates, you could be victim depending on the order of the install and what else was installed into .Net at the time.
The MS reference item is Microsoft KB 928365 / Bug 196380 - http://support.microsoft.com/KB/928365