sql report manager: agent

Showing posts with label agent. Show all posts

Tuesday, March 27, 2012

Can't start SQL Server Agent - wants MSSQLServerADHelper

When I try to start the SQL Server Agent service, it gives an error about
starting MSSQLServerADHelper.
When I look in the event log, it says:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
How can I get SQL Server Agent started? I had maintenance tasks scheduled
(backup, etc.) that now will not run.Are you sure that it is Agent who writes this error?
Check the Agent errorlog for error messages.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"JJ" <jjjj@.nospam.com> wrote in message news:eBOIaBurDHA.2244@.TK2MSFTNGP09.phx.gbl...
> When I try to start the SQL Server Agent service, it gives an error about
> starting MSSQLServerADHelper.
> When I look in the event log, it says:
> The MSSQLServerADHelper service terminated with service-specific error
> 3221225572.
> How can I get SQL Server Agent started? I had maintenance tasks scheduled
> (backup, etc.) that now will not run.
>|||I am positive that this is what occurs:
In the Services Control Panel applet, the SQL Server Agent service is
stopped. (It had been running on this system up until a few weeks ago -
this is a customer system, so I didn't know it stopped until now.)
When I right-click on SQL Server Agent and choose Start, that's when I get
the error on the screen that MSSQLServerADHelper could not be started.
But I think I have found the problem - it looks like someone there changed
SQL Server Agent to run in a specific account. I changed it to run as Local
System and then I could start it.
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:%23dILAtzrDHA.1764@.TK2MSFTNGP10.phx.gbl...
> Are you sure that it is Agent who writes this error?
> Check the Agent errorlog for error messages.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "JJ" <jjjj@.nospam.com> wrote in message
news:eBOIaBurDHA.2244@.TK2MSFTNGP09.phx.gbl...
> > When I try to start the SQL Server Agent service, it gives an error
about
> > starting MSSQLServerADHelper.
> >
> > When I look in the event log, it says:
> >
> > The MSSQLServerADHelper service terminated with service-specific error
> > 3221225572.
> >
> > How can I get SQL Server Agent started? I had maintenance tasks
scheduled
> > (backup, etc.) that now will not run.
> >
> >
>|||The startup account that they changed it to most likely
didn't have permissions to start the MSSQLServerADHelper
service.
-Sue
On Thu, 20 Nov 2003 09:19:49 -0500, "JJ" <jjjj@.nospam.com>
wrote:
>I am positive that this is what occurs:
>In the Services Control Panel applet, the SQL Server Agent service is
>stopped. (It had been running on this system up until a few weeks ago -
>this is a customer system, so I didn't know it stopped until now.)
>When I right-click on SQL Server Agent and choose Start, that's when I get
>the error on the screen that MSSQLServerADHelper could not be started.
>But I think I have found the problem - it looks like someone there changed
>SQL Server Agent to run in a specific account. I changed it to run as Local
>System and then I could start it.
>
>"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
>wrote in message news:%23dILAtzrDHA.1764@.TK2MSFTNGP10.phx.gbl...
>> Are you sure that it is Agent who writes this error?
>> Check the Agent errorlog for error messages.
>> --
>> Tibor Karaszi, SQL Server MVP
>> Archive at:
>http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>>
>> "JJ" <jjjj@.nospam.com> wrote in message
>news:eBOIaBurDHA.2244@.TK2MSFTNGP09.phx.gbl...
>> > When I try to start the SQL Server Agent service, it gives an error
>about
>> > starting MSSQLServerADHelper.
>> >
>> > When I look in the event log, it says:
>> >
>> > The MSSQLServerADHelper service terminated with service-specific error
>> > 3221225572.
>> >
>> > How can I get SQL Server Agent started? I had maintenance tasks
>scheduled
>> > (backup, etc.) that now will not run.
>> >
>> >
>>
>|||Hi JJ,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
MSSQLServerADHelper is a service installed by the SQL Server Setup program
that handles the Active Directory objects for all instances of the SQL
Server relational database engine and all Analysis Manager applications
that are running on the computer. There is only one MSSQLServerADHelper
service on a computer for all of the instances of Microsoft SQL Server
2000. This service is set to use the Local System Account by default.
This error only happens only if someone or some service tried to start the
service manually. It's possible that some "monitoring service" would
attempt to start a service if it identified that the service was not
started/running. If you check for such a service and make sure to remove
MSSQLServerADHelper service from it list of service to watch.
To avoid seeing this message again, you should not set the service to start
automatically. You can change this service to manually by
Start->Programs->Administrative tools->Services", find the
"MSSQLServerADHelper" in the list of services and change the property of
it. You right click the "MSSQLServerADHelper" and choose the "properties"
from the menu. Please check and see if the service MSSQLServerADHelper has
"Interact with the desktop" checked in the properties, if yes, then please
uncheck that. Also set the service to manual.
After the above steps are complete let me know if the event logs still get
the error.
I hope my information will help you to solve your problem. Please feel free
to post new information here and I am ready to provide further support.
Sincerely Yours
Baisong, Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
--
| From: "JJ" <jjjj@.nospam.com>
| Subject: Can't start SQL Server Agent - wants MSSQLServerADHelper
| Date: Wed, 19 Nov 2003 16:01:48 -0500
| Lines: 12
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <eBOIaBurDHA.2244@.TK2MSFTNGP09.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: 146.145.51.166
| Path:
cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08|||I am unable to start the service after following the steps mentioned and it is showing the same error in the event log
From http://www.developmentnow.com/g/118_2003_11_0_0_465849/Cant-start-SQL-Server-Agent--wants-MSSQLServerADHelper.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||Hi
Have tou tried to use the local system account and/or start the service from
SQL Server Service Manager or through enterprise manager? What does the SQL
Agent log file contain?
John
"prashanthi" wrote:
> I am unable to start the service after following the steps mentioned and it is showing the same error in the event log.
> From http://www.developmentnow.com/g/118_2003_11_0_0_465849/Cant-start-SQL-Server-Agent--wants-MSSQLServerADHelper.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
>

can't start sql server agent

Using SS2000 SP4. We rebooted our box this morning and the sql server agent
wouldn't start. I found this error in the event viewer in the system errorlog
- " The SQLSERVERAGENT service failed to start due to the following error:
The account name is invalid or does not exist, or the password is invalid
for the account name specified. "
The agent is using the same login and password as the SQL Server service and
the SQL Server service started fine. I trying putting in the password again
from the services app but the hourglass kept going and going until we finally
killed it. I tried changing the startup account to the local system from
within EM but I got this message - "The new service startup account name you
have supplied is invalid or does not exist." I tried using my domain account
and got the same message. I tried going back to the original login and
password and got the same message.
Our sysadmin said he had some problems with our domain controller over the
weekend. Since it can't seem to verify the accounts I thought that might be
related but if so, why does the SQL Server account work ok with the same
login and password?
Any ideas?
Thanks,
--
Dan D.Did you try log in on Windows on the same box? Sometimes it is a profile
problem.
--
Regards,
Robson Siqueira
Enterprise Architect
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
> Using SS2000 SP4. We rebooted our box this morning and the sql server
> agent
> wouldn't start. I found this error in the event viewer in the system
> errorlog
> - " The SQLSERVERAGENT service failed to start due to the following error:
> The account name is invalid or does not exist, or the password is invalid
> for the account name specified. "
> The agent is using the same login and password as the SQL Server service
> and
> the SQL Server service started fine. I trying putting in the password
> again
> from the services app but the hourglass kept going and going until we
> finally
> killed it. I tried changing the startup account to the local system from
> within EM but I got this message - "The new service startup account name
> you
> have supplied is invalid or does not exist." I tried using my domain
> account
> and got the same message. I tried going back to the original login and
> password and got the same message.
> Our sysadmin said he had some problems with our domain controller over the
> weekend. Since it can't seem to verify the accounts I thought that might
> be
> related but if so, why does the SQL Server account work ok with the same
> login and password?
> Any ideas?
> Thanks,
> --
> Dan D.|||They were changing the monitor in the computer room and this server hasn't
been hooked up yet.
I came in this morning and the agent service had started overnight. So,
we're okay for now. Thanks,
--
Dan D.
"Robson Siqueira" wrote:
> Did you try log in on Windows on the same box? Sometimes it is a profile
> problem.
> --
> Regards,
> Robson Siqueira
> Enterprise Architect
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
> > Using SS2000 SP4. We rebooted our box this morning and the sql server
> > agent
> > wouldn't start. I found this error in the event viewer in the system
> > errorlog
> > - " The SQLSERVERAGENT service failed to start due to the following error:
> > The account name is invalid or does not exist, or the password is invalid
> > for the account name specified. "
> >
> > The agent is using the same login and password as the SQL Server service
> > and
> > the SQL Server service started fine. I trying putting in the password
> > again
> > from the services app but the hourglass kept going and going until we
> > finally
> > killed it. I tried changing the startup account to the local system from
> > within EM but I got this message - "The new service startup account name
> > you
> > have supplied is invalid or does not exist." I tried using my domain
> > account
> > and got the same message. I tried going back to the original login and
> > password and got the same message.
> >
> > Our sysadmin said he had some problems with our domain controller over the
> > weekend. Since it can't seem to verify the accounts I thought that might
> > be
> > related but if so, why does the SQL Server account work ok with the same
> > login and password?
> >
> > Any ideas?
> >
> > Thanks,
> > --
> > Dan D.
>
>

Can't start SQL Server Agent

Hello,
When I try to start SQL Server Agent I get a message "An error 1049 - (The
service did not start due to a logon failure) while performing this service
operation on the SQLServerAgent service."
I am logged on to the machine as Administrator and SQL Server has a login
for Servername\Administrator.
I can perform data manipulation operations with no problems. I have not had
this problem on other servers before.
Any help would be appreciated.
RagnarHello,
Go to the COntrol Panel, Services, SQL Server Agent -- Go to Logon option
and chnage it to Local System Account and try restarting.
If it works fine then use a domain account and specify the password and
restrt the service.
I recommend you to start SQL Server and SQL Server Agent using the same
login account.
Thanks
Hari
"Ragnar Midtskogen" <ragnar_ng@.newsgroups.com> wrote in message
news:%23EzZ4wQYHHA.588@.TK2MSFTNGP06.phx.gbl...
> Hello,
> When I try to start SQL Server Agent I get a message "An error 1049 - (The
> service did not start due to a logon failure) while performing this
> service operation on the SQLServerAgent service."
> I am logged on to the machine as Administrator and SQL Server has a login
> for Servername\Administrator.
> I can perform data manipulation operations with no problems. I have not
> had this problem on other servers before.
> Any help would be appreciated.
> Ragnar
>|||Thank you Hari,
The logon was set as Administrator, so I just reset the password and that
solved the problem.
By the way, the SQL Server Agent properties shows startup account as being
Administrator and it also shows that the connection should use Windows
authentication.
I am a little confused as to what the difference is between the startup and
the connect properties, but as long as it works I am happy.
Ragnarsql

