Home All Groups Group Topic Archive Search About

Urgent SQLDMO Version Problem

Author
21 Mar 2006 3:39 PM
Lee
I have a .Net app that uses SQLDMO to backup and restore databases for SQL
Server 2000. The SQLDMO from my development machine is distributed with the
application and is in the application directory, since the dll does not
register using regsvr32 how will the app locate the DLL? For example I
installed the app on a machine that has MSDE 7 on it and my app uses that dll
instead of the one that it is suppose to use which in turn causes problems
because Ver 7 of the dll does not work with SQL 8 i.e. 2000. How can I get
this dll registered properly?

Author
22 Mar 2006 11:36 AM
Andrea Montanari
hi,
Lee wrote:
> I have a .Net app that uses SQLDMO to backup and restore databases
> for SQL Server 2000. The SQLDMO from my development machine is
> distributed with the application and is in the application directory,
> since the dll does not register using regsvr32 how will the app
> locate the DLL? For example I installed the app on a machine that has
> MSDE 7 on it and my app uses that dll instead of the one that it is
> suppose to use which in turn causes problems because Ver 7 of the dll
> does not work with SQL 8 i.e. 2000. How can I get this dll registered
> properly?

what do you mean by
> since the dll does not register using regsvr32 how will the app
> locate the DLL?
traditionally every application has to locally load DMO components.. and
yes, SQL-DMO v7 can not connect to SQL Server 2000

you can install this components via the Setup CD of Microsoft SQL Server
2000, and are the objects listed as:
;SQL Server service pack 4 SQL-DMO object has been compiled with the newest
Microsoft Visual C++ runtime linked library, msvcr71.dll that must be
redistributed as well;
...\WINDOWS\SYSTEM\msvcr71.dll DestDir: WinSys ; sharedfile
; not licensed by redist.txt but available after installation of MDAC2.6
...\WINDOWS\SYSTEM\odbcbcp.dll; DestDir: WinSys ; sharedfile
; not licensed by redist.txt but available after installation of MDAC2.6
...\WINDOWS\SYSTEM\sqlwoa.dll ; DestDir: WinSys
; not licensed by redist.txt but available after installation of MDAC2.6
...\WINDOWS\SYSTEM\sqlwid.dll ; DestDir: WinSys
...\Programmi\Microsoft SQL Server\80\Tools\Binn\w95scm.dll; DestDir:
DestinationFolder\Binn
...\WINDOWS\SYSTEM\sqlunirl.dll ; DestDir: WinSys
...\Programmi\Microsoft SQL Server\80\Tools\Binn\sqlresld.dll; DestDir:
DestinationFolder\Binn
...\Programmi\Microsoft SQL Server\80\Tools\Binn\sqlsvc.dll; DestDir:
DestinationFolder\Binn
; not licensed by redist.txt but available after installation of MDAC2.6
...\Programmi\Microsoft SQL Server\80\Tools\Binn\Resources\1033\sqlsvc.RLL;
DestDir: DestinationFolder\Binn\Resources\1033
; not licensed by redist.txt but available after installation of MDAC2.6
...\Programmi\Microsoft SQL Server\80\Tools\Binn\Resources\1033\Sqldmo.rll;
DestDir: DestinationFolder\Binn\Resources\1033
...\Programmi\Microsoft SQL Server\80\Tools\Binn\sqldmo.dll; DestDir:
DestinationFolder\Binn ; file to be registered via regserver

DestinationFolder can either be the installation directory of one instance
of Microsoft SqlServer 2000, like ..\Program Files\Microsoft SQL
Server\80\Tools, even if no istance of SQL Server has been installed, or the
installation directory you app, but the first one is recommended. Please do
respect the hierarchy \Binn\Resources\1033 (where 1033 specifies the
language), where needed, in order to grant correct functionality of
Ole-Automation objects.

In order to install SQL-DMO components for MSDE 2000, Microsoft Internet
Explorer 5.5 or higher is required.
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm       http://italy.mvps.org
DbaMgr2k ver 0.18.0  -  DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--------- remove DMO to reply
Author
22 Mar 2006 2:35 PM
Lee
The answer lies in KB326613 which I applied successfully. However I believe
since the customer's machine was windows 2000 that the regsvr32 app on that
machine perhaps was outdated and could not register SQLDMO properly. Don't
really know but it still want register it. Thanks goodness the installed
package created by VB worked.

AddThis Social Bookmark Button