Connect via sqldmo

Attempting to connect to MSDE 2000 via sqldmo w/ vb 6 app. For example,
oSqlServer.Connect sSrvName, "sa", sPswd
However, receiving the following error message "Not associated with a
trusted SQL Server connection"
I've looked on microsoft support, which offered a workaround for this error
(kb #889615). However, the workaround applied to Win98. This error is
occuring on a Win xp machine.
any help is appreciated.
hi Jim
jim wrote:
> Attempting to connect to MSDE 2000 via sqldmo w/ vb 6 app. For
> example, oSqlServer.Connect sSrvName, "sa", sPswd
> However, receiving the following error message "Not associated with a
> trusted SQL Server connection"
> I've looked on microsoft support, which offered a workaround for this
> error (kb #889615). However, the workaround applied to Win98. This
> error is occuring on a Win xp machine.
>
usually that exception means MSDE has been installed without allowing
standard SQL Server authenticated connections but trusted connections only
(that is the default)
please have a look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;285097 for futher
info on how to modify the Windows registry to modify the setting..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Hi Andrea,
That absolutely worked! Your help is greatly appreciated. However, it
appears that I have run into another problem when attempting to attach db
files the msde installation.
I'm receiving the following error:
Error -2147216399. Device activation error. The physical file name
'C:\Program' may be incorrect.
I initially that this was due to permission error, so I included
ALLOWXDBCHAINING=1 in the setup parameters, but to no avail. Would it the
actual file location? That is, the space between "Program" and "Files"?
"Andrea Montanari" wrote:

> hi Jim
> jim wrote:
> usually that exception means MSDE has been installed without allowing
> standard SQL Server authenticated connections but trusted connections only
> (that is the default)
> please have a look at
> http://support.microsoft.com/default.aspx?scid=kb;en-us;285097 for futher
> info on how to modify the Windows registry to modify the setting..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||hi Jim,
jim wrote:
> Hi Andrea,
> That absolutely worked! Your help is greatly appreciated. However, it
> appears that I have run into another problem when attempting to
> attach db files the msde installation.
> I'm receiving the following error:
> Error -2147216399. Device activation error. The physical file name
> 'C:\Program' may be incorrect.
if you are using DMO to perform attabch, backup, restore operations you have
to better enclose paths in square brackets like
fileName = "[c:\program files\folder with spaces\file with spaces.xxx]"
if they include spaces..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Hi Andrea,
Sweet. I will definitely do so. I forgot that the AttachDB() or sp_attach_db
is pretty much a wrapper for CREATE DATABASE.
Thanks again for all of your help.
"Andrea Montanari" wrote:

> hi Jim,
> jim wrote:
> if you are using DMO to perform attabch, backup, restore operations you have
> to better enclose paths in square brackets like
> fileName = "[c:\program files\folder with spaces\file with spaces.xxx]"
> if they include spaces..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>

Connect to SQL server 2005 using SQLDMO

Hi all
i need to know if sql dmo can connect to SQL server 2005
if can! how can i do this ?
i have this code
Dim xServer a SQLDMO.Server
.....bla..bla...
xServer.LoginSecure = True
xServer.Connect("SQLServer2005")
but it cant connect.
is there anyother way ?
thks
JSB
Hi,
What are you trying to do with sqldmo?
Ken
"Joo Santa Brbara" <joaosb@.i24portugal.com> wrote in message
news:OA1xjFcZFHA.3400@.tk2msftngp13.phx.gbl...
Hi all
i need to know if sql dmo can connect to SQL server 2005
if can! how can i do this ?
i have this code
Dim xServer a SQLDMO.Server
.....bla..bla...
xServer.LoginSecure = True
xServer.Connect("SQLServer2005")
but it cant connect.
is there anyother way ?
thks
JSB
|||i just want the get databases listname
thks
"Ken Tucker [MVP]" <vb2ae@.bellsouth.net> wrote in message
news:%23cgSblcZFHA.3280@.TK2MSFTNGP09.phx.gbl...
> Hi,
> What are you trying to do with sqldmo?
> Ken
> --
> "Joo Santa Brbara" <joaosb@.i24portugal.com> wrote in message
> news:OA1xjFcZFHA.3400@.tk2msftngp13.phx.gbl...
> Hi all
> i need to know if sql dmo can connect to SQL server 2005
> if can! how can i do this ?
> i have this code
> Dim xServer a SQLDMO.Server
> ....bla..bla...
> xServer.LoginSecure = True
> xServer.Connect("SQLServer2005")
> but it cant connect.
> is there anyother way ?
> thks
> JSB
>
>
|||Hi,
Use the sp_databases stored procedure to list database names.
Dim strConn As String
Dim conn As SqlConnection
Dim cmd As SqlCommand
Dim dr As SqlDataReader
strConn = "Server =(local);"
strConn &= "Database = ; Integrated Security = SSPI;"
conn = New SqlConnection(strConn)
cmd = New SqlCommand("sp_Databases", conn)
cmd.CommandType = CommandType.StoredProcedure
conn.Open()
dr = cmd.ExecuteReader
If dr.HasRows Then
Do While dr.Read
Trace.WriteLine(String.Format("Name {0} Size {1}", _
dr.Item("Database_Name"), dr.Item("Database_Size")))
Loop
End If
dr.Close()
conn.Close()
Ken
"Joo Santa Brbara" <joaosb@.i24portugal.com> wrote in message
news:OWYlApcZFHA.3164@.TK2MSFTNGP09.phx.gbl...
i just want the get databases listname
thks
"Ken Tucker [MVP]" <vb2ae@.bellsouth.net> wrote in message
news:%23cgSblcZFHA.3280@.TK2MSFTNGP09.phx.gbl...
> Hi,
> What are you trying to do with sqldmo?
> Ken
> --
> "Joo Santa Brbara" <joaosb@.i24portugal.com> wrote in message
> news:OA1xjFcZFHA.3400@.tk2msftngp13.phx.gbl...
> Hi all
> i need to know if sql dmo can connect to SQL server 2005
> if can! how can i do this ?
> i have this code
> Dim xServer a SQLDMO.Server
> ....bla..bla...
> xServer.LoginSecure = True
> xServer.Connect("SQLServer2005")
> but it cant connect.
> is there anyother way ?
> thks
> JSB
>
>

Connect to SQL server 2005 using SQLDMO

Hi all
i need to know if sql dmo can connect to SQL server 2005
if can! how can i do this '
i have this code
Dim xServer a SQLDMO.Server
....bla..bla...
xServer.LoginSecure = True
xServer.Connect("SQLServer2005")
but it cant connect.
is there anyother way '
thks
JSBHi,
What are you trying to do with sqldmo?
Ken
--
"Joo Santa Brbara" <joaosb@.i24portugal.com> wrote in message
news:OA1xjFcZFHA.3400@.tk2msftngp13.phx.gbl...
Hi all
i need to know if sql dmo can connect to SQL server 2005
if can! how can i do this '
i have this code
Dim xServer a SQLDMO.Server
....bla..bla...
xServer.LoginSecure = True
xServer.Connect("SQLServer2005")
but it cant connect.
is there anyother way '
thks
JSB|||i just want the get databases listname
thks
"Ken Tucker [MVP]" <vb2ae@.bellsouth.net> wrote in message
news:%23cgSblcZFHA.3280@.TK2MSFTNGP09.phx.gbl...
> Hi,
> What are you trying to do with sqldmo?
> Ken
> --
> "Joo Santa Brbara" <joaosb@.i24portugal.com> wrote in message
> news:OA1xjFcZFHA.3400@.tk2msftngp13.phx.gbl...
> Hi all
> i need to know if sql dmo can connect to SQL server 2005
> if can! how can i do this '
> i have this code
> Dim xServer a SQLDMO.Server
> ....bla..bla...
> xServer.LoginSecure = True
> xServer.Connect("SQLServer2005")
> but it cant connect.
> is there anyother way '
> thks
> JSB
>
>|||Hi,
Use the sp_databases stored procedure to list database names.
Dim strConn As String
Dim conn As SqlConnection
Dim cmd As SqlCommand
Dim dr As SqlDataReader
strConn = "Server =(local);"
strConn &= "Database = ; Integrated Security = SSPI;"
conn = New SqlConnection(strConn)
cmd = New SqlCommand("sp_Databases", conn)
cmd.CommandType = CommandType.StoredProcedure
conn.Open()
dr = cmd.ExecuteReader
If dr.HasRows Then
Do While dr.Read
Trace.WriteLine(String.Format("Name {0} Size {1}", _
dr.Item("Database_Name"), dr.Item("Database_Size")))
Loop
End If
dr.Close()
conn.Close()
Ken
"Joo Santa Brbara" <joaosb@.i24portugal.com> wrote in message
news:OWYlApcZFHA.3164@.TK2MSFTNGP09.phx.gbl...
i just want the get databases listname
thks
"Ken Tucker [MVP]" <vb2ae@.bellsouth.net> wrote in message
news:%23cgSblcZFHA.3280@.TK2MSFTNGP09.phx.gbl...
> Hi,
> What are you trying to do with sqldmo?
> Ken
> --
> "Joo Santa Brbara" <joaosb@.i24portugal.com> wrote in message
> news:OA1xjFcZFHA.3400@.tk2msftngp13.phx.gbl...
> Hi all
> i need to know if sql dmo can connect to SQL server 2005
> if can! how can i do this '
> i have this code
> Dim xServer a SQLDMO.Server
> ....bla..bla...
> xServer.LoginSecure = True
> xServer.Connect("SQLServer2005")
> but it cant connect.
> is there anyother way '
> thks
> JSB
>
>

Connect to SQL Server 2005 Express Edition using SQLDMO

Hi!
I have small testing sqldmo.vbs script to check sqldmo connectivity:
Dim srv
Set srv = CreateObject("SQLDMO.SQLServer")
srv.LoginSecure = True
srv.Connect "(local)" ' Here is error when trying to connect to Express
Edition
MsgBox srv.VersionString
Under Windows 2000 with SQL Server 2000 it works fine.
But under Windows XP with SQL Server 2005 Express Edition my test fails
with message:
Windows Script Host
--
Script: C:\sqldmo.vbs
Line: 4
Char: 1
Error: Unspecified error
Code: 80004005
Source: (null)
--
I checked version of sqldmo.dll under Windows XP. It is 2000.85.1054.0.
File with the same version is included in Microsoft SQL Server 2005
Backward Compatibility Components. So i believe my test should work with
2005 Express Edition.
What am i doing wrong?Well for one make sure your instance of Express is set to allow remote
connections and that TCPIP is enabled. But in any case I don't think DMO is
upwards compatible with any 2005 editions. While some things may work it
certainly does not know about any of the new features. I believe what the
backwards compatibility part meant was that DMO in the 2005 install can talk
to 2000 machines. For 2005 you should use SMO.
Andrew J. Kelly SQL MVP
"Igor Solodovnikov" <IgorSolodovnikov@.discussions.microsoft.com> wrote in
message news:op.s253k8mfn8ihmu@.iw2k.helpmicro.local...
> Hi!
> I have small testing sqldmo.vbs script to check sqldmo connectivity:
> Dim srv
> Set srv = CreateObject("SQLDMO.SQLServer")
> srv.LoginSecure = True
> srv.Connect "(local)" ' Here is error when trying to connect to Express
> Edition
> MsgBox srv.VersionString
> Under Windows 2000 with SQL Server 2000 it works fine.
> But under Windows XP with SQL Server 2005 Express Edition my test fails
> with message:
> --
> Windows Script Host
> --
> Script: C:\sqldmo.vbs
> Line: 4
> Char: 1
> Error: Unspecified error
> Code: 80004005
> Source: (null)
> --
>
> --
> I checked version of sqldmo.dll under Windows XP. It is 2000.85.1054.0.
> File with the same version is included in Microsoft SQL Server 2005
> Backward Compatibility Components. So i believe my test should work with
> 2005 Express Edition.
> What am i doing wrong?|||Thank you for answer. Actually now i dont need any new features of 2005
editions. I need only old features accessible through old DMO.
Actually my test already working but it started to work only after full
system reboot. Restarting services does not helped me. So now i need some
investigation to figure out which particular configuration options affect
SQLDMO connectivity.
On Tue, 10 Jan 2006 18:26:52 +0200, Andrew J. Kelly
<sqlmvpnooospam@.shadhawk.com> wrote:

> Well for one make sure your instance of Express is set to allow remote
> connections and that TCPIP is enabled. But in any case I don't think
> DMO is
> upwards compatible with any 2005 editions. While some things may work it
> certainly does not know about any of the new features. I believe what the
> backwards compatibility part meant was that DMO in the 2005 install can
> talk
> to 2000 machines. For 2005 you should use SMO.
>|||hmm, try using ".\sqlexpress" in your connect statement.|||Thank you for your hint. ".\sqlexpress" really work. But now i have system
where ".\sqlexpress" works but "(local)" does not. Why? I need "(local)"
because my application has no clue to what version of SQL Server it
connects...
On Tue, 10 Jan 2006 19:34:34 +0200, jonel.rienton@.gmail.com
<jonel.rienton@.gmail.com> wrote:

> hmm, try using ".\sqlexpress" in your connect statement.
>|||(local) is your default sql server installation, .\sqlexpress is a
named instance; as you probably know, one can have multiple instance of
sql server installation in one box.|||If you really need (local) to work for some reason, your only option is to
uninstall SQL Express and reinstall it as the default instance in the
Advanced Options section of setup.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
<jonel.rienton@.gmail.com> wrote in message
news:1137097362.319395.67730@.g14g2000cwa.googlegroups.com...
> (local) is your default sql server installation, .\sqlexpress is a
> named instance; as you probably know, one can have multiple instance of
> sql server installation in one box.
>