"Support Code 62VG-X8MT1" or "Unable to open TBState file for read" when opening Microsoft® Excel® workpapers in CCH® ProSystem fx® Engagement or Workpaper Manager.
"Support Code 62VG-X8MT1" or "Unable to open TBState file for read" when opening Microsoft® Excel® workpapers in CCH® ProSystem fx® Engagement or Workpaper Manager.
The support code "62VG-X8MT1" and/or "Unable to open TBState file for read" may have different root causes:
Known Causes:
- Single instance or multiple instances of Microsoft® Excel® are hung on the current Windows user.
- Press Ctrl+Alt+Delete on the keyboard and click on Task Manager.
- Click on the Details tab of the Task Manager window.
- If the process name EXCEL.EXE exists, highlight the process and click End task.
- Close out of the Task Manager.
- This can also be caused by a bad file in the common folder that was not updated. If the issue continues, rename the common folder and run a repair of Engagement or Workpaper Manager.
- This message can display if there is corruption in the user's engage.opt file. To resolve the message, the engage.opt file will need to be deleted.
- Run a repair to Microsoft Office & Engagement:
- Microsoft® Office (if running Microsoft® Office 365™ perform an online repair instead of a quick repair.)
- Run a repair to Engagement or Workpaper Manager
- This message can display if some Excel Addin and/or Addin Customization files have become corrupted
- Remove any old epace.xla file from any Microsoft® Office folders from prior versions of Microsoft® Office.
- Example: If you are on Microsoft® Office 2016, there will be an C:\Program Files\Microsoft Office\root\Office16\Library folder that contains an epace.xla. Leave that epace.xla alone for now. If there are other folders in the Microsoft Office\root folder that contain Library folders, the Office## folder will need to be renamed and the epace.xla file deleted from that directory. Sometimes there may also be a Library folder in a location like C:\Program Files (x86)\Microsoft Office\Office12.
- Replace epace.xla and epace.dot.
- Delete the excel##.xlb file.
- Reboot the computer.
- Windows has truncated the path to PfxEngagement.exe as PfxEng~1. This issue was identified in both Engagement and Workpaper Manager versions 7.5 and 2017. Please note Engagement and Workpaper Manager versions 7.5 and 2017 are no longer supported and it's recommended to upgrade to a supported version of Engagement or Workpaper Manager.
- This issue is resolved in the latest updates for Engagement and Workpaper Manager v7.5.100.1225 and 2017.4.1. To resolve this issue please download and install the latest update for v7.5 or v2017 on the server and all workstations that are still running this version.
- If you are unable to install the December update, the following is a workaround for the issue:
- Press Windows Key + R
- Type [x]:\Pfx Engagement\WM
- [x] is the drive letter where Engagement is installed
- Copy PfxEngagement.exe and paste it to the desktop.
- Right-click PfxEngagement.exe on the desktop and select Copy.
- Paste the file back into the [x]:\Pfx Engagement\WM directory.
- Select the option "Replace the file in the destination".
- The causes listed above for this message are the known triggers, if you do not get better behavior out of the steps above, please contact support.