migrating domain and sql domain user logins

Hello!
Today, I've successfully migrated a domain controler named DC2 to the new
domain. I've also changed its computer name, after joining him into the
new domain. And later i've promoted this server back to DC.
Now here is my Q: This server is also running SQL 2000 and OLAP services.
The migration of the server was success, I've rebuild the master tables
(on default and second instance) fine with exactly
defined stored procedures. But a lot of applications were using domain
logons to connect to SQL. For examle: on one of the instances there were
users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
Now the problem is that domain name has changed but domain user info
stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
domain, so they already exist in the new domain.
To make thing short:
How to tell SQL server to change the
OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
Please help!!!!
You want to start with this:
http://support.microsoft.com/kb/246133/
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.18.50.16.974701@.email.si...
> Hello!
> Today, I've successfully migrated a domain controler named DC2 to the new
> domain. I've also changed its computer name, after joining him into the
> new domain. And later i've promoted this server back to DC.
> Now here is my Q: This server is also running SQL 2000 and OLAP services.
> The migration of the server was success, I've rebuild the master tables
> (on default and second instance) fine with exactly
> defined stored procedures. But a lot of applications were using domain
> logons to connect to SQL. For examle: on one of the instances there were
> users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
> Now the problem is that domain name has changed but domain user info
> stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
> to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
> domain, so they already exist in the new domain.
> --
> To make thing short:
> How to tell SQL server to change the
> OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
> Please help!!!!
>
|||Hi
Check out the links on http://support.microsoft.com/kb/246133/
John
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.18.50.16.974701@.email.si...
> Hello!
> Today, I've successfully migrated a domain controler named DC2 to the new
> domain. I've also changed its computer name, after joining him into the
> new domain. And later i've promoted this server back to DC.
> Now here is my Q: This server is also running SQL 2000 and OLAP services.
> The migration of the server was success, I've rebuild the master tables
> (on default and second instance) fine with exactly
> defined stored procedures. But a lot of applications were using domain
> logons to connect to SQL. For examle: on one of the instances there were
> users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
> Now the problem is that domain name has changed but domain user info
> stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
> to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
> domain, so they already exist in the new domain.
> --
> To make thing short:
> How to tell SQL server to change the
> OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
> Please help!!!!
>
|||On Sat, 16 Apr 2005 12:23:47 -0700, oj wrote:

> You want to start with this:
> http://support.microsoft.com/kb/246133/
I wrote the whole thing a bit confusing, so here is the article that
describes my dilema:
http://support.microsoft.com/kb/240872/
I'm reading this article and I'm wondering... Do i really need to go thrue
this procedure, or is it enough just to delete old sql domain user
login and than recreate it, for example:
I'll delete OLD_DOMAIN_NAME\user1 (in SQL logins)
and than i will create a new user:
NEW_DOMAIN_NAME\user1.
Is this ok, or will I be experiences some problems when trying to connect
(because of SID's etc..)?
This is a production server, so I really need to get clear with his facts
here.
Thank you!
|||Yes, follow the instruction in this kb. sp_sidmap should help resolve your
issue.
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.20.21.39.620670@.email.si...
> On Sat, 16 Apr 2005 12:23:47 -0700, oj wrote:
>
> I wrote the whole thing a bit confusing, so here is the article that
> describes my dilema:
> http://support.microsoft.com/kb/240872/
> I'm reading this article and I'm wondering... Do i really need to go thrue
> this procedure, or is it enough just to delete old sql domain user
> login and than recreate it, for example:
> I'll delete OLD_DOMAIN_NAME\user1 (in SQL logins)
> and than i will create a new user:
> NEW_DOMAIN_NAME\user1.
> Is this ok, or will I be experiences some problems when trying to connect
> (because of SID's etc..)?
> This is a production server, so I really need to get clear with his facts
> here.
> Thank you!
|||On Sat, 16 Apr 2005 13:25:01 -0700, oj wrote:

> Yes, follow the instruction in this kb. sp_sidmap should help resolve your
> issue.
Ok, so I've study the material, I understand everything except this:
1.) "Log on to the server that is running SQL Server as a system
administrator, and then run the Sp_sidmap.sql file in the user database."
So, where exactly is the user database? I really don't know what's meant
by that.
2.) I need to execute this script and the other things on the second
instance too, right?
Thank you.
|||The script can be download from:
http://download.microsoft.com/downlo...us/mapsids.exe
The user database is your database (i.e. not master, msdb, tempdb, model).
Yes, you will have to do it for each (unfortunately).
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.20.45.00.969560@.email.si...
> On Sat, 16 Apr 2005 13:25:01 -0700, oj wrote:
>
> Ok, so I've study the material, I understand everything except this:
> 1.) "Log on to the server that is running SQL Server as a system
> administrator, and then run the Sp_sidmap.sql file in the user database."
> So, where exactly is the user database? I really don't know what's meant
> by that.
> 2.) I need to execute this script and the other things on the second
> instance too, right?
> Thank you.

