Open TurboTax

Why sign in to the Community?

  • Submit a question
  • Check your notifications
or and start working on your taxes
Close icon
Do you have a TurboTax Online account?

We'll help you get started or pick up where you left off.

cancel
Showing results for 
Search instead for 
Did you mean: 
damirb
New Member

Line 17900 Error Won't Clear

I am trying to NETFILE my return and I get an error on line 17900 (Principal Residence Designation) that won't clear.  It says that I either did not select an option or selected more than one option.  I only selected one option but the error will not clear.  Everything else seems fine and there are no issues with the other related forms but I cannot get this to clear. 

I am using TurboTax Home & Business 2024.

 

Thanks...Damir

3 Replies

Line 17900 Error Won't Clear

If you are using the TurboTax desktop Home & Business, box 17900 should be checked if you have sold your primary residence in 2024. To verify, go to forms mode, click on Forms at the bottom of the screen, and look for Schedule 3. 

 

If you sold your primary residence in 2024 you must also fill out the T2091 and PRWS forms. The easiest way to do this is to enter the information in the EasyStep mode to ensure you do not forget any information. In EasyStep click on income and expenses >> Principal Residence. If you originally filed it out in the forms mode, we recommend reviewing the section in EasyStep.

 

If you did not sell your primary residence, then box 17900 should not be checked. Verify if forms T2091 and PRWS exist in your list of forms and click on Edit menu >> Forms >> Clear current form and repeat and click on Close current form. 

 

Hope this helps resolve the error.

 

Thank you for choosing TurboTax

 

 

damirb
New Member

Line 17900 Error Won't Clear

I have done all that and the error is still there.  Support escalated as it may be a bug.

 

Damir 

damirb
New Member

Line 17900 Error Won't Clear

I had to redo my tax return in order for the forms to be properly cleared and everything to go through.  Looks like an earlier build of the software had a glitch which persisted but was fixed in later builds.