Finally! Official support for Win2k8 r2 and SBS 2011

QuickBooks Support - System requirements for QuickBooks 2012 and 
Enterprise Solutions 12.0:

*Database Servers:*

  * *Windows*: natively installed
    Windows 7 or Vista with UAC on, XP (SP2 or later), Windows Server
    2003, Windows Server 2008, Windows Server 2008 R2, Windows Server
    2008 - Terminal Server Config., Small Business Server 2008, Small
    Business Server 2011

QuickBooks Loan Manager and Internet Explorer 9 Problem FIXED

QuickBooks Loan Manager and Internet Explorer 9 Problem FIXED : Practical QuickBooks:

I’ve had IE9 installed for a while – mainly because if you never use the items that have issues with IE9, you never see the issues.  Bottom line if you were holding back, there’s now a fix.

Don’t install .net 1.1 on SBS 2011

I’m reblogging this as I can’t find it myself under my Susan’s rules of filing.

So I’ll blog these key words.

SBSdiva (that hits this blog) .net 1.1 SBS 2011 don’t

There.  That should let me find the blog post better.

Bottom line if you have an application that wants to install .net 1.1 (older versions of Quickbooks) it will mangle the IIS web sites on the box.

So don’t install a .net 1.1 app on your server.



So your client has Quickbooks 2007 and you are migrating them to SBS 2011. First off I’m going to say you probably want to sit them down and talk about that Quickbooks 2007 multiuser version and ask them to strongly consider upgrading. For one the program/version is no longer supported. Certainly if they had employees they’d have migrated to a newer version before this if they used the payroll module. But there’s another reason… you strongly do not want to be dealing with an app that wants .NET running on a SBS 2011.

When you install .net 1.1 on your SBS 2011 certain things go boom:


WSUS isn’t WSUSing like it should.

And when I went poking around certain things just are not happy.

If your clients absolutely put their foot down — or more likely than not someone’s gone and done it and you are stuck cleaning up the mess, here’s what I did to get it working —

So here’s what I did to get IIS for Companyweb and WSUS working again without reinstalling the server…

From :
.NET 1.1 may have agressively taken over part of IIS. Try running aspnet_regiis /i from the command prompt for the v2.0 folder. (c:\windows\\framework\v2.0.50727). That will register 2.0 but won’t mess up 1.1. This is the most likely fix.

In my case I launched a command window as an administrator and then went to the folder of c:\windows\\framework\2.0.50727 and typed in aspnet_regiis /i and then did the same from c:\windows\\framework\v4.0.30319 and typed in aspnet_regiis /i

I then did a IISreset.

I also went to the IIS console and ensured that the IIS 1 and 4 isapi filters were allowed to run

Orignally the 1.1 said disallowed. I also let the 4.0 isapi filters be allowed.

And voila — companyweb and WSUS work.

But do me a huge favor… get them to upgrade from Quickbooks 2007… it’s old, it’s out of date, it’s not supported, it doesn’t like UAC and you really don’t want it running on that server


Quickbooks 2012 on SBS

Please now see

The system requirements for Quickbooks 2012 installs .net 4 – additional software: 250 MB for Microsoft .NET 4.0 Runtime, provided on the QuickBooks CD.  Due to this you need to be aware that while it won’t mind at all being installed on SBS 2011 (standard or essentials), it will barf big time on SBS 2003 — see –

Quickbooks 2011 also won’t mind SBS 2011 era servers.  Start going back too far where Quickbooks installs .net 1.1 on the Server 2008 r2 platform and you’ll see issues.

So if you are rolling out Quickbooks 2012 anywhere, be aware that it would not be wise to be installing it on SBS 2003.

Is your QuickBooks Enterprise v11 .tlg growing out of control?

Is your QuickBooks Enterprise v11 .tlg growing out of control? | Intuit Community:

Copied from the Quickbooks forum so I don’t forget this for the future —

One of my brilliant blog readers stumbled on the solution. He posted it to the Performance Issues forum, but I believe all Enterprise v11 users need to know about it.

