zhudson Posted February 11, 2015 Report Share Posted February 11, 2015 I have become so frustrated with this years ATX max. I'm able to occasionally open ATX, complete a few returns, but as soon as I try to reenter the program the next day I get kicked out before I can even type my password. This program has encountered an unexpected error and needs to close, with this text accompanying it: Session Summary Information: Date/Time: 2/11/2015 1:34:40 PM ApplicationVersion: 14.4.5500.32074 CommandLine: "C:Program Files (x86)CCH Small Firm ServicesATX2014ATX.exe" CurrentCultureName: en-US CurrentUICultureName: en-US DnsDomainName: Duration: 00:00:09.3105708 HostName: zach MemoryMB: 8057 OSArchitecture: Amd64 OSCultureName: en-US OSFullNameWithServicePack: Windows 8 OSVersion: 6.2.9200 ProcessorCores: 4 OSVersion: 6.2.9200 RuntimeVersion: 4.0.30319.34014 OSVersion: 6.2.9200 TerminalServer: False System.NullReferenceException: Object reference not set to an instance of an object. at MS.Internal.PrintWin32Thunk.AttributeNameToInfoLevelMapping.InfoLevelCoverageList.Release() at MS.Internal.PrintWin32Thunk.EnumDataThunkObject.GetPrintSystemValuesPerPrintQueues(PrintServer printServer, EnumeratedPrintQueueTypes[] flags, Queue`1 printObjectsCollection, String[] propertyFilter) at System.Printing.PrintQueueCollection..ctor(PrintServer printServer, String[] propertyFilter, EnumeratedPrintQueueTypes[] enumerationFlag) at System.Printing.PrintServer.GetPrintQueues(EnumeratedPrintQueueTypes[] enumerationFlag) at Sfs.Runtime.Printing.Services.QueueManager.UpdatePrintDevicesTask() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() Can anyone help??? Quote Link to comment Share on other sites More sharing options...
B. Jani Posted February 11, 2015 Report Share Posted February 11, 2015 I believe a call to ATX help line is needed. 2 Quote Link to comment Share on other sites More sharing options...
zhudson Posted February 11, 2015 Author Report Share Posted February 11, 2015 I've finally managed to operate ATX, I found that my print spooler service needs to be stopped in order for ATX to start up. Back to work for me!! But now I can't print :/ Quote Link to comment Share on other sites More sharing options...
Lee B Posted February 11, 2015 Report Share Posted February 11, 2015 There have been some recent posts on the ATX Board with similar problems. Several posters had to uninstall and reinstall their printers to get going again. Quote Link to comment Share on other sites More sharing options...
Jack from Ohio Posted February 12, 2015 Report Share Posted February 12, 2015 Call tech support. You have an installation, program interference or some other similar problem. Quote Link to comment Share on other sites More sharing options...
Pacun Posted February 12, 2015 Report Share Posted February 12, 2015 Start the print spooler service after you start ATX and call tech support Quote Link to comment Share on other sites More sharing options...
Pacun Posted February 12, 2015 Report Share Posted February 12, 2015 Test this. Make your default printer a PDF printer, then make your default printer another physical printer in your office. Then make your current printer your default printer. If you only have issues with your current printer (out of 4, since no printer gives no error), then the issue is not ATX but your printer driver or your printer device limitation. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.