You have reached the support section of Enfocus.com. This content is only available in English.
You have reached the support section of Enfocus.com. This content is only available in English.
The heartbleed leak is fixed. To still give older clients (including connection via Connect) the possibility to connect to Switch 12 update 1, we added a new preference to Switch. Before you use this setting, please read the article in our knowledge base: http://www.enfocus.com/en/support/knowledge-base/Is-my-Switch-installationaffected-by-the-heartbleed-bug-channel/
If you set the new preference "Allow older client applications to connect (less secure)" to “Yes”, Switch uses the older SSL certifications for HTTPS communication with Switch Client and Switch Designer.
This type of connection is less secure, but required if you want to connect Switch Server to Switch Client versions older than Switch 12 update 1. If this preference is set to “No” (default), Switch is only able to connect to Switch 12 update 1 Clients and higher and uses the latest SSL certifications for HTTPs communication with Switch Client and Switch Designer.
Problems while using the User Pane
Problems with Script Executors
Problems when updating Configurators via PackManager
Number | Description |
30760 | Crashes in User pane |
30865 | Crashes in Switch 12 Script Executors |
30126 | Not possible to update some configurators via Pack Manager with Switch 12 |
31207 | Certain setups trigger a crash in case of extended encrypted communication. Userpane passwords, ODBC, LDAP preferences. |
31237 | Heartbleed vulnerability |
Network communication issues when using Switch 12 on Windows
When using Switch 12 on Windows (Windows Server 2008 R2 or Windows 7), you may encounter problems with the network communication, resulting in a ‘Switch Designer can’t connect to the Switch Service’ message in Switch and errors from other applications installed on the system. This problem is due to changes made in Switch 12, which trigger a known issue in Windows.
If you’re facing this problem, please check the article in our knowledge base on how to solve it. There you can also find the link to the hotfix from Microsoft.