
- #BACKUP EXEC 2010 SERVICES KEEPS STOPPING HOW TO#
- #BACKUP EXEC 2010 SERVICES KEEPS STOPPING DRIVERS#
- #BACKUP EXEC 2010 SERVICES KEEPS STOPPING DRIVER#
- #BACKUP EXEC 2010 SERVICES KEEPS STOPPING UPGRADE#
- #BACKUP EXEC 2010 SERVICES KEEPS STOPPING PASSWORD#
until blue in the face, but I cannot get past the "Queued" status anymore. So I went through and removed all of the tape drive drivers, updated the tape drive firmware, etc.

I ignored this issue and kept everything running, and it ran fine for several months, and now I am having the old "Offline" tape drive issues and the omnipresent "Queued" status in Veritas.
#BACKUP EXEC 2010 SERVICES KEEPS STOPPING DRIVERS#
However, Windows 2003 keeps telling me that the drivers installed by Veritas will cause problems and will be disabled. Create a task schedule that restart the BE services before the Backup starts and run a. After investing 2-months of hard work, I finally gave up, deleted all of the BackupExec products (including all the new agents that had to be installed on every server in our farm, including Linux machines) and re-installed Veritas v8.6 and all the agents again, and everything started working GREAT again. Nothing would work, no matter how many "free" technical support incidents I was given by Veritas (one at a time.while EVALUATING the stupid software).
#BACKUP EXEC 2010 SERVICES KEEPS STOPPING UPGRADE#
Thinking that newer is better, I decided to try the upgrade to Veritas v9.1 and what a horrific nightmare that turned out to be. It's almost a full-time job just keeping these 3 components happy with each other long enough to get a few backups! It's just INSANE. (Also, I'd welcome any advice regarding any of this from someone who understands it.I have had all of these issues and many more with the Adaptec/Dell PV120/Veritas combination for years.
#BACKUP EXEC 2010 SERVICES KEEPS STOPPING HOW TO#
The second part of the error might be cured if I can find out how to install the PSSnapin, can anybody help me out with this please. Which it then repeats over and over again with different instances where it is called. The term 'Start-SetupProcess' is not recognised as a cmdlet, function, operable program or script file.
#BACKUP EXEC 2010 SERVICES KEEPS STOPPING DRIVER#
Service Control Manager (SCM) stops services and driver services. Evaluation of BE 11d worked fine, so I bought a license. Click the Log On tab and clear the Allow service to interact with desktop checkbox. Why couldn't they have said that on their instructions?!?) but it is returning the error:Īdd-PSSnapin : Windows PowerShell snap-in .Setup is not installed on the machine.Īt C:\Program Files\Microsoft\Exchange Server\Scripts\Register-WSBExchange.ps1:171 char:15 Event id 7034 from source Windows SharePoint Services 3 has no comments yet. OK, I have got the Microsoft script to start running (apparently you have to add -Register after you type Register-WSBExchange to get it running. This can be beneficial to other community members reading the thread. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. Add the Windows Server Backup Features again via Server Manager. Sc.exe description wsbexchange "Enables Windows Server Backup users to back up and recover application dataģ. Sc.exe create wsbexchange binpath= $WsbBinPath type= own start= demand error= ignore obj= LocalSystem DisplayName= " MicrosoftĮxchange Server Extension for Windows Server Backup" Reg add "HKLM\Software\ Microsoft\ windows nt\currentversion\WSBAppExchangeHelper" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f Reg add "HKLM\Software\ Microsoft\ windows nt\currentversion\WSBAppExchangeHelper" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f If ((get- service wsbexchange* | where " /f $WsbBinPath="c:\program files\ microsoft\ exchange server\bin\wsbexchange.exe" enable_wsbexchange.ps1), then execute the script from the Copy and paste the following text to a new Powershell script (e.g. This will allow you to modify the accounts credentials. If the account does exist, then select the account and click Edit. Next, check to see if a system logon account exists. Windows Server Backup Features via Server Manager.Ģ. To fix the problem, open Backup Exec and go to Configuration and Settings > Logon Accounts > Manage Logon Accounts. Microsoft Exchange Server Extension for Windows Server Backupįor Windows Server Backup is installed only on the node that /upgradecms is run from whenĬould you please reinstall the service as the following setups?

The Microsoft Exchange Server Extension for Windows Server Backup service entered the stopped state.
#BACKUP EXEC 2010 SERVICES KEEPS STOPPING PASSWORD#
The admin password hasnt changed, I re-entered it for all the services, but they. Weve had Symantec Backup Exec 2010 running just fine on this server but all of a sudden its services keep on stopping all by themselves and we have to keep on restarting them, but, its unusable at the moment. The only log for the service is an information log that states the the service has entered the stopped state as below.Ĭomputer: Symantec Backup Exec 2010 services keep stopping.
