Showing posts with label restored. Show all posts
Showing posts with label restored. Show all posts

Tuesday, March 20, 2012

Problems with mirroring

I have the three server ready to go. The prinicpal is set, the mirror
is set. I have a back up of the prinicipal restored on the mirror and
then I have a third server that acts as the witness. The problem is I
am getting an error message. I am getting this error message:
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\
TITLE: Database Properties
--
An error occurred while starting mirroring.
ADDITIONAL INFORMATION:
Alter failed for Database 'SQLServer'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?Prod...se&LinkId=20476
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
The server network address "TCP://xxx.xxx.org:5022" 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. (Microsoft SQL
Server, Error: 1418)
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\
Any ideas would most helpful.
-ThanasCan you show your scripts that you used to create your mirrors?
Did you open the ports on your firewall?
Thanas wrote:
> I have the three server ready to go. The prinicpal is set, the mirror
> is set. I have a back up of the prinicipal restored on the mirror and
> then I have a third server that acts as the witness. The problem is I
> am getting an error message. I am getting this error message:
> \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\
> TITLE: Database Properties
> --
> An error occurred while starting mirroring.
> --
> ADDITIONAL INFORMATION:
> Alter failed for Database 'SQLServer'. (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...se&LinkId=20476
> --
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The server network address "TCP://xxx.xxx.org:5022" 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. (Microsoft SQL
> Server, Error: 1418)
> \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
>
> Any ideas would most helpful.
> -Thanas|||Used Management Studio to generate the mirror. No firewall up, all
internal. There is not even a windows firewall.
PSPDBA wrote:[vbcol=seagreen]
> Can you show your scripts that you used to create your mirrors?
> Did you open the ports on your firewall?
>
> Thanas wrote:|||Try using TCP://ServerName:5022 rather than the full path.
Thanas wrote:[vbcol=seagreen]
> Used Management Studio to generate the mirror. No firewall up, all
> internal. There is not even a windows firewall.
> PSPDBA wrote:|||Read step 2 in the section "Troubleshooting" in the following document.
http://www.microsoft.com/technet/pr...5/dbmirror.mspx
If your services are running as LocalSystem, it will not work. Try
changing to an account with the appropriate privileges. I changed to a
domian account and my problem went away.
Good Luck
Jamie|||Still having trouble. Not really sure why anymore. here is the error
message that I got. Of course I have "x" out my server information for
obvious reason ...
The witness is a SQL Server Express. It is up to date as far as
updates goes.
Thanks for your help and patience everyone.
-Thanas
TITLE: Database Properties
--
An error occurred while starting mirroring.
ADDITIONAL INFORMATION:
Alter failed for Database 'xxxxSQLServerDev'.
(Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?Prod...se&LinkId=20476
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
The ALTER DATABASE command could not be sent to the remote server
instance 'TCP://xxx.xxx.org:5022'. The database mirroring configuration
was not changed. Verify that the server is connected, and try again.
(Microsoft SQL Server, Error: 1456)
For help, click:
http://go.microsoft.com/fwlink?Prod...56&LinkId=20476
BUTTONS:
OK
--
jamie@.encompassgroup.ca wrote:
> Read step 2 in the section "Troubleshooting" in the following document.
> http://www.microsoft.com/technet/pr...5/dbmirror.mspx
> If your services are running as LocalSystem, it will not work. Try
> changing to an account with the appropriate privileges. I changed to a
> domian account and my problem went away.
> Good Luck
> Jamie

Problems with mirroring

I have the three server ready to go. The prinicpal is set, the mirror
is set. I have a back up of the prinicipal restored on the mirror and
then I have a third server that acts as the witness. The problem is I
am getting an error message. I am getting this error message:
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
TITLE: Database Properties
--
An error occurred while starting mirroring.
--
ADDITIONAL INFORMATION:
Alter failed for Database 'SQLServer'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Alter+Database&LinkId=20476
--
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
--
The server network address "TCP://xxx.xxx.org:5022" 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. (Microsoft SQL
Server, Error: 1418)
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Any ideas would most helpful.
-ThanasCan you show your scripts that you used to create your mirrors?
Did you open the ports on your firewall?
Thanas wrote:
> I have the three server ready to go. The prinicpal is set, the mirror
> is set. I have a back up of the prinicipal restored on the mirror and
> then I have a third server that acts as the witness. The problem is I
> am getting an error message. I am getting this error message:
> \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
> TITLE: Database Properties
> --
> An error occurred while starting mirroring.
> --
> ADDITIONAL INFORMATION:
> Alter failed for Database 'SQLServer'. (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Alter+Database&LinkId=20476
> --
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The server network address "TCP://xxx.xxx.org:5022" 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. (Microsoft SQL
> Server, Error: 1418)
> \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
>
> Any ideas would most helpful.
> -Thanas|||Used Management Studio to generate the mirror. No firewall up, all
internal. There is not even a windows firewall.
PSPDBA wrote:
> Can you show your scripts that you used to create your mirrors?
> Did you open the ports on your firewall?
>
> Thanas wrote:
> > I have the three server ready to go. The prinicpal is set, the mirror
> > is set. I have a back up of the prinicipal restored on the mirror and
> > then I have a third server that acts as the witness. The problem is I
> > am getting an error message. I am getting this error message:
> >
> > \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
> > TITLE: Database Properties
> > --
> >
> > An error occurred while starting mirroring.
> >
> > --
> > ADDITIONAL INFORMATION:
> >
> > Alter failed for Database 'SQLServer'. (Microsoft.SqlServer.Smo)
> >
> > For help, click:
> > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Alter+Database&LinkId=20476
> >
> > --
> >
> > An exception occurred while executing a Transact-SQL statement or
> > batch. (Microsoft.SqlServer.ConnectionInfo)
> >
> > --
> >
> > The server network address "TCP://xxx.xxx.org:5022" 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. (Microsoft SQL
> > Server, Error: 1418)
> > \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
> >
> >
> > Any ideas would most helpful.
> > -Thanas|||Try using TCP://ServerName:5022 rather than the full path.
Thanas wrote:
> Used Management Studio to generate the mirror. No firewall up, all
> internal. There is not even a windows firewall.
> PSPDBA wrote:
> > Can you show your scripts that you used to create your mirrors?
> >
> > Did you open the ports on your firewall?
> >
> >
> > Thanas wrote:
> > > I have the three server ready to go. The prinicpal is set, the mirror
> > > is set. I have a back up of the prinicipal restored on the mirror and
> > > then I have a third server that acts as the witness. The problem is I
> > > am getting an error message. I am getting this error message:
> > >
> > > \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
> > > TITLE: Database Properties
> > > --
> > >
> > > An error occurred while starting mirroring.
> > >
> > > --
> > > ADDITIONAL INFORMATION:
> > >
> > > Alter failed for Database 'SQLServer'. (Microsoft.SqlServer.Smo)
> > >
> > > For help, click:
> > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Alter+Database&LinkId=20476
> > >
> > > --
> > >
> > > An exception occurred while executing a Transact-SQL statement or
> > > batch. (Microsoft.SqlServer.ConnectionInfo)
> > >
> > > --
> > >
> > > The server network address "TCP://xxx.xxx.org:5022" 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. (Microsoft SQL
> > > Server, Error: 1418)
> > > \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
> > >
> > >
> > > Any ideas would most helpful.
> > > -Thanas|||Read step 2 in the section "Troubleshooting" in the following document.
http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
If your services are running as LocalSystem, it will not work. Try
changing to an account with the appropriate privileges. I changed to a
domian account and my problem went away.
Good Luck
Jamie|||Still having trouble. Not really sure why anymore. here is the error
message that I got. Of course I have "x" out my server information for
obvious reason :)...
The witness is a SQL Server Express. It is up to date as far as
updates goes.
Thanks for your help and patience everyone.
-Thanas
TITLE: Database Properties
--
An error occurred while starting mirroring.
--
ADDITIONAL INFORMATION:
Alter failed for Database 'xxxxSQLServerDev'.
(Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Alter+Database&LinkId=20476
--
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
--
The ALTER DATABASE command could not be sent to the remote server
instance 'TCP://xxx.xxx.org:5022'. The database mirroring configuration
was not changed. Verify that the server is connected, and try again.
(Microsoft SQL Server, Error: 1456)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=1456&LinkId=20476
--
BUTTONS:
OK
--
jamie@.encompassgroup.ca wrote:
> Read step 2 in the section "Troubleshooting" in the following document.
> http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
> If your services are running as LocalSystem, it will not work. Try
> changing to an account with the appropriate privileges. I changed to a
> domian account and my problem went away.
> Good Luck
> Jamie

Friday, March 9, 2012

Problems with debugging remotely SQLCLR stored procedures?

Hello,

my username is se\levalencia, I had before the database on my machine, but as now we have a server I backed up the database and restored on the server, it seems that it has the sames logins and security users,

Its strange because the user dbo is assigned the user se\levalencia on the server, and I cant alter the user dbo.

The user dbo should be the login sa? I am in big trouble with this, beacuase I cant debug my sql clr stored procedure.

T-Sql execution ended without debugging. You may have not have sufficient permissions to debug.

I am using a connection with windows authentication, so it means that its sending tha tokes as se\levalencia to the server.

Please feel free to ask for more information about it. Thanks

More strange yet, I just changed the connection and put SA as the user which executes the sql clr stored procedure, I got the same problem, its supposed to be a super user.

|||

You would need to add se\levalencia as a member of sysadmin role on the server. For debugging T-SQL as well as SQLCLR the debugger needs to run under an account that is a member of sysadmin role on SQL Server.

Thanks,

-Vineet.

Problems with debugging remotely SQLCLR stored procedures?

Hello,

my username is se\levalencia, I had before the database on my machine, but as now we have a server I backed up the database and restored on the server, it seems that it has the sames logins and security users,

Its strange because the user dbo is assigned the user se\levalencia on the server, and I cant alter the user dbo.

The user dbo should be the login sa? I am in big trouble with this, beacuase I cant debug my sql clr stored procedure.

T-Sql execution ended without debugging. You may have not have sufficient permissions to debug.

I am using a connection with windows authentication, so it means that its sending tha tokes as se\levalencia to the server.

Please feel free to ask for more information about it. Thanks

More strange yet, I just changed the connection and put SA as the user which executes the sql clr stored procedure, I got the same problem, its supposed to be a super user.

|||

You would need to add se\levalencia as a member of sysadmin role on the server. For debugging T-SQL as well as SQLCLR the debugger needs to run under an account that is a member of sysadmin role on SQL Server.

Thanks,

-Vineet.