Known Issues

The following table lists the known issues in Webspace 6.0.

Defect Number Area Description
N/A Sound

Sound Does Not Work in Webspace Sessions

To play sounds in Webspace sessions, re-install proficy-host.windows_x64.exe on your web server. You can find this executable on the install media in the WebServer folder. If Webspace is installed in a virtual environment, make sure the Audio card is connected to the host and that it is available to the virtual machine when powered on.

DE5356 Uninstall

Uninstall keeps Display Driver.

After a Webspace uninstall, all Webspace components should be removed. However, after a reboot, the iFIX Webspace Display Driver is still in the Device Manager.

When upgrading Webspace, you may be prompted to uninstall iFIX Webspace. After the uninstall and a system reboot, the iFIX Webspace Display Driver may still be in the Device Manager. You must manually remove the iFIX Webspace Device Driver.

US12012 Sound

When you turn on the Sound Option for the first time in an iFIX Webspace session, the client session may fail.

After attempting to turn on the Sound Option, stop and then start your Proficy Webspace Application Publishing Service found in Control Pane->System and Security->Administrative Tools->Services. Otherwise, reboot. Then, this allows you to toggle this option on and off.

DE8244 The /p option with iFIX 5.5 and higher versions

The /p command line option does not work in iFIX 5.5 and higher versions.

The /p command line option is not supported in iFIX 5.5 and higher versions, and will not work. For example, the following command line results in an error:

"C:\Program Files (x86)\Proficy\Proficy Webspace\Client\Proficy.exe" -h MyServer -c -a iFIX -r IFIX /puserscreen.grf.

DE8323 Long File Names on Disk Volume

Webspace displays the error " Can Not Start SCADA on Browser session" when iFIX 5.8 and Webspace 5.0 are installed on a disk volume that has 8dot3name disabled.

When using Webspace with iFIX 5.8 on a disk volume with only long file name support (8dot3name disabled), then iFIX SIM iFIX58_SCU_001 is required to start a Webspace session. This issue does not exist with iFIX 5.9 or greater.

DE10226 iFIX .NET Component

"Failed to create component" error appears when re-opening an iFIX picture that contains a .NET Component.

This error will not be encountered if the CacheEnable property in your iFIX picture is set to False.

US12012 Client

Sound Not Working Properly on Webspace Client.

When an Administrator enables the Sound option on the Client Access tab of the Host Options dialog box in the Webspace Admin Console, the Windows Audio Service may fail to start. If this happens, sounds will not play on Webspace clients.

N/A Windows 10 Hosts

32-bit Version of Internet Explorer Fails to Start.

The 32-bit version of Internet Explorer fails to start in Webspace sessions on Windows 10 hosts. Use Microsoft Edge instead.

N/A Windows 10 and Windows Server 2016 hosts

Password Expiration Message Box Clipped.

On Windows 10 and Windows Server 2016 hosts, the message that notifies a user that his or her password is about to expire is clipped.

N/A Windows 8.1 and Windows 10 Clients

Cannot Add a Client Printer.

Cannot add a client printer from Windows 8.1 and Windows 10 clients when the Universal Printer Driver and Windows Printers Drivers are both enabled in the Webspace Admin Console.

N/A Windows 7

Office 2013 and Other Applications Using DirectX Do Not Run in Webspace Sessions.

Applications such as Office 2013 that use DirectX will not run in Webspace sessions on Windows Server 2008 R2 or Windows 7 when Windows Update KB 2670838 is installed. To work around this issue, uninstall KB 2670838.

Background: Windows Update KB 2670838 replaces the user-mode DirectX runtime with a version that requires display drivers to support DirectX. The Webspace display driver does not support DirectX in versions 4.8.1 and earlier. Beginning in version 4.8.2, the Webspace display driver supports DirectX, but only on Windows 8, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2. The Webspace driver only supports DirectX on these versions of Windows because it relies on a Windows component that is not available in earlier versions of Windows.


MIME Types for Needed Extensions Do Not Exist.