Can't start SQL Server Agent

Hello,
When I try to start SQL Server Agent I get a message "An error 1049 - (The
service did not start due to a logon failure) while performing this service
operation on the SQLServerAgent service."
I am logged on to the machine as Administrator and SQL Server has a login
for Servername\Administrator.
I can perform data manipulation operations with no problems. I have not had
this problem on other servers before.
Any help would be appreciated.
Ragnar
Hello,
Go to the COntrol Panel, Services, SQL Server Agent -- Go to Logon option
and chnage it to Local System Account and try restarting.
If it works fine then use a domain account and specify the password and
restrt the service.
I recommend you to start SQL Server and SQL Server Agent using the same
login account.
Thanks
Hari
"Ragnar Midtskogen" <ragnar_ng@.newsgroups.com> wrote in message
news:%23EzZ4wQYHHA.588@.TK2MSFTNGP06.phx.gbl...
> Hello,
> When I try to start SQL Server Agent I get a message "An error 1049 - (The
> service did not start due to a logon failure) while performing this
> service operation on the SQLServerAgent service."
> I am logged on to the machine as Administrator and SQL Server has a login
> for Servername\Administrator.
> I can perform data manipulation operations with no problems. I have not
> had this problem on other servers before.
> Any help would be appreciated.
> Ragnar
>
|||Thank you Hari,
The logon was set as Administrator, so I just reset the password and that
solved the problem.
By the way, the SQL Server Agent properties shows startup account as being
Administrator and it also shows that the connection should use Windows
authentication.
I am a little confused as to what the difference is between the startup and
the connect properties, but as long as it works I am happy.
Ragnar

