Hello, based on what I can tell, Tax Cycle is a 32-bit application. When running Client Manager, we continue to run into memory errors. From what I understand, adding more RAM won’t resolve the issue. Is Data Mining my only other option to run queries without hitting out of memory issues? My machine runs Windows 11 Pro, AMD Ryzen 5 PRO 5650GE, 16 GB RAM. A typical Client Manager query would be year: 2024, return type: T1/P1, Transmission: T1 Efile = successful.
The batch should return approximately 6,200 records. If it completes, I would then want 8-10 fields such as: client name, SIN, RRSP contributions, balance owing/refund, preparer ID.
I’ve adjusted Client Manager options to remove unwanted years from monitored folders to help things out and that has helped, however, I’m then re-indexing the database, all the while staff in the office are trying to work. It feels really cumbersome. Re-indexing records from 2015-2024 takes over an hour as well we have 48,000 records across those 10 years to index.
If DataMining is the way to go about it, is the DataMining license annual or one-time?
Are you sure it is not a RAM issue? 16GB of RAM is nothing in today’s world.
I have two tabs open in Chrome. Just this program alone uses 2 Gigabyte.
How much is your usage of RAM in the Task Manager?
Just because one program doesn’t use much RAM doesn’t mean that overall, with other programs running in the background, an additional program can cause issues.
I’m think it’s not. When I run it, TaxCycle is the only thing running. From what I’m reading online, a 32-bit application, like TaxCycle is, can only use 4 GB of RAM on when running on a 64-bit OS such as Windows 11 Pro. I wonder if someone from the TaxCycle dev team to confirm that throwing more RAM at it won’t help too much and I should either look at Data Mining or running reports on segments of client data, not the entire 48,000 dataset. @Elizabeth - are you able to point me in the right direction?
The Client Manager server is a 32-bit application and will use a maximum of 3GB of memory (even on 64-bit operating systems). Adding more memory would only be beneficial if numerous applications were running concurrently on the same server.
From TaxCycle, filters are applied to the search results. If no search has been entered in the search box, all returns will be served. For large result sets, this may lead to memory pressure. To reduce the number of results the server must serve up, try entering the type of return (module) in the search bar. For example, enter T12024 to fetch just your 2024 T1 returns. Combine to fetch multiple years e.g. T12024 T12025
Like the server, TaxCycle itself will use a maximum of 3GB of memory (even on 64-bit operating systems)
Hi Andrew, I believe I’m already doing this and still seeing the issue. I select the year, return type and 2 additional filters. This creates a batch of 1,161 items. Once the batch is selected, I add 4 query fields and run the batch. It runs for about 4-5 minutes and throws an error.
I’ve attached a screenshot to confirm I’m filtering as you suggested and another to show the 4 fields. I’ve also pasted the error.
If that looks as you suggested, then my options are: (a) add another filter to reduce the batch size, such as clients with last name A-E, F-J, and so on or (b) purchase the DataMining module as it may be more suited for what I’m trying to extract out of TaxCycle. I will be attending the DataMining webinar next week to check it out. Maybe there’s another option I haven’t considered?
Are you able to confirm whether what I’m doing in the screenshots is what you suggested?
Error shows as:
Title: Something is not quite right...
Message: TaxCycle has encountered an unexpected problem and was unable to complete this task.
Please call \*\*1-888-841-3040\*\* for assistance with this error.
Details: TaxCycle 14.1.56212.0
System.OutOfMemoryException Exception of type 'System.OutOfMemoryException' was thrown.
Source : PresentationFramework
at System.Windows.Data.BindingExpressionBase.GetSources()
at System.Windows.DependentList.InvalidateDependents(DependencyObject source, DependencyPropertyChangedEventArgs sourceArgs)
at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
at System.Windows.Media.Animation.AnimationStorage.OnCurrentTimeInvalidated(Object sender, EventArgs args)
System.Windows.Media.Animation.AnimationException Cannot animate the 'Angle' property on a 'System.Windows.Shapes.Ellipse' using a 'System.Windows.Media.Animation.DoubleAnimation'. For details see the inner exception.
Source : PresentationCore
at System.Windows.Media.Animation.AnimationStorage.OnCurrentTimeInvalidated(Object sender, EventArgs args)
at System.Windows.Media.Animation.Clock.RaiseAccumulatedEvents()
at System.Windows.Media.Animation.TimeManager.Tick()
at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
at System.Windows.Media.MediaContext.AnimatedRenderMessageHandler(Object resizedCompositionTarget)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
Try entering << T12024 >> into the search bar first. Then apply the prior year and EFILE filters. Based on the image you’ve provided (thanks), the server should only need to serve up ~1200 files rather than ~63,000.
Combine for two or more years -
Let me know if this helps!
That helped, although now I’m getting more results than before. The ‘no prior year return’ filter doesn’t appear to be doing anything. The good news is I can run the query and export my report. I just have no way to see who had no prior return.
When searching for T12024, I have 6,665 records returned:
When adding ‘e filed successful’, the record count is reduced to 6,248:
When adding ‘no prior return’, the record count stays at 6,248, and I was expecting it to be 1,168 as before:
Could this be a bug?
I took a look at the prior year filter. Try << T12024 T12023 >> in the search box. This filter is looking for a ‘prior year’ return in the existing result set. Now there aren’t any 2023 T1 returns (only 2024 T1), the filter is including all returns.
That makes sense, I’ve updated my filter and it’s working as expected. Thanks for your help on this. It’s greatly appreciated.