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
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
- :
- User Groups
- :
- Lacerte SDK Group
- :
- Sign In Completion Failed
Sign In Completion Failed
Options
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Printer Friendly Page
JasonAtIntuit
Employee
03-14-2019
01:33 PM
- Mark as New
- Permalink
- Report Inappropriate Content
A few people have reported issues with the login screen when accessing the ODBC driver with an error like:
Authorization Error
Sign In Completion failed. The underlying connection was closed: An unexpected error occured on a send.
or
Unable to validate your online credentials. Please try again later.
I'm currently troubleshooting the issue but it seems related to an issue I heard yesterday where people who were on older versions of Lacerte 2016 and 2017 were seeing the same error logging in to Lacerte. If you're getting the error in the ODBC driver, make sure you can login to Lacerte in whichever year you are trying to access, and run an update.
Also, the key update for this issue had to do with enabling TLS1.2 as our login endpoints were deprecating the older TLS versions, so be sure that your Internet Options in IE have a checkmark for TLS1.2, on the Advanced tab.
I'll update this thread with more information as it is available.
1 Comment 1
JasonAtIntuit
Employee
05-28-2019
10:30 AM
- Mark as New
- Permalink
- Report Inappropriate Content
This tool:
QuickBooks TLS 1.2 Readiness Tool
has been solving several issues related to this - the error sometimes doesn't seem related to sign-in but the underlying cause is usually a problem with the TLS 1.2 connection. Sometimes it shows up as a configuration or resource error, but if the error occurs right after sign-in, this solution is a safe bet.