Community
User Guides
Support
Community
Help Forums
English Forum
General
About our Community
General Discussion
News and Feedback
Products
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Beta programs
Feature Requests
Finnish Forum (Tukifoorumi)
Tuotteet Kotiin
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Muut tietoturvatuotteet
Support Articles
Language
English
Suomi
Deutsch
Français
日本語
Svenska
Dansk
Italiano
Nederlands
Norsk
Polski
中文 (繁體)
Products & Services
F-Secure TOTAL
F-Secure SAFE / Internet Security / Anti-Virus
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Common topics
User Guides
Support
Login
|
Register
After upgrading to F-Secure Email and Server Security 14.x, emails are no longer quarantined. Error message: 159 Access denied - F-Secure Community
<main> <article class="userContent"> <h3 data-version="4" data-article="000020341" data-id="issue">Issue:</h3> <p></p><ul><li>After upgrading to F-Secure Email and Server Security 14.x, emails are no longer quarantined. Error message: 159 Access denied</li><li>SQL information such as instance name, database name and the user are not shown on the Web Console, neither in Policy Manager console</li></ul><h3 data-id="resolution">Resolution:</h3> <p><b>Note:</b> When you upgrade to F-Secure Email and Server Security 14.x, you can run the installer locally or using F-Secure Policy Manager "policy based upgrade" option. <a rel="nofollow" href="https://community.f-secure.com/t5/Business-Suite/How-to-upgrade-or-install-F/ta-p/121128">Read</a> more about this topic. However, you still need to configure few sections, as the <a rel="nofollow" href="https://help.f-secure.com/data/pdf/fsess14.00-deployment-eng.pdf">admin guide</a> advises to do so.<br><br>In this case, you can see the lack of permissions and configurations are not completed after the upgrade.<br><br>You can identify this behavior, by checking the logs. The product writes all logs into C:\ProgramData\F-Secure\<br>If you open the quarantine.log, you may be able to see a similar line:<br><br><i>Unable to download quarantine item because of access denied error in E-mail and Server Security<br>2020-01-31 17:21:06.585 [0a4c.0010] I: FQM: Deleting Qid 11518 from storage <br>2020-01-31 17:21:06.585 [0a4c.0010] *E: FQM: Failed to delete Qid 11518 from storage System.IO.DirectoryNotFoundException: A part of the path "C:\Program Files (x86)\F-Secure\Quarantine Manager\quarantine\XXXXXX\Q20190906_000001\Q20191209104816_11518.[eml]" could not be found.<br> for System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)<br> for System.IO.File.InternalDelete(String path, Boolean checkHost)<br> for FSecure.Ess.Fqm.Impl.QuarantineStorage.DeleteMail(String storagePath)<br> with FSecure.Ess.Fqm.Impl.QuarantineProcessor.Delete()</i><br><br>Besides the permissions, the quarantine path was not found, so either it is not configured or it does not exist.<br><br>If you check the TransportAgent.log, you will see another error which denies the access, so the Agent can not process the items.<br>Exception rethrown at [0]: <br><br> <i> for System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)<br> for System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)<br> at FSecure.Ess.FqmApi.IQuarantineManager.QuarantineMail(Mail mail)<br> for FSecure.AntiVirus.Exchange.Transport.QuarantineManager.QuarantineMail(Mail mail)<br> for FSecure.AntiVirus.Exchange.Transport.FSMessageScanner.QuarantineMail(String strPathToSavedMail, Int64 lSavedMailSize, QuarantineReason reason, String reasonDetails, Int64& resQuarantineId, String& resErrorDescription)<br>2020-01-31 17:20:39.958 [36f8.0007] *E: FSecure.AntiVirus.Exchange.Transport.FSMessageScanner: QuarantineMail() Failed System.ServiceModel.Security.SecurityAccessDeniedException: Access was denied.</i><br><br>If you check the F-Secure.Ess.Config.log:<br><br><i>FSecure.ESS_Installer.ViewModel.WizardPageViewModel: Could not set user 'fqmuser' as owner for db 'FSMSE_Quarantine'. Reason: The database principal owns a schema in the database, and cannot be dropped. 2020-01-31 17:20:05.929 [39d4.0001] I: FSecure.ESS_Installer.ViewModel.WizardPageViewModel: Setected quarantine method is 'Local</i><br><br>To solve the issue, follow these steps: <br></p><ol><li>Run <b>F-Secure.Ess.Config.exe</b> as administrator from the target server. <b>F-Secure.Ess.Config.exe</b> is located at C:\Program Files (x86)\F-Secure\Email and Server Security\ui</li><li>Configure the setup for an existing database or create a new database. For the database setup/deployment, you can refer to the <a rel="nofollow" href="https://help.f-secure.com/data/pdf/fsess14.00-deployment-eng.pdf">admin guide</a></li><li>Make sure that permissions are set correctly. You can refer to the F-Secure Community <a rel="nofollow" href="http://community.f-secure.com/t5/Business-Suite/After-upgrading-to-F-Secure/ta-p/121611">article</a> for more details</li></ol> Once you have performed the following: <ol><li>Run/entered the configuration locally</li><li>All the authorizations are in place explained as above.</li></ol> Proceed to open the Email and Server Security web console and test the connection to the quarantine database. <p>Article no: 000020341</p> </article> </main>