In a nutshell, the new Search feature can cause some .tlg files to grow out of control. I checked, and mine is just fine. But if you read his story, you’ll see that his was growing up to 1.7GB a day!

You can turn it off by going to Edit > Preferences > Search > Company Preferences and un-checking the little check box next to ‘Update Automatically’. If you use the Search feature, you’ll need to update manually, which will probably cause your .tlg file to grow so you’ll want to follow it up with a manual backup (with full verify).

It’s always a good idea to routinely perform manual backups. Not only does it bring your .tlg file size down, but it verifies your data which is essential to your file’s health. I have my QuickBooks files automatically backed up automatically by three different services – Intuit Data Services, Gillware and Mozy – and I still do manual backups very week or so. Let’s just say I’d be in a heap of trouble if I ever lost any of m client’s files!”

QuickBooks Support – Error: Qbw32.exe or AVMTimer:qbw32.exe application error, or QuickBooks has stopped working:

QuickBooks Support – Error: Qbw32.exe or AVMTimer:qbw32.exe application error, or QuickBooks has stopped working:

.net mangles Quickbooks

QuickBooks 2010 R8 : Practical QuickBooks:

R8 is the release that will fix it.

Bottom line poke the hole in the firewall, it works.

The tweet says…..So, according to QB support, you cannot host #Quickbooks 2010 data files on 2008 SBS. Considering that is what most of our clients do, #FAIL

And there’s a difference between “support” and “it works”.
The reality is it works.  (That’s 2008 but the 2010 info is similar)
And per that it kinda sounds like they do support it..
Windows Server 2008 or Windows Server 2003 Standard, Small Business and Enterprise editions including 64 bit
It’s just that the wording is a bit off.
Bottom line poke the hole in the firewall, it works.

QuickBooks 2009 R10 and Sales Tax Reports

Story on Sales Tax Reports in QuickBooks 2009 Continues.      See Web version.
QuickBooks ProAdvisor Critical Alert

Dear Susan Bradley,

Today Intuit will be notifying customers using QuickBooks® 2009 [1] about our progress in resolving potential issues with the sales tax reports, issues introduced in QuickBooks 2009 R9. We recommend all users read the Alert as posted on the Intuit site:

Important Information Concerning Sales Tax Reporting in QuickBooks 2009 Release 10

Following we identify issues of most importance to QuickBooks ProAdvisors.


R10: Fixes Sales Tax Liability Report

Practitioners typically use the Sales Tax Liability Report as the primary means of reporting to sales tax authorities and identifying the tax owed. That report is fixed in R10. [2]

Because the Sales Tax Liability Report is crucial to sales tax reporting, Intuit has moved R10 to the Automatic Update stage. With R10, practitioners will be able to move forward with generating reports for sales tax reporting and compliance with sales tax authorities.

R11 (Coming): Will Fix Sales Tax Revenue Summary Report

Because R10 does not fix the Sales Tax Revenue Summary Report, Intuit is preparing R11 now.

R11 will be out as soon as possible. R11 will fix both sales tax reports.

Sign Up for Notice When R11 Is Ready

While Intuit cannot guarantee that R11 will be out by a specific date, we want you or clients to have the chance to be informed just as soon as it is ready.

Sign up for notification here.


Intuit Posts Resources for Sales Tax Reporting

Some ProAdvisors or their clients are in the middle of sales tax reporting now. Intuit has posted updated recommendations on how to proceed in such cases, as contained in the Alert link at the top of this notice, and duplicated following:

Important Information Concerning Sales Tax Reporting in QuickBooks 2009 Release 10


Sales Tax Reports Unaffected in QuickBooks 2009 R8 or Earlier

In some cases you or your clients may not have updated yet to R9 or R10 from earlier releases of QuickBooks 2009. In these instances there will be no sales tax issues.

However, There Are Good Reasons to Update

Intuit recommends that all users update to the latest release because each release addresses specific issues and further improves functionality and performance.

