Category: RESOLVED

TaxSlayer Pro Online: Michigan Returns with Retirement Exclusion (RESOLVED)

24 May 19
Craig Smith
No Comments

5/28 – Impacted returns have been resubmitted for processing. Acknowledgements should be returning over the next 24-48 hours.


Update: The fix for this is tentatively scheduled to be deployed on Tuesday, May 28th.

We wanted to make everyone aware of an issue discovered with Michigan returns with Retirement Exclusions after the deployment Thursday, May 23rd.  When transmitting these returns, the MeF backup is not being created, ultimately causing impacted MI returns with Retirement Exclusions to be “stuck”. This just means that these returns will not return an acknowledgement until the issue has been resolved and returns resubmitted internally. Our development staff is aware and expects to have the fix deployed live by the end of next week.

VITA/TCE Phones are not currently available (RESOLVED)

22 Apr 19
Kim Manuel
No Comments

The phone system is not currently taking calls.  We are working to resolve.  Please reach out to VITA/TCE Support via chat or email

2018 States not Loading (Resolved)

17 Apr 19
Kim Manuel
No Comments

This was resolved

Update:  Press Ctrl+F5 to reload the page

We are getting reports that certain states such as NY, MA, WV and NJ are not loading.  We are currently investigating

 

 

TaxSlayer Pro Online: Issue Generating PDF with CA Returns (RESOLVED)

01 Apr 19
Craig Smith
No Comments

4/4/2019 – The fix was deployed this morning.


4/3/2019 – Issue 3389 was not deployed this morning as the scheduled deployment was postponed until Thursday, 4/4.


Late last week, Issue 3389 was opened to look into sporadic reports of returns not being able to generate a PDF. Further investigation found that returns with CA added as the state were experiencing sporadic issues generating a PDF from the Summary/Print menu and other print areas inside and outside of the return. The underlying issue causing the print issue specific to CA returns was related to CA returns that reported certain adjustments to CA income. The underlying issue has been resolved by development and the fix will be pushed live with our next deployment (scheduled for Wednesday, April 3rd).

TaxSlayer Pro Online: 2017 Returns Receiving “Unexpected Error” (RESOLVED)

01 Apr 19
Craig Smith
No Comments

10:06am ET – All deployments have been released and access to 2017 returns for those that had issues should be resolved at this time.


10:00am ET – Deployments for 2017 are still going out, however, you will gradually see the issue resolved as the deployments continue.


9:36am ET – Deployments for 2017 are currently going out at this time.


9:00am ET – Our engineers are actively investigating the root cause at this time.


8:45am ET – We have received reports of users receiving “Program Has Received Unexpected Error” message when attempting to open a 2017 return from the Client List. We are actively looking into this issue.

Printing not rendering a PDF (RESOLVED)

10 Mar 19
Kim Manuel
No Comments

10:49 am EST:  All returns for all years should be rendering PDFs as expected


10:17 am EST:  The PDF is generating for new returns, both inside and outside of the return.  There is still period of time where already created returns will not render a PDF for both 2018 and 2017


9:37 am EST:  We are currently working to resolve this.  We have identified the issue.


The PDF is not generating from the client list, submission page or Print/Summary in the following years:

  • 2018
  • 2017

We are currently working to resolve this.

TaxSlayer Pro Online: Printing in a Return – Issue 3062 (RESOLVED)

08 Mar 19
Craig Smith
No Comments

RESOLVED: 3/11/19 – Issue 3062 has been closed out. The fix is now live.


UPDATE: 3/8/19 – The fix is currently working its way through internal testing. Assuming it passes all levels of testing, the fix should be deployed on Monday, March 11th


We have opened a high priority issue with development to look into and resolve the issue related to sporadic reports of users indicating printing issues when inside of a tax return. Below are the details of what we’ve determined as the root cause and why it is so sporadic. We expect to have this corrected soon, hopefully before the weekend.

Any user assigned the below default security templates will NOT be able to generate a PDF from inside of a tax return (Summary/Print, State PDF, and View Forms). They CAN generate a PDF from outside of a return (Client List and Submission page of e-file).

The issue is specifically tied to templates that DO NOT allow transmission of returns to the IRS – specifically the “Send Return to IRS” security role. In the simplest terms, if a Security Template has e-file rights, they can generate a PDF from anywhere inside a return and outside of a return. If a Security Template does not have e-file rights, they CANNOT generate a PDF when inside of a tax return (Summary/Print, State PDF View, and View Forms) but CAN generate a PDF when outside of a return (Client List and Submission page of E-file).

  • Preparer Current Year
  • Preparer All Years
  • Setup Manager
  • Interviewer
  • Reviewer

Note: This will also impact any custom security template with and without e-file rights.

TaxSlayer Pro Online: NY Empire State Child Credit (RESOLVED)

07 Mar 19
Craig Smith
No Comments

3/8/19 – RESOLVED: Issue 3094 is now resolved. Any NY returns being held due to this error can now be submitted for processing. Be sure to open each impacted return from Client List so the updated calc is applied. The range of impacted NY returns falls between 3/6 at 5:00am ET to 3/8 at 5:00am ET.


Issue 3094 was opened on March 6th to resolve an issue where the NY Empire State Child Credit was being awarded in error. Dependents listed on the Federal return age 17 or older are being considered as qualifying children for this credit which is incorrect. The fix for this issue is expected to be deployed tomorrow morning, assuming it passes internal testing. If your site is holding any NY returns where the NY Empire State Child Credit is being awarded in error, you will be able to submit those returns once this post has been marked “Resolved”.