This article lists known issues are found in Enterprise Console v. 4.5.
Additional product release information is available in the Release Notes
- (DEF61122) If you attempt to subscribe to a product that has been removed from the warehouse, the GUI crashes and an exception message is generated when opening the bootstrap locations dialogue.
Find the defective subscription by clicking on the subscriptions and looking for one that has a GUID for the product version (and the status column states that the product no longer exists) then deselect the product.
- (DEF 60191) Installing Enterprise Console to a path containing accented characters results in the console dashboard status indicators not displaying correctly. Workaround: install to a path containing only standard US-ASCII characters.
- (WKI 59904) Enterprise Console will not install if only Microsoft .NET 4 is present. .NET 4 replaces .NET 3.5, but does not include some necessary components. Workaround: Install .NET 3.5 SP1 from the Enterprise Console installer prerequisites folder.
- (DEF 59111) Windows Event Viewer may show many errors from MSSQL$SOPHOS. These are spurious, generated by the Microsoft SQL Server 2008 Express installer, and may safely be ignored.
- (DEF 58819) Enterprise Console installs Microsoft .NET Framework 3.5 Service Pack 1 as a prerequisite, because of which you may experience issues with components related to Exchange Web services including:
To resolve these issues, install the update for .NET Framework provided in Microsoft Knowledge Base article 959209 (http://support.microsoft.com/kb/959209).
- Outlook Web Access,
- Office Communications Server integration,
- Outlook Address Book,
- Out of Office notifications.
- (DEF 57377) On a custom install when opting to create the database impersonation account, the installation wizard suggests that the created account can be added to a group of your choice by entering that group name. If you enter a group, the newly-created account will not be added to the group; however, this should not prevent Enterprise Console from functioning. (
- DEF56835 and DEF56836) When using a custom install, if you select the “Use an existing user” option to connect to the database, the username is erroneously saved in the registry as SophosUpdateMgr. This prevents the management service from connecting to the database. The symptoms are that a Connection Failure message is displayed when starting the console.
On the computer hosting the management service:
- In the registry, Navigate to HKLM\Software\Sophos\EE\ Management Tools\DatabaseUser
- Correct the DatabaseUsername and DatabaseUserDomain values.
Note: DatabaseUserPassword is correct and should not be changed as it is encrypted.
- On the computer hosting the database:
Add the user to the Sophos DB Admin group.
- (DEF 56630) If an Internet connection is present, the included Microsoft .NET 3.5 SP1 installer will download the latest .NET installer, even if unnecessary. This can take a long time. Workaround: disable internet access during installation.
- (DEF56407) Distributed Installation: Sophos Management service doesn't start after the required log off/log back on if database instance is present without the appropriate network protocols enabled.
For distributed installations of Sophos Enterprise Console (with SQL Server on a different server) the Sophos Management Service may not start (after the required log off/log back on) if the 'SOPHOS' database instance was created by PureMessage for Microsoft Exchange, or if the chosen SQL Server instance has TCP/IP protocol disabled.
- When installing Sophos Enterprise Console and PureMessage together, you must first install Sophos Enterprise Console.
- If PureMessage for Exchange is already present, or if you are using a SQL Server 2005/2008 database on a different server (a remote database) and the defect occurs, use the SQL Server Configuration Manager to enable the TCP/IP protocol for the database instance and also start the SQL Server Browser service.
- (WKI 53802) pre-requisite .NET 3.5 not installing on Windows 2008 R2
When running the installer on Windows 2008 R2, the pre-requisite installer cannot install for .NET 3.5. Running the installer directly fails for the same reason. On Windows 2008 R2 the .NET 3.5 is a feature that has to be activated, not an application that can be automatically installed.
- (WKI 51823, 52363) Microsoft SQL Server 2008 is incompatible with Windows 2003 Server SP1 and Windows Essential Business Server 2008. Workaround: Before installing Enterprise Console, install Microsoft SQL Server 2005 (Express); When installing Enterprise Console, choose Custom install and deselect SQL Server 2008.
- (DEF 50935) Installing SQL Server Express 2008 SP1 on Windows 7 or Windows 2008 R2 as part of Sophos Enterprise Console installation may fail, showing "InstallShield Wizard Interrupted" and error "Microsoft SQL Server 2008 Express Edition installation failed. Re-run Sophos Enterprise Console setup when this error has been rectified." This is a SQL Server Express 2008 bug. Workaround: re-attempt installation of Enterprise Console.
- (DEF 57375) Sophos Agent and Message Router services stop running after a managed Enterprise Console computer is downgraded. Workaround: manually restart the Sophos Agent and Sophos Message Router services.
- (DEF 61278) Default distribution share reserved name SophosUpdate
When creating an Update Manager distribution, you cannot reference new shares named SophosUpdate because "SophosUpdate" is now a reserved share name used for the default share.
When creating new shares, use other names such as "Update".
In updating policies, when you are selecting a primary or secondary update location, the dropdown list shows the default share paths only in NetBIOS format, for example \\Server\SophosUpdate, although you may need to use the Fully-Qualified Domain Name form, for example \\server.de.acme\SophosUpdate.
Type the FQDN path into the server location update path field.
- (DEF 52458) Where an installation contains multiple SUMs that update directly from Sophos, when setting up a new subscription or editing an existing subscription, the list of available software versions may not immediately contain the latest information. The delay is due to uncertainty about which is the authoritative/master SUM. The delay length is related to SUM update period and number of SUMs updating from Sophos.
do one of the following:
On the management server, open %ProgramFiles%\Sophos\Enterprise Console\Objects.xml in a text editor and find the text
<object name="ServerDataMonitor type="Sophos.Management.Services.Sddma.ServerDataMonitor, Sophos.Management.Services.Sddma" singleton="false">
Change "false" to "true" and save. Restart the Sophos Management service.