can't start sql server agent

Using SS2000 SP4. We rebooted our box this morning and the sql server agent
wouldn't start. I found this error in the event viewer in the system errorlog
- " The SQLSERVERAGENT service failed to start due to the following error:
The account name is invalid or does not exist, or the password is invalid
for the account name specified. "
The agent is using the same login and password as the SQL Server service and
the SQL Server service started fine. I trying putting in the password again
from the services app but the hourglass kept going and going until we finally
killed it. I tried changing the startup account to the local system from
within EM but I got this message - "The new service startup account name you
have supplied is invalid or does not exist." I tried using my domain account
and got the same message. I tried going back to the original login and
password and got the same message.
Our sysadmin said he had some problems with our domain controller over the
weekend. Since it can't seem to verify the accounts I thought that might be
related but if so, why does the SQL Server account work ok with the same
login and password?
Any ideas?
Thanks,
Dan D.
Did you try log in on Windows on the same box? Sometimes it is a profile
problem.
Regards,
Robson Siqueira
Enterprise Architect
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
> Using SS2000 SP4. We rebooted our box this morning and the sql server
> agent
> wouldn't start. I found this error in the event viewer in the system
> errorlog
> - " The SQLSERVERAGENT service failed to start due to the following error:
> The account name is invalid or does not exist, or the password is invalid
> for the account name specified. "
> The agent is using the same login and password as the SQL Server service
> and
> the SQL Server service started fine. I trying putting in the password
> again
> from the services app but the hourglass kept going and going until we
> finally
> killed it. I tried changing the startup account to the local system from
> within EM but I got this message - "The new service startup account name
> you
> have supplied is invalid or does not exist." I tried using my domain
> account
> and got the same message. I tried going back to the original login and
> password and got the same message.
> Our sysadmin said he had some problems with our domain controller over the
> weekend. Since it can't seem to verify the accounts I thought that might
> be
> related but if so, why does the SQL Server account work ok with the same
> login and password?
> Any ideas?
> Thanks,
> --
> Dan D.
|||They were changing the monitor in the computer room and this server hasn't
been hooked up yet.
I came in this morning and the agent service had started overnight. So,
we're okay for now. Thanks,
Dan D.
"Robson Siqueira" wrote:

