I am having great difficulty installing SQL Server 7 Desktop Edition onto WinXP
Pro. The installation proceeds without error until an attempt is made to
configure and then connect to SQL Server, at which point the installation fails and all installed components are removed from the PC. I have tried to install on repeated occasions, always with the same result.
I would be very grateful for any help in solving this problem.
The contents of the CNFGSVR.OUT and ERRORLOG are as below:
CNFGSVR.OUT
===========
Starting Service ...
Connecting to Server ...
driver={sql server};server=.;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
driver={sql server};server=.;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
driver={sql server};server=DAVIS;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
SQL Server configuration failed.
ERRORLOG
========
2003-05-25 23:32:19.09 kernel Microsoft SQL Server 7.00 - 7.00.623 (Intel X86)
Nov 27 1998 22:20:07
Copyright (c) 1988-1998 Microsoft Corporation
Desktop Edition on Windows NT 5.1 (Build 2600: Service Pack 1)
2003-05-25 23:32:19.09 kernel Copyright (C) 1988-1997 MicrosoftCorporation.
2003-05-25 23:32:19.09 kernel All rights reserved.
2003-05-25 23:32:19.09 kernel Logging SQL Server messages in file
'C:\MSSQL7\log\ERRORLOG'.
2003-05-25 23:32:19.12 kernel initconfig: Number of user connections limited to 32767.
2003-05-25 23:32:19.12 kernel SQL Server is starting at priority class
'normal'(1 CPU detected).
2003-05-25 23:32:19.12 kernel User Mode Scheduler configured for thread processing
2003-05-25 23:32:20.17 server Directory Size: 21633
2003-05-25 23:32:20.18 spid1 Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks
2003-05-25 23:32:20.18 spid1 Warning ******************
2003-05-25 23:32:20.18 spid1 SQL Server started in single user mode. Updates allowed to system catalogs.
2003-05-25 23:32:20.18 spid1 Warning ******************
2003-05-25 23:32:20.18 spid1 Recovering only master database
2003-05-25 23:32:20.18 spid1 Starting up database 'master'.
2003-05-25 23:32:20.18 spid1 Opening file C:\MSSQL7\data\master.mdf.
2003-05-25 23:32:20.20 spid1 Opening file C:\MSSQL7\data\mastlog.ldf.
2003-05-25 23:32:20.26 spid1 Loading SQL Server's Unicode collation.
2003-05-25 23:32:20.28 spid1 Loading SQL Server's non-Unicode sort order and character set.
2003-05-25 23:32:20.40 spid1 4 transactions rolled forward in database 'master' (1).
2003-05-25 23:32:20.40 spid1 0 transactions rolled back in database 'master' (1).
2003-05-25 23:32:20.58 spid1 Server is unnamed.
2003-05-25 23:32:20.58 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
2003-05-25 23:32:20.58 kernel Using 'OPENDS60.DLL' version '7.00.00.0623'.
2003-05-25 23:32:20.59 ods Using 'SSNMPN70.DLL' version '7.0.623' to listen on '\\.\pipe\sql\query'.
2003-05-25 23:32:20.59 ods Using 'SSMSSO70.DLL' version '7.0.623' to listen on '1433'.
2003-05-25 23:32:21.09 ods Using 'SSMSRP70.DLL' version '7.0.623' to listen on 'DAVIS'.
2003-05-25 23:32:21.19 spid1 SQL Server's Unicode collation is:
2003-05-25 23:32:21.19 spid1 'English' (ID = 1033).
2003-05-25 23:32:21.19 spid1 comparison style = 196609.
2003-05-25 23:32:21.19 spid1 SQL Server's non-Unicode sort order is:
2003-05-25 23:32:21.19 spid1 'nocase_iso' (ID = 52).
2003-05-25 23:32:21.19 spid1 SQL Server's non-Unicode character set is:
2003-05-25 23:32:21.19 spid1 'iso_1' (ID = 1).
2003-05-25 23:32:21.20 kernel Warning: override, autoexec procedures skipped.
2003-05-25 23:32:35.88 kernel SQL Server is terminating due to 'stop' request from Service Control Manager.Try downloading latest MDAC from MS Data (http://www.microsoft.com/data) and reinstall again.|||Satya,
I have already downloaded MDAC 2.7 but the install still fails.
It's probably not relevant but if I run Component Checker against version "2.7 SP1(WinXP)" the utility reports the following anomalies:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MSDASC\Default Icon
Registry
Field 'Value' mismatch: Expect 'C:\Program Files\Common Files\System\Ole DB\oledb32.dll^0' Got 'C:\WINDOWS\System32\migicons.exe^101'
Error
MSADCO.DLL
COM
Unknown Class ID = {9381d8f1-0288-11d0-9501-00aa00b911a5}
Warning
MSDATT.DLL
COM
Unknown Class ID = {c8b522ce-5cf3-11ce-ade5-00aa0044773d}
Warning|||Refer to dasetup.log files in the windows directory that might shed some light on the problem. You can log MDAC installation by using \MDACSetup\Setup.exe /gc C:\MdacInstalllog.txt
If no avail then make sure those 2 DLLs got registered properly on XP, try reinstall XP with all available SPs.|||Any ideas how I can stop the install removing all components on failure? If I could stop the components being removed I might be able to try starting and configuring the service by hand.|||Remove all reference registry keys and delete the directories during the installation.
Showing posts with label desktop. Show all posts
Showing posts with label desktop. Show all posts
Friday, March 30, 2012
Problems installing MSDE with the Server Service disabled
Hello ;
We are having problems installing our desktop Application at a
customer's site where the policy is to disable the Server Service.
Being a desktop configuration, our installation places MSDE on the
same PC as the rest of the application. Unfortunately the
installation will not succeed unless the Server Service is enabled.
Interestingly, we can disable the Server Service after installation
and the Application will still function normally. However, enabling
the Server Service --even just during installation-- would violate our
customer's network policy.
It is my understanding that Server Service is not required if your
references are confined to the local system. Therefore my question is
: Is there a way to install MSDE or Standard Edition on the local
system when the Server Service is disabled?
Thanks in advance for any feedback,
BobThe following article has a fix for the problem you are experiencing:
http://support.microsoft.com/?id=829386.
You will need to contact Microsft support to get the fix.
Rand
This posting is provided "as is" with no warranties and confers no rights.sql
We are having problems installing our desktop Application at a
customer's site where the policy is to disable the Server Service.
Being a desktop configuration, our installation places MSDE on the
same PC as the rest of the application. Unfortunately the
installation will not succeed unless the Server Service is enabled.
Interestingly, we can disable the Server Service after installation
and the Application will still function normally. However, enabling
the Server Service --even just during installation-- would violate our
customer's network policy.
It is my understanding that Server Service is not required if your
references are confined to the local system. Therefore my question is
: Is there a way to install MSDE or Standard Edition on the local
system when the Server Service is disabled?
Thanks in advance for any feedback,
BobThe following article has a fix for the problem you are experiencing:
http://support.microsoft.com/?id=829386.
You will need to contact Microsft support to get the fix.
Rand
This posting is provided "as is" with no warranties and confers no rights.sql
Problems installing MSDE Desktop SP3a SQL server
Hi,
I'm trying to install MSDE Desktop SP3a SQL server on my Windows 2000 Professional Laptop.
Every time I try it nearly finishes the installation and then just rollsback.
Can anyone help? Is this a known issue?
Thanks in advance,
JockyHave you tried using the verbose logging switch when you install? You need to add something like this to the setup.exe you are running fromthe commandline:
|||The following article might help you setup MSDE from command line.
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q324998|||
I'm trying to install MSDE Desktop SP3a SQL server on my Windows 2000 Professional Laptop.
Every time I try it nearly finishes the installation and then just rollsback.
Can anyone help? Is this a known issue?
Thanks in advance,
JockyHave you tried using the verbose logging switch when you install? You need to add something like this to the setup.exe you are running fromthe commandline:
/L*v c:\msde_install.log
|||The following article might help you setup MSDE from command line.
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q324998|||
That Microsoft article did the trick. Thanks y'all!
Jocky.
Problems installing MSDE
When a double click setup.exe, I get the following message:
My machine is running Windows 2000 5.00.2195 Service Pack 4.
Anyone knows how to solve this problem?
Part of the problems installing MSDE is trying to install the service pack before SQL Server, try the link below and download the eval edition good for 120 days and the developer edition is $30 or less on the web . Hope this helps.
http://www.microsoft.com/sql/evaluation/trial/default.mspx|||Thanks for your advice. I didn't write back earlier because I wanted to try our solution until I it was successful.
I tried what you suggested, but I was still getting the error message.I looked into the autorun.inf file. In it it had these lines
...
[servicepack]
NTVersion=4
...
I verified that I could run MSDE on my OS by reading the documentation.Then, I commented out the line, and the installation rancorrectly.
"SQL Server 2000 Desktop Engine Setup
SQL Server 2000 Desktop Engine cannot be installed on thiscomputer. This product requires Microsoft Windows NT Version 4.0 Service Pack 5or higher. Please download the service pack fromwww.microsoft.com prior to installing."
My machine is running Windows 2000 5.00.2195 Service Pack 4.
Anyone knows how to solve this problem?
Part of the problems installing MSDE is trying to install the service pack before SQL Server, try the link below and download the eval edition good for 120 days and the developer edition is $30 or less on the web . Hope this helps.
http://www.microsoft.com/sql/evaluation/trial/default.mspx|||Thanks for your advice. I didn't write back earlier because I wanted to try our solution until I it was successful.
I tried what you suggested, but I was still getting the error message.I looked into the autorun.inf file. In it it had these lines
...
[servicepack]
NTVersion=4
...
I verified that I could run MSDE on my OS by reading the documentation.Then, I commented out the line, and the installation rancorrectly.
Friday, March 23, 2012
Problems creating mirroring on 2005.
SQL2K5 sp1
Instance names:
Development\MySQL2K5
Development\Subscriber
Development\Witness
Im trying to set up mirroring on 3 instances on my desktop and having some
issues (not ideal I know, but it's what I've got to work with for now). Here
is what I've done:
--Create endpoint on principal instance and set recovery model
CREATE ENDPOINT endpoint_mirroring
STATE = STARTED
AS TCP ( LISTENER_PORT = 5022 )
FOR DATABASE_MIRRORING (ROLE=PARTNER);
GO
ALTER DATABASE AdventureWorks
SET RECOVERY FULL;
--Create endpoint on mirror instance
CREATE ENDPOINT endpoint_mirroring
STATE = STARTED
AS TCP ( LISTENER_PORT = 5023 )
FOR DATABASE_MIRRORING (ROLE=PARTNER);
GO
--Create endpoint on witness instance
CREATE ENDPOINT endpoint_mirroring
STATE = STARTED
AS TCP ( LISTENER_PORT = 5024 )
FOR DATABASE_MIRRORING (ROLE=WITNESS);
GO
--Backup principal database
BACKUP DATABASE AdventureWorks
TO DISK='C:\MirrorBackup\AWBackup.BAK'
with init;
GO
--Restore mirror database
RESTORE DATABASE AdventureWorks
FROM DISK='C:\MirrorBackup\AWBackup.BAK'
WITH NORECOVERY,
MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
GO
--On the mirror server set the principal server
ALTER DATABASE AdventureWorks
SET PARTNER = 'TCP://MySQL2K5:5022'
GO
--On the principal server set the mirror server
ALTER DATABASE AdventureWorks
SET PARTNER = 'TCP://MySQL2K5:5023'
GO
That last step blows up with:
Msg 1418, Level 16, State 1, Line 1
The server network address "TCP://MYSQL2K5:5023" 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.
Any ideas?
TIA, ChrisRWhat about the security configuration? Have you granted connect permissions
to the other servers' accounts to the database mirroring endpoints?
You should use
grant connect on endpoint::endpoint_mirroring to [domain\account]
Ben Nevarez, MCDBA, OCP
Database Administrator
"ChrisR" wrote:
> SQL2K5 sp1
> Instance names:
> Development\MySQL2K5
> Development\Subscriber
> Development\Witness
> Im trying to set up mirroring on 3 instances on my desktop and having some
> issues (not ideal I know, but it's what I've got to work with for now). Here
> is what I've done:
> --Create endpoint on principal instance and set recovery model
> CREATE ENDPOINT endpoint_mirroring
> STATE = STARTED
> AS TCP ( LISTENER_PORT = 5022 )
> FOR DATABASE_MIRRORING (ROLE=PARTNER);
> GO
> ALTER DATABASE AdventureWorks
> SET RECOVERY FULL;
> --Create endpoint on mirror instance
> CREATE ENDPOINT endpoint_mirroring
> STATE = STARTED
> AS TCP ( LISTENER_PORT = 5023 )
> FOR DATABASE_MIRRORING (ROLE=PARTNER);
> GO
> --Create endpoint on witness instance
> CREATE ENDPOINT endpoint_mirroring
> STATE = STARTED
> AS TCP ( LISTENER_PORT = 5024 )
> FOR DATABASE_MIRRORING (ROLE=WITNESS);
> GO
> --Backup principal database
> BACKUP DATABASE AdventureWorks
> TO DISK='C:\MirrorBackup\AWBackup.BAK'
> with init;
> GO
> --Restore mirror database
> RESTORE DATABASE AdventureWorks
> FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> WITH NORECOVERY,
> MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> GO
> --On the mirror server set the principal server
> ALTER DATABASE AdventureWorks
> SET PARTNER => 'TCP://MySQL2K5:5022'
> GO
> --On the principal server set the mirror server
> ALTER DATABASE AdventureWorks
> SET PARTNER = 'TCP://MySQL2K5:5023'
> GO
> That last step blows up with:
> Msg 1418, Level 16, State 1, Line 1
> The server network address "TCP://MYSQL2K5:5023" 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.
> Any ideas?
> TIA, ChrisR
>
>|||That didn't fix it. As an FYI all 3 instances are running under the same
domain account.
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> What about the security configuration? Have you granted connect
permissions
> to the other servers' accounts to the database mirroring endpoints?
> You should use
> grant connect on endpoint::endpoint_mirroring to [domain\account]
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "ChrisR" wrote:
> > SQL2K5 sp1
> >
> > Instance names:
> >
> > Development\MySQL2K5
> > Development\Subscriber
> > Development\Witness
> >
> > Im trying to set up mirroring on 3 instances on my desktop and having
some
> > issues (not ideal I know, but it's what I've got to work with for now).
Here
> > is what I've done:
> >
> > --Create endpoint on principal instance and set recovery model
> > CREATE ENDPOINT endpoint_mirroring
> > STATE = STARTED
> > AS TCP ( LISTENER_PORT = 5022 )
> > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > GO
> > ALTER DATABASE AdventureWorks
> > SET RECOVERY FULL;
> > --Create endpoint on mirror instance
> > CREATE ENDPOINT endpoint_mirroring
> > STATE = STARTED
> > AS TCP ( LISTENER_PORT = 5023 )
> > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > GO
> > --Create endpoint on witness instance
> > CREATE ENDPOINT endpoint_mirroring
> > STATE = STARTED
> > AS TCP ( LISTENER_PORT = 5024 )
> > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > GO
> > --Backup principal database
> > BACKUP DATABASE AdventureWorks
> > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > with init;
> > GO
> > --Restore mirror database
> > RESTORE DATABASE AdventureWorks
> > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > WITH NORECOVERY,
> > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > GO
> > --On the mirror server set the principal server
> > ALTER DATABASE AdventureWorks
> > SET PARTNER => > 'TCP://MySQL2K5:5022'
> > GO
> > --On the principal server set the mirror server
> > ALTER DATABASE AdventureWorks
> > SET PARTNER = 'TCP://MySQL2K5:5023'
> > GO
> >
> > That last step blows up with:
> > Msg 1418, Level 16, State 1, Line 1
> > The server network address "TCP://MYSQL2K5:5023" 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.
> >
> > Any ideas?
> > TIA, ChrisR
> >
> >
> >|||Let us try something else then.
Is MYSQL2K5 the name of your computer?
BOL recommends to use the fully qualified domain name. Try ipconfig /all and
look for host name and primary dns suffix.
Ben Nevarez, MCDBA, OCP
Database Administrator
"ChrisR" wrote:
> That didn't fix it. As an FYI all 3 instances are running under the same
> domain account.
> "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> >
> > What about the security configuration? Have you granted connect
> permissions
> > to the other servers' accounts to the database mirroring endpoints?
> >
> > You should use
> >
> > grant connect on endpoint::endpoint_mirroring to [domain\account]
> >
> > Ben Nevarez, MCDBA, OCP
> > Database Administrator
> >
> >
> > "ChrisR" wrote:
> >
> > > SQL2K5 sp1
> > >
> > > Instance names:
> > >
> > > Development\MySQL2K5
> > > Development\Subscriber
> > > Development\Witness
> > >
> > > Im trying to set up mirroring on 3 instances on my desktop and having
> some
> > > issues (not ideal I know, but it's what I've got to work with for now).
> Here
> > > is what I've done:
> > >
> > > --Create endpoint on principal instance and set recovery model
> > > CREATE ENDPOINT endpoint_mirroring
> > > STATE = STARTED
> > > AS TCP ( LISTENER_PORT = 5022 )
> > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > GO
> > > ALTER DATABASE AdventureWorks
> > > SET RECOVERY FULL;
> > > --Create endpoint on mirror instance
> > > CREATE ENDPOINT endpoint_mirroring
> > > STATE = STARTED
> > > AS TCP ( LISTENER_PORT = 5023 )
> > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > GO
> > > --Create endpoint on witness instance
> > > CREATE ENDPOINT endpoint_mirroring
> > > STATE = STARTED
> > > AS TCP ( LISTENER_PORT = 5024 )
> > > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > > GO
> > > --Backup principal database
> > > BACKUP DATABASE AdventureWorks
> > > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > > with init;
> > > GO
> > > --Restore mirror database
> > > RESTORE DATABASE AdventureWorks
> > > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > > WITH NORECOVERY,
> > > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > > GO
> > > --On the mirror server set the principal server
> > > ALTER DATABASE AdventureWorks
> > > SET PARTNER => > > 'TCP://MySQL2K5:5022'
> > > GO
> > > --On the principal server set the mirror server
> > > ALTER DATABASE AdventureWorks
> > > SET PARTNER = 'TCP://MySQL2K5:5023'
> > > GO
> > >
> > > That last step blows up with:
> > > Msg 1418, Level 16, State 1, Line 1
> > > The server network address "TCP://MYSQL2K5:5023" 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.
> > >
> > > Any ideas?
> > > TIA, ChrisR
> > >
> > >
> > >
>
>|||The box name is Development. The instance name is MySQL2K5. I have tried
development\mysql2k5 and many variations of it and get incorrect syntax
errors. I also tried the FQDN and still got the original error.
Thanks for all the help.
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:2F186919-F424-4707-9320-68474A3A59C1@.microsoft.com...
> Let us try something else then.
> Is MYSQL2K5 the name of your computer?
> BOL recommends to use the fully qualified domain name. Try ipconfig /all
and
> look for host name and primary dns suffix.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "ChrisR" wrote:
> > That didn't fix it. As an FYI all 3 instances are running under the same
> > domain account.
> >
> > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> > >
> > > What about the security configuration? Have you granted connect
> > permissions
> > > to the other servers' accounts to the database mirroring endpoints?
> > >
> > > You should use
> > >
> > > grant connect on endpoint::endpoint_mirroring to [domain\account]
> > >
> > > Ben Nevarez, MCDBA, OCP
> > > Database Administrator
> > >
> > >
> > > "ChrisR" wrote:
> > >
> > > > SQL2K5 sp1
> > > >
> > > > Instance names:
> > > >
> > > > Development\MySQL2K5
> > > > Development\Subscriber
> > > > Development\Witness
> > > >
> > > > Im trying to set up mirroring on 3 instances on my desktop and
having
> > some
> > > > issues (not ideal I know, but it's what I've got to work with for
now).
> > Here
> > > > is what I've done:
> > > >
> > > > --Create endpoint on principal instance and set recovery model
> > > > CREATE ENDPOINT endpoint_mirroring
> > > > STATE = STARTED
> > > > AS TCP ( LISTENER_PORT = 5022 )
> > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > GO
> > > > ALTER DATABASE AdventureWorks
> > > > SET RECOVERY FULL;
> > > > --Create endpoint on mirror instance
> > > > CREATE ENDPOINT endpoint_mirroring
> > > > STATE = STARTED
> > > > AS TCP ( LISTENER_PORT = 5023 )
> > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > GO
> > > > --Create endpoint on witness instance
> > > > CREATE ENDPOINT endpoint_mirroring
> > > > STATE = STARTED
> > > > AS TCP ( LISTENER_PORT = 5024 )
> > > > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > > > GO
> > > > --Backup principal database
> > > > BACKUP DATABASE AdventureWorks
> > > > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > with init;
> > > > GO
> > > > --Restore mirror database
> > > > RESTORE DATABASE AdventureWorks
> > > > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > WITH NORECOVERY,
> > > > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > > > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > > > GO
> > > > --On the mirror server set the principal server
> > > > ALTER DATABASE AdventureWorks
> > > > SET PARTNER => > > > 'TCP://MySQL2K5:5022'
> > > > GO
> > > > --On the principal server set the mirror server
> > > > ALTER DATABASE AdventureWorks
> > > > SET PARTNER = 'TCP://MySQL2K5:5023'
> > > > GO
> > > >
> > > > That last step blows up with:
> > > > Msg 1418, Level 16, State 1, Line 1
> > > > The server network address "TCP://MYSQL2K5:5023" 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.
> > > >
> > > > Any ideas?
> > > > TIA, ChrisR
> > > >
> > > >
> > > >
> >
> >
> >|||On
ALTER DATABASE AdventureWorks
> > > > > SET PARTNER => > > > > 'TCP://MySQL2K5:5022'
you need to specify your host name and domain name NOT the SQL Server
instance name. For example, development.yourdomain.com.
Run ipconfig /all and look into host name and primary dns suffix.
Ben Nevarez, MCDBA, OCP
Database Administrator
"ChrisR" wrote:
> The box name is Development. The instance name is MySQL2K5. I have tried
> development\mysql2k5 and many variations of it and get incorrect syntax
> errors. I also tried the FQDN and still got the original error.
> Thanks for all the help.
> "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> news:2F186919-F424-4707-9320-68474A3A59C1@.microsoft.com...
> >
> > Let us try something else then.
> >
> > Is MYSQL2K5 the name of your computer?
> >
> > BOL recommends to use the fully qualified domain name. Try ipconfig /all
> and
> > look for host name and primary dns suffix.
> >
> > Ben Nevarez, MCDBA, OCP
> > Database Administrator
> >
> >
> > "ChrisR" wrote:
> >
> > > That didn't fix it. As an FYI all 3 instances are running under the same
> > > domain account.
> > >
> > > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > > news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> > > >
> > > > What about the security configuration? Have you granted connect
> > > permissions
> > > > to the other servers' accounts to the database mirroring endpoints?
> > > >
> > > > You should use
> > > >
> > > > grant connect on endpoint::endpoint_mirroring to [domain\account]
> > > >
> > > > Ben Nevarez, MCDBA, OCP
> > > > Database Administrator
> > > >
> > > >
> > > > "ChrisR" wrote:
> > > >
> > > > > SQL2K5 sp1
> > > > >
> > > > > Instance names:
> > > > >
> > > > > Development\MySQL2K5
> > > > > Development\Subscriber
> > > > > Development\Witness
> > > > >
> > > > > Im trying to set up mirroring on 3 instances on my desktop and
> having
> > > some
> > > > > issues (not ideal I know, but it's what I've got to work with for
> now).
> > > Here
> > > > > is what I've done:
> > > > >
> > > > > --Create endpoint on principal instance and set recovery model
> > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > STATE = STARTED
> > > > > AS TCP ( LISTENER_PORT = 5022 )
> > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > GO
> > > > > ALTER DATABASE AdventureWorks
> > > > > SET RECOVERY FULL;
> > > > > --Create endpoint on mirror instance
> > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > STATE = STARTED
> > > > > AS TCP ( LISTENER_PORT = 5023 )
> > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > GO
> > > > > --Create endpoint on witness instance
> > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > STATE = STARTED
> > > > > AS TCP ( LISTENER_PORT = 5024 )
> > > > > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > > > > GO
> > > > > --Backup principal database
> > > > > BACKUP DATABASE AdventureWorks
> > > > > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > with init;
> > > > > GO
> > > > > --Restore mirror database
> > > > > RESTORE DATABASE AdventureWorks
> > > > > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > WITH NORECOVERY,
> > > > > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > > > > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > > > > GO
> > > > > --On the mirror server set the principal server
> > > > > ALTER DATABASE AdventureWorks
> > > > > SET PARTNER => > > > > 'TCP://MySQL2K5:5022'
> > > > > GO
> > > > > --On the principal server set the mirror server
> > > > > ALTER DATABASE AdventureWorks
> > > > > SET PARTNER = 'TCP://MySQL2K5:5023'
> > > > > GO
> > > > >
> > > > > That last step blows up with:
> > > > > Msg 1418, Level 16, State 1, Line 1
> > > > > The server network address "TCP://MYSQL2K5:5023" 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.
> > > > >
> > > > > Any ideas?
> > > > > TIA, ChrisR
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||Doh! I thought it was instance name.
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:5B6FD5FC-E687-4B1F-A01B-57C0C265D5DE@.microsoft.com...
> On
> ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER => > > > > > 'TCP://MySQL2K5:5022'
> you need to specify your host name and domain name NOT the SQL Server
> instance name. For example, development.yourdomain.com.
> Run ipconfig /all and look into host name and primary dns suffix.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "ChrisR" wrote:
> > The box name is Development. The instance name is MySQL2K5. I have tried
> > development\mysql2k5 and many variations of it and get incorrect syntax
> > errors. I also tried the FQDN and still got the original error.
> >
> > Thanks for all the help.
> >
> > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > news:2F186919-F424-4707-9320-68474A3A59C1@.microsoft.com...
> > >
> > > Let us try something else then.
> > >
> > > Is MYSQL2K5 the name of your computer?
> > >
> > > BOL recommends to use the fully qualified domain name. Try ipconfig
/all
> > and
> > > look for host name and primary dns suffix.
> > >
> > > Ben Nevarez, MCDBA, OCP
> > > Database Administrator
> > >
> > >
> > > "ChrisR" wrote:
> > >
> > > > That didn't fix it. As an FYI all 3 instances are running under the
same
> > > > domain account.
> > > >
> > > > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > > > news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> > > > >
> > > > > What about the security configuration? Have you granted connect
> > > > permissions
> > > > > to the other servers' accounts to the database mirroring
endpoints?
> > > > >
> > > > > You should use
> > > > >
> > > > > grant connect on endpoint::endpoint_mirroring to [domain\account]
> > > > >
> > > > > Ben Nevarez, MCDBA, OCP
> > > > > Database Administrator
> > > > >
> > > > >
> > > > > "ChrisR" wrote:
> > > > >
> > > > > > SQL2K5 sp1
> > > > > >
> > > > > > Instance names:
> > > > > >
> > > > > > Development\MySQL2K5
> > > > > > Development\Subscriber
> > > > > > Development\Witness
> > > > > >
> > > > > > Im trying to set up mirroring on 3 instances on my desktop and
> > having
> > > > some
> > > > > > issues (not ideal I know, but it's what I've got to work with
for
> > now).
> > > > Here
> > > > > > is what I've done:
> > > > > >
> > > > > > --Create endpoint on principal instance and set recovery model
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5022 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > > GO
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET RECOVERY FULL;
> > > > > > --Create endpoint on mirror instance
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5023 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > > GO
> > > > > > --Create endpoint on witness instance
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5024 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > > > > > GO
> > > > > > --Backup principal database
> > > > > > BACKUP DATABASE AdventureWorks
> > > > > > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > > with init;
> > > > > > GO
> > > > > > --Restore mirror database
> > > > > > RESTORE DATABASE AdventureWorks
> > > > > > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > > WITH NORECOVERY,
> > > > > > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > > > > > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > > > > > GO
> > > > > > --On the mirror server set the principal server
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER => > > > > > 'TCP://MySQL2K5:5022'
> > > > > > GO
> > > > > > --On the principal server set the mirror server
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER = 'TCP://MySQL2K5:5023'
> > > > > > GO
> > > > > >
> > > > > > That last step blows up with:
> > > > > > Msg 1418, Level 16, State 1, Line 1
> > > > > > The server network address "TCP://MYSQL2K5:5023" 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.
> > > > > >
> > > > > > Any ideas?
> > > > > > TIA, ChrisR
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||Thanks a lot!
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:5B6FD5FC-E687-4B1F-A01B-57C0C265D5DE@.microsoft.com...
> On
> ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER => > > > > > 'TCP://MySQL2K5:5022'
> you need to specify your host name and domain name NOT the SQL Server
> instance name. For example, development.yourdomain.com.
> Run ipconfig /all and look into host name and primary dns suffix.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "ChrisR" wrote:
> > The box name is Development. The instance name is MySQL2K5. I have tried
> > development\mysql2k5 and many variations of it and get incorrect syntax
> > errors. I also tried the FQDN and still got the original error.
> >
> > Thanks for all the help.
> >
> > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > news:2F186919-F424-4707-9320-68474A3A59C1@.microsoft.com...
> > >
> > > Let us try something else then.
> > >
> > > Is MYSQL2K5 the name of your computer?
> > >
> > > BOL recommends to use the fully qualified domain name. Try ipconfig
/all
> > and
> > > look for host name and primary dns suffix.
> > >
> > > Ben Nevarez, MCDBA, OCP
> > > Database Administrator
> > >
> > >
> > > "ChrisR" wrote:
> > >
> > > > That didn't fix it. As an FYI all 3 instances are running under the
same
> > > > domain account.
> > > >
> > > > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > > > news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> > > > >
> > > > > What about the security configuration? Have you granted connect
> > > > permissions
> > > > > to the other servers' accounts to the database mirroring
endpoints?
> > > > >
> > > > > You should use
> > > > >
> > > > > grant connect on endpoint::endpoint_mirroring to [domain\account]
> > > > >
> > > > > Ben Nevarez, MCDBA, OCP
> > > > > Database Administrator
> > > > >
> > > > >
> > > > > "ChrisR" wrote:
> > > > >
> > > > > > SQL2K5 sp1
> > > > > >
> > > > > > Instance names:
> > > > > >
> > > > > > Development\MySQL2K5
> > > > > > Development\Subscriber
> > > > > > Development\Witness
> > > > > >
> > > > > > Im trying to set up mirroring on 3 instances on my desktop and
> > having
> > > > some
> > > > > > issues (not ideal I know, but it's what I've got to work with
for
> > now).
> > > > Here
> > > > > > is what I've done:
> > > > > >
> > > > > > --Create endpoint on principal instance and set recovery model
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5022 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > > GO
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET RECOVERY FULL;
> > > > > > --Create endpoint on mirror instance
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5023 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > > GO
> > > > > > --Create endpoint on witness instance
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5024 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > > > > > GO
> > > > > > --Backup principal database
> > > > > > BACKUP DATABASE AdventureWorks
> > > > > > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > > with init;
> > > > > > GO
> > > > > > --Restore mirror database
> > > > > > RESTORE DATABASE AdventureWorks
> > > > > > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > > WITH NORECOVERY,
> > > > > > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > > > > > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > > > > > GO
> > > > > > --On the mirror server set the principal server
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER => > > > > > 'TCP://MySQL2K5:5022'
> > > > > > GO
> > > > > > --On the principal server set the mirror server
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER = 'TCP://MySQL2K5:5023'
> > > > > > GO
> > > > > >
> > > > > > That last step blows up with:
> > > > > > Msg 1418, Level 16, State 1, Line 1
> > > > > > The server network address "TCP://MYSQL2K5:5023" 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.
> > > > > >
> > > > > > Any ideas?
> > > > > > TIA, ChrisR
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >
Instance names:
Development\MySQL2K5
Development\Subscriber
Development\Witness
Im trying to set up mirroring on 3 instances on my desktop and having some
issues (not ideal I know, but it's what I've got to work with for now). Here
is what I've done:
--Create endpoint on principal instance and set recovery model
CREATE ENDPOINT endpoint_mirroring
STATE = STARTED
AS TCP ( LISTENER_PORT = 5022 )
FOR DATABASE_MIRRORING (ROLE=PARTNER);
GO
ALTER DATABASE AdventureWorks
SET RECOVERY FULL;
--Create endpoint on mirror instance
CREATE ENDPOINT endpoint_mirroring
STATE = STARTED
AS TCP ( LISTENER_PORT = 5023 )
FOR DATABASE_MIRRORING (ROLE=PARTNER);
GO
--Create endpoint on witness instance
CREATE ENDPOINT endpoint_mirroring
STATE = STARTED
AS TCP ( LISTENER_PORT = 5024 )
FOR DATABASE_MIRRORING (ROLE=WITNESS);
GO
--Backup principal database
BACKUP DATABASE AdventureWorks
TO DISK='C:\MirrorBackup\AWBackup.BAK'
with init;
GO
--Restore mirror database
RESTORE DATABASE AdventureWorks
FROM DISK='C:\MirrorBackup\AWBackup.BAK'
WITH NORECOVERY,
MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
GO
--On the mirror server set the principal server
ALTER DATABASE AdventureWorks
SET PARTNER = 'TCP://MySQL2K5:5022'
GO
--On the principal server set the mirror server
ALTER DATABASE AdventureWorks
SET PARTNER = 'TCP://MySQL2K5:5023'
GO
That last step blows up with:
Msg 1418, Level 16, State 1, Line 1
The server network address "TCP://MYSQL2K5:5023" 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.
Any ideas?
TIA, ChrisRWhat about the security configuration? Have you granted connect permissions
to the other servers' accounts to the database mirroring endpoints?
You should use
grant connect on endpoint::endpoint_mirroring to [domain\account]
Ben Nevarez, MCDBA, OCP
Database Administrator
"ChrisR" wrote:
> SQL2K5 sp1
> Instance names:
> Development\MySQL2K5
> Development\Subscriber
> Development\Witness
> Im trying to set up mirroring on 3 instances on my desktop and having some
> issues (not ideal I know, but it's what I've got to work with for now). Here
> is what I've done:
> --Create endpoint on principal instance and set recovery model
> CREATE ENDPOINT endpoint_mirroring
> STATE = STARTED
> AS TCP ( LISTENER_PORT = 5022 )
> FOR DATABASE_MIRRORING (ROLE=PARTNER);
> GO
> ALTER DATABASE AdventureWorks
> SET RECOVERY FULL;
> --Create endpoint on mirror instance
> CREATE ENDPOINT endpoint_mirroring
> STATE = STARTED
> AS TCP ( LISTENER_PORT = 5023 )
> FOR DATABASE_MIRRORING (ROLE=PARTNER);
> GO
> --Create endpoint on witness instance
> CREATE ENDPOINT endpoint_mirroring
> STATE = STARTED
> AS TCP ( LISTENER_PORT = 5024 )
> FOR DATABASE_MIRRORING (ROLE=WITNESS);
> GO
> --Backup principal database
> BACKUP DATABASE AdventureWorks
> TO DISK='C:\MirrorBackup\AWBackup.BAK'
> with init;
> GO
> --Restore mirror database
> RESTORE DATABASE AdventureWorks
> FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> WITH NORECOVERY,
> MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> GO
> --On the mirror server set the principal server
> ALTER DATABASE AdventureWorks
> SET PARTNER => 'TCP://MySQL2K5:5022'
> GO
> --On the principal server set the mirror server
> ALTER DATABASE AdventureWorks
> SET PARTNER = 'TCP://MySQL2K5:5023'
> GO
> That last step blows up with:
> Msg 1418, Level 16, State 1, Line 1
> The server network address "TCP://MYSQL2K5:5023" 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.
> Any ideas?
> TIA, ChrisR
>
>|||That didn't fix it. As an FYI all 3 instances are running under the same
domain account.
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> What about the security configuration? Have you granted connect
permissions
> to the other servers' accounts to the database mirroring endpoints?
> You should use
> grant connect on endpoint::endpoint_mirroring to [domain\account]
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "ChrisR" wrote:
> > SQL2K5 sp1
> >
> > Instance names:
> >
> > Development\MySQL2K5
> > Development\Subscriber
> > Development\Witness
> >
> > Im trying to set up mirroring on 3 instances on my desktop and having
some
> > issues (not ideal I know, but it's what I've got to work with for now).
Here
> > is what I've done:
> >
> > --Create endpoint on principal instance and set recovery model
> > CREATE ENDPOINT endpoint_mirroring
> > STATE = STARTED
> > AS TCP ( LISTENER_PORT = 5022 )
> > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > GO
> > ALTER DATABASE AdventureWorks
> > SET RECOVERY FULL;
> > --Create endpoint on mirror instance
> > CREATE ENDPOINT endpoint_mirroring
> > STATE = STARTED
> > AS TCP ( LISTENER_PORT = 5023 )
> > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > GO
> > --Create endpoint on witness instance
> > CREATE ENDPOINT endpoint_mirroring
> > STATE = STARTED
> > AS TCP ( LISTENER_PORT = 5024 )
> > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > GO
> > --Backup principal database
> > BACKUP DATABASE AdventureWorks
> > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > with init;
> > GO
> > --Restore mirror database
> > RESTORE DATABASE AdventureWorks
> > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > WITH NORECOVERY,
> > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > GO
> > --On the mirror server set the principal server
> > ALTER DATABASE AdventureWorks
> > SET PARTNER => > 'TCP://MySQL2K5:5022'
> > GO
> > --On the principal server set the mirror server
> > ALTER DATABASE AdventureWorks
> > SET PARTNER = 'TCP://MySQL2K5:5023'
> > GO
> >
> > That last step blows up with:
> > Msg 1418, Level 16, State 1, Line 1
> > The server network address "TCP://MYSQL2K5:5023" 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.
> >
> > Any ideas?
> > TIA, ChrisR
> >
> >
> >|||Let us try something else then.
Is MYSQL2K5 the name of your computer?
BOL recommends to use the fully qualified domain name. Try ipconfig /all and
look for host name and primary dns suffix.
Ben Nevarez, MCDBA, OCP
Database Administrator
"ChrisR" wrote:
> That didn't fix it. As an FYI all 3 instances are running under the same
> domain account.
> "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> >
> > What about the security configuration? Have you granted connect
> permissions
> > to the other servers' accounts to the database mirroring endpoints?
> >
> > You should use
> >
> > grant connect on endpoint::endpoint_mirroring to [domain\account]
> >
> > Ben Nevarez, MCDBA, OCP
> > Database Administrator
> >
> >
> > "ChrisR" wrote:
> >
> > > SQL2K5 sp1
> > >
> > > Instance names:
> > >
> > > Development\MySQL2K5
> > > Development\Subscriber
> > > Development\Witness
> > >
> > > Im trying to set up mirroring on 3 instances on my desktop and having
> some
> > > issues (not ideal I know, but it's what I've got to work with for now).
> Here
> > > is what I've done:
> > >
> > > --Create endpoint on principal instance and set recovery model
> > > CREATE ENDPOINT endpoint_mirroring
> > > STATE = STARTED
> > > AS TCP ( LISTENER_PORT = 5022 )
> > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > GO
> > > ALTER DATABASE AdventureWorks
> > > SET RECOVERY FULL;
> > > --Create endpoint on mirror instance
> > > CREATE ENDPOINT endpoint_mirroring
> > > STATE = STARTED
> > > AS TCP ( LISTENER_PORT = 5023 )
> > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > GO
> > > --Create endpoint on witness instance
> > > CREATE ENDPOINT endpoint_mirroring
> > > STATE = STARTED
> > > AS TCP ( LISTENER_PORT = 5024 )
> > > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > > GO
> > > --Backup principal database
> > > BACKUP DATABASE AdventureWorks
> > > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > > with init;
> > > GO
> > > --Restore mirror database
> > > RESTORE DATABASE AdventureWorks
> > > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > > WITH NORECOVERY,
> > > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > > GO
> > > --On the mirror server set the principal server
> > > ALTER DATABASE AdventureWorks
> > > SET PARTNER => > > 'TCP://MySQL2K5:5022'
> > > GO
> > > --On the principal server set the mirror server
> > > ALTER DATABASE AdventureWorks
> > > SET PARTNER = 'TCP://MySQL2K5:5023'
> > > GO
> > >
> > > That last step blows up with:
> > > Msg 1418, Level 16, State 1, Line 1
> > > The server network address "TCP://MYSQL2K5:5023" 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.
> > >
> > > Any ideas?
> > > TIA, ChrisR
> > >
> > >
> > >
>
>|||The box name is Development. The instance name is MySQL2K5. I have tried
development\mysql2k5 and many variations of it and get incorrect syntax
errors. I also tried the FQDN and still got the original error.
Thanks for all the help.
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:2F186919-F424-4707-9320-68474A3A59C1@.microsoft.com...
> Let us try something else then.
> Is MYSQL2K5 the name of your computer?
> BOL recommends to use the fully qualified domain name. Try ipconfig /all
and
> look for host name and primary dns suffix.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "ChrisR" wrote:
> > That didn't fix it. As an FYI all 3 instances are running under the same
> > domain account.
> >
> > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> > >
> > > What about the security configuration? Have you granted connect
> > permissions
> > > to the other servers' accounts to the database mirroring endpoints?
> > >
> > > You should use
> > >
> > > grant connect on endpoint::endpoint_mirroring to [domain\account]
> > >
> > > Ben Nevarez, MCDBA, OCP
> > > Database Administrator
> > >
> > >
> > > "ChrisR" wrote:
> > >
> > > > SQL2K5 sp1
> > > >
> > > > Instance names:
> > > >
> > > > Development\MySQL2K5
> > > > Development\Subscriber
> > > > Development\Witness
> > > >
> > > > Im trying to set up mirroring on 3 instances on my desktop and
having
> > some
> > > > issues (not ideal I know, but it's what I've got to work with for
now).
> > Here
> > > > is what I've done:
> > > >
> > > > --Create endpoint on principal instance and set recovery model
> > > > CREATE ENDPOINT endpoint_mirroring
> > > > STATE = STARTED
> > > > AS TCP ( LISTENER_PORT = 5022 )
> > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > GO
> > > > ALTER DATABASE AdventureWorks
> > > > SET RECOVERY FULL;
> > > > --Create endpoint on mirror instance
> > > > CREATE ENDPOINT endpoint_mirroring
> > > > STATE = STARTED
> > > > AS TCP ( LISTENER_PORT = 5023 )
> > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > GO
> > > > --Create endpoint on witness instance
> > > > CREATE ENDPOINT endpoint_mirroring
> > > > STATE = STARTED
> > > > AS TCP ( LISTENER_PORT = 5024 )
> > > > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > > > GO
> > > > --Backup principal database
> > > > BACKUP DATABASE AdventureWorks
> > > > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > with init;
> > > > GO
> > > > --Restore mirror database
> > > > RESTORE DATABASE AdventureWorks
> > > > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > WITH NORECOVERY,
> > > > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > > > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > > > GO
> > > > --On the mirror server set the principal server
> > > > ALTER DATABASE AdventureWorks
> > > > SET PARTNER => > > > 'TCP://MySQL2K5:5022'
> > > > GO
> > > > --On the principal server set the mirror server
> > > > ALTER DATABASE AdventureWorks
> > > > SET PARTNER = 'TCP://MySQL2K5:5023'
> > > > GO
> > > >
> > > > That last step blows up with:
> > > > Msg 1418, Level 16, State 1, Line 1
> > > > The server network address "TCP://MYSQL2K5:5023" 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.
> > > >
> > > > Any ideas?
> > > > TIA, ChrisR
> > > >
> > > >
> > > >
> >
> >
> >|||On
ALTER DATABASE AdventureWorks
> > > > > SET PARTNER => > > > > 'TCP://MySQL2K5:5022'
you need to specify your host name and domain name NOT the SQL Server
instance name. For example, development.yourdomain.com.
Run ipconfig /all and look into host name and primary dns suffix.
Ben Nevarez, MCDBA, OCP
Database Administrator
"ChrisR" wrote:
> The box name is Development. The instance name is MySQL2K5. I have tried
> development\mysql2k5 and many variations of it and get incorrect syntax
> errors. I also tried the FQDN and still got the original error.
> Thanks for all the help.
> "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> news:2F186919-F424-4707-9320-68474A3A59C1@.microsoft.com...
> >
> > Let us try something else then.
> >
> > Is MYSQL2K5 the name of your computer?
> >
> > BOL recommends to use the fully qualified domain name. Try ipconfig /all
> and
> > look for host name and primary dns suffix.
> >
> > Ben Nevarez, MCDBA, OCP
> > Database Administrator
> >
> >
> > "ChrisR" wrote:
> >
> > > That didn't fix it. As an FYI all 3 instances are running under the same
> > > domain account.
> > >
> > > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > > news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> > > >
> > > > What about the security configuration? Have you granted connect
> > > permissions
> > > > to the other servers' accounts to the database mirroring endpoints?
> > > >
> > > > You should use
> > > >
> > > > grant connect on endpoint::endpoint_mirroring to [domain\account]
> > > >
> > > > Ben Nevarez, MCDBA, OCP
> > > > Database Administrator
> > > >
> > > >
> > > > "ChrisR" wrote:
> > > >
> > > > > SQL2K5 sp1
> > > > >
> > > > > Instance names:
> > > > >
> > > > > Development\MySQL2K5
> > > > > Development\Subscriber
> > > > > Development\Witness
> > > > >
> > > > > Im trying to set up mirroring on 3 instances on my desktop and
> having
> > > some
> > > > > issues (not ideal I know, but it's what I've got to work with for
> now).
> > > Here
> > > > > is what I've done:
> > > > >
> > > > > --Create endpoint on principal instance and set recovery model
> > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > STATE = STARTED
> > > > > AS TCP ( LISTENER_PORT = 5022 )
> > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > GO
> > > > > ALTER DATABASE AdventureWorks
> > > > > SET RECOVERY FULL;
> > > > > --Create endpoint on mirror instance
> > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > STATE = STARTED
> > > > > AS TCP ( LISTENER_PORT = 5023 )
> > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > GO
> > > > > --Create endpoint on witness instance
> > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > STATE = STARTED
> > > > > AS TCP ( LISTENER_PORT = 5024 )
> > > > > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > > > > GO
> > > > > --Backup principal database
> > > > > BACKUP DATABASE AdventureWorks
> > > > > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > with init;
> > > > > GO
> > > > > --Restore mirror database
> > > > > RESTORE DATABASE AdventureWorks
> > > > > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > WITH NORECOVERY,
> > > > > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > > > > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > > > > GO
> > > > > --On the mirror server set the principal server
> > > > > ALTER DATABASE AdventureWorks
> > > > > SET PARTNER => > > > > 'TCP://MySQL2K5:5022'
> > > > > GO
> > > > > --On the principal server set the mirror server
> > > > > ALTER DATABASE AdventureWorks
> > > > > SET PARTNER = 'TCP://MySQL2K5:5023'
> > > > > GO
> > > > >
> > > > > That last step blows up with:
> > > > > Msg 1418, Level 16, State 1, Line 1
> > > > > The server network address "TCP://MYSQL2K5:5023" 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.
> > > > >
> > > > > Any ideas?
> > > > > TIA, ChrisR
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||Doh! I thought it was instance name.
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:5B6FD5FC-E687-4B1F-A01B-57C0C265D5DE@.microsoft.com...
> On
> ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER => > > > > > 'TCP://MySQL2K5:5022'
> you need to specify your host name and domain name NOT the SQL Server
> instance name. For example, development.yourdomain.com.
> Run ipconfig /all and look into host name and primary dns suffix.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "ChrisR" wrote:
> > The box name is Development. The instance name is MySQL2K5. I have tried
> > development\mysql2k5 and many variations of it and get incorrect syntax
> > errors. I also tried the FQDN and still got the original error.
> >
> > Thanks for all the help.
> >
> > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > news:2F186919-F424-4707-9320-68474A3A59C1@.microsoft.com...
> > >
> > > Let us try something else then.
> > >
> > > Is MYSQL2K5 the name of your computer?
> > >
> > > BOL recommends to use the fully qualified domain name. Try ipconfig
/all
> > and
> > > look for host name and primary dns suffix.
> > >
> > > Ben Nevarez, MCDBA, OCP
> > > Database Administrator
> > >
> > >
> > > "ChrisR" wrote:
> > >
> > > > That didn't fix it. As an FYI all 3 instances are running under the
same
> > > > domain account.
> > > >
> > > > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > > > news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> > > > >
> > > > > What about the security configuration? Have you granted connect
> > > > permissions
> > > > > to the other servers' accounts to the database mirroring
endpoints?
> > > > >
> > > > > You should use
> > > > >
> > > > > grant connect on endpoint::endpoint_mirroring to [domain\account]
> > > > >
> > > > > Ben Nevarez, MCDBA, OCP
> > > > > Database Administrator
> > > > >
> > > > >
> > > > > "ChrisR" wrote:
> > > > >
> > > > > > SQL2K5 sp1
> > > > > >
> > > > > > Instance names:
> > > > > >
> > > > > > Development\MySQL2K5
> > > > > > Development\Subscriber
> > > > > > Development\Witness
> > > > > >
> > > > > > Im trying to set up mirroring on 3 instances on my desktop and
> > having
> > > > some
> > > > > > issues (not ideal I know, but it's what I've got to work with
for
> > now).
> > > > Here
> > > > > > is what I've done:
> > > > > >
> > > > > > --Create endpoint on principal instance and set recovery model
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5022 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > > GO
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET RECOVERY FULL;
> > > > > > --Create endpoint on mirror instance
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5023 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > > GO
> > > > > > --Create endpoint on witness instance
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5024 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > > > > > GO
> > > > > > --Backup principal database
> > > > > > BACKUP DATABASE AdventureWorks
> > > > > > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > > with init;
> > > > > > GO
> > > > > > --Restore mirror database
> > > > > > RESTORE DATABASE AdventureWorks
> > > > > > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > > WITH NORECOVERY,
> > > > > > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > > > > > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > > > > > GO
> > > > > > --On the mirror server set the principal server
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER => > > > > > 'TCP://MySQL2K5:5022'
> > > > > > GO
> > > > > > --On the principal server set the mirror server
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER = 'TCP://MySQL2K5:5023'
> > > > > > GO
> > > > > >
> > > > > > That last step blows up with:
> > > > > > Msg 1418, Level 16, State 1, Line 1
> > > > > > The server network address "TCP://MYSQL2K5:5023" 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.
> > > > > >
> > > > > > Any ideas?
> > > > > > TIA, ChrisR
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||Thanks a lot!
"Ben Nevarez" <bnevarez@.sjm.com> wrote in message
news:5B6FD5FC-E687-4B1F-A01B-57C0C265D5DE@.microsoft.com...
> On
> ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER => > > > > > 'TCP://MySQL2K5:5022'
> you need to specify your host name and domain name NOT the SQL Server
> instance name. For example, development.yourdomain.com.
> Run ipconfig /all and look into host name and primary dns suffix.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "ChrisR" wrote:
> > The box name is Development. The instance name is MySQL2K5. I have tried
> > development\mysql2k5 and many variations of it and get incorrect syntax
> > errors. I also tried the FQDN and still got the original error.
> >
> > Thanks for all the help.
> >
> > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > news:2F186919-F424-4707-9320-68474A3A59C1@.microsoft.com...
> > >
> > > Let us try something else then.
> > >
> > > Is MYSQL2K5 the name of your computer?
> > >
> > > BOL recommends to use the fully qualified domain name. Try ipconfig
/all
> > and
> > > look for host name and primary dns suffix.
> > >
> > > Ben Nevarez, MCDBA, OCP
> > > Database Administrator
> > >
> > >
> > > "ChrisR" wrote:
> > >
> > > > That didn't fix it. As an FYI all 3 instances are running under the
same
> > > > domain account.
> > > >
> > > > "Ben Nevarez" <bnevarez@.sjm.com> wrote in message
> > > > news:D8493E83-C7A3-4A76-9302-7FA2C77EE3EF@.microsoft.com...
> > > > >
> > > > > What about the security configuration? Have you granted connect
> > > > permissions
> > > > > to the other servers' accounts to the database mirroring
endpoints?
> > > > >
> > > > > You should use
> > > > >
> > > > > grant connect on endpoint::endpoint_mirroring to [domain\account]
> > > > >
> > > > > Ben Nevarez, MCDBA, OCP
> > > > > Database Administrator
> > > > >
> > > > >
> > > > > "ChrisR" wrote:
> > > > >
> > > > > > SQL2K5 sp1
> > > > > >
> > > > > > Instance names:
> > > > > >
> > > > > > Development\MySQL2K5
> > > > > > Development\Subscriber
> > > > > > Development\Witness
> > > > > >
> > > > > > Im trying to set up mirroring on 3 instances on my desktop and
> > having
> > > > some
> > > > > > issues (not ideal I know, but it's what I've got to work with
for
> > now).
> > > > Here
> > > > > > is what I've done:
> > > > > >
> > > > > > --Create endpoint on principal instance and set recovery model
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5022 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > > GO
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET RECOVERY FULL;
> > > > > > --Create endpoint on mirror instance
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5023 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=PARTNER);
> > > > > > GO
> > > > > > --Create endpoint on witness instance
> > > > > > CREATE ENDPOINT endpoint_mirroring
> > > > > > STATE = STARTED
> > > > > > AS TCP ( LISTENER_PORT = 5024 )
> > > > > > FOR DATABASE_MIRRORING (ROLE=WITNESS);
> > > > > > GO
> > > > > > --Backup principal database
> > > > > > BACKUP DATABASE AdventureWorks
> > > > > > TO DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > > with init;
> > > > > > GO
> > > > > > --Restore mirror database
> > > > > > RESTORE DATABASE AdventureWorks
> > > > > > FROM DISK='C:\MirrorBackup\AWBackup.BAK'
> > > > > > WITH NORECOVERY,
> > > > > > MOVE 'AdventureWorks_Data' TO 'C:\Program Files\Microsoft SQL
> > > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Data.mdf',
> > > > > > MOVE 'AdventureWorks_Log' TO 'C:\Program Files\Microsoft SQL
> > > > > > Server\MSSQL.2\MSSQL\DATA\AdventureWorks_Log.ldf';
> > > > > > GO
> > > > > > --On the mirror server set the principal server
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER => > > > > > 'TCP://MySQL2K5:5022'
> > > > > > GO
> > > > > > --On the principal server set the mirror server
> > > > > > ALTER DATABASE AdventureWorks
> > > > > > SET PARTNER = 'TCP://MySQL2K5:5023'
> > > > > > GO
> > > > > >
> > > > > > That last step blows up with:
> > > > > > Msg 1418, Level 16, State 1, Line 1
> > > > > > The server network address "TCP://MYSQL2K5:5023" 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.
> > > > > >
> > > > > > Any ideas?
> > > > > > TIA, ChrisR
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >
Monday, March 12, 2012
Problem:fail to invoke remote RPC method
I have two xp sp2 machines(one desktop with sql server running, the other is
a virtual pc, on the same domain), I'm trying to connect between the two
using the dtcping.exe tool from ms
the virtual pc has vs2005 etc installed and I can't get it to run a
distributed transaction on the sql server machine, both machines have the sp2
firewall disabled.
the rpc services are running, msdtc service are running,
on the virtual pc I get the following
Firewall Port Settings:
Port:5000-5015
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
08-03, 12:09:03.756-->Start DTC connection test
Name Resolution:
Gilbert-->10.0.4.22-->Gilbert
08-03, 12:09:03.776-->Start RPC test (PERTH-->Gilbert)
Problem:fail to invoke remote RPC method
Error(0x6BA) at dtcping.cpp @.289
-->RPC pinging exception
-->1722(The RPC server is unavailable.)
RPC test failed
on the desktop sql server machine I get this
Firewall Port Settings:
Port:5000-5015
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
08-03, 12:08:50.353-->Start DTC connection test
Name Resolution:
Perth-->10.0.4.23-->Perth
08-03, 12:08:50.368-->Start RPC test (GILBERT-->Perth)
Problem:fail to invoke remote RPC method
Error(0x5) at dtcping.cpp @.289
-->RPC pinging exception
-->5(Access is denied.)
RPC test failed
the msdtc service has been set to use my domain account and all the options
have been enabled, network access, inbound, outbound etc.
I have set up the msdtc to use ports 5000-5015
any ideas out there?
to get this poc working
Try turning off Norton internet worm protection...
Stuart
"SP" wrote:
> I have two xp sp2 machines(one desktop with sql server running, the other is
> a virtual pc, on the same domain), I'm trying to connect between the two
> using the dtcping.exe tool from ms
> the virtual pc has vs2005 etc installed and I can't get it to run a
> distributed transaction on the sql server machine, both machines have the sp2
> firewall disabled.
> the rpc services are running, msdtc service are running,
> on the virtual pc I get the following
> Firewall Port Settings:
> Port:5000-5015
> RPC server is ready
> ++++++++++++Validating Remote Computer Name++++++++++++
> 08-03, 12:09:03.756-->Start DTC connection test
> Name Resolution:
> Gilbert-->10.0.4.22-->Gilbert
> 08-03, 12:09:03.776-->Start RPC test (PERTH-->Gilbert)
> Problem:fail to invoke remote RPC method
> Error(0x6BA) at dtcping.cpp @.289
> -->RPC pinging exception
> -->1722(The RPC server is unavailable.)
> RPC test failed
> on the desktop sql server machine I get this
> Firewall Port Settings:
> Port:5000-5015
> RPC server is ready
> ++++++++++++Validating Remote Computer Name++++++++++++
> 08-03, 12:08:50.353-->Start DTC connection test
> Name Resolution:
> Perth-->10.0.4.23-->Perth
> 08-03, 12:08:50.368-->Start RPC test (GILBERT-->Perth)
> Problem:fail to invoke remote RPC method
> Error(0x5) at dtcping.cpp @.289
> -->RPC pinging exception
> -->5(Access is denied.)
> RPC test failed
> the msdtc service has been set to use my domain account and all the options
> have been enabled, network access, inbound, outbound etc.
> I have set up the msdtc to use ports 5000-5015
> any ideas out there?
> to get this poc working
>
|||Thanks Stuart, you are the man!
"Stuart" wrote:
[vbcol=seagreen]
> Try turning off Norton internet worm protection...
> Stuart
> "SP" wrote:
a virtual pc, on the same domain), I'm trying to connect between the two
using the dtcping.exe tool from ms
the virtual pc has vs2005 etc installed and I can't get it to run a
distributed transaction on the sql server machine, both machines have the sp2
firewall disabled.
the rpc services are running, msdtc service are running,
on the virtual pc I get the following
Firewall Port Settings:
Port:5000-5015
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
08-03, 12:09:03.756-->Start DTC connection test
Name Resolution:
Gilbert-->10.0.4.22-->Gilbert
08-03, 12:09:03.776-->Start RPC test (PERTH-->Gilbert)
Problem:fail to invoke remote RPC method
Error(0x6BA) at dtcping.cpp @.289
-->RPC pinging exception
-->1722(The RPC server is unavailable.)
RPC test failed
on the desktop sql server machine I get this
Firewall Port Settings:
Port:5000-5015
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
08-03, 12:08:50.353-->Start DTC connection test
Name Resolution:
Perth-->10.0.4.23-->Perth
08-03, 12:08:50.368-->Start RPC test (GILBERT-->Perth)
Problem:fail to invoke remote RPC method
Error(0x5) at dtcping.cpp @.289
-->RPC pinging exception
-->5(Access is denied.)
RPC test failed
the msdtc service has been set to use my domain account and all the options
have been enabled, network access, inbound, outbound etc.
I have set up the msdtc to use ports 5000-5015
any ideas out there?
to get this poc working
Try turning off Norton internet worm protection...
Stuart
"SP" wrote:
> I have two xp sp2 machines(one desktop with sql server running, the other is
> a virtual pc, on the same domain), I'm trying to connect between the two
> using the dtcping.exe tool from ms
> the virtual pc has vs2005 etc installed and I can't get it to run a
> distributed transaction on the sql server machine, both machines have the sp2
> firewall disabled.
> the rpc services are running, msdtc service are running,
> on the virtual pc I get the following
> Firewall Port Settings:
> Port:5000-5015
> RPC server is ready
> ++++++++++++Validating Remote Computer Name++++++++++++
> 08-03, 12:09:03.756-->Start DTC connection test
> Name Resolution:
> Gilbert-->10.0.4.22-->Gilbert
> 08-03, 12:09:03.776-->Start RPC test (PERTH-->Gilbert)
> Problem:fail to invoke remote RPC method
> Error(0x6BA) at dtcping.cpp @.289
> -->RPC pinging exception
> -->1722(The RPC server is unavailable.)
> RPC test failed
> on the desktop sql server machine I get this
> Firewall Port Settings:
> Port:5000-5015
> RPC server is ready
> ++++++++++++Validating Remote Computer Name++++++++++++
> 08-03, 12:08:50.353-->Start DTC connection test
> Name Resolution:
> Perth-->10.0.4.23-->Perth
> 08-03, 12:08:50.368-->Start RPC test (GILBERT-->Perth)
> Problem:fail to invoke remote RPC method
> Error(0x5) at dtcping.cpp @.289
> -->RPC pinging exception
> -->5(Access is denied.)
> RPC test failed
> the msdtc service has been set to use my domain account and all the options
> have been enabled, network access, inbound, outbound etc.
> I have set up the msdtc to use ports 5000-5015
> any ideas out there?
> to get this poc working
>
|||Thanks Stuart, you are the man!
"Stuart" wrote:
[vbcol=seagreen]
> Try turning off Norton internet worm protection...
> Stuart
> "SP" wrote:
Problem:fail to invoke remote RPC method
I have two xp sp2 machines(one desktop with sql server running, the other is
a virtual pc, on the same domain), I'm trying to connect between the two
using the dtcping.exe tool from ms
the virtual pc has vs2005 etc installed and I can't get it to run a
distributed transaction on the sql server machine, both machines have the sp
2
firewall disabled.
the rpc services are running, msdtc service are running,
on the virtual pc I get the following
Firewall Port Settings:
Port:5000-5015
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
08-03, 12:09:03.756-->Start DTC connection test
Name Resolution:
Gilbert-->10.0.4.22-->Gilbert
08-03, 12:09:03.776-->Start RPC test (PERTH-->Gilbert)
Problem:fail to invoke remote RPC method
Error(0x6BA) at dtcping.cpp @.289
-->RPC pinging exception
-->1722(The RPC server is unavailable.)
RPC test failed
on the desktop sql server machine I get this
Firewall Port Settings:
Port:5000-5015
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
08-03, 12:08:50.353-->Start DTC connection test
Name Resolution:
Perth-->10.0.4.23-->Perth
08-03, 12:08:50.368-->Start RPC test (GILBERT-->Perth)
Problem:fail to invoke remote RPC method
Error(0x5) at dtcping.cpp @.289
-->RPC pinging exception
-->5(Access is denied.)
RPC test failed
the msdtc service has been set to use my domain account and all the options
have been enabled, network access, inbound, outbound etc.
I have set up the msdtc to use ports 5000-5015
any ideas out there?
to get this poc workingTry turning off Norton internet worm protection...
Stuart
"SP" wrote:
> I have two xp sp2 machines(one desktop with sql server running, the other
is
> a virtual pc, on the same domain), I'm trying to connect between the two
> using the dtcping.exe tool from ms
> the virtual pc has vs2005 etc installed and I can't get it to run a
> distributed transaction on the sql server machine, both machines have the
sp2
> firewall disabled.
> the rpc services are running, msdtc service are running,
> on the virtual pc I get the following
> Firewall Port Settings:
> Port:5000-5015
> RPC server is ready
> ++++++++++++Validating Remote Computer Name++++++++++++
> 08-03, 12:09:03.756-->Start DTC connection test
> Name Resolution:
> Gilbert-->10.0.4.22-->Gilbert
> 08-03, 12:09:03.776-->Start RPC test (PERTH-->Gilbert)
> Problem:fail to invoke remote RPC method
> Error(0x6BA) at dtcping.cpp @.289
> -->RPC pinging exception
> -->1722(The RPC server is unavailable.)
> RPC test failed
> on the desktop sql server machine I get this
> Firewall Port Settings:
> Port:5000-5015
> RPC server is ready
> ++++++++++++Validating Remote Computer Name++++++++++++
> 08-03, 12:08:50.353-->Start DTC connection test
> Name Resolution:
> Perth-->10.0.4.23-->Perth
> 08-03, 12:08:50.368-->Start RPC test (GILBERT-->Perth)
> Problem:fail to invoke remote RPC method
> Error(0x5) at dtcping.cpp @.289
> -->RPC pinging exception
> -->5(Access is denied.)
> RPC test failed
> the msdtc service has been set to use my domain account and all the option
s
> have been enabled, network access, inbound, outbound etc.
> I have set up the msdtc to use ports 5000-5015
> any ideas out there?
> to get this poc working
>|||Thanks Stuart, you are the man!
"Stuart" wrote:
[vbcol=seagreen]
> Try turning off Norton internet worm protection...
> Stuart
> "SP" wrote:
>
a virtual pc, on the same domain), I'm trying to connect between the two
using the dtcping.exe tool from ms
the virtual pc has vs2005 etc installed and I can't get it to run a
distributed transaction on the sql server machine, both machines have the sp
2
firewall disabled.
the rpc services are running, msdtc service are running,
on the virtual pc I get the following
Firewall Port Settings:
Port:5000-5015
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
08-03, 12:09:03.756-->Start DTC connection test
Name Resolution:
Gilbert-->10.0.4.22-->Gilbert
08-03, 12:09:03.776-->Start RPC test (PERTH-->Gilbert)
Problem:fail to invoke remote RPC method
Error(0x6BA) at dtcping.cpp @.289
-->RPC pinging exception
-->1722(The RPC server is unavailable.)
RPC test failed
on the desktop sql server machine I get this
Firewall Port Settings:
Port:5000-5015
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
08-03, 12:08:50.353-->Start DTC connection test
Name Resolution:
Perth-->10.0.4.23-->Perth
08-03, 12:08:50.368-->Start RPC test (GILBERT-->Perth)
Problem:fail to invoke remote RPC method
Error(0x5) at dtcping.cpp @.289
-->RPC pinging exception
-->5(Access is denied.)
RPC test failed
the msdtc service has been set to use my domain account and all the options
have been enabled, network access, inbound, outbound etc.
I have set up the msdtc to use ports 5000-5015
any ideas out there?
to get this poc working
Try turning off Norton internet worm protection... Stuart
"SP" wrote:
> I have two xp sp2 machines(one desktop with sql server running, the other
is
> a virtual pc, on the same domain), I'm trying to connect between the two
> using the dtcping.exe tool from ms
> the virtual pc has vs2005 etc installed and I can't get it to run a
> distributed transaction on the sql server machine, both machines have the
sp2
> firewall disabled.
> the rpc services are running, msdtc service are running,
> on the virtual pc I get the following
> Firewall Port Settings:
> Port:5000-5015
> RPC server is ready
> ++++++++++++Validating Remote Computer Name++++++++++++
> 08-03, 12:09:03.756-->Start DTC connection test
> Name Resolution:
> Gilbert-->10.0.4.22-->Gilbert
> 08-03, 12:09:03.776-->Start RPC test (PERTH-->Gilbert)
> Problem:fail to invoke remote RPC method
> Error(0x6BA) at dtcping.cpp @.289
> -->RPC pinging exception
> -->1722(The RPC server is unavailable.)
> RPC test failed
> on the desktop sql server machine I get this
> Firewall Port Settings:
> Port:5000-5015
> RPC server is ready
> ++++++++++++Validating Remote Computer Name++++++++++++
> 08-03, 12:08:50.353-->Start DTC connection test
> Name Resolution:
> Perth-->10.0.4.23-->Perth
> 08-03, 12:08:50.368-->Start RPC test (GILBERT-->Perth)
> Problem:fail to invoke remote RPC method
> Error(0x5) at dtcping.cpp @.289
> -->RPC pinging exception
> -->5(Access is denied.)
> RPC test failed
> the msdtc service has been set to use my domain account and all the option
s
> have been enabled, network access, inbound, outbound etc.
> I have set up the msdtc to use ports 5000-5015
> any ideas out there?
> to get this poc working
>|||Thanks Stuart, you are the man!
"Stuart" wrote:
[vbcol=seagreen]
> Try turning off Norton internet worm protection...
> Stuart
> "SP" wrote:
>
Subscribe to:
Posts (Atom)