- Mark as New
- Permalink
- Report Inappropriate Content
I've connected to the 2020 DBs (IDATA, PDATA, etc) via pyodbc. This has been working for some time.
Recently, however, my queries to the IDATA DB are simply being returned empty - as if I do not have any Clients in the individual Tax Type.
Troubleshooting steps:
- It's a network installation, I've restarted the server and local system.
- Connecting to the same IDATA location using Excel (ODBC) returns the expected results.
- Altering the pyodbc query to find a non-existent field returns an error, so the query structure and connection are presumed to be valid.
- Creating a backup of the individual data, restoring it on the local system, and running the query to point to the local installation returns the results as expected.
- Altering the connection string in the query to point to the PDATA DB returns the expected results.
- Querying the table data (i.e. columns or fields) returns the expected results.
As part of the troubleshooting, I want to refresh the 'Access Confirmation' to reconnect pyodbc to the DB. I changed my login password in the hopes that it would trigger a prompt to reconnect, to no avail.
To be clear, as mentioned in the SDK developer instructions, below are the connections I'd like to refresh or remove and reconnect.
Is this possible? Or does anyone have any other ideas?
*********************************** UPDATE ***********************************
The authorization timeout requested my password. I entered my new password and the query completed without error but the returned results are still empty.
- Mark as New
- Permalink
- Report Inappropriate Content
I'm from Lacerte engineering team and want to check this issue and support you. Can you please send details to LacerteEncryption email so that can troubleshoot further and collect more details.
- Mark as New
- Permalink
- Report Inappropriate Content
@ John_Samuel
Our firm is also having trouble with this issue.
Please advise how to access LacerteEncryption email .
Thank you.
Joneil
- Mark as New
- Permalink
- Report Inappropriate Content
LacerteEncryption@intuit.com
- Mark as New
- Permalink
- Report Inappropriate Content
Turns out the DB was corrupted. Not sure what caused it.
In my case, the CLPack Repair Utility did not fix the corruption.
But here's the workaround:
- Ensure all users are out of Lacerte.
- Create a full backup of all clients in the affected Tax Type.
The above creates a full working DB of the Tax Type. - Rename the existing Tax Type DB folder, e.g. IDATA to IDATA-current
- Move the backup folder into the same location and rename it to IDATA.
- Repeat the process for all affected Tax Types.
Thanks, @JAS & @john_samuel for their assistance.