> Did you try log in on Windows on the same box? Sometimes it is a profile
> problem.
> --
> Regards,
> Robson Siqueira
> Enterprise Architect
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
>
>

can't start sql server agent

Using SS2000 SP4. We rebooted our box this morning and the sql server agent
wouldn't start. I found this error in the event viewer in the system errorlo
g
- " The SQLSERVERAGENT service failed to start due to the following error:
The account name is invalid or does not exist, or the password is invalid
for the account name specified. "
The agent is using the same login and password as the SQL Server service and
the SQL Server service started fine. I trying putting in the password again
from the services app but the hourglass kept going and going until we finall
y
killed it. I tried changing the startup account to the local system from
within EM but I got this message - "The new service startup account name you
have supplied is invalid or does not exist." I tried using my domain account
and got the same message. I tried going back to the original login and
password and got the same message.
Our sysadmin said he had some problems with our domain controller over the
weekend. Since it can't seem to verify the accounts I thought that might be
related but if so, why does the SQL Server account work ok with the same
login and password?
Any ideas?
Thanks,
--
Dan D.Did you try log in on Windows on the same box? Sometimes it is a profile
problem.
Regards,
Robson Siqueira
Enterprise Architect
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
> Using SS2000 SP4. We rebooted our box this morning and the sql server
> agent
> wouldn't start. I found this error in the event viewer in the system
> errorlog
> - " The SQLSERVERAGENT service failed to start due to the following error:
> The account name is invalid or does not exist, or the password is invalid
> for the account name specified. "
> The agent is using the same login and password as the SQL Server service
> and
> the SQL Server service started fine. I trying putting in the password
> again
> from the services app but the hourglass kept going and going until we
> finally
> killed it. I tried changing the startup account to the local system from
> within EM but I got this message - "The new service startup account name
> you
> have supplied is invalid or does not exist." I tried using my domain
> account
> and got the same message. I tried going back to the original login and
> password and got the same message.
> Our sysadmin said he had some problems with our domain controller over the
> weekend. Since it can't seem to verify the accounts I thought that might
> be
> related but if so, why does the SQL Server account work ok with the same
> login and password?
> Any ideas?
> Thanks,
> --
> Dan D.|||They were changing the monitor in the computer room and this server hasn't
been hooked up yet.
I came in this morning and the agent service had started overnight. So,
we're okay for now. Thanks,
--
Dan D.
"Robson Siqueira" wrote:

