Friday, March 30, 2012
Multi Server Jobs
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (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=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 server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
Any help would be greatly appreciated,
leilaHello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (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.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=2047
> 6
> --
> 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 server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
> Any help would be greatly appreciated,
> leil|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews.microsoft.com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>> I am running two instances of SQL Server 2005 Developer Edition (SP1)
>> on the same machine. Both SQL Server and Agent services use a local
>> user account which is member of Windows Administrators. The wizard for
>> Enlisting TSX fails with the following report:
>> Enlist TSX Progress
>> - Create MSXOperator (Success)
>> Checking for an existing MSXOperator.
>> Updating existing MSXOperator.
>> Successfully updated MSXOperator.
>> - Make sure the Agent service for 'NIMA\sql2005_1' is running
>> (Success)
>> The service 'SQLAgent$SQL2005_1' is running.
>> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
>> Enlisting target server 'NIMA\sql2005_2' with master server
>> 'NIMA\sql2005_1'.
>> Using new enlistment method.
>> Messages
>> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
>> (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.ExceptionTemplat
>> es.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=2047
>> 6
>> --
>> 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 server. .) (Microsoft SQL Server, Error: 22026)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
>> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
>> Any help would be greatly appreciated,
>> leila
>
Multi Server Jobs
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (Microsoft.SqlServer.Smo)
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 server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?Prod...26&LinkId=20476
Any help would be greatly appreciated,
leilaHello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...erver&ProdVer=9
> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=2047
> 6
> --
> 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 server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...erver&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
> Any help would be greatly appreciated,
> leila|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews
.microsoft.com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>sql
Wednesday, March 28, 2012
Multi Server Jobs
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (Microsoft.SqlServer.Smo)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=MSX+enlist+JobServer&LinkId=20476[/url]
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 server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476[ /url]
Any help would be greatly appreciated,
leila
Hello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (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.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+J obServer&LinkId=2047
> 6
> --
> 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 server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20 476
> Any help would be greatly appreciated,
> leila
|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews.microsoft .com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>
Monday, March 12, 2012
MSSQLSERVER ERROR
Could not start MSSQLSERVER service on Local Computer.
The service did not return an error. This could be an internal Windows
error or an internal service error.
Any clues from anyone?
Thanks
cleb1 wrote:
> I got this message:
> Could not start MSSQLSERVER service on Local Computer.
> The service did not return an error. This could be an internal
> Windows error or an internal service error.
> Any clues from anyone?
> Thanks
Check the account you are running SQL Server under (from Services) and
make sure it is still valid.
Check the event log for any other information.
David G.
|||Please post your SQL errorlog for review.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
mssqlserver account
Should it be a local account or a domain account?
Thanks,
MTI like using a Domain account when there may be multiple servers because it
is easier to share file permissions etc... If there is only one server it
doesn't much matter.. If you wish to use mail integration for SQL Server
you may wish to use multiple domain accounts, since email is connected to
the login account - if you wish to separate the email for each server...
The Domain account should have limited permissions (as doc'd in BOL.)
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"mt" <miketownsend33@.yahoo.com> wrote in message
news:028601c37775$9fe611c0$a001280a@.phx.gbl...
> What account should run mssqlserver and sqlserveragent.
> Should it be a local account or a domain account?
> Thanks,
> MT
mssqlserver account
Should it be a local account or a domain account?
Thanks,
MTYou often need a domain account. If SQL Server agent executes a job which fetches a file from
another machine, for instance., Or you want to use SQL Mail, where you need a domain account for the
mail account.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"mt" <miketownsend33@.yahoo.com> wrote in message news:0a7201c37775$a0c993f0$a301280a@.phx.gbl...
> What account should run mssqlserver and sqlserveragent.
> Should it be a local account or a domain account?
> Thanks,
> MT
Saturday, February 25, 2012
MSSQL Server connectivity
Hi,
I have two Windows machines in the Local Area Network. One of the machines has MSSQL Enterprise Server 8.0 installed whereas the other has MSSQL Server 2005 installed. When I try to establish the connectivity between these two servers, I can not do so. When I try to look up Network servers, the two machines can't see each other. How can I make them talk to each other? Is there some type of driver or some such thing to be installed which can help the matter?
Please let me know.
Need a bit more information to help you:
Are the instances default or named?
Do you have any firewall software running on either server?
What is the error msg you're getting?
Can you use SQLCMD to connect to the remote server?
Thanks for the response.
Answers to your questions:
1. The MSSQL Server instances are the default ones.
2. I don't think I have a firewall running on the servers.
3. When I go to SQL Server Management Studio and try to register the server by looking on the network, I can not find my other machine with Enterprise Manager 8.0. So I don't get any error, but I can not see the machine either.
4. Login failed for user 'xyz'.
HResult 0x2746, Level 16, State 1
TCP Provider: An existing connection was forcibly closed by the remote host.
Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.
This is the error that I see on the command prompt.
Here's what I suggest: You may want to go through my answers above, but I think I don't know much about this new SQL version? Can you quickly list a set of steps I can follow to connect from SQL Server 2005 to another machine having SQL Enterprise Manager 8.0 running on it? Thanks in advance.
|||Enterprise Manager has nothing to do with remote connectivity. This is what I understand you're doing:
Machine 1: Running SQL Server 2000, default instance
Machine 2: Running SQL Server 2005, default instance
From Machine 2 running SQL Server Management Studio you want to connect to Machine 1.
First, make sure that Machine 1 is setup to accept remote connections. This is documented in Books Online for SQL Server 2000.
You'll want to make sure you're providing the correct credentials: Windows or SQL Server depending on how the instance is configured.
|||Hi Dan,
Thanks for the response. However, we somehow managed to do the connectivity between the 2 servers. Apparently, the SQL user which we were using to establish the connectivity did not work initially. We dropped and recreated the user and then it went through fine. Don't know why it did not connect initially.
I have another problem though. And I would really appreciate if someone could help with this real quick.
So, there's this MSSQL 2005 installed on a new machine, which has 40 G on C Drive and 250+ G on a D Drive. But all of my C Drive has been taken up by "tempdb.mdf". It has taken up nearly 26 G of space on this drive. Why should that be the case? I know that this is a System database that gets created when one installs MSSQL Server, but I have never seen it this big. Is there a problem with the installation that I can fix? Please let me know.
Thanks.
|||This is certainly suspicious. I'm not expert on tempdb so I recommend you post this issue to http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=93&SiteID=1. Someone there will certainly be able to help you.MSSQL Server connectivity
Hi,
I have two Windows machines in the Local Area Network. One of the machines has MSSQL Enterprise Server 8.0 installed whereas the other has MSSQL Server 2005 installed. When I try to establish the connectivity between these two servers, I can not do so. When I try to look up Network servers, the two machines can't see each other. How can I make them talk to each other? Is there some type of driver or some such thing to be installed which can help the matter?
Please let me know.
Need a bit more information to help you:
Are the instances default or named?
Do you have any firewall software running on either server?
What is the error msg you're getting?
Can you use SQLCMD to connect to the remote server?
Thanks for the response.
Answers to your questions:
1. The MSSQL Server instances are the default ones.
2. I don't think I have a firewall running on the servers.
3. When I go to SQL Server Management Studio and try to register the server by looking on the network, I can not find my other machine with Enterprise Manager 8.0. So I don't get any error, but I can not see the machine either.
4. Login failed for user 'xyz'.
HResult 0x2746, Level 16, State 1
TCP Provider: An existing connection was forcibly closed by the remote host.
Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.
This is the error that I see on the command prompt.
Here's what I suggest: You may want to go through my answers above, but I think I don't know much about this new SQL version? Can you quickly list a set of steps I can follow to connect from SQL Server 2005 to another machine having SQL Enterprise Manager 8.0 running on it? Thanks in advance.
|||Enterprise Manager has nothing to do with remote connectivity. This is what I understand you're doing:
Machine 1: Running SQL Server 2000, default instance
Machine 2: Running SQL Server 2005, default instance
From Machine 2 running SQL Server Management Studio you want to connect to Machine 1.
First, make sure that Machine 1 is setup to accept remote connections. This is documented in Books Online for SQL Server 2000.
You'll want to make sure you're providing the correct credentials: Windows or SQL Server depending on how the instance is configured.
|||Hi Dan,
Thanks for the response. However, we somehow managed to do the connectivity between the 2 servers. Apparently, the SQL user which we were using to establish the connectivity did not work initially. We dropped and recreated the user and then it went through fine. Don't know why it did not connect initially.
I have another problem though. And I would really appreciate if someone could help with this real quick.
So, there's this MSSQL 2005 installed on a new machine, which has 40 G on C Drive and 250+ G on a D Drive. But all of my C Drive has been taken up by "tempdb.mdf". It has taken up nearly 26 G of space on this drive. Why should that be the case? I know that this is a System database that gets created when one installs MSSQL Server, but I have never seen it this big. Is there a problem with the installation that I can fix? Please let me know.
Thanks.
|||This is certainly suspicious. I'm not expert on tempdb so I recommend you post this issue to http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=93&SiteID=1. Someone there will certainly be able to help you.