Hi All
I am trying to test db mirroring. I went exactly as book says: started 2 sql
servers with the same domain accounts, created endpoints. Checked if
endpoints exist and listen - they do.
Than I try to alter test db:
ALTER DATABASE test
SET PARTNER =
'TCP://pc500:5000'
and get:
Msg 1418, Level 16, State 1, Line 2
The server network address "TCP://pc500:5000" can not be reached or does not
exist. Check the network address name and that the ports for the local and
remote endpoints are operational.
pc500 is a partner pc.
I also tried to use full domain name and ip addres. Each time I removed
endpoints and checked from os prompt if anything listens on the port - no.
But no matter what I do, I get this error. I also checked with my sysadmin
if there is any kind of filtering or firewalls - no.
As a matter of fact, pc500 is virtual pc which resides on my pc.
It does not work. I tried replication from 2005 to 2005 - the same problem.
But replication from 2k to 2005 - works painlessly.
Does anybody have clue what's the problem here?
Hello,
I supposed you can ping that server, right? :-)
Is the endpoint started? When it is created the default is stopped. Check
state_desc on
select * from sys.database_mirroring_endpoints
Always use full domain name.
Check port is correct on sys.tcp_endpoints.
Hope this helps,
Ben Nevarez
"Gene." wrote:
> Hi All
> I am trying to test db mirroring. I went exactly as book says: started 2 sql
> servers with the same domain accounts, created endpoints. Checked if
> endpoints exist and listen - they do.
> Than I try to alter test db:
> ALTER DATABASE test
> SET PARTNER =
> 'TCP://pc500:5000'
> and get:
> Msg 1418, Level 16, State 1, Line 2
> The server network address "TCP://pc500:5000" can not be reached or does not
> exist. Check the network address name and that the ports for the local and
> remote endpoints are operational.
> pc500 is a partner pc.
> I also tried to use full domain name and ip addres. Each time I removed
> endpoints and checked from os prompt if anything listens on the port - no.
> But no matter what I do, I get this error. I also checked with my sysadmin
> if there is any kind of filtering or firewalls - no.
> As a matter of fact, pc500 is virtual pc which resides on my pc.
> It does not work. I tried replication from 2005 to 2005 - the same problem.
> But replication from 2k to 2005 - works painlessly.
> Does anybody have clue what's the problem here?
>
|||Hi Ben
Here is an output from:
select name, type_desc, port, ip_address from sys.tcp_endpoints
select name, role_desc, state_desc from sys.database_mirroring_endpoints
name
type_desc
port ip_address
------
---- --
Dedicated Admin Connection
TSQL
0 NULL
TSQL Default TCP
TSQL
0 NULL
Endpoint_Mirroring
DATABASE_MIRRORING
5001 NULL
(3 row(s) affected)
name
role_desc
state_desc
------
----
Endpoint_Mirroring
ALL
STARTED
Yes, it's started.
In addition to it I found message which looks so innocent:
Login failed for user 'group\user'. [CLIENT: <local machine>]
I logged in with that user hundreds times for sure.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hello,
> I supposed you can ping that server, right? :-)
> Is the endpoint started? When it is created the default is stopped. Check
> state_desc on
> select * from sys.database_mirroring_endpoints
> Always use full domain name.
> Check port is correct on sys.tcp_endpoints.
> Hope this helps,
> Ben Nevarez
>
>
> "Gene." wrote:
|||Gene,
According to that output the port number is 5001 not 5000. So you should use
ALTER DATABASE test
SET PARTNER =
'TCP://pc500:5001'
Please add the full domain name too.
Please test this and see if it works.
Hope this helps,
Ben Nevarez
"Gene." wrote:
[vbcol=seagreen]
> Hi Ben
> Here is an output from:
> select name, type_desc, port, ip_address from sys.tcp_endpoints
> select name, role_desc, state_desc from sys.database_mirroring_endpoints
>
> name
> type_desc
> port ip_address
> ------
> ---- --
> Dedicated Admin Connection
> TSQL
> 0 NULL
> TSQL Default TCP
> TSQL
> 0 NULL
> Endpoint_Mirroring
> DATABASE_MIRRORING
> 5001 NULL
> (3 row(s) affected)
> name
> role_desc
> state_desc
> ------
> ----
> ----
> Endpoint_Mirroring
> ALL
> STARTED
>
> Yes, it's started.
> In addition to it I found message which looks so innocent:
> Login failed for user 'group\user'. [CLIENT: <local machine>]
> I logged in with that user hundreds times for sure.
>
> "Ben Nevarez" wrote:
|||Ben
That's correct. Principal uses 5000 port for it's own end point, but refers
to port 5001 of the partner. And vice verse.
I am using full domain names but for this post I used short ones. As I said
before, full domain names were tested with ping from both hosts. I also used
ip's in their place.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Gene,
> According to that output the port number is 5001 not 5000. So you should use
> ALTER DATABASE test
> SET PARTNER =
> 'TCP://pc500:5001'
> Please add the full domain name too.
> Please test this and see if it works.
> Hope this helps,
> Ben Nevarez
>
>
> "Gene." wrote:
|||Have you applied SP1, or better, SP2?
Is the login failed message from the user who is supposed to connect to the
endpoint? if so, assign connect permissions to the required logins like in
grant connect on endpoint::endpoint_mirroring to [user]
Hope this helps,
Ben Nevarez
"Gene." wrote:
[vbcol=seagreen]
> Ben
> That's correct. Principal uses 5000 port for it's own end point, but refers
> to port 5001 of the partner. And vice verse.
> I am using full domain names but for this post I used short ones. As I said
> before, full domain names were tested with ping from both hosts. I also used
> ip's in their place.
> "Ben Nevarez" wrote:
|||Hi Ben
It finaly started working.
The problem was quite simple.
I created end points and tried to alter db to communicate with partner.
Instead of it I had to dump and load partner with db and tran and only than
to finalize it's communication by altering db.
Thank you for your help anyway.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Have you applied SP1, or better, SP2?
> Is the login failed message from the user who is supposed to connect to the
> endpoint? if so, assign connect permissions to the required logins like in
> grant connect on endpoint::endpoint_mirroring to [user]
> Hope this helps,
> Ben Nevarez
>
>
> "Gene." wrote:
Showing posts with label created. Show all posts
Showing posts with label created. Show all posts
Friday, March 30, 2012
mirroring db: communication problem
Hi All
I am trying to test db mirroring. I went exactly as book says: started 2 sql
servers with the same domain accounts, created endpoints. Checked if
endpoints exist and listen - they do.
Than I try to alter test db:
ALTER DATABASE test
SET PARTNER = 'TCP://pc500:5000'
and get:
Msg 1418, Level 16, State 1, Line 2
The server network address "TCP://pc500:5000" can not be reached or does not
exist. Check the network address name and that the ports for the local and
remote endpoints are operational.
pc500 is a partner pc.
I also tried to use full domain name and ip addres. Each time I removed
endpoints and checked from os prompt if anything listens on the port - no.
But no matter what I do, I get this error. I also checked with my sysadmin
if there is any kind of filtering or firewalls - no.
As a matter of fact, pc500 is virtual pc which resides on my pc.
It does not work. I tried replication from 2005 to 2005 - the same problem.
But replication from 2k to 2005 - works painlessly.
Does anybody have clue what's the problem here?Hello,
I supposed you can ping that server, right? :-)
Is the endpoint started? When it is created the default is stopped. Check
state_desc on
select * from sys.database_mirroring_endpoints
Always use full domain name.
Check port is correct on sys.tcp_endpoints.
Hope this helps,
Ben Nevarez
"Gene." wrote:
> Hi All
> I am trying to test db mirroring. I went exactly as book says: started 2 sql
> servers with the same domain accounts, created endpoints. Checked if
> endpoints exist and listen - they do.
> Than I try to alter test db:
> ALTER DATABASE test
> SET PARTNER => 'TCP://pc500:5000'
> and get:
> Msg 1418, Level 16, State 1, Line 2
> The server network address "TCP://pc500:5000" can not be reached or does not
> exist. Check the network address name and that the ports for the local and
> remote endpoints are operational.
> pc500 is a partner pc.
> I also tried to use full domain name and ip addres. Each time I removed
> endpoints and checked from os prompt if anything listens on the port - no.
> But no matter what I do, I get this error. I also checked with my sysadmin
> if there is any kind of filtering or firewalls - no.
> As a matter of fact, pc500 is virtual pc which resides on my pc.
> It does not work. I tried replication from 2005 to 2005 - the same problem.
> But replication from 2k to 2005 - works painlessly.
> Does anybody have clue what's the problem here?
>|||Hi Ben
Here is an output from:
select name, type_desc, port, ip_address from sys.tcp_endpoints
select name, role_desc, state_desc from sys.database_mirroring_endpoints
name
type_desc
port ip_address
------
---- --
---
Dedicated Admin Connection
TSQL
0 NULL
TSQL Default TCP
TSQL
0 NULL
Endpoint_Mirroring
DATABASE_MIRRORING
5001 NULL
(3 row(s) affected)
name
role_desc
state_desc
------
----
----
Endpoint_Mirroring
ALL
STARTED
Yes, it's started.
In addition to it I found message which looks so innocent:
Login failed for user 'group\user'. [CLIENT: <local machine>]
I logged in with that user hundreds times for sure.
"Ben Nevarez" wrote:
> Hello,
> I supposed you can ping that server, right? :-)
> Is the endpoint started? When it is created the default is stopped. Check
> state_desc on
> select * from sys.database_mirroring_endpoints
> Always use full domain name.
> Check port is correct on sys.tcp_endpoints.
> Hope this helps,
> Ben Nevarez
>
>
> "Gene." wrote:
> > Hi All
> > I am trying to test db mirroring. I went exactly as book says: started 2 sql
> > servers with the same domain accounts, created endpoints. Checked if
> > endpoints exist and listen - they do.
> > Than I try to alter test db:
> >
> > ALTER DATABASE test
> > SET PARTNER => > 'TCP://pc500:5000'
> > and get:
> >
> > Msg 1418, Level 16, State 1, Line 2
> > The server network address "TCP://pc500:5000" can not be reached or does not
> > exist. Check the network address name and that the ports for the local and
> > remote endpoints are operational.
> >
> > pc500 is a partner pc.
> >
> > I also tried to use full domain name and ip addres. Each time I removed
> > endpoints and checked from os prompt if anything listens on the port - no.
> > But no matter what I do, I get this error. I also checked with my sysadmin
> > if there is any kind of filtering or firewalls - no.
> > As a matter of fact, pc500 is virtual pc which resides on my pc.
> >
> > It does not work. I tried replication from 2005 to 2005 - the same problem.
> > But replication from 2k to 2005 - works painlessly.
> >
> > Does anybody have clue what's the problem here?
> >|||Gene,
According to that output the port number is 5001 not 5000. So you should use
ALTER DATABASE test
SET PARTNER = 'TCP://pc500:5001'
Please add the full domain name too.
Please test this and see if it works.
Hope this helps,
Ben Nevarez
"Gene." wrote:
> Hi Ben
> Here is an output from:
> select name, type_desc, port, ip_address from sys.tcp_endpoints
> select name, role_desc, state_desc from sys.database_mirroring_endpoints
>
> name
> type_desc
> port ip_address
> ------
> ---- --
> ---
> Dedicated Admin Connection
> TSQL
> 0 NULL
> TSQL Default TCP
> TSQL
> 0 NULL
> Endpoint_Mirroring
> DATABASE_MIRRORING
> 5001 NULL
> (3 row(s) affected)
> name
> role_desc
> state_desc
> ------
> ----
> ----
> Endpoint_Mirroring
> ALL
> STARTED
>
> Yes, it's started.
> In addition to it I found message which looks so innocent:
> Login failed for user 'group\user'. [CLIENT: <local machine>]
> I logged in with that user hundreds times for sure.
>
> "Ben Nevarez" wrote:
> >
> > Hello,
> >
> > I supposed you can ping that server, right? :-)
> >
> > Is the endpoint started? When it is created the default is stopped. Check
> > state_desc on
> >
> > select * from sys.database_mirroring_endpoints
> >
> > Always use full domain name.
> >
> > Check port is correct on sys.tcp_endpoints.
> >
> > Hope this helps,
> >
> > Ben Nevarez
> >
> >
> >
> >
> > "Gene." wrote:
> >
> > > Hi All
> > > I am trying to test db mirroring. I went exactly as book says: started 2 sql
> > > servers with the same domain accounts, created endpoints. Checked if
> > > endpoints exist and listen - they do.
> > > Than I try to alter test db:
> > >
> > > ALTER DATABASE test
> > > SET PARTNER => > > 'TCP://pc500:5000'
> > > and get:
> > >
> > > Msg 1418, Level 16, State 1, Line 2
> > > The server network address "TCP://pc500:5000" can not be reached or does not
> > > exist. Check the network address name and that the ports for the local and
> > > remote endpoints are operational.
> > >
> > > pc500 is a partner pc.
> > >
> > > I also tried to use full domain name and ip addres. Each time I removed
> > > endpoints and checked from os prompt if anything listens on the port - no.
> > > But no matter what I do, I get this error. I also checked with my sysadmin
> > > if there is any kind of filtering or firewalls - no.
> > > As a matter of fact, pc500 is virtual pc which resides on my pc.
> > >
> > > It does not work. I tried replication from 2005 to 2005 - the same problem.
> > > But replication from 2k to 2005 - works painlessly.
> > >
> > > Does anybody have clue what's the problem here?
> > >|||Ben
That's correct. Principal uses 5000 port for it's own end point, but refers
to port 5001 of the partner. And vice verse.
I am using full domain names but for this post I used short ones. As I said
before, full domain names were tested with ping from both hosts. I also used
ip's in their place.
"Ben Nevarez" wrote:
> Gene,
> According to that output the port number is 5001 not 5000. So you should use
> ALTER DATABASE test
> SET PARTNER => 'TCP://pc500:5001'
> Please add the full domain name too.
> Please test this and see if it works.
> Hope this helps,
> Ben Nevarez
>
>
> "Gene." wrote:
> > Hi Ben
> >
> > Here is an output from:
> >
> > select name, type_desc, port, ip_address from sys.tcp_endpoints
> > select name, role_desc, state_desc from sys.database_mirroring_endpoints
> >
> >
> >
> > name
> > type_desc
> > port ip_address
> > ------
> > ---- --
> > ---
> > Dedicated Admin Connection
> > TSQL
> > 0 NULL
> > TSQL Default TCP
> > TSQL
> > 0 NULL
> > Endpoint_Mirroring
> > DATABASE_MIRRORING
> > 5001 NULL
> >
> > (3 row(s) affected)
> >
> > name
> > role_desc
> > state_desc
> > ------
> > ----
> > ----
> > Endpoint_Mirroring
> > ALL
> > STARTED
> >
> >
> >
> > Yes, it's started.
> >
> > In addition to it I found message which looks so innocent:
> >
> > Login failed for user 'group\user'. [CLIENT: <local machine>]
> >
> > I logged in with that user hundreds times for sure.
> >
> >
> > "Ben Nevarez" wrote:
> >
> > >
> > > Hello,
> > >
> > > I supposed you can ping that server, right? :-)
> > >
> > > Is the endpoint started? When it is created the default is stopped. Check
> > > state_desc on
> > >
> > > select * from sys.database_mirroring_endpoints
> > >
> > > Always use full domain name.
> > >
> > > Check port is correct on sys.tcp_endpoints.
> > >
> > > Hope this helps,
> > >
> > > Ben Nevarez
> > >
> > >
> > >
> > >
> > > "Gene." wrote:
> > >
> > > > Hi All
> > > > I am trying to test db mirroring. I went exactly as book says: started 2 sql
> > > > servers with the same domain accounts, created endpoints. Checked if
> > > > endpoints exist and listen - they do.
> > > > Than I try to alter test db:
> > > >
> > > > ALTER DATABASE test
> > > > SET PARTNER => > > > 'TCP://pc500:5000'
> > > > and get:
> > > >
> > > > Msg 1418, Level 16, State 1, Line 2
> > > > The server network address "TCP://pc500:5000" can not be reached or does not
> > > > exist. Check the network address name and that the ports for the local and
> > > > remote endpoints are operational.
> > > >
> > > > pc500 is a partner pc.
> > > >
> > > > I also tried to use full domain name and ip addres. Each time I removed
> > > > endpoints and checked from os prompt if anything listens on the port - no.
> > > > But no matter what I do, I get this error. I also checked with my sysadmin
> > > > if there is any kind of filtering or firewalls - no.
> > > > As a matter of fact, pc500 is virtual pc which resides on my pc.
> > > >
> > > > It does not work. I tried replication from 2005 to 2005 - the same problem.
> > > > But replication from 2k to 2005 - works painlessly.
> > > >
> > > > Does anybody have clue what's the problem here?
> > > >|||Have you applied SP1, or better, SP2?
Is the login failed message from the user who is supposed to connect to the
endpoint? if so, assign connect permissions to the required logins like in
grant connect on endpoint::endpoint_mirroring to [user]
Hope this helps,
Ben Nevarez
"Gene." wrote:
> Ben
> That's correct. Principal uses 5000 port for it's own end point, but refers
> to port 5001 of the partner. And vice verse.
> I am using full domain names but for this post I used short ones. As I said
> before, full domain names were tested with ping from both hosts. I also used
> ip's in their place.
> "Ben Nevarez" wrote:
> >
> > Gene,
> >
> > According to that output the port number is 5001 not 5000. So you should use
> >
> > ALTER DATABASE test
> > SET PARTNER => > 'TCP://pc500:5001'
> >
> > Please add the full domain name too.
> >
> > Please test this and see if it works.
> >
> > Hope this helps,
> >
> > Ben Nevarez
> >
> >
> >
> >
> > "Gene." wrote:
> >
> > > Hi Ben
> > >
> > > Here is an output from:
> > >
> > > select name, type_desc, port, ip_address from sys.tcp_endpoints
> > > select name, role_desc, state_desc from sys.database_mirroring_endpoints
> > >
> > >
> > >
> > > name
> > > type_desc
> > > port ip_address
> > > ------
> > > ---- --
> > > ---
> > > Dedicated Admin Connection
> > > TSQL
> > > 0 NULL
> > > TSQL Default TCP
> > > TSQL
> > > 0 NULL
> > > Endpoint_Mirroring
> > > DATABASE_MIRRORING
> > > 5001 NULL
> > >
> > > (3 row(s) affected)
> > >
> > > name
> > > role_desc
> > > state_desc
> > > ------
> > > ----
> > > ----
> > > Endpoint_Mirroring
> > > ALL
> > > STARTED
> > >
> > >
> > >
> > > Yes, it's started.
> > >
> > > In addition to it I found message which looks so innocent:
> > >
> > > Login failed for user 'group\user'. [CLIENT: <local machine>]
> > >
> > > I logged in with that user hundreds times for sure.
> > >
> > >
> > > "Ben Nevarez" wrote:
> > >
> > > >
> > > > Hello,
> > > >
> > > > I supposed you can ping that server, right? :-)
> > > >
> > > > Is the endpoint started? When it is created the default is stopped. Check
> > > > state_desc on
> > > >
> > > > select * from sys.database_mirroring_endpoints
> > > >
> > > > Always use full domain name.
> > > >
> > > > Check port is correct on sys.tcp_endpoints.
> > > >
> > > > Hope this helps,
> > > >
> > > > Ben Nevarez
> > > >
> > > >
> > > >
> > > >
> > > > "Gene." wrote:
> > > >
> > > > > Hi All
> > > > > I am trying to test db mirroring. I went exactly as book says: started 2 sql
> > > > > servers with the same domain accounts, created endpoints. Checked if
> > > > > endpoints exist and listen - they do.
> > > > > Than I try to alter test db:
> > > > >
> > > > > ALTER DATABASE test
> > > > > SET PARTNER => > > > > 'TCP://pc500:5000'
> > > > > and get:
> > > > >
> > > > > Msg 1418, Level 16, State 1, Line 2
> > > > > The server network address "TCP://pc500:5000" can not be reached or does not
> > > > > exist. Check the network address name and that the ports for the local and
> > > > > remote endpoints are operational.
> > > > >
> > > > > pc500 is a partner pc.
> > > > >
> > > > > I also tried to use full domain name and ip addres. Each time I removed
> > > > > endpoints and checked from os prompt if anything listens on the port - no.
> > > > > But no matter what I do, I get this error. I also checked with my sysadmin
> > > > > if there is any kind of filtering or firewalls - no.
> > > > > As a matter of fact, pc500 is virtual pc which resides on my pc.
> > > > >
> > > > > It does not work. I tried replication from 2005 to 2005 - the same problem.
> > > > > But replication from 2k to 2005 - works painlessly.
> > > > >
> > > > > Does anybody have clue what's the problem here?
> > > > >|||Hi Ben
It finaly started working.
The problem was quite simple.
I created end points and tried to alter db to communicate with partner.
Instead of it I had to dump and load partner with db and tran and only than
to finalize it's communication by altering db.
Thank you for your help anyway.
"Ben Nevarez" wrote:
> Have you applied SP1, or better, SP2?
> Is the login failed message from the user who is supposed to connect to the
> endpoint? if so, assign connect permissions to the required logins like in
> grant connect on endpoint::endpoint_mirroring to [user]
> Hope this helps,
> Ben Nevarez
>
>
> "Gene." wrote:
> > Ben
> >
> > That's correct. Principal uses 5000 port for it's own end point, but refers
> > to port 5001 of the partner. And vice verse.
> > I am using full domain names but for this post I used short ones. As I said
> > before, full domain names were tested with ping from both hosts. I also used
> > ip's in their place.
> >
> > "Ben Nevarez" wrote:
> >
> > >
> > > Gene,
> > >
> > > According to that output the port number is 5001 not 5000. So you should use
> > >
> > > ALTER DATABASE test
> > > SET PARTNER => > > 'TCP://pc500:5001'
> > >
> > > Please add the full domain name too.
> > >
> > > Please test this and see if it works.
> > >
> > > Hope this helps,
> > >
> > > Ben Nevarez
> > >
> > >
> > >
> > >
> > > "Gene." wrote:
> > >
> > > > Hi Ben
> > > >
> > > > Here is an output from:
> > > >
> > > > select name, type_desc, port, ip_address from sys.tcp_endpoints
> > > > select name, role_desc, state_desc from sys.database_mirroring_endpoints
> > > >
> > > >
> > > >
> > > > name
> > > > type_desc
> > > > port ip_address
> > > > ------
> > > > ---- --
> > > > ---
> > > > Dedicated Admin Connection
> > > > TSQL
> > > > 0 NULL
> > > > TSQL Default TCP
> > > > TSQL
> > > > 0 NULL
> > > > Endpoint_Mirroring
> > > > DATABASE_MIRRORING
> > > > 5001 NULL
> > > >
> > > > (3 row(s) affected)
> > > >
> > > > name
> > > > role_desc
> > > > state_desc
> > > > ------
> > > > ----
> > > > ----
> > > > Endpoint_Mirroring
> > > > ALL
> > > > STARTED
> > > >
> > > >
> > > >
> > > > Yes, it's started.
> > > >
> > > > In addition to it I found message which looks so innocent:
> > > >
> > > > Login failed for user 'group\user'. [CLIENT: <local machine>]
> > > >
> > > > I logged in with that user hundreds times for sure.
> > > >
> > > >
> > > > "Ben Nevarez" wrote:
> > > >
> > > > >
> > > > > Hello,
> > > > >
> > > > > I supposed you can ping that server, right? :-)
> > > > >
> > > > > Is the endpoint started? When it is created the default is stopped. Check
> > > > > state_desc on
> > > > >
> > > > > select * from sys.database_mirroring_endpoints
> > > > >
> > > > > Always use full domain name.
> > > > >
> > > > > Check port is correct on sys.tcp_endpoints.
> > > > >
> > > > > Hope this helps,
> > > > >
> > > > > Ben Nevarez
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "Gene." wrote:
> > > > >
> > > > > > Hi All
> > > > > > I am trying to test db mirroring. I went exactly as book says: started 2 sql
> > > > > > servers with the same domain accounts, created endpoints. Checked if
> > > > > > endpoints exist and listen - they do.
> > > > > > Than I try to alter test db:
> > > > > >
> > > > > > ALTER DATABASE test
> > > > > > SET PARTNER => > > > > > 'TCP://pc500:5000'
> > > > > > and get:
> > > > > >
> > > > > > Msg 1418, Level 16, State 1, Line 2
> > > > > > The server network address "TCP://pc500:5000" can not be reached or does not
> > > > > > exist. Check the network address name and that the ports for the local and
> > > > > > remote endpoints are operational.
> > > > > >
> > > > > > pc500 is a partner pc.
> > > > > >
> > > > > > I also tried to use full domain name and ip addres. Each time I removed
> > > > > > endpoints and checked from os prompt if anything listens on the port - no.
> > > > > > But no matter what I do, I get this error. I also checked with my sysadmin
> > > > > > if there is any kind of filtering or firewalls - no.
> > > > > > As a matter of fact, pc500 is virtual pc which resides on my pc.
> > > > > >
> > > > > > It does not work. I tried replication from 2005 to 2005 - the same problem.
> > > > > > But replication from 2k to 2005 - works painlessly.
> > > > > >
> > > > > > Does anybody have clue what's the problem here?
> > > > > >
I am trying to test db mirroring. I went exactly as book says: started 2 sql
servers with the same domain accounts, created endpoints. Checked if
endpoints exist and listen - they do.
Than I try to alter test db:
ALTER DATABASE test
SET PARTNER = 'TCP://pc500:5000'
and get:
Msg 1418, Level 16, State 1, Line 2
The server network address "TCP://pc500:5000" can not be reached or does not
exist. Check the network address name and that the ports for the local and
remote endpoints are operational.
pc500 is a partner pc.
I also tried to use full domain name and ip addres. Each time I removed
endpoints and checked from os prompt if anything listens on the port - no.
But no matter what I do, I get this error. I also checked with my sysadmin
if there is any kind of filtering or firewalls - no.
As a matter of fact, pc500 is virtual pc which resides on my pc.
It does not work. I tried replication from 2005 to 2005 - the same problem.
But replication from 2k to 2005 - works painlessly.
Does anybody have clue what's the problem here?Hello,
I supposed you can ping that server, right? :-)
Is the endpoint started? When it is created the default is stopped. Check
state_desc on
select * from sys.database_mirroring_endpoints
Always use full domain name.
Check port is correct on sys.tcp_endpoints.
Hope this helps,
Ben Nevarez
"Gene." wrote:
> Hi All
> I am trying to test db mirroring. I went exactly as book says: started 2 sql
> servers with the same domain accounts, created endpoints. Checked if
> endpoints exist and listen - they do.
> Than I try to alter test db:
> ALTER DATABASE test
> SET PARTNER => 'TCP://pc500:5000'
> and get:
> Msg 1418, Level 16, State 1, Line 2
> The server network address "TCP://pc500:5000" can not be reached or does not
> exist. Check the network address name and that the ports for the local and
> remote endpoints are operational.
> pc500 is a partner pc.
> I also tried to use full domain name and ip addres. Each time I removed
> endpoints and checked from os prompt if anything listens on the port - no.
> But no matter what I do, I get this error. I also checked with my sysadmin
> if there is any kind of filtering or firewalls - no.
> As a matter of fact, pc500 is virtual pc which resides on my pc.
> It does not work. I tried replication from 2005 to 2005 - the same problem.
> But replication from 2k to 2005 - works painlessly.
> Does anybody have clue what's the problem here?
>|||Hi Ben
Here is an output from:
select name, type_desc, port, ip_address from sys.tcp_endpoints
select name, role_desc, state_desc from sys.database_mirroring_endpoints
name
type_desc
port ip_address
------
---- --
---
Dedicated Admin Connection
TSQL
0 NULL
TSQL Default TCP
TSQL
0 NULL
Endpoint_Mirroring
DATABASE_MIRRORING
5001 NULL
(3 row(s) affected)
name
role_desc
state_desc
------
----
----
Endpoint_Mirroring
ALL
STARTED
Yes, it's started.
In addition to it I found message which looks so innocent:
Login failed for user 'group\user'. [CLIENT: <local machine>]
I logged in with that user hundreds times for sure.
"Ben Nevarez" wrote:
> Hello,
> I supposed you can ping that server, right? :-)
> Is the endpoint started? When it is created the default is stopped. Check
> state_desc on
> select * from sys.database_mirroring_endpoints
> Always use full domain name.
> Check port is correct on sys.tcp_endpoints.
> Hope this helps,
> Ben Nevarez
>
>
> "Gene." wrote:
> > Hi All
> > I am trying to test db mirroring. I went exactly as book says: started 2 sql
> > servers with the same domain accounts, created endpoints. Checked if
> > endpoints exist and listen - they do.
> > Than I try to alter test db:
> >
> > ALTER DATABASE test
> > SET PARTNER => > 'TCP://pc500:5000'
> > and get:
> >
> > Msg 1418, Level 16, State 1, Line 2
> > The server network address "TCP://pc500:5000" can not be reached or does not
> > exist. Check the network address name and that the ports for the local and
> > remote endpoints are operational.
> >
> > pc500 is a partner pc.
> >
> > I also tried to use full domain name and ip addres. Each time I removed
> > endpoints and checked from os prompt if anything listens on the port - no.
> > But no matter what I do, I get this error. I also checked with my sysadmin
> > if there is any kind of filtering or firewalls - no.
> > As a matter of fact, pc500 is virtual pc which resides on my pc.
> >
> > It does not work. I tried replication from 2005 to 2005 - the same problem.
> > But replication from 2k to 2005 - works painlessly.
> >
> > Does anybody have clue what's the problem here?
> >|||Gene,
According to that output the port number is 5001 not 5000. So you should use
ALTER DATABASE test
SET PARTNER = 'TCP://pc500:5001'
Please add the full domain name too.
Please test this and see if it works.
Hope this helps,
Ben Nevarez
"Gene." wrote:
> Hi Ben
> Here is an output from:
> select name, type_desc, port, ip_address from sys.tcp_endpoints
> select name, role_desc, state_desc from sys.database_mirroring_endpoints
>
> name
> type_desc
> port ip_address
> ------
> ---- --
> ---
> Dedicated Admin Connection
> TSQL
> 0 NULL
> TSQL Default TCP
> TSQL
> 0 NULL
> Endpoint_Mirroring
> DATABASE_MIRRORING
> 5001 NULL
> (3 row(s) affected)
> name
> role_desc
> state_desc
> ------
> ----
> ----
> Endpoint_Mirroring
> ALL
> STARTED
>
> Yes, it's started.
> In addition to it I found message which looks so innocent:
> Login failed for user 'group\user'. [CLIENT: <local machine>]
> I logged in with that user hundreds times for sure.
>
> "Ben Nevarez" wrote:
> >
> > Hello,
> >
> > I supposed you can ping that server, right? :-)
> >
> > Is the endpoint started? When it is created the default is stopped. Check
> > state_desc on
> >
> > select * from sys.database_mirroring_endpoints
> >
> > Always use full domain name.
> >
> > Check port is correct on sys.tcp_endpoints.
> >
> > Hope this helps,
> >
> > Ben Nevarez
> >
> >
> >
> >
> > "Gene." wrote:
> >
> > > Hi All
> > > I am trying to test db mirroring. I went exactly as book says: started 2 sql
> > > servers with the same domain accounts, created endpoints. Checked if
> > > endpoints exist and listen - they do.
> > > Than I try to alter test db:
> > >
> > > ALTER DATABASE test
> > > SET PARTNER => > > 'TCP://pc500:5000'
> > > and get:
> > >
> > > Msg 1418, Level 16, State 1, Line 2
> > > The server network address "TCP://pc500:5000" can not be reached or does not
> > > exist. Check the network address name and that the ports for the local and
> > > remote endpoints are operational.
> > >
> > > pc500 is a partner pc.
> > >
> > > I also tried to use full domain name and ip addres. Each time I removed
> > > endpoints and checked from os prompt if anything listens on the port - no.
> > > But no matter what I do, I get this error. I also checked with my sysadmin
> > > if there is any kind of filtering or firewalls - no.
> > > As a matter of fact, pc500 is virtual pc which resides on my pc.
> > >
> > > It does not work. I tried replication from 2005 to 2005 - the same problem.
> > > But replication from 2k to 2005 - works painlessly.
> > >
> > > Does anybody have clue what's the problem here?
> > >|||Ben
That's correct. Principal uses 5000 port for it's own end point, but refers
to port 5001 of the partner. And vice verse.
I am using full domain names but for this post I used short ones. As I said
before, full domain names were tested with ping from both hosts. I also used
ip's in their place.
"Ben Nevarez" wrote:
> Gene,
> According to that output the port number is 5001 not 5000. So you should use
> ALTER DATABASE test
> SET PARTNER => 'TCP://pc500:5001'
> Please add the full domain name too.
> Please test this and see if it works.
> Hope this helps,
> Ben Nevarez
>
>
> "Gene." wrote:
> > Hi Ben
> >
> > Here is an output from:
> >
> > select name, type_desc, port, ip_address from sys.tcp_endpoints
> > select name, role_desc, state_desc from sys.database_mirroring_endpoints
> >
> >
> >
> > name
> > type_desc
> > port ip_address
> > ------
> > ---- --
> > ---
> > Dedicated Admin Connection
> > TSQL
> > 0 NULL
> > TSQL Default TCP
> > TSQL
> > 0 NULL
> > Endpoint_Mirroring
> > DATABASE_MIRRORING
> > 5001 NULL
> >
> > (3 row(s) affected)
> >
> > name
> > role_desc
> > state_desc
> > ------
> > ----
> > ----
> > Endpoint_Mirroring
> > ALL
> > STARTED
> >
> >
> >
> > Yes, it's started.
> >
> > In addition to it I found message which looks so innocent:
> >
> > Login failed for user 'group\user'. [CLIENT: <local machine>]
> >
> > I logged in with that user hundreds times for sure.
> >
> >
> > "Ben Nevarez" wrote:
> >
> > >
> > > Hello,
> > >
> > > I supposed you can ping that server, right? :-)
> > >
> > > Is the endpoint started? When it is created the default is stopped. Check
> > > state_desc on
> > >
> > > select * from sys.database_mirroring_endpoints
> > >
> > > Always use full domain name.
> > >
> > > Check port is correct on sys.tcp_endpoints.
> > >
> > > Hope this helps,
> > >
> > > Ben Nevarez
> > >
> > >
> > >
> > >
> > > "Gene." wrote:
> > >
> > > > Hi All
> > > > I am trying to test db mirroring. I went exactly as book says: started 2 sql
> > > > servers with the same domain accounts, created endpoints. Checked if
> > > > endpoints exist and listen - they do.
> > > > Than I try to alter test db:
> > > >
> > > > ALTER DATABASE test
> > > > SET PARTNER => > > > 'TCP://pc500:5000'
> > > > and get:
> > > >
> > > > Msg 1418, Level 16, State 1, Line 2
> > > > The server network address "TCP://pc500:5000" can not be reached or does not
> > > > exist. Check the network address name and that the ports for the local and
> > > > remote endpoints are operational.
> > > >
> > > > pc500 is a partner pc.
> > > >
> > > > I also tried to use full domain name and ip addres. Each time I removed
> > > > endpoints and checked from os prompt if anything listens on the port - no.
> > > > But no matter what I do, I get this error. I also checked with my sysadmin
> > > > if there is any kind of filtering or firewalls - no.
> > > > As a matter of fact, pc500 is virtual pc which resides on my pc.
> > > >
> > > > It does not work. I tried replication from 2005 to 2005 - the same problem.
> > > > But replication from 2k to 2005 - works painlessly.
> > > >
> > > > Does anybody have clue what's the problem here?
> > > >|||Have you applied SP1, or better, SP2?
Is the login failed message from the user who is supposed to connect to the
endpoint? if so, assign connect permissions to the required logins like in
grant connect on endpoint::endpoint_mirroring to [user]
Hope this helps,
Ben Nevarez
"Gene." wrote:
> Ben
> That's correct. Principal uses 5000 port for it's own end point, but refers
> to port 5001 of the partner. And vice verse.
> I am using full domain names but for this post I used short ones. As I said
> before, full domain names were tested with ping from both hosts. I also used
> ip's in their place.
> "Ben Nevarez" wrote:
> >
> > Gene,
> >
> > According to that output the port number is 5001 not 5000. So you should use
> >
> > ALTER DATABASE test
> > SET PARTNER => > 'TCP://pc500:5001'
> >
> > Please add the full domain name too.
> >
> > Please test this and see if it works.
> >
> > Hope this helps,
> >
> > Ben Nevarez
> >
> >
> >
> >
> > "Gene." wrote:
> >
> > > Hi Ben
> > >
> > > Here is an output from:
> > >
> > > select name, type_desc, port, ip_address from sys.tcp_endpoints
> > > select name, role_desc, state_desc from sys.database_mirroring_endpoints
> > >
> > >
> > >
> > > name
> > > type_desc
> > > port ip_address
> > > ------
> > > ---- --
> > > ---
> > > Dedicated Admin Connection
> > > TSQL
> > > 0 NULL
> > > TSQL Default TCP
> > > TSQL
> > > 0 NULL
> > > Endpoint_Mirroring
> > > DATABASE_MIRRORING
> > > 5001 NULL
> > >
> > > (3 row(s) affected)
> > >
> > > name
> > > role_desc
> > > state_desc
> > > ------
> > > ----
> > > ----
> > > Endpoint_Mirroring
> > > ALL
> > > STARTED
> > >
> > >
> > >
> > > Yes, it's started.
> > >
> > > In addition to it I found message which looks so innocent:
> > >
> > > Login failed for user 'group\user'. [CLIENT: <local machine>]
> > >
> > > I logged in with that user hundreds times for sure.
> > >
> > >
> > > "Ben Nevarez" wrote:
> > >
> > > >
> > > > Hello,
> > > >
> > > > I supposed you can ping that server, right? :-)
> > > >
> > > > Is the endpoint started? When it is created the default is stopped. Check
> > > > state_desc on
> > > >
> > > > select * from sys.database_mirroring_endpoints
> > > >
> > > > Always use full domain name.
> > > >
> > > > Check port is correct on sys.tcp_endpoints.
> > > >
> > > > Hope this helps,
> > > >
> > > > Ben Nevarez
> > > >
> > > >
> > > >
> > > >
> > > > "Gene." wrote:
> > > >
> > > > > Hi All
> > > > > I am trying to test db mirroring. I went exactly as book says: started 2 sql
> > > > > servers with the same domain accounts, created endpoints. Checked if
> > > > > endpoints exist and listen - they do.
> > > > > Than I try to alter test db:
> > > > >
> > > > > ALTER DATABASE test
> > > > > SET PARTNER => > > > > 'TCP://pc500:5000'
> > > > > and get:
> > > > >
> > > > > Msg 1418, Level 16, State 1, Line 2
> > > > > The server network address "TCP://pc500:5000" can not be reached or does not
> > > > > exist. Check the network address name and that the ports for the local and
> > > > > remote endpoints are operational.
> > > > >
> > > > > pc500 is a partner pc.
> > > > >
> > > > > I also tried to use full domain name and ip addres. Each time I removed
> > > > > endpoints and checked from os prompt if anything listens on the port - no.
> > > > > But no matter what I do, I get this error. I also checked with my sysadmin
> > > > > if there is any kind of filtering or firewalls - no.
> > > > > As a matter of fact, pc500 is virtual pc which resides on my pc.
> > > > >
> > > > > It does not work. I tried replication from 2005 to 2005 - the same problem.
> > > > > But replication from 2k to 2005 - works painlessly.
> > > > >
> > > > > Does anybody have clue what's the problem here?
> > > > >|||Hi Ben
It finaly started working.
The problem was quite simple.
I created end points and tried to alter db to communicate with partner.
Instead of it I had to dump and load partner with db and tran and only than
to finalize it's communication by altering db.
Thank you for your help anyway.
"Ben Nevarez" wrote:
> Have you applied SP1, or better, SP2?
> Is the login failed message from the user who is supposed to connect to the
> endpoint? if so, assign connect permissions to the required logins like in
> grant connect on endpoint::endpoint_mirroring to [user]
> Hope this helps,
> Ben Nevarez
>
>
> "Gene." wrote:
> > Ben
> >
> > That's correct. Principal uses 5000 port for it's own end point, but refers
> > to port 5001 of the partner. And vice verse.
> > I am using full domain names but for this post I used short ones. As I said
> > before, full domain names were tested with ping from both hosts. I also used
> > ip's in their place.
> >
> > "Ben Nevarez" wrote:
> >
> > >
> > > Gene,
> > >
> > > According to that output the port number is 5001 not 5000. So you should use
> > >
> > > ALTER DATABASE test
> > > SET PARTNER => > > 'TCP://pc500:5001'
> > >
> > > Please add the full domain name too.
> > >
> > > Please test this and see if it works.
> > >
> > > Hope this helps,
> > >
> > > Ben Nevarez
> > >
> > >
> > >
> > >
> > > "Gene." wrote:
> > >
> > > > Hi Ben
> > > >
> > > > Here is an output from:
> > > >
> > > > select name, type_desc, port, ip_address from sys.tcp_endpoints
> > > > select name, role_desc, state_desc from sys.database_mirroring_endpoints
> > > >
> > > >
> > > >
> > > > name
> > > > type_desc
> > > > port ip_address
> > > > ------
> > > > ---- --
> > > > ---
> > > > Dedicated Admin Connection
> > > > TSQL
> > > > 0 NULL
> > > > TSQL Default TCP
> > > > TSQL
> > > > 0 NULL
> > > > Endpoint_Mirroring
> > > > DATABASE_MIRRORING
> > > > 5001 NULL
> > > >
> > > > (3 row(s) affected)
> > > >
> > > > name
> > > > role_desc
> > > > state_desc
> > > > ------
> > > > ----
> > > > ----
> > > > Endpoint_Mirroring
> > > > ALL
> > > > STARTED
> > > >
> > > >
> > > >
> > > > Yes, it's started.
> > > >
> > > > In addition to it I found message which looks so innocent:
> > > >
> > > > Login failed for user 'group\user'. [CLIENT: <local machine>]
> > > >
> > > > I logged in with that user hundreds times for sure.
> > > >
> > > >
> > > > "Ben Nevarez" wrote:
> > > >
> > > > >
> > > > > Hello,
> > > > >
> > > > > I supposed you can ping that server, right? :-)
> > > > >
> > > > > Is the endpoint started? When it is created the default is stopped. Check
> > > > > state_desc on
> > > > >
> > > > > select * from sys.database_mirroring_endpoints
> > > > >
> > > > > Always use full domain name.
> > > > >
> > > > > Check port is correct on sys.tcp_endpoints.
> > > > >
> > > > > Hope this helps,
> > > > >
> > > > > Ben Nevarez
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "Gene." wrote:
> > > > >
> > > > > > Hi All
> > > > > > I am trying to test db mirroring. I went exactly as book says: started 2 sql
> > > > > > servers with the same domain accounts, created endpoints. Checked if
> > > > > > endpoints exist and listen - they do.
> > > > > > Than I try to alter test db:
> > > > > >
> > > > > > ALTER DATABASE test
> > > > > > SET PARTNER => > > > > > 'TCP://pc500:5000'
> > > > > > and get:
> > > > > >
> > > > > > Msg 1418, Level 16, State 1, Line 2
> > > > > > The server network address "TCP://pc500:5000" can not be reached or does not
> > > > > > exist. Check the network address name and that the ports for the local and
> > > > > > remote endpoints are operational.
> > > > > >
> > > > > > pc500 is a partner pc.
> > > > > >
> > > > > > I also tried to use full domain name and ip addres. Each time I removed
> > > > > > endpoints and checked from os prompt if anything listens on the port - no.
> > > > > > But no matter what I do, I get this error. I also checked with my sysadmin
> > > > > > if there is any kind of filtering or firewalls - no.
> > > > > > As a matter of fact, pc500 is virtual pc which resides on my pc.
> > > > > >
> > > > > > It does not work. I tried replication from 2005 to 2005 - the same problem.
> > > > > > But replication from 2k to 2005 - works painlessly.
> > > > > >
> > > > > > Does anybody have clue what's the problem here?
> > > > > >
Mirroring and Logins
I've created some SSIS packages to move logins from the Primary server to the Mirror server. But I'm having a small glitch. Lets say I have a database dbA that's mirrored. I then add a login of some sort, say userA. userA's default database is dbA. When I add that login to the mirrored server, how do I get the default database to be dbA? Currently I'm getting the following error from Alter Login:
ALTER LOGIN [userA] WITH DEFAULT_DATABASE=[dbA]
Msg 954, Level 14, State 1, Line 1
The database "dbA" cannot be opened. It is acting as a mirror database. I'm currently adding the logins with master as the default and then using Alter to attempt setting it. I can mask the error with a TRY block, but if I fail over it seems I'm going to have an issue. Any thoughts on this would be greatly appreciated.
Thanks,
Larry
I think the mirrored DB is inaccessible (just think of it never existed)
The only way I can think of to change the default DB, is to actually break the mirror (or swap Primary/Mirror role = manual failover)
alter the default databases, then re-establish the mirror (swap the role again = manual failover back to original Primary/Mirror)
|||Thanks. I guess we'll have to implement a policy that we only add logins after hours or create a window of time for adding logins where we can take the database down a couple of times (to fail over and back). Seems a bit out there for a High Availability solution since it will increase downtime a lot compared to what we have now.
Thanks again,
Larry
sqlFriday, March 23, 2012
Mining Access 2003
I created a AS 2005 data source to an Access 2003 database on my PC. The connection tests fine, I can browse the data from AS 2005. But when I try to process the mining model, I get a userid & password error. There is no password on the Access database. When I set up the data source, the wizard wanted a userid and password - the default was Admin - and I left the password blank. The connection tested ok. I tried changing the Impersonation settings, but that gives me a deployment error. Any ideas why the model process can't find a connection?
Is the AS Client and Server on the same machine? Since the access connection string contains a path to the file, the path has to be the same from the client tools as it is from the server.
|||I assumed that it was since I was able to get a connection and explore the data from AS. I have an entry under SQL Server Management Studio that's on my machine. Let me check a few things....|||Nope, still doesn't work. It still wants a userid and password for the Access table. It doesn't like the Impersonation type if I tell it to use the current user credentials. It doesn't like the Class if a pick Default or Service Account. I even tried putting a password on the Access database - and it still says it's invalid. What really confuses me is that I can right-click the table in the data source view and explore the data in the Access database with no problem.|||Is the server physically located on the same machine as the client?|||I think that may be the problem. I've been trying to find a machine that I know has the server on it to verify the solution. But our techs are upgrading the dev servers this week. At this point, I think I'll wait until things settle down and I can upgrade my PC to the new release - then I can make sure the server gets loaded as well.Thanks!|||
If your server's not on the same system, the reason you are seeing this behavior is that the access connection string contains a path that is relative to the location from where the connection originates. For example "C:\MyDB.mdb" on your client machine is not the same as "C:\MyDB.mdb" on the server machine.
What you can do is put the Access file on a share that is accessible via the same path from the client and the server, e.g. "\\MyMachine\MyShare\MyDB.mdb"
Mining Access 2003
I created a AS 2005 data source to an Access 2003 database on my PC. The connection tests fine, I can browse the data from AS 2005. But when I try to process the mining model, I get a userid & password error. There is no password on the Access database. When I set up the data source, the wizard wanted a userid and password - the default was Admin - and I left the password blank. The connection tested ok. I tried changing the Impersonation settings, but that gives me a deployment error. Any ideas why the model process can't find a connection?
Is the AS Client and Server on the same machine? Since the access connection string contains a path to the file, the path has to be the same from the client tools as it is from the server.
|||I assumed that it was since I was able to get a connection and explore the data from AS. I have an entry under SQL Server Management Studio that's on my machine. Let me check a few things....|||Nope, still doesn't work. It still wants a userid and password for the Access table. It doesn't like the Impersonation type if I tell it to use the current user credentials. It doesn't like the Class if a pick Default or Service Account. I even tried putting a password on the Access database - and it still says it's invalid. What really confuses me is that I can right-click the table in the data source view and explore the data in the Access database with no problem.|||Is the server physically located on the same machine as the client?|||I think that may be the problem. I've been trying to find a machine that I know has the server on it to verify the solution. But our techs are upgrading the dev servers this week. At this point, I think I'll wait until things settle down and I can upgrade my PC to the new release - then I can make sure the server gets loaded as well.Thanks!|||
If your server's not on the same system, the reason you are seeing this behavior is that the access connection string contains a path that is relative to the location from where the connection originates. For example "C:\MyDB.mdb" on your client machine is not the same as "C:\MyDB.mdb" on the server machine.
What you can do is put the Access file on a share that is accessible via the same path from the client and the server, e.g. "\\MyMachine\MyShare\MyDB.mdb"
Friday, March 9, 2012
Migration path of Reporting Servcies 2000 to 2005
This may have been asked before but can some one comment on migration path
for moving reporting services 2000 created reports to 2005.
Many thanks.It is supposed to be transparent. I am counting on it being so.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"ah_la_ma" <ah_la_ma@.yahoo.com> wrote in message
news:O0TL8xcNFHA.3420@.tk2msftngp13.phx.gbl...
> This may have been asked before but can some one comment on migration path
> for moving reporting services 2000 created reports to 2005.
> Many thanks.
>|||The goal is it is completely transparent. RS 2005 supports both 2000 and
2005 report definitions. If you load a 2000 report into the 2005 report
designer, it will upgrade it. The server will also support both 2000 and
2005 web services clients.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"ah_la_ma" <ah_la_ma@.yahoo.com> wrote in message
news:O0TL8xcNFHA.3420@.tk2msftngp13.phx.gbl...
> This may have been asked before but can some one comment on migration path
> for moving reporting services 2000 created reports to 2005.
> Many thanks.
>
for moving reporting services 2000 created reports to 2005.
Many thanks.It is supposed to be transparent. I am counting on it being so.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"ah_la_ma" <ah_la_ma@.yahoo.com> wrote in message
news:O0TL8xcNFHA.3420@.tk2msftngp13.phx.gbl...
> This may have been asked before but can some one comment on migration path
> for moving reporting services 2000 created reports to 2005.
> Many thanks.
>|||The goal is it is completely transparent. RS 2005 supports both 2000 and
2005 report definitions. If you load a 2000 report into the 2005 report
designer, it will upgrade it. The server will also support both 2000 and
2005 web services clients.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"ah_la_ma" <ah_la_ma@.yahoo.com> wrote in message
news:O0TL8xcNFHA.3420@.tk2msftngp13.phx.gbl...
> This may have been asked before but can some one comment on migration path
> for moving reporting services 2000 created reports to 2005.
> Many thanks.
>
Saturday, February 25, 2012
Migration Assistant For Access Can''t Find SQL Database?
I've installed SQL 2005 Express Addition which created a default database using Windows Authentication -- MachineName/SQLEXPRES. I want to convert some access databases to sql server in the migration assistant, however, when I try to connect the migration assistant to the default database I can't find the database in the drop down box wizard? I'm perplexed? Please shed some light or point me to some articles that will help. Thanks.
It is not practical to use standard Express to migrate Access so see if you can use the one with Management Studio instead, this will give you control of all the steps. Hope this helps.
http://msdn.microsoft.com/vstudio/express/sql/download/
|||
Yes, Management Studio is the one I used. I am able to connect via Management Studio, however, the Migration Assistant can't locate it? Looking for other suggestions? Thanks.
|||Try the eval good for 6 months, you could buy the developer for under $40 online if you have the ram this can help you move Access if all you have is tables and queries. If you have VBA you may need professional help. I have seen Access migration taking six months or more because it lets users add stuff SQL Server will not accept and it uses limited data types.
http://www.microsoft.com/sql/downloads/trial-software.mspx
|||
I'm not sure I understand what you mean by "default database" in this context. SQL Server does not create any default databases when you install it.
In my use of SSMS I find that the drop down box that show the database name does not actually show the list of databases in the server because it has not actually connected to the server yet, so it can not list the databases. You can either specify a new database to be created or specify an existing database to open once you connect, but you need to type the name of the database, it won't populate the list for you.
Regards,
Mike
Subscribe to:
Posts (Atom)