migrating domain and sql domain user logins

Hello!
Today, I've successfully migrated a domain controler named DC2 to the new
domain. I've also changed its computer name, after joining him into the
new domain. And later i've promoted this server back to DC.
Now here is my Q: This server is also running SQL 2000 and OLAP services.
The migration of the server was success, I've rebuild the master tables
(on default and second instance) fine with exactly
defined stored procedures. But a lot of applications were using domain
logons to connect to SQL. For examle: on one of the instances there were
users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
Now the problem is that domain name has changed but domain user info
stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
domain, so they already exist in the new domain.
--
To make thing short:
How to tell SQL server to change the
OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
Please help!!!!You want to start with this:
http://support.microsoft.com/kb/246133/
--
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.18.50.16.974701@.email.si...
> Hello!
> Today, I've successfully migrated a domain controler named DC2 to the new
> domain. I've also changed its computer name, after joining him into the
> new domain. And later i've promoted this server back to DC.
> Now here is my Q: This server is also running SQL 2000 and OLAP services.
> The migration of the server was success, I've rebuild the master tables
> (on default and second instance) fine with exactly
> defined stored procedures. But a lot of applications were using domain
> logons to connect to SQL. For examle: on one of the instances there were
> users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
> Now the problem is that domain name has changed but domain user info
> stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
> to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
> domain, so they already exist in the new domain.
> --
> To make thing short:
> How to tell SQL server to change the
> OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
> Please help!!!!
>|||Hi
Check out the links on http://support.microsoft.com/kb/246133/
John
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.18.50.16.974701@.email.si...
> Hello!
> Today, I've successfully migrated a domain controler named DC2 to the new
> domain. I've also changed its computer name, after joining him into the
> new domain. And later i've promoted this server back to DC.
> Now here is my Q: This server is also running SQL 2000 and OLAP services.
> The migration of the server was success, I've rebuild the master tables
> (on default and second instance) fine with exactly
> defined stored procedures. But a lot of applications were using domain
> logons to connect to SQL. For examle: on one of the instances there were
> users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
> Now the problem is that domain name has changed but domain user info
> stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
> to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
> domain, so they already exist in the new domain.
> --
> To make thing short:
> How to tell SQL server to change the
> OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
> Please help!!!!
>|||On Sat, 16 Apr 2005 12:23:47 -0700, oj wrote:
> You want to start with this:
> http://support.microsoft.com/kb/246133/
I wrote the whole thing a bit confusing, so here is the article that
describes my dilema:
http://support.microsoft.com/kb/240872/
I'm reading this article and I'm wondering... Do i really need to go thrue
this procedure, or is it enough just to delete old sql domain user
login and than recreate it, for example:
I'll delete OLD_DOMAIN_NAME\user1 (in SQL logins)
and than i will create a new user:
NEW_DOMAIN_NAME\user1.
Is this ok, or will I be experiences some problems when trying to connect
(because of SID's etc..)?
This is a production server, so I really need to get clear with his facts
here.
Thank you!|||Yes, follow the instruction in this kb. sp_sidmap should help resolve your
issue.
--
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.20.21.39.620670@.email.si...
> On Sat, 16 Apr 2005 12:23:47 -0700, oj wrote:
>> You want to start with this:
>> http://support.microsoft.com/kb/246133/
> I wrote the whole thing a bit confusing, so here is the article that
> describes my dilema:
> http://support.microsoft.com/kb/240872/
> I'm reading this article and I'm wondering... Do i really need to go thrue
> this procedure, or is it enough just to delete old sql domain user
> login and than recreate it, for example:
> I'll delete OLD_DOMAIN_NAME\user1 (in SQL logins)
> and than i will create a new user:
> NEW_DOMAIN_NAME\user1.
> Is this ok, or will I be experiences some problems when trying to connect
> (because of SID's etc..)?
> This is a production server, so I really need to get clear with his facts
> here.
> Thank you!|||On Sat, 16 Apr 2005 13:25:01 -0700, oj wrote:
> Yes, follow the instruction in this kb. sp_sidmap should help resolve your
> issue.
Ok, so I've study the material, I understand everything except this:
1.) "Log on to the server that is running SQL Server as a system
administrator, and then run the Sp_sidmap.sql file in the user database."
So, where exactly is the user database? I really don't know what's meant
by that.
2.) I need to execute this script and the other things on the second
instance too, right?
Thank you.|||The script can be download from:
http://download.microsoft.com/download/sqlsvr2000/utility/5.0/win98me/en-us/mapsids.exe
The user database is your database (i.e. not master, msdb, tempdb, model).
Yes, you will have to do it for each (unfortunately).
--
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.20.45.00.969560@.email.si...
> On Sat, 16 Apr 2005 13:25:01 -0700, oj wrote:
>> Yes, follow the instruction in this kb. sp_sidmap should help resolve
>> your
>> issue.
> Ok, so I've study the material, I understand everything except this:
> 1.) "Log on to the server that is running SQL Server as a system
> administrator, and then run the Sp_sidmap.sql file in the user database."
> So, where exactly is the user database? I really don't know what's meant
> by that.
> 2.) I need to execute this script and the other things on the second
> instance too, right?
> Thank you.sql

