Has anyone installed 14.3 RU2 yet?

[MDubya]

If you have, any issues/improvements to report? I'm still battling the Audit Log error when upgrading from the Sybase DB to SQL express. :-(

What's new for Symantec Endpoint Protection 14.3 RU2?

TIA!
-Mike

[Mithun Sanghavi]

Hello iamadmin,

Audit Log error?? Please specify the issue in detail along with screenshot and error message please.

Thanks and Regards,

Mithun Sanghavi
Trusted Advisor

[Valentine Leamy]

Please see screenshot

------------------------------
Technical Support
eGOV Jamaica Limited
------------------------------

[Maco Wong]

I have the same error when upgrading from 14.3MP1 to 14.3RU2

[Siva Rathina Pandiyan M]

Hi,
Kindly install the version you had previously and restore the database. Else if snapshot available revert it back to previous state. Now generate a certificate if self signed Symantec certificate is used and start upgrading again. It should go through.

Hope this should help. 

For detailed information https://knowledge.broadcom.com/external/article/205321/upgrade-wizard-fails-with-warning-failed.html

[Valentine Leamy]

If we do the above instructions will the "new certificate" disconnect clients from SEPM hence clients and servers will be using the old certificate rather than the new certificate generate?

------------------------------
Technical Support
eGOV Jamaica Limited
------------------------------

[Maco Wong]

I have tried to create new certificate and run setup. Audit log error still occur.

[Maco Wong]

I have tried to install new certificate but audit log error still occur during installation.

[Maco Wong]

The proposed solution is not worked.

[John Owens]

There may be an issue with your database. Do you have a case opened?

------------------------------
John Owens
Strategic Support Engineer | Symantec Enterprise Division (SED)
Symantec
United States
------------------------------

[MDubya]

Hey John,

Yes, I have a case open for this issue: 32657344

DBValidator came back clean, Certs have been renewed/upgraded. The last thing we have been trying to do is decrease the size of the DB. Currently at 11.5 GB, and we read somewhere that part of the upgrade process will fail if the DB is over 10GB. So far the steps below have not decreased the DB size one iota on a SEPM with ~300 clients.

1. Remove replication partners not in use.
2. Decrease the size of the logs and learned application data. (Application learning.)
3. Change the default settings for the database maintenance schedule.
4. Restart management server and wait at least several hours.
5. Schedule replication partners to occur once or more.

Wait for several hours after each scheduled replication before restarting the upgrade.

Very frustrating issue. And it's exactly the same thing others have described above.

-Mike

[John Owens]

Hi,

You will get a specific error for DB size if that is the issue and the upgrade will stop.

Are you following this:

Reducing the database size when the database is full before an upgrade to Microsoft SQL Server Express (broadcom.com)

Have you uploaded a db backup to Support and asked them to try to reproduce the issue?

Thanks,

------------------------------
John Owens
Strategic Support Engineer | Symantec Enterprise Division (SED)
Symantec
United States
------------------------------

[MDubya]

Thanks for the article link, John, we have these steps scheduled for later this week.

-Mike

[John Owens]

Thanks, Mike. (got your direct message and totally understand)

If anyone can open a case and upload their DB for support to reproduce the issue it may be the quickest answer to resolution. Is anyone able/willing to do that?

------------------------------
John Owens
Strategic Support Engineer | Symantec Enterprise Division (SED)
Symantec
United States
------------------------------

[John Owens]

Also, if anyone can run Symdiag How to collect full support logs for Support with the SymDiag utility on the SEPM and send to me I can take a look.

------------------------------
John Owens
Strategic Support Engineer | Symantec Enterprise Division (SED)
Symantec
United States
------------------------------

[ace1]

@iamadmin and db size issue maybe this is of help...

I had the same problem trying to upgrade, because of db file over > 10GB (I'm still on MP1 now, with embedded db).
I've found that the suggestions above are worthless in reducing physical size, I don't know why Broadcom promote them (they are useful to avoid *increasing* the size, not reducing it).
One way to compact the database is to use the sybase tools (and this would let you solve the problem in 1 minutes in theory), but Broadcom doesn't support them (they were available for the 12.x release I think).

A proper implementation of the installer should copy only recent db records and not hassle the user (if they want to push a radical change of technology, like a DBMS change, the migration workflow should be flawless and with big investment in quality assurance of this process, see also the recent "certificate problems"...)...

But .... anyway.... to "solve" the problem, personally, to reduce the size, being on MP1, I've just uninstalled and reinstalled MP1 (using the recovery key, and restoring previously exported policies). This recreated the database to a proper size, so at least I'm ready to upgrade.
Yes, not elegant, yet another "power it off , reinstall all again", but, well....

------------------------------
Ace It
------------------------------