Error on SBS2003 Standart while running Acronis Image Job

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

Hi Forum,
i write from germany, so i hope you will excuse my english.
I have a job once each week that will make an image of our system disk.
The job runs fine and i have no errors reported by TI.
But every time the job executs i got error in the SBS System log
1.)SQLWriter Ereigniskennung 24583
Sqllib-Fehler: OLE DB-Fehler beim Aufrufen von ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: BACKUP DATABASE wird fehlerbedingt beendet.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: Nicht behebbarer E/A-Fehler für die Datei "{6B19C42A-4375-4942-B809-A839D8F7FB02}5:" 995(Der E/A-Vorgang wurde wegen eines Threadendes oder einer Anwendungsanforderung abgebrochen.).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Native Client
Error message: 0 Seiten wurden für die 'SUSDB'-Datenbank, Datei 'SUSDB' für Datei 1, verarbeitet.

2.) SQLVDI Ereigniskennung 1
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=2488. Thread=8820. Server. Instance=BKUPEXEC. VD=Global\{6B19C42A-4375-4942-B809-A839D8F7FB02}6_SQLVDIMemoryName_0.

3.) SQLVDI Ereigniskennung 1
SQLVDI: Loc=SVDS::CloseDevice. Desc=Abort detected. ErrorCode=(0). Process=2488. Thread=3456. Server. Instance=BKUPEXEC. VD=Global\{6B19C42A-4375-4942-B809-A839D8F7FB02}2_SQLVDIMemoryName_0

4.)MSSQL$BKUPEXEC Ereigniskennung 3041
BACKUP-Fehler beim Abschließen des BACKUP DATABASE BE_DLO-Befehls. Ausführliche Informationen finden Sie im Sicherungsanwendungsprotokoll.

5.)MSSQL$BKUPEXEC Ereigniskennung 18210
BackupVirtualDeviceFile::SendFileInfoBegin: Fehler bei beim Sicherungsmedium '{6B19C42A-4375-4942-B809-A839D8F7FB02}4'. Betriebssystemfehler = 995(Der E/A-Vorgang wurde wegen eines Threadendes oder einer Anwendungsanforderung abgebrochen.).

6.) SQLVDI Ereigniskennung 1
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=3948. Thread=5904. Client. Instance=BKUPEXEC. VD=Global\{6B19C42A-4375-4942-B809-A839D8F7FB02}7_SQLVDIMemoryName_0.

I do not have any idea what this means and how i can get those errors disappear.
By searching the internet i found different threats that claim that this might have to do with not correct running VSS System. so i tried to rerigister the VSS system, but the erros remain.
I´m running also a Symantec Backup Exec Job each night also using VSS (other time) that runs fine without errors.

So please could anyone help me.
Greetings Hartmut

Mon, 09/06/2010 - 07:25
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 24
Comments: 3268

Hello Hartmut!

Welcome to our Forum, we're glad to greet you here! I understand your concern and will gladly help you.

According to the error you've provided, the VSS is really corrupted. The logs also complaint regarding the SQL instances of the Symantec Backup Exec. (... Instance = BKUPEXEC).

The best way to solve the issue is to

  1. Rebuild VSS
  2. Uninstall Symantec and see whether the issue persists

Symantec is actually using another provider for the backup, that's why it never errored out.

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you!

Tue, 09/21/2010 - 11:05
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

Hi Yana,
thank you for your (late) reply.
The error seems to adress only the databases from SQL 2005 (the Instance is running more than one DB) (not MSDE)
Your link "Rebuild VSS" does not point to any specific Artikel ?
I think i already did rebuild the VSS, because before rebuilding the VSS also Symantec rans with errors, but since i rebuild the VSS System it works fine. Symantec is using Microsoft VSS according to its protocol.
So i think that Acronis is using its own VSS provider ? And that is not working !.
I also did a repair installation of Acronis, that did change nothing.
Also the partition i make an image of is not hosting any databank files, they all located on drive D: and i make only Image of C: and E:
Greetings

Tue, 09/21/2010 - 12:33
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

After another Week with no response from Acronis and searching the Internet i have found a resolution.
I will post it here, maybe someone gets the same problem.
There is a service called VSS SQL Writer which normaly logs in with the NT-Authority. Sometime this does not work correctly.
If it uses the Administratot Account instead it will work.
No Problems left so far . Anything works fine.

Mon, 09/27/2010 - 06:55