cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
ashburnconsulting
Level 3

Profile T1 (v2022.0.0): Multiple Problems (Classic Database)

Hi Mario,

 

1. Has Intuit identified the Classic Database dropbox problem source OR still under investigation?

2. What is the ETA on the fix?

3. What is the likelihood that a fix is provided before start of efiling date (Feb-20-2023)?

 

Thanks.

ProFile Duncan
ProFile Team

Profile T1 (v2022.0.0): Multiple Problems (Classic Database)

Hi,

The drop box issue resolution is under final testing. The fix will be in 2022.2.5 due to be released later this month (Jan 2023)
I apologize for the inconvenience but this will be resolved soon

AshleyEsplen
Level 2

Profile T1 (v2022.0.0): Multiple Problems (Classic Database)

I am using 2022.2.5 and my client explorer still doesn't work, unless I make my own computer a shared database but that isn't ideal for tax season if we aren't all sharing the same database.
We used to have it set up on the network but that hasn't worked since I first updated to 2022.

 

I have called in a couple times, and the agents have been unable to solve this for me.
I'd like to get it sorted before I have all of the T1's to e-file.

Please advise.

Mario B
ProFile Team

Profile T1 (v2022.0.0): Multiple Problems (Classic Database)

Hello Ashley, there is no known issues with the client explorer, they have been fixed. I am going to send you an email and open a case for you, please reply to the email so I can reach you, thankyou!

Erusson
Level 1

Profile T1 (v2022.0.0): Multiple Problems (Classic Database)

Hello just wondering if there is a fix with the error “the database is being changed by someone else…etc”? I am having that issue with the 2022 T3 database. I tried to clear and re-index but the same error keeps coming up. It’s only an issue for 2022 T3s. Our 2021 and prior T3s load fine and so do the rest of the 2022 files (T1,T2,FX). we have tried restarting computer and server.

Mario B
ProFile Team

Profile T1 (v2022.0.0): Multiple Problems (Classic Database)

Account4nt
Level 2

Profile T1 (v2022.0.0): Multiple Problems (Classic Database)

We recently updated to 2022.3 and are experiencing the "The database is being changed by someone and cannot be opened for reading (10010)." error when trying to open T1's for 2020, 2021, and 2022.

 

We've tried turning off anti-virus and the steps here but are still experiencing the error:
https://profile.intuit.ca/support/en-ca/help-article/electronic-filing/files-excluded-incorrectly-di...

 

Edit: Forgot to mention we are using classic database, could that be the issue?

Mario B
ProFile Team

Profile T1 (v2022.0.0): Multiple Problems (Classic Database)

Yes, the issue could be with the classic database, I have not heard of any issues with client explorer.

Account4nt
Level 2

Profile T1 (v2022.0.0): Multiple Problems (Classic Database)

I noticed for the databases that are having issues, the .GIX file is missing. There is only a .GDT file. 

What is the .GIX file for? 

Account4nt
Level 2

Profile T1 (v2022.0.0): Multiple Problems (Classic Database)

Anything else I can try? Or does anyone know where the .GIX file went? 

Mario B
ProFile Team

Profile T1 (v2022.0.0): Multiple Problems (Classic Database)

there should be a .GIX and a .GDT created automatically. Have you tryed to setup your classic database file on a local drive.

Account4nt
Level 2

Profile T1 (v2022.0.0): Multiple Problems (Classic Database)

Okay so I tested and I have a better understanding of what's going on now.

There are 2 files the .GDT and .GIX file when using classic database. When you go to "Index" and CLEAR the database, it deletes the .GIX file but NOT the .GDT file. When the user tries to re-index the database, it will give you the error "The database is being changed by someone and cannot be opened for reading (10010)." because the .GDT file is still there. I have to manually delete this file to be able to re-index it.

 

Now the question is was that .GDT file being deleted in previous versions prior to updating to 2022.3? Also is it better to clear the database first and then Index for a cleaner slate or just to re-Index the current database?

Mario B
ProFile Team

Profile T1 (v2022.0.0): Multiple Problems (Classic Database)

In the past, If you reindexed  without clearing the database, the files were duplicated. I recommend to always clear the database before re-indexing.