Welcome back! Ask questions, get answers, and join our large community of tax professionals.
- Topics
- Training
- Community
- Product Help
- Industry Discussions
- User Groups
- Discover
- Resources
In anticipation of the upcoming Exempt Org and Texas Franchise deadlines (5/15), we've compiled a list of the most common questions here.
In anticipation of the upcoming Exempt Org and Texas Franchise deadlines (5/15), we've compiled a list of the most common questions here.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Intuit Accountants Community
- :
- Lacerte Tax
- :
- Lacerte Tax Discussions
- :
- Slip Sheet Editor - SSLTR[NN] related errors
Slip Sheet Editor - SSLTR[NN] related errors
Options
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
steven
Level 5
02-24-2022
05:05 PM
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
We are experiencing "Catastrophic Failures" that, in the F10=> Errors tab, point to access issues with SSLTR[NN] files. Users are getting these errors while performing basic tax processing and when sending eSignature requests.
SSLTR[NN] are the these are the slip sheet files. We have been modifying one of these to use as an internal cover document and manually print the form to paper. It's not part of the tax return print options.
We realized yesterday that if the document was open for editing (we are still tweaking its content) that we get these errors. So, it appears that the file is locked for editing. I have now learned is that just opening the Slip Sheet editor will cause the errors.
These crashes are occurring even if a form is not being viewed. I can see that a user may want to look at a form while one is being edited, it would seem that a temp copy should be made for editing and when save then replace the stored copy.
Opening the tool, should not cause a crash.
Support was not able to help with the issue. They had me reboot the server to clear the lock.
Labels
