Quickbooks Enterprise crashing

tek9

Active Member
Reaction score
102
Location
NJ
I hope somebody here is experienced with Quickbooks Enterprise.
I have a client, 7 active users on Quickbooks Enterprise 15. It's a workgroup environment, no servers. One of the computers is the database server hosting the company file. Most are Dell Optiplex 9020's running Windows 7 Pro, core i5 processors with either 4 or 8 GB or RAM. The "server" is a core i7 with 8GB RAM. Gigabit business grade network equipment.
They basically have no issues using Quickbooks for regular tasks, but they regularly run large batches of stuff. For example, they don't send invoices via email or print them out one at a time. They generally choose to "Print Later" or "Email Later" when entering invoices and then run the batch process whenever they're ready. They're pretty busy, so when they run the Print or Email process, it can be between 250 to 900 email to send, or invoices/statements to print. Now the user who runs the Email process says that whenever he runs the Send Forms process in QB, first it takes about a minute just to pull up the Send Forms windows, and then it would start the process and then crash after around 70 to 100 emails. It's set up to send the emails via Outlook 2016, and I can see those 70 emails in the Outbox, but QB would abort midway through the process.
I thought maybe since he only had 4GB of RAM in his system, that would cause this, so I upgraded him to 8GB with no difference. I made exceptions in his Antivirus and on the "server's" antivirus to not scan the QB processes and folders, with no difference.
Does anybody know if QB Enterprise can handle sending so many emails at once? Had anybody run into anything similar with this? Is there something I should try?
I was thinking up upgrading the "server's" hard drive to an SSD, Some reports that they run can take a while to load, so I was thinking that the SSD should improve that part, but I'd like to know what you guys think if it would solve the emailing issue?
Thanks for reading.
 
What do the logs say?

They are using Outlook 2016 client but what is on the SMTP side?

Has Intuit support been engaged?

Is this something new with an existing, working installation or has it been happening all of the time?

Nothing wrong with upgrading the server's HD to SSD but my guess is it's related to the Outlook integration. If it was me I'd be having them run a upward scaling send schedule. Start with 50 at a time. All OK, then bump it up by adding 25 at a time to the queue.
 
What do the logs say?

They are using Outlook 2016 client but what is on the SMTP side?

Has Intuit support been engaged?

Is this something new with an existing, working installation or has it been happening all of the time?

Nothing wrong with upgrading the server's HD to SSD but my guess is it's related to the Outlook integration. If it was me I'd be having them run a upward scaling send schedule. Start with 50 at a time. All OK, then bump it up by adding 25 at a time to the queue.
Which logs are you referring to?
The email they're using is a Hostgator hosting package. The problem is not with the email side of things, because I set Outlook to work offline to see how many emails gather in the Outbox before QB crashes. So nothing is hitting the SMTP server before QB goes down. Outlook works fine, it's still open and working while QB throws an error and shuts down.
We haven't contacted QB support because you need to be on a support plan with Enterprise to get support, and they want like over $4,000 for that.
I don't know if it ever worked with this kind of volume of emails. It might have worked with previous versions of QB for them, but not with QB Enterprise 15, which they're using for the past few months.
It was happening even before they had Outlook installed and integrated. They used to use Gmail and had it set up in QB to go via webmail. When that was in effect, we had no way of knowing what, if any, emails went out because I couldn't track the Outbox like I can with Outlook. So they got a domain and setup Outlook, hoping it would be better, but it's not. So I really doubt Outlook is to blame here. I think it's QB crashing on the sending process.
I told them to start with smaller batches, but it's a bit of a pain because they have to select each individual statement to send from the Send Forms list.
 
If they are using QB Enterprise, they have more money than you think. a 5-user version is about $3,400 and single users after that are about $900 each. Plus, QB Enterprise 15 was only released about 10/1/14, so they may still have support depending on when they purchased it.

QB has always been a resource hog, so I'll bet it's more about that than anything else. Add Outlook (another resource hog) and you are going to be in trouble with only 8GB of RAM. Look at the event logs to see what they might tell you about the crash. Try it with no other users logged in (change to single user mode) is also a thought. Also, what version of Outlook? If it's an old one, that could be the problem right there.

If QB is mission-critical for them, and it sounds like it is, I think it's time they spent some money on infrastructure.
 
