SEP Issue with Intuit Quickbooks

[Migration User]

My client made the transition Friday from SAV Corporate 10.1 to SEP 11.05.  This morning there was an issue with the workstations using quickbooks.  I searched the Quickbook error codes and found this article from the Quickbooks website:
http://support.quickbooks.intuit.com/support/pages/knowledgebasearticle/403317

This link led me to this Symantec Knowledge base discussion:
http://service1.symantec.com/support/ent-security.nsf/0/6cc9274310e110968825763b0067ee3f?OpenDocument


I followed all the steps in the above article but was unable to gain access in Quickbooks without disabling auto-protect on the server.  I called in to attempt to gain access to a copy of 11.04, but since this is a non-profit company they do not have technical support.  My fourth person on the phone directed me to this site here:
http://www.symantec.com/business/support/downloads.jsp?pid=54619

These are patch upgrades though, not full client SEP installations, and do not solve my problem.

For reference to any Symantec personel, my Case ID is:  100201001506

I need assistance with getting copy of 11.04 SEP or more information on allowing access to Quickbooks in SEP 11.05 that isn't already outlined in the symantec documentation above.

[Migration User]

QuickBooks error after installing Symantec Endpoint Protection 11 Release Update 5

 http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/6b33b0195b635e3d882576a900041112?OpenDocument

[Migration User]

The link you have posted suggests to upgrade Quickbooks to 2009/2010.  This will require purchasing the software and may reveal other issues with the upgrade.  The symantec article I have provided earlier simply recommends reverting the client installation back to 11.04.  I feel this is the smiplest/easiest solution to our problem.

[Migration User]

 Guess your client should buy support with their product.  That is about the only way to get them to talk to you and provide you with an alternate download link.

You could also try contacting the licensing group.  Contact information is on this page licensing.symantec.com