migrating domain and sql domain user logins

Hello!
Today, I've successfully migrated a domain controler named DC2 to the new
domain. I've also changed its computer name, after joining him into the
new domain. And later i've promoted this server back to DC.
Now here is my Q: This server is also running SQL 2000 and OLAP services.
The migration of the server was success, I've rebuild the master tables
(on default and second instance) fine with exactly
defined stored procedures. But a lot of applications were using domain
logons to connect to SQL. For examle: on one of the instances there were
users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
Now the problem is that domain name has changed but domain user info
stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
domain, so they already exist in the new domain.
To make thing short:
How to tell SQL server to change the
OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
Please help!!!!You want to start with this:
http://support.microsoft.com/kb/246133/
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.18.50.16.974701@.email.si...
> Hello!
> Today, I've successfully migrated a domain controler named DC2 to the new
> domain. I've also changed its computer name, after joining him into the
> new domain. And later i've promoted this server back to DC.
> Now here is my Q: This server is also running SQL 2000 and OLAP services.
> The migration of the server was success, I've rebuild the master tables
> (on default and second instance) fine with exactly
> defined stored procedures. But a lot of applications were using domain
> logons to connect to SQL. For examle: on one of the instances there were
> users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
> Now the problem is that domain name has changed but domain user info
> stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
> to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
> domain, so they already exist in the new domain.
> --
> To make thing short:
> How to tell SQL server to change the
> OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
> Please help!!!!
>|||Hi
Check out the links on http://support.microsoft.com/kb/246133/
John
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.18.50.16.974701@.email.si...
> Hello!
> Today, I've successfully migrated a domain controler named DC2 to the new
> domain. I've also changed its computer name, after joining him into the
> new domain. And later i've promoted this server back to DC.
> Now here is my Q: This server is also running SQL 2000 and OLAP services.
> The migration of the server was success, I've rebuild the master tables
> (on default and second instance) fine with exactly
> defined stored procedures. But a lot of applications were using domain
> logons to connect to SQL. For examle: on one of the instances there were
> users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
> Now the problem is that domain name has changed but domain user info
> stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
> to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
> domain, so they already exist in the new domain.
> --
> To make thing short:
> How to tell SQL server to change the
> OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
> Please help!!!!
>|||On Sat, 16 Apr 2005 12:23:47 -0700, oj wrote:

