17:09:32.779 THREAD 93 INFO: DbUtil> addReporterUser> adding REPOTER role to report user! 17:09:32.779 THREAD 93 INFO: doesDbUserExist > Result: true 17:09:32.777 THREAD 93 INFO: doesDbUserExist > loginUsername: REPORTER_sem5SEM5 17:09:32.777 THREAD 93 INFO: DbUtil> addReporterUser> Checking and adding report user! 17:09:32.777 THREAD 93 INFO: DbUtil> addReporterUser> Report login was altered successfully! 17:09:32.777 THREAD 93 INFO: Reset password successfully! 17:09:32.737 THREAD 93 INFO: Altered login default database: ALTER LOGIN with DEFAULT_DATABASE = 17:09:32.721 THREAD 93 INFO: alterReporterLogin > dbName: sem5, reporterUserName: REPORTER_sem5SEM5 17:09:32.721 THREAD 93 INFO: doesDbLoginExist > Result: true 17:09:32.721 THREAD 93 INFO: doesDbLoginExist > loginUsername: REPORTER_sem5SEM5 17:09:32.721 THREAD 93 INFO: DbUtil> addReporterUser> Checking and adding report login! 17:09:32.721 THREAD 93 INFO: DbUtil> addReporterUser> hasPermissionAlterAnyLogin: true 17:09:32.721 THREAD 93 WARNING: DatabaseUtilities> hasUserAlterAnyLoginPermission> Account permission verification done! hasRequiredPermission: true You must recreate or modify the reporting account in SQL Server Management Studio"Ī review of the upgrade-0.log reveals the following error. You may also see the error "The Symantec Endpoint Protection Manager reporting account does not connect to the Microsoft SQL Server database. Upgrade Wizard fails with Warning: Null, when upgrading to Symantec Endpoint Protection Manager (SEPM) to 14.3 RU5
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |