Initially,
look you servers Windows Application logs... I have noticed that after some upgrades the Symantec Endpoint was posting TAMPER Alerts and blocking apps to run.... OR your system try to apply the SQL 2005 Express SP4!!! (please apply manually http://call2fixit.blogspot.com/2012/10/installing-microsoft-sql-server-2005.html)
* Enter below exception and especially if you have Citrix on the machine...
>C:\Program Files\Citrix\Server Resource Management\CPU Utilization Management\bin\ctxcpusched.exe
or Disable/only log TAMPER control (Endpoint Client Management, Tamper tab)
1. Put in your Antivirus exceptions the Symantec folder
2. Upgrade and install SQL service packs (optional)
3. Open your SQL manager and see with which account your BackupExe SQL service is running. It would be nice to have the already privileged account you are using for your Backup Exec services!
If not change and restart service.
* (Always restart the SQL service in your SQL manager prior starting Backup Exec Services)
4. In the Backup Exec services login pop up window, click and select your services credentials to be (or make sure they are) using your default account for example vbesa.
So now your Backup services should have all same account!
Click on Restart All Services and should be OK now!
look you servers Windows Application logs... I have noticed that after some upgrades the Symantec Endpoint was posting TAMPER Alerts and blocking apps to run.... OR your system try to apply the SQL 2005 Express SP4!!! (please apply manually http://call2fixit.blogspot.com/2012/10/installing-microsoft-sql-server-2005.html)
* Enter below exception and especially if you have Citrix on the machine...
>C:\Program Files\Citrix\Server Resource Management\CPU Utilization Management\bin\ctxcpusched.exe
or Disable/only log TAMPER control (Endpoint Client Management, Tamper tab)
1. Put in your Antivirus exceptions the Symantec folder
2. Upgrade and install SQL service packs (optional)
3. Open your SQL manager and see with which account your BackupExe SQL service is running. It would be nice to have the already privileged account you are using for your Backup Exec services!
If not change and restart service.
* (Always restart the SQL service in your SQL manager prior starting Backup Exec Services)
4. In the Backup Exec services login pop up window, click and select your services credentials to be (or make sure they are) using your default account for example vbesa.
So now your Backup services should have all same account!
Click on Restart All Services and should be OK now!
No comments:
Post a Comment