> You want to start with this:
> http://support.microsoft.com/kb/246133/
I wrote the whole thing a bit confusing, so here is the article that
describes my dilema:
http://support.microsoft.com/kb/240872/
I'm reading this article and I'm wondering... Do i really need to go thrue
this procedure, or is it enough just to delete old sql domain user
login and than recreate it, for example:
I'll delete OLD_DOMAIN_NAME\user1 (in SQL logins)
and than i will create a new user:
NEW_DOMAIN_NAME\user1.
Is this ok, or will I be experiences some problems when trying to connect
(because of SID's etc..)?
This is a production server, so I really need to get clear with his facts
here.
Thank you!|||Yes, follow the instruction in this kb. sp_sidmap should help resolve your
issue.
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.20.21.39.620670@.email.si...
> On Sat, 16 Apr 2005 12:23:47 -0700, oj wrote:
>
> I wrote the whole thing a bit confusing, so here is the article that
> describes my dilema:
> http://support.microsoft.com/kb/240872/
> I'm reading this article and I'm wondering... Do i really need to go thrue
> this procedure, or is it enough just to delete old sql domain user
> login and than recreate it, for example:
> I'll delete OLD_DOMAIN_NAME\user1 (in SQL logins)
> and than i will create a new user:
> NEW_DOMAIN_NAME\user1.
> Is this ok, or will I be experiences some problems when trying to connect
> (because of SID's etc..)?
> This is a production server, so I really need to get clear with his facts
> here.
> Thank you!|||On Sat, 16 Apr 2005 13:25:01 -0700, oj wrote:

> Yes, follow the instruction in this kb. sp_sidmap should help resolve your
> issue.
Ok, so I've study the material, I understand everything except this:
1.) "Log on to the server that is running SQL Server as a system
administrator, and then run the Sp_sidmap.sql file in the user database."
So, where exactly is the user database? I really don't know what's meant
by that.
2.) I need to execute this script and the other things on the second
instance too, right?
Thank you.|||The script can be download from:
http://download.microsoft.com/downl...id
s.exe
The user database is your database (i.e. not master, msdb, tempdb, model).
Yes, you will have to do it for each (unfortunately).
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.20.45.00.969560@.email.si...
> On Sat, 16 Apr 2005 13:25:01 -0700, oj wrote:
>
> Ok, so I've study the material, I understand everything except this:
> 1.) "Log on to the server that is running SQL Server as a system
> administrator, and then run the Sp_sidmap.sql file in the user database."
> So, where exactly is the user database? I really don't know what's meant
> by that.
> 2.) I need to execute this script and the other things on the second
> instance too, right?
> Thank you.

migrating 7.0 to 2000

i have computer with windows 2000 an sql 7.0 (computerA)
goal is windows 2003 with sql 2005

I see my choices as is:

A) upgrade win2k to 2k3 then upgrade sql7 on w2k3 to sql2k5 on win2k3.
(i see many potential problems with that)

B) have computerB with clean install of win2k3 and install sql2k5 on it.
if this is the case, what is the best / easiest way to get the database from 7 to 2k5? Database copy wizard? dts? attaching the db?

Anything else I should lookout for ?

thnx,
vextThere might be better answers, but I'd set up the new server with the software that you intend to run on it (Windows 2003, SQL 2005). I'd backup the existing database, and restore that backup onto the new server.

-PatP|||what is the actual difference between using the Database copy wizard and Restoring a backup? and is the datafile still the same structure in 2005? will the restore upgrade if not?|||Theoretically, there shouldn't be a difference between Restoring a Backup and Copying a Database. That leads to all kinds of amusing observations, but I'll behave myself (at least for now). The primary difference is that restoring a backup is logically much more "solid" in that there are far fewer ways for it to go wrong...