> Did you try log in on Windows on the same box? Sometimes it is a profile
> problem.
> --
> Regards,
> Robson Siqueira
> Enterprise Architect
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:A5683D25-040C-4A91-A6E9-3ACE159E9DA8@.microsoft.com...
>
>

Can't start SQL Server Agent

Can't start sql agent

Hi there,
I install SQL server 2000 in Win 2000 server with SQL SP3
and Win 2000 SP4.
The SQL is default instance and use local system as
service startup account.
Currently I change the startup services account from local
system to domain user account.
SQL Server success start but the sql agant no! I don't
know why? I check the error message - it say cannot
connect local server.
Now I change back the sql agent startup agent to local
system but it still can't start!!
Please help cause I need SQL agent!!
ThanksMay be that the BUILTIN\Administrators group was dropped from SQL Server. If
so, recreate it.
--
Sérgio Monteiro - Brasil
www.sqlpass.org
"Chai" <wingschai@.hotmail.com> escreveu na mensagem
news:082a01c38a25$78aa36f0$a401280a@.phx.gbl...
> Hi there,
> I install SQL server 2000 in Win 2000 server with SQL SP3
> and Win 2000 SP4.
> The SQL is default instance and use local system as
> service startup account.
> Currently I change the startup services account from local
> system to domain user account.
> SQL Server success start but the sql agant no! I don't
> know why? I check the error message - it say cannot
> connect local server.
> Now I change back the sql agent startup agent to local
> system but it still can't start!!
> Please help cause I need SQL agent!!
> Thanks|||I'd check what the SQL Server instance is listening on. In the errorlog, you
should find entries similar to the following:
2003-10-03 20:45:28.95 server SQL server listening on 67.83.16.85: 1058.
2003-10-03 20:45:28.95 server SQL server listening on 127.0.0.1: 1058.
2003-10-03 20:45:32.49 server SQL server listening on TCP, Shared Memory,
Named Pipes.
Also, you may want to log into the SQL Server box with the SQL Agent account
and try osql -S<ServerName> -E from the command line.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Chai" <wingschai@.hotmail.com> wrote in message
news:082a01c38a25$78aa36f0$a401280a@.phx.gbl...
> Hi there,
> I install SQL server 2000 in Win 2000 server with SQL SP3
> and Win 2000 SP4.
> The SQL is default instance and use local system as
> service startup account.
> Currently I change the startup services account from local
> system to domain user account.
> SQL Server success start but the sql agant no! I don't
> know why? I check the error message - it say cannot
> connect local server.
> Now I change back the sql agent startup agent to local
> system but it still can't start!!
> Please help cause I need SQL agent!!
> Thanks|||If I'm not mistaken, a different error (other than cannot connect to local
server) would be issued if you drop BUILTIN\Administrators from SQL Server
and then try to start SQLServerAgent.
By the way, SQL Server Agent log file SQLAgent.out may contain useful info.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Sérgio Monteiro" <shsmonteiro@.horizon.com.br> wrote in message
news:ucRO6piiDHA.3204@.TK2MSFTNGP11.phx.gbl...
> May be that the BUILTIN\Administrators group was dropped from SQL Server.
If
> so, recreate it.
> --
> Sérgio Monteiro - Brasil
> www.sqlpass.org
> "Chai" <wingschai@.hotmail.com> escreveu na mensagem
> news:082a01c38a25$78aa36f0$a401280a@.phx.gbl...
> > Hi there,
> >
> > I install SQL server 2000 in Win 2000 server with SQL SP3
> > and Win 2000 SP4.
> >
> > The SQL is default instance and use local system as
> > service startup account.
> >
> > Currently I change the startup services account from local
> > system to domain user account.
> >
> > SQL Server success start but the sql agant no! I don't
> > know why? I check the error message - it say cannot
> > connect local server.
> >
> > Now I change back the sql agent startup agent to local
> > system but it still can't start!!
> >
> > Please help cause I need SQL agent!!
> >
> > Thanks
>|||You're right. The exact message is "SQLServerAgent could not be started
(reason: SQLServerAgent must be able to
connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of the
SysAdmin role). "
But I remember one situation in which I faced this issue and somebody had
dropped the BUILTIN\Administrators. May be I'm confusing the situations.
Sérgio Monteiro - Brasil
www.sqlpass.org
"Linchi Shea" <linchi_shea@.NOSPAMml.com> escreveu na mensagem
news:#kncH4iiDHA.1692@.TK2MSFTNGP10.phx.gbl...
> If I'm not mistaken, a different error (other than cannot connect to local
> server) would be issued if you drop BUILTIN\Administrators from SQL Server
> and then try to start SQLServerAgent.
> By the way, SQL Server Agent log file SQLAgent.out may contain useful
info.
> --
> Linchi Shea
> linchi_shea@.NOSPAMml.com
>
> "Sérgio Monteiro" <shsmonteiro@.horizon.com.br> wrote in message
> news:ucRO6piiDHA.3204@.TK2MSFTNGP11.phx.gbl...
> > May be that the BUILTIN\Administrators group was dropped from SQL
Server.
> If
> > so, recreate it.
> >
> > --
> > Sérgio Monteiro - Brasil
> > www.sqlpass.org
> > "Chai" <wingschai@.hotmail.com> escreveu na mensagem
> > news:082a01c38a25$78aa36f0$a401280a@.phx.gbl...
> > > Hi there,
> > >
> > > I install SQL server 2000 in Win 2000 server with SQL SP3
> > > and Win 2000 SP4.
> > >
> > > The SQL is default instance and use local system as
> > > service startup account.
> > >
> > > Currently I change the startup services account from local
> > > system to domain user account.
> > >
> > > SQL Server success start but the sql agant no! I don't
> > > know why? I check the error message - it say cannot
> > > connect local server.
> > >
> > > Now I change back the sql agent startup agent to local
> > > system but it still can't start!!
> > >
> > > Please help cause I need SQL agent!!
> > >
> > > Thanks
> >
> >
>

