BUG: The SQL Server VDI Backup and Restore Operations Are Not Successful
and
the CoCreateInstance Error Occurs
The information in this article applies to:
Microsoft SQL Server 2000 (all editions)
Microsoft SQL Server 7.0
This article was previously published under Q323602
IMPORTANT: This article contains information about modifying the
registry. Before you modify the registry, make sure to back it up and
make sure that you understand how to restore the registry if a problem
occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the
Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
BUG #: 357231 (SHILOH_BUGS)
SYMPTOMS
Backup or restore operations that use the SQL Server Virtual Device
Interface (VDI) may not succeed and SQL Server logs one of the following
errors in the SQL Server error log:
BackupVirtualDeviceSet::Initialize: CoCreateInstance failure on backup
device 'TDPSQL-00000798-0000'. Operating system error -2147467262 (No
such interface supported).
-or-
BackupVirtualDeviceSet::Initialize: CoCreateInstance failure on backup
device 'TDPSQL-00000036-0000'. Operating system error -2147221163
(Interface not registered).
CAUSE
This problem occurs because a worker thread in SQL Server that was
previously initialized in the Component Object Model (COM) has remained
in a single-threaded apartment (STA). This worker thread then tries to
load the SQL Server VDI. Because the SQL Server VDI is free threaded, it
cannot be loaded to an STA, and one of error messages that is listed in
the "Symptoms" section occur.
WORKAROUND
WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system.
Microsoft cannot guarantee that you can solve problems that result from
using Registry Editor incorrectly. Use Registry Editor at your own risk.
To change the registered threading model for the SQL Server VDI:
Start Registry Editor (Regedt32.exe).
Locate, and then click the following key in the registry:
HKEY_CLASSES_ROOT\CLSID\{40700425-0080-11d2-851f-00c04fc21759}\InprocSer
ver32
Edit the ThreadingModel value from Free to Both.
Locate, and then click the following key in the registry:
HKEY_CLASSES_ROOT\CLSID\{b5e7a132-a7bd-11d1-84c2-00c04fc21759}\InprocSer
ver32
Edit the ThreadingModel value from Free to Both.
Quit Registry Editor.
You may have to stop, and then restart SQL Server for the workaround to
take affect.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products
that are listed at the beginning of this article.
MORE INFORMATION
For more information about how to use the SQL Server VDI, see the
"Virtual Backup Device Samples" topic in SQL Server Books Online.
Last Reviewed: 7/17/2002
Keywords: kbbug KB323602
Best Regards,
Elenara
-----Mensagem original-----
De: Adams, Matt (US - Hermitage) [mailto:maadams AT DELOITTE DOT COM]
Enviada em: quarta-feira, 3 de setembro de 2003 11:02
Para: ADSM-L AT VM.MARIST DOT EDU
Assunto: TDP for SQL v2.2 backup errors..
B/A client 4.1.2.12
TDP for SQL v2.2
SQL 2000 SP3
TSM server 5.1.6.2
AIX 5.1.5
We are having trouble backing up on particular DB. Anyone seen this
before?
>From tdpsql.log
09/03/2003 08:27:26 ACO0302E A failure occured on stripe number (0), rc
=
418
09/03/2003 08:27:26 ANS1245E (RC122) Format unknown
09/03/2003 08:27:26 ACO5452E Unable to delete temporary object:
(USHERNC132SQL\data\0001) (\gns) (\full.2003090308263900000CF4)
09/03/2003 08:27:26 ANS1026E (RC136) Session rejected: Communications
protocol error
09/03/2003 08:27:26 Backup of gns failed.
09/03/2003 08:27:26 ANS1245E (RC122) Format unknown
>From W2K event logs...
18210 :
BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on
backup device 'TDPSQL-00000CF4-0000'. Operating system error 995(The I/O
operation has been aborted because of either a thread exit or an
application
request.).
3041 :
BACKUP failed to complete the command USE master BACKUP DATABASE
[gns] TO VIRTUAL_DEVICE=N'TDPSQL-00000CF4-0000' WITH BLOCKSIZE=512,
MAXTRANSFERSIZE=1048576, NAME=N'full',
DESCRIPTION=N'TDPSQL-00000CF4-0000
(TDP MS SQL V2)'
Any thoughts??
Regards,
Matt
This message (including any attachments) contains confidential
information
intended for a specific individual and purpose, and is protected by law.
If
you are not the intended recipient, you should delete this message. Any
disclosure, copying, or distribution of this message, or the taking of
any
action based on it, is strictly prohibited.
|
