UltraTax CS ELF Error: There are no electronic files to error check

Alerts and notices
Leave feedback

Contact information (optional):

Leave this blank:

Please tell us how we can make this information more helpful.

Characters left:

In certain instances, creating an electronic file for a return or an extension may generate the following message. "There are no electronic filing files to error check. Either the files were suppressed or there is data entry preventing their creation."

If you receive this message, try the following:

Note: If you have a situation where you have a multi-state return and some of the states and / or the federal return was accepted and you need to generate a new e-file for those rejected returns, you may have to suppress those files from e-filing before you re-create the e-file for the rejected returns. Example: Federal and UT returns were accepted but WV and MD returns were rejected… open Screen ELF for both the federal returns and the UT return, mark the checkbox to suppress the e-file, and try to create your e-file with the WV and MD corrected returns.

Internal notes


Dev implemented logging in the 1040-US ELF DLL (IYUSELF.DLL where Y refers to the year of UltraTax CS) as an attempt to identify the cause of the "there are no electronic filing files to check" issue.

Here are the steps:

  1. Create a file named utwapp.logcsi in \WinCSI\UTYY, where YY refers to the year of UltraTax CS.
  2. Duplicate the "there are no electronic filing files to check" issue.
  3. Have the user e-mail the utwapp.logcsi file from the \WinCSI\UTYY to you, where YY refers to the year of UltraTax CS.
  4. Remove or rename the utwapp.logcsi file.
  5. Obtain the client data that it was duplicated on.
  6. Get the user's operating system including 32-bit vs. 64 bit (Windows 7 64-bit, Windows 8 32-bit, etc.).
  7. Finally, use the known workarounds of having users exit UltraTax and re-open. Let us know which workaround fixed it.
  8. Submit the info in a CF Request.

If the above items do not work, try the following:

  • Delete the contents of the Windows Temporary directory. This is accomplished by accessing Start > Run, typing %temp%, clicking OK, and deleting all contents from the folder which appears. Verify that all programs are closed before doing so.
  • If the problem persists and does not appear to be related to licenses, attempt to reinstall the affected product(s).
  • This has resolved the issue in the past for a segment of users experiencing it, particularly for those receiving the message for 1120 and 1065 clients.
    • If it's for just 1120 and 1065s only - go to Setup > Office Configuration > FileCabinet CS tab > clear the checkbox to print K1 packages to FCS drawer if K1 recipient is also a UT client.
  • Renaming the ELFSTAT.DAT file and then renaming it back.

Share This