Most Recent Posts
Archiving Old Data Solution
by JamesNT - 06/28/2025 12:06 AM
Need Advice regarding Data Archiving
by JamesNT - 06/28/2025 12:06 AM
Prescription Drug Monitoring Program
by Bert - 06/26/2025 8:25 AM
AI?
by Bert - 06/25/2025 7:52 AM
PRINTING SCHEDULE
by Raj1 - 06/24/2025 9:54 AM
AC Version 12.3
by beagle - 06/15/2025 8:57 PM
A Tale of Woe: Only Partial Backups
by JamesNT - 06/12/2025 3:00 PM
Member Spotlight
barcafan1990
barcafan1990
Brandon, FL
Posts: 272
Joined: June 2012
Newest Members
ESMI, It's me, Paradise Family, MedCode, MZ Medical Billi
4,594 Registered Users
Previous Thread
Next Thread
Print Thread
Rate Thread
Joined: Sep 2006
Posts: 531
Member
OP Offline
Member
Joined: Sep 2006
Posts: 531
I have been having a recurring problem with the letter writer. If I write more than one letter in a row, (such as end of day, Did Not Keep Appointment letters, ) on the secord or third letter I get,

"Exception of the type, "system Out of Memory Exception" was thrown. The letter writer will now close."

Any further attempt to write a letter for this patient or any other, close and open the chart etc. throws the same error. Close AC, restart it and all is well, until you write two or more letters, then the same thing.

AC version 6.5.6
Happens on multiple machines, Windows XP, Windows 7.
Happens running AC directly on the server, which is HP Prolient blade RAID 5 with hot spare, dual processors, Server 8 etc.

Any thoughts? Went one round with AC tech support and this is the first time that did not go well. Will continue with workarounds for now.




Martin T. Sechrist, D.O.
Striving for the "Outcome Oriented Medical Record".
Joined: Jun 2009
Posts: 1,811
Member
Offline
Member
Joined: Jun 2009
Posts: 1,811
Martin,

Good to see you around!

I'll give you a shout later today, but I'm hoping you are available 24-26 Oct.

The short answer is that there is probably not going to be a fix for that error until they release a version that fixes it.

Memory allocation errors are generally because the programmer grabbed data from the DB, put it in an array, and didn't clear the array after he was done using it. When that happens, you can quickly run out of memory, and once you are out of memory, you are also out of luck. The only way you free memory is to quit the program so that the memory is released.

At this point I would ask AC support to pass this to Dev, and see if they can get the fix in the next version.


Indy
"Boss"

Indy's Blog

www.BestForYourPractice.com
Our Name is Our Creed

Moderated by  ChrisFNP, DocGene, JBS, Wendell365 

Link Copied to Clipboard
ShoutChat
Comment Guidelines: Do post respectful and insightful comments. Don't flame, hate, spam.
Who's Online Now
0 members (), 45 guests, and 34 robots.
Key: Admin, Global Mod, Mod
Top Posters(30 Days)
Bert 10
imcffp 3
beagle 3
ESMI 2
Top Posters
Bert 12,884
JBS 2,986
Wendell365 2,366
Sandeep 2,316
ryanjo 2,084
Leslie 2,002
Wayne 1,889
This board is dedicated to the memory of Michael "Indy" Astleford. February 6, 1961 -- April 16, 2019




SiteLock
Powered by UBB.threads™ PHP Forum Software 7.7.5