FROM QUICKBOOKS 2009 R8 to R9 or R10

From R8 (or Earlier) to R9 or R10 Requires Special Care

As identified in earlier Alerts, [3] 2009 R9 addresses many issues and also leverages an existing upgrade of the QuickBooks Database to further improve data stability. [4]

The change is significant: the R9 or R10 update behaves more as a yearly upgrade to a new QuickBooks version than as an update to an existing QuickBooks version.

This affects two dimensions of your practice:

  • In backwards compatibility. [5]
  • In network implementations.

R8 to R10 Same as R8 to R9 in This Regard

ProAdvisors or their clients on 2009 R8 would simply update to R10. R10 includes everything in R9, less the issue with the Sales Tax Liability Report. It is not necessary to update to R9, and then R10. R10 is cumulative.

FROM QUICKBOOKS 2009 R9 to R10 or R11; or R10 to R11

After First Update from R8, Next Update Is Standard

The major update to the QuickBooks 2009 database, which for network implementations requires extra effort, only needs to happen once.

Therefore, for ProAdvisors or their clients operating in a network environment, the next update can be implemented normally. The server does not need to be updated separately.

ProAdvisors or their clients operating on stand-alone machines would proceed normally with any of these 2009 releases; no extra effort is required.


You and your fellow QuickBooks ProAdvisors have played a crucial role in identifying some of the issues and workarounds that are identified in postings in our support Knowledge Base.

We very much appreciate your patience and support while we work to resolve the remaining sales tax report issue in QuickBooks 2009.


~ The QuickBooks ProAdvisor Team

  1. The release affects Windows desktop versions of QuickBooks 2009 and QuickBooks Enterprise 9.0. Specific product names include QuickBooks Simple Start, Pro, Premier, and Enterprise Solutions. R10 further affects backwards compatibility with R8 and earlier releases of the same software products.
  2. Here are release notes on QuicKBooks 2009 R10.
  3. Previously reported in recent Alerts dated Nov. 14, Dec., 3, and Dec. 14, 2009. For reference, PDF files of recent Alerts have been posted at this location.
  4. QuickBooks 2009 R9 and R10 will move the underpinnings of the QuickBooks database from Sybase SA10 patch 3712 to patch 3960. Intuit has tested the patch in multiple scenarios and found that with the patch, QuickBooks 2009 shows significant improvements in many areas of data handling, including those areas which are associated with rare instances of data corruption, especially among heavy users.
  5. Backwards compatibility in the QuickBooks 2009 R9 and R10 Accountant Copy includes previous all releases of QuickBooks 2009 and QuickBooks 2008. However, company files in versions of 2009 R9 or later cannot be opened in 2009 R8 or earlier, and vice versa.
© 2009 Intuit Inc. All rights reserved. Intuit, the Intuit logo, Intuit ProConnection, Intuit ProLine, EasyACCT, Lacerte, ProSeries, QuickBooks, QuickBooks ProAdvisor, Quicken, and TurboTax, among others, are trademarks, registered trademarks and/or registered service marks of Intuit Inc. in the United States and other countries. Other parties’ trademarks or service marks are the property of their respective owners and should be treated as such.

Program terms and conditions, pricing, features and service options are subject to change without notice.

This newsletter is provided as a convenience for our customers and is not intended to supplement, modify, or extend the Intuit software license agreement between Intuit and the customer for any Intuit product or service. Terms and conditions subject to change without notice.

Please Note: Intuit respects the personal nature of email communication. Every effort is made to offer only information or products that may be of value to you. This critical alert is not subject to other marketing suppressions or unsubscription from the QuickBooks ProAdvisor Newsletter. Intuit makes every attempt to restrict critical alerts to only those items that are truly critical, such as discovery of a software bug or other issue. If you do not wish to receive even critical alerts, and you desire to halt ALL communications from Intuit across the board, please send an email to The editor will assist you in this effort.

If you would like to change your e-mail address in our database, please update your QuickBooks ProAdvisor Profile. Each newsletter or alert is mailed using the most recent listing in the ProAdvisor Database.

