This error is related to the Windows Viewer when trying to view a document or when using the Workflow Designer. You might see the viewer splash screen appear briefly before the following error message is displayed:
The following are the primary factors that can lead to this error:
- Missing files in the DLLs folder.
- The application is being blocked by a firewall, antivirus or proxy.
- The user does not have sufficient permissions to the viewer DLLs.
Missing files in the DLLs folder
Navigate to the User's DLLs for the viewer on the PC. They will be in a folder location similar to this:
C:\Users\(username)\AppData\Local\FileBound\DLLs\(version of FileBound you are using)
Once the folder is located, verify that these two items are in that folder.
FB6LauncherAdmin.exe
FB6LauncherViewer.exe
If either of these items is not in the folder STOP!
This typically means that an AntiVirus is removing the files preventing the viewer from working.
If both listed files are there, select all other items in the folder location and delete them. After you delete all items EXCEPT the FB6LauncherAdmin.exe and FB6LauncherViewer.exe, relaunch your viewer. This process will rewrite the files to your DLLs folder; potentially replacing any missing files and the viewer should now work.
If for any reason you still get the viewer error, continue below.
Review Antivirus, Firewall, or Proxy possibly blocking the viewer/access to the viewer.
Some AntiVirus applications will remove the viewer application files from the DLLs folder, preventing the viewer to work as expected. Typically, it will remove the FB6LauncherAdmin.exe file. If you find that this specific item is missing from your viewer DLLs folder, an exception will need to be added to AntiVirus for the viewer to work.
Firewalls can also block access to the viewer files preventing the viewer to work. To test this, go into the Control Panel and temporarily turn off the Firewall. Then retest launching the viewer. If the viewer works, discuss with your IT how to add an exception to the Firewall for the FileBound viewer as needed.
A proxy can also block access to the viewer files preventing the viewer to work. The Proxy settings can be checked through the Internet Explorer browser. If enabled, temporarily disable this, then retest launching the viewer. If the viewer works, discuss with your IT how to add an exception to the proxy for the FileBound Viewer as needed.
Verify permissions to the viewer DLL location.
Navigate to C:\Users\(username)\AppData\Local\FileBound, then right-click on the folder and go to Properties. Once the window opens, click on the Security Tab.
Select the User from the list and check the permissions. Modify has to be enabled (at the minimum) for the viewer to work.