If they are using QB Enterprise, they have more money than you think. a 5-user version is about $3,400 and single users after that are about $900 each. Plus, QB Enterprise 15 was only released about 10/1/14, so they may still have support depending on when they purchased it.

QB has always been a resource hog, so I'll bet it's more about that than anything else. Add Outlook (another resource hog) and you are going to be in trouble with only 8GB of RAM. Look at the event logs to see what they might tell you about the crash. Try it with no other users logged in (change to single user mode) is also a thought. Also, what version of Outlook? If it's an old one, that could be the problem right there.

If QB is mission-critical for them, and it sounds like it is, I think it's time they spent some money on infrastructure.
QB Enterprise switched to a subscription-only model. So they have to now pay over $4,000 a year just for "support" which they never had a need for. I can understand why it's hard for them to stomach that.
They're using Outlook 2016. Can't get newer than that. They're not using anywhere near 8GB of RAM with all their apps open: Outlook, QB, Access, Word, Excel, so I'm certain bumping up the RAM even more would not make a difference.
I'll try to see event logs, but I don't think I'll get anywhere. They once emailed me a screenshot of the error and the code that was noted was: 15908 92976. I Googled but didn't find anything (useful) on this error code.
Good idea on the single user mode. I'll have them try that and see what happens. Thanks.
 
Good on the 8 gigs....I'd hate to suffer through Quickbooks on a 4 gig system...else it would REALLY be "Slowbooks" instead of Quickbooks.

Have you tried the direct send e-mail..through Intuit? Even though we have our own Exchange server (and naturally Outlook)...we've always had our Quickbooks Premier send through Intuits service.

7 users in a workgroup...is that desktop computer pretending it's a server "dedicated"? Or does an end user sit down at it, using it..and having it try to share? Big "no-no" if so. Is Windows 7 flipped to "server mode"?

I'm wondering if the issue still stems around a desktop operating system. They increased the max concurrent connections from 10 to 20 when they went to Win7....but it's still "20 concurrent sessions". This isn't just SMB shares...it's TCP connections. Have 5 users open Quickbooks from the "server"..there's at least 5x SMB connections...do they access a shared printer too? There's more. Other mapped drives? There's more. Fire off some e-mails? Here's the fun part...a whole crapload of SMTP sessions trying to squirt through rapid fire. In addition to the others. I see that 20 session max hitting the ceiling really quickly.

If they're running QB Enterprise....time to step up and get the network on a dedicated server.
I'd try the direct send e-mail from QB direct to Intuits mail handling services (I saw you mention web mail but dunno if you're just talking about GMail account)
Latest Adobe reader on everyone
Invoice templates...try to simplify it...basic TT fonts or something. Wipe that slate clean just to test.
 
Good on the 8 gigs....I'd hate to suffer through Quickbooks on a 4 gig system...else it would REALLY be "Slowbooks" instead of Quickbooks.

Have you tried the direct send e-mail..through Intuit? Even though we have our own Exchange server (and naturally Outlook)...we've always had our Quickbooks Premier send through Intuits service.

7 users in a workgroup...is that desktop computer pretending it's a server "dedicated"? Or does an end user sit down at it, using it..and having it try to share? Big "no-no" if so. Is Windows 7 flipped to "server mode"?

I'm wondering if the issue still stems around a desktop operating system. They increased the max concurrent connections from 10 to 20 when they went to Win7....but it's still "20 concurrent sessions". This isn't just SMB shares...it's TCP connections. Have 5 users open Quickbooks from the "server"..there's at least 5x SMB connections...do they access a shared printer too? There's more. Other mapped drives? There's more. Fire off some e-mails? Here's the fun part...a whole crapload of SMTP sessions trying to squirt through rapid fire. In addition to the others. I see that 20 session max hitting the ceiling really quickly.

