Has a solution been found yet? I didn't see this advisory until the update was installed. I have rolled the update back, but still having connectivity issues.

I'm getting the error: “You cannot use Sage 50 right now because the serial number you have… is already in use by the maximum number of computers. Wait 1 minute and then try again." A month later and still no solution or fix?

Any time that you get this message you should be able to go to Services (on the workstation), scroll down to Pervasive PSQL Workgroup Engine, and click on Restart. After the Pervasive service has been restarted you ought to be able to log in without any trouble. **NOTE** If you restart the Pervasive service on the server it will cause everyone's Sage software to crash and people will not be happy with you. They will all have to log back in and they will lose whatever they were in the middle of.

Thanks for the tips. I ended up updating .NET on the server and rebooting. Everything seems to be working now.

Hello GRF5290,

I just sent you a friend request. If you would kindly send me a private message with your contact information, someone from our Sage Support team will be happy to contact you and take a look at the issue you are experiencing. 

Thank you!   

Update: I just had a local IT guy come out. He talked with Sage Tech Support and they told him about a temporary workaround. If anyone is currently fighting this battle, you can disable the IPv6 on every machine on your LAN. My understanding is that Sage should have a patch out soon to fix this. Once the patch has been installed you can enable your IPv6 again and everything will be back to normal. If I have relayed any of this information incorrectly, please feel free to correct my mistakes!!

We currently do not have a patch planned, since this is not something that can be corrected from within Sage 50.  Option II in KB 90972 (disabling IPv6 on the server & workstations) will fix these issues in the majority of cases.

And in the cases where disabling IPv6 does nothing, nor do any of the other options, what should we do? We can't rollback updates to a server that has just been rebuilt due to a failed OS drive.

Have you already tried using a static IP address on the server and updating the hosts file on the workstations (Option III in KB 90972)?

Yes, we've tried all four of the options listed in that article, along with other things such as setting the compatibility mode on the services themselves that are controlled by the connection manager, disabling all firewalls, and even creating a tiny LAN of just the server computer and one workstation. Nothing has worked.