6/18/2019 at 8:15am ET
The fix has been pushed live.
6/17/2019 at 6:25am ET
The fix for Issue 3679 is scheduled to be pushed live the morning of 6/18/2019.
6/13/2019 at 3:55pm ET:
We have opened a high priority ticket (Issue 3679) for development to review/resolve an issue where users are receiving a 404 error screen when clicking “Continue” to save a dependent/qualifying person entry. We will update this post once this issue has been resolved.
12:01 pm est: The printing issues have been resolved
Printing inside and outside of returns for all years is currently not generating the PDF. We have our engineers looking at the error logs to determine the problem.
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.
The phone system is not currently taking calls. We are working to resolve. Please reach out to VITA/TCE Support via chat or email
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
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).
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.
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:
We are currently working to resolve this.