Can't start replication agent

Hi,
I am using snapshot replication and want to create pull /
push replication but I always encountered same problem :
Login failed for user . . .
I think I had already set my user as an Administrator but
it didn't work.
Thanks in advance !
Michael Rawi
Michael,
in the subscriber database, right-click the distribution agent and select
properties.
On the security tab, choose to impersonate the SQL Server Agent.
You can change the service accounts to use the same domain user or have the
windows login of the subscriber's agent as a separate login on the
publisher.
HTH,
Paul Ibison
sql

Tuesday, March 20, 2012

Can't see property of SQL Server Agent

Hello!

I am working on Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2) and want just see properties of SQL Agent. What I do: Start Agent's service, right click on SQL Server Agent node(in Object Explorer) and select "Properties". All I get is:

TITLE: Microsoft SQL Server Management Studio

Cannot show requested dialog.

ADDITIONAL INFORMATION:

Property ErrorLogFile is not available for JobServer '[ASUS]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.PropertyCannotBeRetrievedExceptionText&EvtID=ErrorLogFile&LinkId=20476

BUTTONS:

Do you have any idea about this trouble?

Thanks In Advance for your tips!!

I looked through our bug database and could not find any bug mentioned after RTM related to this issue.

Questions:
1) Can you install Microsoft SQL Server 2005 Service Pack 1?
2) Are you running as an administrator?
3) Are you connecting to a local server?

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||