If they're running QB Enterprise....time to step up and get the network on a dedicated server.
I'd try the direct send e-mail from QB direct to Intuits mail handling services (I saw you mention web mail but dunno if you're just talking about GMail account)
Latest Adobe reader on everyone
Invoice templates...try to simplify it...basic TT fonts or something. Wipe that slate clean just to test.
They're not using Intuit's webmail. I think they need a subscription for that, and they're not looking to pay extra as of yet.
The computer is not a dedicated system. It's being used by one of them. What do you mean by flipping Windows 7 to server mode?
The printers are networked directly, not shared via the computers. There's a mapped drive from the other computers to the "Company Share" folder on this same "server" computer.
The webmail they were using was the gmail account, not Intuit's webmail service.
Do you think getting a dedicated desktop computer just for the QB file would help any, or do they really need to get an actual server? If so, would a basic entry level server work for them, or would I have to quote them on of those high-end servers you guys like?
I just feel funny telling them they need more stuff now, after they just spent on a new Enterprise grade printer, domain, hosting, online backup and some other stuff.
Thanks for all the help, btw.
 
Another question:
Servers are generally configured with RAID. I was reading online that Intuit does not recommend having the company file on a RAID volume for performance reasons. How, then, would QB be installed on a server? Do you have a dedicated HDD just for QB? Sounds weird...
 
Which logs are you referring to?
The email they're using is a Hostgator hosting package. The problem is not with the email side of things, because I set Outlook to work offline to see how many emails gather in the Outbox before QB crashes. So nothing is hitting the SMTP server before QB goes down. Outlook works fine, it's still open and working while QB throws an error and shuts down.
We haven't contacted QB support because you need to be on a support plan with Enterprise to get support, and they want like over $4,000 for that.
I don't know if it ever worked with this kind of volume of emails. It might have worked with previous versions of QB for them, but not with QB Enterprise 15, which they're using for the past few months.
It was happening even before they had Outlook installed and integrated. They used to use Gmail and had it set up in QB to go via webmail. When that was in effect, we had no way of knowing what, if any, emails went out because I couldn't track the Outbox like I can with Outlook. So they got a domain and setup Outlook, hoping it would be better, but it's not. So I really doubt Outlook is to blame here. I think it's QB crashing on the sending process.
I told them to start with smaller batches, but it's a bit of a pain because they have to select each individual statement to send from the Send Forms list.

Windows logs as well as QB logs. Ok, since it's happening when Outlook is offline then it has nothing to do with the SMTP side. Can you use another email client such as Thunderbird? Have you tried running one of their repair tools on the DB?

To be honest, unless you find a smoking gun, the smaller batches working up to bigger ones is going to be an important part of the trouble shooting.
 
Another question:
Servers are generally configured with RAID. I was reading online that Intuit does not recommend having the company file on a RAID volume for performance reasons. How, then, would QB be installed on a server? Do you have a dedicated HDD just for QB? Sounds weird...

I think that's leftover from the old days when software RAID was a bit more common on servers. Good hardware RAID controllers on enterprise drivers blow the doors off of a single disk, performance is very very high, so it's not a concern. The vast majority of businesses are running QB on servers with RAID.
 
T What do you mean by flipping Windows 7 to server mode?.

To pay more attention to foreground apps, or background services. There is a toggle switch for that. It can take a desktop operating system and make it run a little bit better as a "server".
Servers automatically do this. Desktop OS is naturally tuned to give more CPU attention to programs that are launched locally, and they don't react to services as quickly. Flipping the radio button choice to have it pay more attention to background services (such as database, or any "service")...of course gives better performance for those services. Such as the Quickbooks database manager.

Go to system properties, Advanced tab, Performance box, Settings button, another Advanced tab, and you'll see the Processor scheduling box there and the radio button choices.
 
Other stuff in my head...the programmatic access within Outlook? Double check those settings/exceptions.
Can't help wondering if the TCP concurrent connection limitations of Windows 7 as the "server" is causing an issue. I'm sure there has to be an event log entry you can find to see if/when the limit is bumped...
I know there are registry edits you can make to remove that limit, but it is against the licensing EULA...as we as professionals should stay away from those pizza tech hacks. You're missing out on money by doing that...when you could be selling a server, along with the labor and maintenance that comes along with graduating a clients network from a little workgroup to a real business network.

Maybe try shutting down 6 workstations (so there are no client connections to the server)...and just running the batch invoicing from the "server" itself...will it complete a large mailout? Or still have the issue?
 
Thanks for all that info. So much to learn.
I wanted to try sending from the "server" itself, but they weren't so eager to do that. Reason being is that they want the statements to come from a certain email account which is only setup in Outlook on one of the other computers. I guess I'll set it up temporarily on the server to test this and we'll see how it goes. Probably next week sometime.
 
Back
Top