See more information on Intuit’s privacy policies and options here.

If you receive a message that you suspect is a phishing email, please forward it immediately to — this email address is purposely not hyperlinked. Just cut and past the address into your email browser address field. Please visit for additional security information.

Intuit Inc., Customer Communications, 2800 E. Commerce Center Place, Tucson, AZ 85706

QuickBooks ProAdvisor Newsletter

Phishing for Quickbooks

On the topic of Quickbooks… be aware that there is a phishing email scam going around to grab your information.

Intuit – Security Alert:

IMPORTANT UPDATE FOR QuickBooks Customers:  Intuit is receiving reports of individuals receiving fraudulent email from QuickBooks or QuickBooks Online. The emails asks customers to download a plug in to assess their security. Customers should delete this email. As we discover these fraudulent sites (cyber criminals often use the same email repeatedly, although they change web sites), we take them down.

Warning on Quickbooks 2009 R9 update

Important information on QuickBooks 2009 Release 9.      See Web version.


QuickBooks ProAdvisor Critical Alert


Dear Susan Bradley,

Last month we announced QuickBooks 2009 Release 9. [1] This major update introduces many fine changes, including an important update to the underlying QuickBooks database. [2]

That earlier Alert also included advice on using the Accountant’s Copy to overcome the lack of backwards compatibility between R9 and earlier releases. [3]

What’s New: Recent calls to our support centers now show that some users may need extra guidance, especially in network implementations or with QuickBooks Enterprise Solutions 9.0.

Intuit Response: We’ve significantly beefed up our resources to such users with new guidance in our Knowledge Base.


Based on Real Experience of QuickBooks Users

From the Calls We’ve Received: Our support team has created a new update guide to help users with the most likely pitfalls in applying R9. You can find the update guide here:

We think the guide will help your clients avoid common problems.

Please Note: We continue to update these resources based on what our customers are telling us. That is, this is a dynamic site, and when your clients visit the site, it will have the most current information available.


Especially for Your Clients Using Enterprise Solutions 9.0 or with Network Implementations

Few of the calls coming into QuickBooks support have to do with individual users on a stand-alone machine. Most problems arise when the QuickBooks user has only partially updated a networked implementation of QuickBooks.

Server Issues: In this scenario, the user has followed the prompt for an Automatic Update; that action has applied R9 to the networked machine (a “client”as opposed to a “server” in the jargon of information technology). However, the server remains on Release 8.

Then, when the user next tries to open a QuickBooks data file, the user receives an error message, because the QuickBase Database Manager and the data file are on different releases.

One Extra Step: In this scenario, the QuickBooks user needs to update the server to Release 9, using the Manual Update. Instructions on how to do this are part of the Step-by-Step Update Guide noted above.


As You See Fit

Inform Clients as Needed: If you have clients using Enterprise Solutions 9.0, or QuickBooks 2009 over a network, or other clients you suspect will need more support in applying R9, please send them the below link to this useful online guide.

Short URL for Client Convenience: Because some clients have a hard time with longer URLs, we’ve prepared the following short alias to share with your clients:

This is a link that will redirect the user to a different location. Some clients may be more comfortable with the full link given above.

Thanks again for helping your clients with this unique release.


~ The ProAdvisor Team.

  1. The release affects Windows desktop versions of QuickBooks 2009 and QuickBooks Enterprise 9.0. It further affects backwards compatibility with earlier releases of the same software products.
  2. QuickBooks 2009 R9 will move the underpinnings of the QuickBooks database from Sybase SA10 patch 3712 to patch 3960. Intuit has tested the patch in multiple scenarios and found that with the patch, QuickBooks 2009 shows significant improvements in many areas of data handling, including those areas which are associated with rare instances of data corruption, especially among heavy users.
  3. Backwards compatibility in the QuickBooks 2009 R9 Accountant’s Copy includes previous releases of QuickBooks 2009 and QuickBooks 2008