The Copy Database Wizard is free to make many assumptions, many of which have a significant impact on performance and operational simplicity. These assumptions should not affect the copy of the quality, but I'm often unpleasantly surprised by them.

Restoring a backup is much less problematic for me. While some things (features, objects, etc) might change due to the difference in software releases (SQL 7 to SQL 2005 is a big jump), at least in my experience there will be far fewer surprises than you'd get via the Copy Database Wizard.

-PatP|||understood.

thnx for the input. I will do a restore when the time comes. thnxsql

Microsoft user group

Sorry for this post but can anyone direct me to Windows XP
Home edition user group ? I Think I locked myself out of
my computer unless Installing SP2 messed me up which is
not installed at all......
Thanks.....
Users group or newsgroup?
For newsgroups, try:
microsoft.public.windowsxp.help_and_support
-Sue
On Mon, 15 Nov 2004 11:20:44 -0800, "Dan"
<anonymous@.discussions.microsoft.com> wrote:

>Sorry for this post but can anyone direct me to Windows XP
>Home edition user group ? I Think I locked myself out of
>my computer unless Installing SP2 messed me up which is
>not installed at all......
>Thanks.....

Microsoft user group

Sorry for this post but can anyone direct me to Windows XP
Home edition user group ? I Think I locked myself out of
my computer unless Installing SP2 messed me up which is
not installed at all......
Thanks.....
"Dan" <anonymous@.discussions.microsoft.com> wrote in news:5be201c4cb48
$325c2540$a401280a@.phx.gbl:

> Sorry for this post but can anyone direct me to Windows XP
> Home edition user group ? I Think I locked myself out of
> my computer unless Installing SP2 messed me up which is
> not installed at all......
> Thanks.....
>
alt.os.windows-xp

Microsoft user group

Sorry for this post but can anyone direct me to Windows XP
Home edition user group ' I Think I locked myself out of
my computer unless Installing SP2 messed me up which is
not installed at all......
Thanks....."Dan" <anonymous@.discussions.microsoft.com> wrote in news:5be201c4cb48
$325c2540$a401280a@.phx.gbl:

> Sorry for this post but can anyone direct me to Windows XP
> Home edition user group ' I Think I locked myself out of
> my computer unless Installing SP2 messed me up which is
> not installed at all......
> Thanks.....
>
alt.os.windows-xp

Microsoft user group

Sorry for this post but can anyone direct me to Windows XP
Home edition user group ' I Think I locked myself out of
my computer unless Installing SP2 messed me up which is
not installed at all......
Thanks.....Sorry for the double post......
>--Original Message--
>Sorry for this post but can anyone direct me to Windows
XP
>Home edition user group ' I Think I locked myself out of
>my computer unless Installing SP2 messed me up which is
>not installed at all......
>Thanks.....
>.
>|||Users group or newsgroup?
For newsgroups, try:
microsoft.public.windowsxp.help_and_support
-Sue
On Mon, 15 Nov 2004 11:20:44 -0800, "Dan"
<anonymous@.discussions.microsoft.com> wrote:
>Sorry for this post but can anyone direct me to Windows XP
>Home edition user group ' I Think I locked myself out of
>my computer unless Installing SP2 messed me up which is
>not installed at all......
>Thanks.....

Microsoft user group

Sorry for this post but can anyone direct me to Windows XP
Home edition user group ' I Think I locked myself out of
my computer unless Installing SP2 messed me up which is
not installed at all......
Thanks....."Dan" <anonymous@.discussions.microsoft.com> wrote in news:5be201c4cb48
$325c2540$a401280a@.phx.gbl:
> Sorry for this post but can anyone direct me to Windows XP
> Home edition user group ' I Think I locked myself out of
> my computer unless Installing SP2 messed me up which is
> not installed at all......
> Thanks.....
>
alt.os.windows-xp

Microsoft SQL Server, Error: 87 17march