When the web server on the host is IIS, and IIS is configured to only serve documents with file extensions that are registered MIME types, files with the following extensions may not download: .deb, .crx, .dmg, .xpi. For example, Firefox may display the following error message when a user attempts to install the plug-in: “Not a valid install package.” To resolve this issue, define a MIME type for the needed extensions as described in Microsoft Knowledge Base article 326965 ( For the Chrome Extension, specify the MIME type as application/gg-chrome.

N/A Total Defense Anti-Virus

Sessions Fail to Start on Webspace Hosts after an Upgrade of the Operating System.

Sessions fail to start on Webspace hosts after the operating system is upgraded. To work around this issue, uninstall and reinstall the Webspace Display Driver: Users must disable the firewall from Total Defense Anti-Virus before a client is able to connect to a Webspace host.

DE106751 iFIX Autologin iFIX Windows Autologin user does not work with the Webspace Client.

For Webspace auto login to work, be sure to enable the Integrated Windows Authentication option in the Host Options dialog box > Security tab, and add the SHOWIFIXLOGIN=0 line in the Fixuserpreferences.ini file in the iFIX Local folder under the WebspacePreferences section.

N/A Firefox Encrypted browser session does not open in Firefox.

Firefox does not, by default, recognize certificates in the Windows certificate store. Use an enterprise policy to add CA certificates and set the ImportEnterpriseRoots key to True. In Firefox, type about:config to access the configuration. Configure the security.enterprise_roots.enabled setting to true. For more information, see:

N/A Zero Install App

When you run the Webspace App and the Webspace App is either not installed or not enabled (for example, the useApp URL parameter is set to false), only text can be cut, copied, or pasted between local and remote applications.

In addition, users must type CTRL+X, CTRL+C, and CTRL+V to cut, copy, and paste text between local and remote applications. In this configuration, the Cut, Copy, and Paste menu options of applications running in a Webspace session cannot be used to transfer data between local and remote applications; they can only be used to transfer data between applications that are running within the Webspace session.

N/A Internet Explorer

When a user runs the Webspace App in Internet Explorer and the Webspace App is either not installed or not enabled, the first time the user types CTRL+X, CTRL+C, or CTRL+V, Internet Explorer may display the following message:

“Do you want to allow this webpage to access your Clipboard?

After the user dismisses this message by clicking either Allow access or Don’t allow, double characters may be displayed every time the user presses a key. To work around this issue, press and release the CTRL key.

In addition, in the case where the user types CTRL+C, the selected text may be replaced by a “c”. To work around this issue, use the application’s Undo function (e.g., type CTRL+Z) to restore the deleted text.

The above message is only displayed once per session. These issues do not occur when the user subsequently presses CTRL+X, CTRL+C, or CTRL+V to cut, copy, or paste text within an instance of the Webspace Web App.

N/A All browsers When you run the Webspace App in Google Chrome or Mozilla Firefox and types CTRL+N or CTRL+T, the browser opens a new window or a new tab, respectively. Similarly, when a user runs the Webspace Web App in Internet Explorer and types CTRL+O or CTRL+P, Internet Explorer opens its File Open or Print dialog, respectively. In these, and other cases, browsers do not allow the Webspace App to suppress their default behavior.
N/A Safari When the Webspace App is moved to a background tab on Safari on Mac OS X, the client is disconnected from the session.
N/A Internet Explorer 11 When users browse to Webspace Hosts from Internet Explorer 11 on Windows 7, they are prompted to install the Webspace App even if the app has been installed.
N/A Scaling DPI Scaling may not work in the Webspace App.
N/A All browsers The Webspace App may not start automatically after it is installed. If this happens, click the reload link.
N/A Windows Server 2019 When the Webspace Host installer is run on Windows Server 2019, the computer may not restart when the installer’s Restart button is clicked. If this occurs, simply restart the computer from the Start menu.
N/A 64-bit Chrome and Firefox No content is displayed in the browser when 64-bit Chrome or 64-bit Firefox is run in a Webspace session. To work around this issue in Firefox, set browser.tabs.remote.autostart.2.false in about:config. There is no known workaround for this issue in Chrome
N/A Microsoft Word Files cannot be saved on the local computer from Microsoft Word running in a Webspace session on a Windows 10 host.
N/A Webspace Admin Console The context-sensitive help does not display or displays the wrong content. The workaround is to use the help from the Help menu from within the application.
N/A Session Startup Sometimes the time needed to start the first WebSpace client session appears long. This applies to the first session only.
DE116666 Session Startup When using the certificate installed with Webspace and strong encryption, you cannot start a Webspace session with the IP address of the WebSpace server. The IP address cannot be used for the host name. Use the Full Computer Name in the URL instead.
N/A Session Startup The WebSpace session cannot be established and an HTTP Error 500.19 Internal Server Error appears. If this occurs, delete the Web.config file in C:\Program Files\Proficy\ ProficyWebspace\Web folder, and then try to establish a connection again.
N/A Relay Server When using the Failover Relay Server with Strong Encryption, the clients are not able to connect to a secondary Webspace Server.

In this instance, Webspace client sessions can connect to the primary Webspace server. But, when the primary server becomes unavailable, clients are unable to connect.