Quantcast
Channel: Symantec Connect - Products - Discussions
Viewing latest article 19
Browse Latest Browse All 400

Reports generated by SMSMSE 7.9.1.51 are empty

$
0
0
I need a solution

Recently, daily reports generated by SMSMSE version 7.9.1.51 have no information in them for the past week aside from the header, and the template hasn't been altered (this would be for both the detailed and summary reports). Previous to a couple weeks ago, most of the content of the reports was related to the logging of encrypted attachments and some quarantined messages, as that is the setting for that content. I do not want spam in the reports, and that setting is off. The detail template is set to show all types of violations, no filters are applied, all columns (except violating term and file name under 'rule violated') are shown. The executive summary template has all checkboxes marked.

I'm still receiving emailed notifications of SMSME finding the encrypted files in email and logging them. The Event Log also shows the logging of the encrypted attachments, as it should, but I did notice that the logging seems to be truncated to start at 22Nov19 no matter what 'entries since' selection I make. That suggests to me that there is a problem with the logs, maybe a permissions or corruption issue.

I checked the properties of the 'logs' folder in C:\Program Files\Symantec\SMSMSE\7.9\Server\ has security settings for SMSMSE Admins and SMSMSE Viewers and both seem to have appropriate access (full and read, respectively), although I do not know if those are relevant.

I did notice that there are a lot of errors logged for Brightmail license not being valid, even though the Licensing section of SMSMSE shows status of valid with 155 days left (as of today) for both virus definitions and Premium AntiSpam, in case that's important info. SymDiag reports the same issue, although it also suggests my version of SMSMSE is newer than what it thinks it should be. SymDiag thinks that version 7.9.1.0 is the latest. I reinstalled the license file but it did not have an effect on this problem. The virus definitions are up to date.

This is on Windows Server 2016, Exchange Server 2016. SymDiag also suggests that Windows Server 2016 is not supported even though it's listed in the system requirements, as is Exchange Server 2016.

Looking for some pointers on where to go from here. Since nothing has changed with the product, it might be related to a security update for Exchange Server 2016 that was installed on the last date the log worked (KB4523171).

0

Viewing latest article 19
Browse Latest Browse All 400

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>