Source computer: SQL server 2005 SP1
Remote computer : SQLEXPRESS
When I try to register/connect with remote server (named instance) using sql
server management studio I am getting following error:
TITLE: New Server Registration
--
Testing the registered server failed. Verify the server name, login
credentials, and database, and then click Test again.
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: SQL Network Interfaces, error: 25 - Connection string is not
valid) (Microsoft SQL Server, Error: 87)
Thanks
Ontario, canadaSource computer: SQL server 2005 SP1 (Microsoft windows nt 5.1)
Remote computer : Microsoft SQL server express edition (Microsoft windows
nt 5.1)
-
ontario, canada
"db" wrote:
> Source computer: SQL server 2005 SP1
> Remote computer : SQLEXPRESS
>
> When I try to register/connect with remote server (named instance) using sql
> server management studio I am getting following error:
> TITLE: New Server Registration
> --
> Testing the registered server failed. Verify the server name, login
> credentials, and database, and then click Test again.
> --
> ADDITIONAL INFORMATION:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: SQL Network Interfaces, error: 25 - Connection string is not
> valid) (Microsoft SQL Server, Error: 87)
>
> Thanks
> Ontario, canada

Microsoft SQL Server, Error: 87 17march

Source computer: SQL server 2005 SP1
Remote computer : SQLEXPRESS
When I try to register/connect with remote server (named instance) using sql
server management studio I am getting following error:
TITLE: New Server Registration
Testing the registered server failed. Verify the server name, login
credentials, and database, and then click Test again.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: SQL Network Interfaces, error: 25 - Connection string is not
valid) (Microsoft SQL Server, Error: 87)
Thanks
Ontario, canada
Source computer: SQL server 2005 SP1 (Microsoft windows nt 5.1)
Remote computer : Microsoft SQL server express edition (Microsoft windows
nt 5.1)
-
ontario, canada
"db" wrote:

> Source computer: SQL server 2005 SP1
> Remote computer : SQLEXPRESS
>
> When I try to register/connect with remote server (named instance) using sql
> server management studio I am getting following error:
> TITLE: New Server Registration
> --
> Testing the registered server failed. Verify the server name, login
> credentials, and database, and then click Test again.
> --
> ADDITIONAL INFORMATION:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: SQL Network Interfaces, error: 25 - Connection string is not
> valid) (Microsoft SQL Server, Error: 87)
>
> Thanks
> Ontario, canada

Microsoft sql server smo

Im trying to use

Microsoft.SqlServer.Management.Smo

to load a dropdown of available sql server databases.

On my computer it works fine but when i try and run the application on my virtual it throws and unhandled exception that it couldn't load SMO assembly. I know this is because 2005 isn't installed on my virtual but i want to be able to catch this error and just ignore it and load a blank dropdown. I tried putting try catch blocks around the load but it still errors. I then tried instead of importing it i tried to reference smo by using the whole name inside of my try catch block.

Does anyone know how to catch this error

Try' Create a new connection to the selected server nameDim srvConnAs New Microsoft.SqlServer.Management.Common.ServerConnection(txtServerName.Text)Dim srvSqlAs Microsoft.SqlServer.Management.Smo.Server' Log in using SQL authentication instead of Windows authentication srvConn.LoginSecure =False' Give the login username srvConn.Login = txtUserID.Text' Give the login password srvConn.Password = txtPassword.Text' Create a new SQL Server object using the connection we created srvSql =New Microsoft.SqlServer.Management.Smo.Server(srvConn)' Loop through the databases listFor Each dbServerAs Microsoft.SqlServer.Management.Smo.DatabaseIn srvSql.Databases' Add database to combobox txtDatabase.Items.Add(dbServer.Name)Next Catch exAs Exception MsgBox(ex.Message)End Try

I know this is because 2005 isn't installed on my virtual but i want to be able to catch this error and just ignore it and load a blank dropdown

smo object should work on a sql 2000 server, I have done it before. What is th exact error message your getting?

|||

What i have read tells me that smo is new in 2005 and does not work in 2000. But any case i want to ignore this error and just populate the dropdowns as blank if no sql server is installed at all.

The exact error message is:

Could not load file or assembly Microsoft.SqlServer.SMO
Version 9.0.242.0, Culture=neutral
PublicKey Token=89845dcd8080cc91 or one of its dependencies. The system cannot find the file specified