I am creating a job in master server where in one step, it creates
stored procedure in target server. The proc text is exceeding the
limit to directly paste in job scheduler. What is the best way to push
procedure to target servers?
You can either split the sproc into smaller ones to bypass the text size
limit, or save the proc in a text file and use osql in the job to call the
input file.
"tram" <tram_e@.hotmail.com> wrote in message
news:26ee1067.0407130929.62a38b86@.posting.google.c om...
> I am creating a job in master server where in one step, it creates
> stored procedure in target server. The proc text is exceeding the
> limit to directly paste in job scheduler. What is the best way to push
> procedure to target servers?
|||Thanks for the reply. OSQL could be used, but I need to copy the sql
to every server. It doesn't take if it is located at central server.
Any ideas?
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:<eJ6GcnQaEHA.3664@.TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
> You can either split the sproc into smaller ones to bypass the text size
> limit, or save the proc in a text file and use osql in the job to call the
> input file.
>
> "tram" <tram_e@.hotmail.com> wrote in message
> news:26ee1067.0407130929.62a38b86@.posting.google.c om...
|||Thanks for the reply. OSQL could be used, but I need to copy the sql
to every server. It doesn't take if it is located at central server.
Any ideas?
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:<eJ6GcnQaEHA.3664@.TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
> You can either split the sproc into smaller ones to bypass the text size
> limit, or save the proc in a text file and use osql in the job to call the
> input file.
>
> "tram" <tram_e@.hotmail.com> wrote in message
> news:26ee1067.0407130929.62a38b86@.posting.google.c om...
|||Thanks for the reply. OSQL could be used, but I need to copy the sql
to every server. It doesn't take if it is located at central server.
Any ideas?
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:<eJ6GcnQaEHA.3664@.TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
> You can either split the sproc into smaller ones to bypass the text size
> limit, or save the proc in a text file and use osql in the job to call the
> input file.
>
> "tram" <tram_e@.hotmail.com> wrote in message
> news:26ee1067.0407130929.62a38b86@.posting.google.c om...
Showing posts with label step. Show all posts
Showing posts with label step. Show all posts
Monday, March 19, 2012
Sunday, March 11, 2012
Create procedure in target servers
I am creating a job in master server where in one step, it creates
stored procedure in target server. The proc text is exceeding the
limit to directly paste in job scheduler. What is the best way to push
procedure to target servers?You can either split the sproc into smaller ones to bypass the text size
limit, or save the proc in a text file and use osql in the job to call the
input file.
"tram" <tram_e@.hotmail.com> wrote in message
news:26ee1067.0407130929.62a38b86@.posting.google.com...
> I am creating a job in master server where in one step, it creates
> stored procedure in target server. The proc text is exceeding the
> limit to directly paste in job scheduler. What is the best way to push
> procedure to target servers?|||Thanks for the reply. OSQL could be used, but I need to copy the sql
to every server. It doesn't take if it is located at central server.
Any ideas?
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:<eJ6GcnQaEHA.3664@.TK2MSFTNGP1
2.phx.gbl>...[vbcol=seagreen]
> You can either split the sproc into smaller ones to bypass the text size
> limit, or save the proc in a text file and use osql in the job to call the
> input file.
>
> "tram" <tram_e@.hotmail.com> wrote in message
> news:26ee1067.0407130929.62a38b86@.posting.google.com...|||Thanks for the reply. OSQL could be used, but I need to copy the sql
to every server. It doesn't take if it is located at central server.
Any ideas?
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:<eJ6GcnQaEHA.3664@.TK2MSFTNGP1
2.phx.gbl>...[vbcol=seagreen]
> You can either split the sproc into smaller ones to bypass the text size
> limit, or save the proc in a text file and use osql in the job to call the
> input file.
>
> "tram" <tram_e@.hotmail.com> wrote in message
> news:26ee1067.0407130929.62a38b86@.posting.google.com...|||Thanks for the reply. OSQL could be used, but I need to copy the sql
to every server. It doesn't take if it is located at central server.
Any ideas?
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:<eJ6GcnQaEHA.3664@.TK2MSFTNGP1
2.phx.gbl>...[vbcol=seagreen]
> You can either split the sproc into smaller ones to bypass the text size
> limit, or save the proc in a text file and use osql in the job to call the
> input file.
>
> "tram" <tram_e@.hotmail.com> wrote in message
> news:26ee1067.0407130929.62a38b86@.posting.google.com...
stored procedure in target server. The proc text is exceeding the
limit to directly paste in job scheduler. What is the best way to push
procedure to target servers?You can either split the sproc into smaller ones to bypass the text size
limit, or save the proc in a text file and use osql in the job to call the
input file.
"tram" <tram_e@.hotmail.com> wrote in message
news:26ee1067.0407130929.62a38b86@.posting.google.com...
> I am creating a job in master server where in one step, it creates
> stored procedure in target server. The proc text is exceeding the
> limit to directly paste in job scheduler. What is the best way to push
> procedure to target servers?|||Thanks for the reply. OSQL could be used, but I need to copy the sql
to every server. It doesn't take if it is located at central server.
Any ideas?
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:<eJ6GcnQaEHA.3664@.TK2MSFTNGP1
2.phx.gbl>...[vbcol=seagreen]
> You can either split the sproc into smaller ones to bypass the text size
> limit, or save the proc in a text file and use osql in the job to call the
> input file.
>
> "tram" <tram_e@.hotmail.com> wrote in message
> news:26ee1067.0407130929.62a38b86@.posting.google.com...|||Thanks for the reply. OSQL could be used, but I need to copy the sql
to every server. It doesn't take if it is located at central server.
Any ideas?
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:<eJ6GcnQaEHA.3664@.TK2MSFTNGP1
2.phx.gbl>...[vbcol=seagreen]
> You can either split the sproc into smaller ones to bypass the text size
> limit, or save the proc in a text file and use osql in the job to call the
> input file.
>
> "tram" <tram_e@.hotmail.com> wrote in message
> news:26ee1067.0407130929.62a38b86@.posting.google.com...|||Thanks for the reply. OSQL could be used, but I need to copy the sql
to every server. It doesn't take if it is located at central server.
Any ideas?
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:<eJ6GcnQaEHA.3664@.TK2MSFTNGP1
2.phx.gbl>...[vbcol=seagreen]
> You can either split the sproc into smaller ones to bypass the text size
> limit, or save the proc in a text file and use osql in the job to call the
> input file.
>
> "tram" <tram_e@.hotmail.com> wrote in message
> news:26ee1067.0407130929.62a38b86@.posting.google.com...
Create procedure in target servers
I am creating a job in master server where in one step, it creates
stored procedure in target server. The proc text is exceeding the
limit to directly paste in job scheduler. What is the best way to push
procedure to target servers?You can either split the sproc into smaller ones to bypass the text size
limit, or save the proc in a text file and use osql in the job to call the
input file.
"tram" <tram_e@.hotmail.com> wrote in message
news:26ee1067.0407130929.62a38b86@.posting.google.com...
> I am creating a job in master server where in one step, it creates
> stored procedure in target server. The proc text is exceeding the
> limit to directly paste in job scheduler. What is the best way to push
> procedure to target servers?|||Thanks for the reply. OSQL could be used, but I need to copy the sql
to every server. It doesn't take if it is located at central server.
Any ideas?
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:<eJ6GcnQaEHA.3664@.TK2MSFTNGP12.phx.gbl>...
> You can either split the sproc into smaller ones to bypass the text size
> limit, or save the proc in a text file and use osql in the job to call the
> input file.
>
> "tram" <tram_e@.hotmail.com> wrote in message
> news:26ee1067.0407130929.62a38b86@.posting.google.com...
> > I am creating a job in master server where in one step, it creates
> > stored procedure in target server. The proc text is exceeding the
> > limit to directly paste in job scheduler. What is the best way to push
> > procedure to target servers?|||Thanks for the reply. OSQL could be used, but I need to copy the sql
to every server. It doesn't take if it is located at central server.
Any ideas?
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:<eJ6GcnQaEHA.3664@.TK2MSFTNGP12.phx.gbl>...
> You can either split the sproc into smaller ones to bypass the text size
> limit, or save the proc in a text file and use osql in the job to call the
> input file.
>
> "tram" <tram_e@.hotmail.com> wrote in message
> news:26ee1067.0407130929.62a38b86@.posting.google.com...
> > I am creating a job in master server where in one step, it creates
> > stored procedure in target server. The proc text is exceeding the
> > limit to directly paste in job scheduler. What is the best way to push
> > procedure to target servers?|||Thanks for the reply. OSQL could be used, but I need to copy the sql
to every server. It doesn't take if it is located at central server.
Any ideas?
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:<eJ6GcnQaEHA.3664@.TK2MSFTNGP12.phx.gbl>...
> You can either split the sproc into smaller ones to bypass the text size
> limit, or save the proc in a text file and use osql in the job to call the
> input file.
>
> "tram" <tram_e@.hotmail.com> wrote in message
> news:26ee1067.0407130929.62a38b86@.posting.google.com...
> > I am creating a job in master server where in one step, it creates
> > stored procedure in target server. The proc text is exceeding the
> > limit to directly paste in job scheduler. What is the best way to push
> > procedure to target servers?
stored procedure in target server. The proc text is exceeding the
limit to directly paste in job scheduler. What is the best way to push
procedure to target servers?You can either split the sproc into smaller ones to bypass the text size
limit, or save the proc in a text file and use osql in the job to call the
input file.
"tram" <tram_e@.hotmail.com> wrote in message
news:26ee1067.0407130929.62a38b86@.posting.google.com...
> I am creating a job in master server where in one step, it creates
> stored procedure in target server. The proc text is exceeding the
> limit to directly paste in job scheduler. What is the best way to push
> procedure to target servers?|||Thanks for the reply. OSQL could be used, but I need to copy the sql
to every server. It doesn't take if it is located at central server.
Any ideas?
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:<eJ6GcnQaEHA.3664@.TK2MSFTNGP12.phx.gbl>...
> You can either split the sproc into smaller ones to bypass the text size
> limit, or save the proc in a text file and use osql in the job to call the
> input file.
>
> "tram" <tram_e@.hotmail.com> wrote in message
> news:26ee1067.0407130929.62a38b86@.posting.google.com...
> > I am creating a job in master server where in one step, it creates
> > stored procedure in target server. The proc text is exceeding the
> > limit to directly paste in job scheduler. What is the best way to push
> > procedure to target servers?|||Thanks for the reply. OSQL could be used, but I need to copy the sql
to every server. It doesn't take if it is located at central server.
Any ideas?
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:<eJ6GcnQaEHA.3664@.TK2MSFTNGP12.phx.gbl>...
> You can either split the sproc into smaller ones to bypass the text size
> limit, or save the proc in a text file and use osql in the job to call the
> input file.
>
> "tram" <tram_e@.hotmail.com> wrote in message
> news:26ee1067.0407130929.62a38b86@.posting.google.com...
> > I am creating a job in master server where in one step, it creates
> > stored procedure in target server. The proc text is exceeding the
> > limit to directly paste in job scheduler. What is the best way to push
> > procedure to target servers?|||Thanks for the reply. OSQL could be used, but I need to copy the sql
to every server. It doesn't take if it is located at central server.
Any ideas?
"Richard Ding" <rding@.acadian-asset.com> wrote in message news:<eJ6GcnQaEHA.3664@.TK2MSFTNGP12.phx.gbl>...
> You can either split the sproc into smaller ones to bypass the text size
> limit, or save the proc in a text file and use osql in the job to call the
> input file.
>
> "tram" <tram_e@.hotmail.com> wrote in message
> news:26ee1067.0407130929.62a38b86@.posting.google.com...
> > I am creating a job in master server where in one step, it creates
> > stored procedure in target server. The proc text is exceeding the
> > limit to directly paste in job scheduler. What is the best way to push
> > procedure to target servers?
Wednesday, March 7, 2012
Create Multi-server environment in the SQL 2005- need HELP
I tried to setup a master-target server for the multi-server
environment
I tried the step in the microsoft support page already, but I keep
getting stucked with Create master wizard's third and fourth step.
This is my scenario: I have computer A and B connected in my network.
All of the SQLServer and SQL Agent in both machines uses a windows
authentications.
Both machines can communicate well already.
So, in the Create Master Server Wizard at Computer A I do:
-> Next
-> Next (leave all values blank for the email, pager and net send
address)
-> Add Connection to Computer B with windows authentication
-> Check compatibility success (meaning that the login successful as
well), then close
-> I check the "create a new login if necessary and assign it rights to
the MSX", then next
-> Finish
In the 3rd step: "Ensure the agent startup account for 'Computer B' has
rights to login as a target server", I got this error message:
===================================================================================== TITLE: Microsoft.SqlServer.Smo
--
Create failed for Login '.\TargetAdmin'.
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+Login&LinkId=20476
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
--
Windows NT user or group '.\TargetAdmin' not found. Check the name
again. (Microsoft SQL Server, Error: 15401)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=15401&LinkId=20476
--
BUTTONS:
OK
--
==========================================================================================================
In the fourth step: "Enlist 'Computer B' to 'Computer A', I got this
error message:
========================================================================================================== TITLE: Microsoft.SqlServer.Smo
--
MSX enlist failed for JobServer '155.64.154.169'.
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=20476
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
--
The enlist operation failed (reason: SQLServerAgent Error: Unable to
connect to MSX 'SYMANTEC-6VBB5C'.) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
--
BUTTONS:
OK
--
==========================================================================================================
Need help deperately >,<Are your servers domain members?
It looks like you have a problem with login from one server to other.
Accordint to the error messge '.\TargetAdmin' is a local account.
"ipramono@.gmail.com" wrote:
> I tried to setup a master-target server for the multi-server
> environment
> I tried the step in the microsoft support page already, but I keep
> getting stucked with Create master wizard's third and fourth step.
> This is my scenario: I have computer A and B connected in my network.
> All of the SQLServer and SQL Agent in both machines uses a windows
> authentications.
> Both machines can communicate well already.
> So, in the Create Master Server Wizard at Computer A I do:
> -> Next
> -> Next (leave all values blank for the email, pager and net send
> address)
> -> Add Connection to Computer B with windows authentication
> -> Check compatibility success (meaning that the login successful as
> well), then close
> -> I check the "create a new login if necessary and assign it rights to
> the MSX", then next
> -> Finish
> In the 3rd step: "Ensure the agent startup account for 'Computer B' has
> rights to login as a target server", I got this error message:
> =====================================================================================> TITLE: Microsoft.SqlServer.Smo
> --
> Create failed for Login '.\TargetAdmin'.
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+Login&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> Windows NT user or group '.\TargetAdmin' not found. Check the name
> again. (Microsoft SQL Server, Error: 15401)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=15401&LinkId=20476
> --
> BUTTONS:
> OK
> --
> ==========================================================================================================> In the fourth step: "Enlist 'Computer B' to 'Computer A', I got this
> error message:
> ==========================================================================================================> TITLE: Microsoft.SqlServer.Smo
> --
> MSX enlist failed for JobServer '155.64.154.169'.
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to MSX 'SYMANTEC-6VBB5C'.) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
> --
> BUTTONS:
> OK
> --
> ==========================================================================================================> Need help deperately >,<
>
environment
I tried the step in the microsoft support page already, but I keep
getting stucked with Create master wizard's third and fourth step.
This is my scenario: I have computer A and B connected in my network.
All of the SQLServer and SQL Agent in both machines uses a windows
authentications.
Both machines can communicate well already.
So, in the Create Master Server Wizard at Computer A I do:
-> Next
-> Next (leave all values blank for the email, pager and net send
address)
-> Add Connection to Computer B with windows authentication
-> Check compatibility success (meaning that the login successful as
well), then close
-> I check the "create a new login if necessary and assign it rights to
the MSX", then next
-> Finish
In the 3rd step: "Ensure the agent startup account for 'Computer B' has
rights to login as a target server", I got this error message:
===================================================================================== TITLE: Microsoft.SqlServer.Smo
--
Create failed for Login '.\TargetAdmin'.
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+Login&LinkId=20476
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
--
Windows NT user or group '.\TargetAdmin' not found. Check the name
again. (Microsoft SQL Server, Error: 15401)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=15401&LinkId=20476
--
BUTTONS:
OK
--
==========================================================================================================
In the fourth step: "Enlist 'Computer B' to 'Computer A', I got this
error message:
========================================================================================================== TITLE: Microsoft.SqlServer.Smo
--
MSX enlist failed for JobServer '155.64.154.169'.
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=20476
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
--
The enlist operation failed (reason: SQLServerAgent Error: Unable to
connect to MSX 'SYMANTEC-6VBB5C'.) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
--
BUTTONS:
OK
--
==========================================================================================================
Need help deperately >,<Are your servers domain members?
It looks like you have a problem with login from one server to other.
Accordint to the error messge '.\TargetAdmin' is a local account.
"ipramono@.gmail.com" wrote:
> I tried to setup a master-target server for the multi-server
> environment
> I tried the step in the microsoft support page already, but I keep
> getting stucked with Create master wizard's third and fourth step.
> This is my scenario: I have computer A and B connected in my network.
> All of the SQLServer and SQL Agent in both machines uses a windows
> authentications.
> Both machines can communicate well already.
> So, in the Create Master Server Wizard at Computer A I do:
> -> Next
> -> Next (leave all values blank for the email, pager and net send
> address)
> -> Add Connection to Computer B with windows authentication
> -> Check compatibility success (meaning that the login successful as
> well), then close
> -> I check the "create a new login if necessary and assign it rights to
> the MSX", then next
> -> Finish
> In the 3rd step: "Ensure the agent startup account for 'Computer B' has
> rights to login as a target server", I got this error message:
> =====================================================================================> TITLE: Microsoft.SqlServer.Smo
> --
> Create failed for Login '.\TargetAdmin'.
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+Login&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> Windows NT user or group '.\TargetAdmin' not found. Check the name
> again. (Microsoft SQL Server, Error: 15401)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=15401&LinkId=20476
> --
> BUTTONS:
> OK
> --
> ==========================================================================================================> In the fourth step: "Enlist 'Computer B' to 'Computer A', I got this
> error message:
> ==========================================================================================================> TITLE: Microsoft.SqlServer.Smo
> --
> MSX enlist failed for JobServer '155.64.154.169'.
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to MSX 'SYMANTEC-6VBB5C'.) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
> --
> BUTTONS:
> OK
> --
> ==========================================================================================================> Need help deperately >,<
>
Create Multi-server environment in the SQL 2005- need HELP
I tried to setup a master-target server for the multi-server
environment
I tried the step in the microsoft support page already, but I keep
getting stucked with Create master wizard's third and fourth step.
This is my scenario: I have computer A and B connected in my network.
All of the SQLServer and SQL Agent in both machines uses a windows
authentications.
Both machines can communicate well already.
So, in the Create Master Server Wizard at Computer A I do:
-> Next
-> Next (leave all values blank for the email, pager and net send
address)
-> Add Connection to Computer B with windows authentication
-> Check compatibility success (meaning that the login successful as
well), then close
-> I check the "create a new login if necessary and assign it rights to
the MSX", then next
-> Finish
In the 3rd step: "Ensure the agent startup account for 'Computer B' has
rights to login as a target server", I got this error message:
========================================
====================================
=========
TITLE: Microsoft.SqlServer.Smo
--
Create failed for Login '.\TargetAdmin'.
For help, click:
http://go.microsoft.com/fwlink?Prod...in&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
Windows NT user or group '.\TargetAdmin' not found. Check the name
again. (Microsoft SQL Server, Error: 15401)
For help, click:
http://go.microsoft.com/fwlink?Prod...01&LinkId=20476
BUTTONS:
OK
--
========================================
====================================
==============================
In the fourth step: "Enlist 'Computer B' to 'Computer A', I got this
error message:
========================================
====================================
==============================
TITLE: Microsoft.SqlServer.Smo
--
MSX enlist failed for JobServer '155.64.154.169'.
For help, click:
http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to
connect to MSX 'SYMANTEC-6VBB5C'.) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?Prod...26&LinkId=20476
BUTTONS:
OK
--
========================================
====================================
==============================
Need help deperately >,<Are your servers domain members?
It looks like you have a problem with login from one server to other.
Accordint to the error messge '.\TargetAdmin' is a local account.
"ipramono@.gmail.com" wrote:
> I tried to setup a master-target server for the multi-server
> environment
> I tried the step in the microsoft support page already, but I keep
> getting stucked with Create master wizard's third and fourth step.
> This is my scenario: I have computer A and B connected in my network.
> All of the SQLServer and SQL Agent in both machines uses a windows
> authentications.
> Both machines can communicate well already.
> So, in the Create Master Server Wizard at Computer A I do:
> -> Next
> -> Next (leave all values blank for the email, pager and net send
> address)
> -> Add Connection to Computer B with windows authentication
> -> Check compatibility success (meaning that the login successful as
> well), then close
> -> I check the "create a new login if necessary and assign it rights to
> the MSX", then next
> -> Finish
> In the 3rd step: "Ensure the agent startup account for 'Computer B' has
> rights to login as a target server", I got this error message:
> ========================================
==================================
===========
> TITLE: Microsoft.SqlServer.Smo
> --
> Create failed for Login '.\TargetAdmin'.
> For help, click:
> http://go.microsoft.com/fwlink?Prod...in&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> Windows NT user or group '.\TargetAdmin' not found. Check the name
> again. (Microsoft SQL Server, Error: 15401)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...01&LinkId=20476
> --
> BUTTONS:
> OK
> --
> ========================================
==================================
================================
> In the fourth step: "Enlist 'Computer B' to 'Computer A', I got this
> error message:
> ========================================
==================================
================================
> TITLE: Microsoft.SqlServer.Smo
> --
> MSX enlist failed for JobServer '155.64.154.169'.
> For help, click:
> http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to MSX 'SYMANTEC-6VBB5C'.) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...26&LinkId=20476
> --
> BUTTONS:
> OK
> --
> ========================================
==================================
================================
> Need help deperately >,<
>
environment
I tried the step in the microsoft support page already, but I keep
getting stucked with Create master wizard's third and fourth step.
This is my scenario: I have computer A and B connected in my network.
All of the SQLServer and SQL Agent in both machines uses a windows
authentications.
Both machines can communicate well already.
So, in the Create Master Server Wizard at Computer A I do:
-> Next
-> Next (leave all values blank for the email, pager and net send
address)
-> Add Connection to Computer B with windows authentication
-> Check compatibility success (meaning that the login successful as
well), then close
-> I check the "create a new login if necessary and assign it rights to
the MSX", then next
-> Finish
In the 3rd step: "Ensure the agent startup account for 'Computer B' has
rights to login as a target server", I got this error message:
========================================
====================================
=========
TITLE: Microsoft.SqlServer.Smo
--
Create failed for Login '.\TargetAdmin'.
For help, click:
http://go.microsoft.com/fwlink?Prod...in&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
Windows NT user or group '.\TargetAdmin' not found. Check the name
again. (Microsoft SQL Server, Error: 15401)
For help, click:
http://go.microsoft.com/fwlink?Prod...01&LinkId=20476
BUTTONS:
OK
--
========================================
====================================
==============================
In the fourth step: "Enlist 'Computer B' to 'Computer A', I got this
error message:
========================================
====================================
==============================
TITLE: Microsoft.SqlServer.Smo
--
MSX enlist failed for JobServer '155.64.154.169'.
For help, click:
http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to
connect to MSX 'SYMANTEC-6VBB5C'.) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?Prod...26&LinkId=20476
BUTTONS:
OK
--
========================================
====================================
==============================
Need help deperately >,<Are your servers domain members?
It looks like you have a problem with login from one server to other.
Accordint to the error messge '.\TargetAdmin' is a local account.
"ipramono@.gmail.com" wrote:
> I tried to setup a master-target server for the multi-server
> environment
> I tried the step in the microsoft support page already, but I keep
> getting stucked with Create master wizard's third and fourth step.
> This is my scenario: I have computer A and B connected in my network.
> All of the SQLServer and SQL Agent in both machines uses a windows
> authentications.
> Both machines can communicate well already.
> So, in the Create Master Server Wizard at Computer A I do:
> -> Next
> -> Next (leave all values blank for the email, pager and net send
> address)
> -> Add Connection to Computer B with windows authentication
> -> Check compatibility success (meaning that the login successful as
> well), then close
> -> I check the "create a new login if necessary and assign it rights to
> the MSX", then next
> -> Finish
> In the 3rd step: "Ensure the agent startup account for 'Computer B' has
> rights to login as a target server", I got this error message:
> ========================================
==================================
===========
> TITLE: Microsoft.SqlServer.Smo
> --
> Create failed for Login '.\TargetAdmin'.
> For help, click:
> http://go.microsoft.com/fwlink?Prod...in&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> Windows NT user or group '.\TargetAdmin' not found. Check the name
> again. (Microsoft SQL Server, Error: 15401)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...01&LinkId=20476
> --
> BUTTONS:
> OK
> --
> ========================================
==================================
================================
> In the fourth step: "Enlist 'Computer B' to 'Computer A', I got this
> error message:
> ========================================
==================================
================================
> TITLE: Microsoft.SqlServer.Smo
> --
> MSX enlist failed for JobServer '155.64.154.169'.
> For help, click:
> http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to MSX 'SYMANTEC-6VBB5C'.) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...26&LinkId=20476
> --
> BUTTONS:
> OK
> --
> ========================================
==================================
================================
> Need help deperately >,<
>
Subscribe to:
Posts (Atom)