Paul Mestemaker - MSFT wrote:

I looked through our bug database and could not find any bug mentioned after RTM related to this issue.
Questions:
1) Can you install Microsoft SQL Server 2005 Service Pack 1?

YES! This simple step solve all my troubles. :) Thanks a lot!

Monday, March 19, 2012

Can't run the scheduled SQL Agent Job?

Hi,

I'm tried to run the job that created from maintenance plan. It fail and give me the following message:

[298] SQLServer Error: 15404, Could not obtain information about Windows NT group/user 'DOMAIN\MYNAME', error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

We are using the Windows Autheniciaton mode only and my id is set as sysadmin, setadmin, processadmin in the server roles.

I don't why I can't run the job, I check the SQL agent services is login using LOCALSYSTEM.

I try to the NT admin account to login the box, but still getting the same error message.

Any idea?

Thanks!

use a local login for the SQLAgent and try to schedule it again.|||

Hi,

What is local login? we only setup use the windows authenication mode for the sql server?

Thanks!

|||

this may help u : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=102884&SiteID=1

change the owner of the job

Madhu

|||

Is the SQL Server machine in the same domain as the user mentioned in the error message?

The 0x5 error code means access denied - the DC doesn't allow you to query the user information. If there are different domains involved, you may need to set the trust between them.

Also, what did you say you tried at the end of your message? There is a word missing I think.

Thanks
Laurentiu

Sunday, March 11, 2012

Can''t run SSIS package via Agent

I've seen many postings on various forums on how to get SQL agent to execute an SSIS package. I have one that was originally created via the import wizard in SSMS, later modified in VS2005, and then re-imported in SSMS using the Object Explorer interface to load the dtsx file into SQL storage. I've tried several package protection options when importing the package: "Don't save sensitive data" (the package has no passwords in it), server storage and roles, and a specified package password (which I entered as a /DECRYPT command line parameter in the Agent job step). Agent is running using a domain admin account. No matter what I've tried, I still get an error during job execution that it failed to decrypt the password XML node. The package runs just fine when executed manually in the SSIS Object Explorer.

How can I resolve this?

Are you sure you have been talking about the same packge? You have clearly tried the options, including those which mean there is no encryption to decrypt, so it makes no sense. I have often got confused between versions or a similar mix up when frustated and trying to debug an issue like this.

|||

And by this, I believe that darren means versions of the same package. I have had similar problems in the past where I will continue to bang my head against the wall knowing that something should be working before remembering that I didn't copy the latest version of the package over to the release folder, or from the release folder to the sql package storage etc...

Anywho, I would try pushing it out with encrypt sensitive with password and if it asks you for a password when you are setting up the package in the job step you know that you have the correct version... If you use the sql package store on your ssis server, I would use the serverstorage method of encryption.

|||

Bear with me -- this is my first SSIS project; I've only used DTS in the past. I have only one version of the dtsx file. I've been setting the protection options when I import the file into SSIS via the object explorer. When you say "push it out with 'encrypt sensitive with password'", do you mean there is some way to set that option in the VS designer IDE? When I tried the pw option on import to SSIS, I did not get prompted for the pw when I created the Agent job step. Instead, I put a /DECRYPT switch in the job step's command line options. Please explain.

(And thanks very much for your help!)

|||yes there is a way to set this in the visual studios designer. Right click on the background of the control flow task of your package and select properties. About half way down the list there is a property for "protection level" where there is a drop down for the different types of encryption. If you choose encrypt sensitive w/ password it will prompt you for a password and a confirm password to encrypt the package with. After you have filled this out, any time that you go to the job step maintenance screen it will prompt you for the password (to verify your right to see the connection strings and whatnot).|||

That worked! I found the property setting in the designer and set it as you suggested. When I re-imported the dtsx file into SSIS on the production server, I also set the same protection option and entered the package pw set in the designer. I then deleted the old Agent job step and created a new one. It did not prompt for the package password, but it did execute the SSIS package this time. I saw no place in the various settings tabs for a package pw, nor did it prompt me for one, and I did not alter the command line defaults. Should it have prompted for a pw?