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

Profile (version# 2023.2.7): Printer issues

Hello,

Running Profile (version# 2023.2.7)

 

1. This issue is for year-2023. On the screen, T183 shows top-right-corner "2023" but printout shows "2022"

 

2. This issue is for all years. When trying to print forms (F12): T183, RC71, AuthorizeRep, get the attached error "The path is not a legal form". I do not get this error when printing other forms (not sure what forms are affected by this error).

 

Kindly assist.

Thanks.

 

pic01.jpg

9 Comments 9
Mauden66
Level 3

Profile (version# 2023.2.7): Printer issues

HI, I just called Intuit about this issue. They told me CRA hasn't approved the T183 for 2023 yet, so apparently you are supposed to wait until it has been approved and Profile has updated the software to show the T183 as 2023.. very inconvenient for those of us who are already seeing clients...

JamesCampbell
Level 5

Profile (version# 2023.2.7): Printer issues

i don't understand why it takes cra and profile so long to get things ready each tax season?? so frustrating!!

ashburnconsulting
Level 3

Profile (version# 2023.2.7): Printer issues

Hello,

Would appreciate a response from a Profile employee on both issues.

 

This issue is for all years and not only 2023:

2. This issue is for all years. When trying to print forms (F12): T183, RC71, AuthorizeRep, get the attached error "The path is not a legal form". I do not get this error when printing other forms (not sure what forms are affected by this error).

 

Thanks.

Mario B
ProFile Team

Profile (version# 2023.2.7): Printer issues

The 2023 issue has been resolved. Please note that the form was marked as draft. As per previous yrs, illegal path,  this iis usually caused by your settings. Please acrchive the setting to start from fresh. You can find the info on how to archive settings here...

 

https://help-content-sso.app.intuit.com/content/pcg/en-CA/L7fG6VObf_CA_en_CA

ashburnconsulting
Level 3

Profile (version# 2023.2.7): Printer issues

Hi Mario,

- Not sure if the problem is Settings. This error started after installation of the latest Profile-T1 version

 

- Archive Settings link doesn't work. Its asking for "Corporate User ID"

 

Kindly assist.

Mario B
ProFile Team

Profile (version# 2023.2.7): Printer issues

I have copied instructions here...

 

How to archive settings
Exit ProFile.
Go to the folder where Settings are stored, usually C:\users\%user name%\documents\My ProFile Data.
Find the Settings folder and the Settings back-up folders. Create a new folder called settings archive. Move the 4 Settings folders into here.
Open ProFile. The software will automatically rebuild new settings folders.
Have the customer test that the issue was resolved
settings archive.png

If the issue you are troubleshooting is resolved, then it means a file was corrupted in one of the Settings folders.

If the issue continues, you may move the settings back to the original location and continue troubleshooting. The settings will be preserved.

How to restore Settings folders
Exit ProFile
Delete the new Settings folder that ProFile created
Open the settings archive folder you created and move the old settings folder back into the My ProFile Data directory, or wherever settings were originally stored.

 

Jajji
Level 2

Profile (version# 2023.2.7): Printer issues

Yes it worked, thank you

 

ashburnconsulting
Level 3

Profile (version# 2023.2.7): Printer issues

Hi Mario,

 

- Firstly, updated to Profile-T1-2023.3.1, and printing error "The path is not a legal form" continues

 

- Your solution of "Settings Archive folder" does not work for us, as we use a "Shared Folder" for the Options-Package

 

- The printing error "The path is not a legal form" always come for blank-returns for all years, and frequently comes for nonblank-returns

 

Kindly assist

Mario B
ProFile Team

Profile (version# 2023.2.7): Printer issues

if you could just try to archive the setitings, whitout using the option package, then we could conclude that the issue is due to your option packages or not. Then we will need to review the option package.