Citrix or Terminal Server) please review the guidelines for using the plug-in in server environments. If you encounter this error on a server environment (e.g. Foxit-Reader - update-problem the download-page needs an additional warn-info, that the update-feature in FoxitReader is not functioning properly: it will always come as a new full-install in the normal program-path, which conflicts with the portable install, and it always tries to install advertising and 'home-calling'-features. Once you have verified that the FileOpenBroker64.exe is running as a process in your Task Manager, you should be able to open protected documents for which you have permission. After creating the shortcut you can start FileOpenBroker64.exe manually by double-clicking either on the original. To do this you can create a shortcut toĬ:\ProgramFiles\FileOpen\Services\FileOpenBroker64.exeĬ:\Users\ YOUR USERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startupįor launching the FileOpenBroker64.exe at login time. You will also want the FileOpenBroker64.exe to start every time you log in to the machine. If you just installed the FileOpen client plug-in and this is your first time trying to open a protected file, then you need to get the FileOpenBroker64.exe running.If a reboot does not solve the problem, please request technical support. The easiest way to get the broker process running again is to simply reboot. If you have been able to view protected documents until recently, then the broker process was running and has stopped for some reason. Although the MS Office works normally and no issues detected in Windows 8.What we want to do is get the broker process running again. These error messages are displayed when a companion process, FileOpenBroker64.exe, is not running.
0 kommentar(er)
