Error when starting SQLSERVER AGENT

Hello!, I have the following error message when I want to start the
sqlserver agent: "The SQLSERVER AGENT SERVICE on local computer started and
then stopped. Some services stop automatically if they have no work to do,
for example the performance logs and alerts service"
In this server I have windows 2003 and sql server 2000 (it has the service
pack already), actually some days ago it had no problem, suddenly the jobs
did not run so I realized this problem.
Help!!!!!!!!
Message posted via http://www.droptable.com
The MSDB database has some problem,maybe it is running in single user mode.
maybe you moved it from another BD check the MSDB for any thing out of the
normal.

Error when starting SQLSERVER AGENT

Hello!, I have the following error message when I want to start the
sqlserver agent: "The SQLSERVER AGENT SERVICE on local computer started and
then stopped. Some services stop automatically if they have no work to do,
for example the performance logs and alerts service"
In this server I have windows 2003 and sql server 2000 (it has the service
pack already), actually some days ago it had no problem, suddenly the jobs
did not run so I realized this problem.
Help!!!!!!!!
--
Message posted via http://www.sqlmonster.comThe MSDB database has some problem,maybe it is running in single user mode.
maybe you moved it from another BD check the MSDB for any thing out of the
normal.

Error when starting SQLSERVER AGENT

Hello!, I have the following error message when I want to start the
sqlserver agent: "The SQLSERVER AGENT SERVICE on local computer started and
then stopped. Some services stop automatically if they have no work to do,
for example the performance logs and alerts service"
In this server I have windows 2003 and sql server 2000 (it has the service
pack already), actually some days ago it had no problem, suddenly the jobs
did not run so I realized this problem.
Help!!!!!!!!
Message posted via http://www.droptable.comThe MSDB database has some problem,maybe it is running in single user mode.
maybe you moved it from another BD check the MSDB for any thing out of the
normal.sql

error when running SSIS package as a job

I am running into an error when running a package using a scheduled job under SQL Server Agent account. I am getting following error:

Date 6/12/2007 4:19:15 PM
Log Job History (VistaODSFeed)

Step ID 0
Server 006-DEVSQL2005
Job Name VistaODSFeed
Step Name (Job outcome)
Duration 00:00:00
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
The job failed. Unable to determine if the owner (ACI\snasir) of job VistaODSFeed has server access (reason: Could not obtain information about Windows NT group/user 'ACI\snasir', error code 0x6ba. [SQLSTATE 42000] (Error 15404)).

ACI\snasir is not the account under which SQL Server Agent service runs. However ACI\snasir has sa priveleges. not sure why am I getting ACI\snasir in the error and not the account under which sql server agent runs.

ideas?

Hi Shahab,

Is ACI\snasir hard-coded as the username in any of the connection managers?

Andy

Error when running Snapshot Agent

David,
can you have a look at the list of processes and see if
the snapshot.exe is listed, then kill it if it is.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
No - definitely no snapshot.exe.
"Paul Ibison" wrote:

> David,
> can you have a look at the list of processes and see if
> the snapshot.exe is listed, then kill it if it is.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||David,
have a look at sp_removedbreplication, which should
remove any lingering system table traces. Have a look for
any orphaned jobs which are running the snapshot agent.
Also, consider restarting the sql server service.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||An update on this issue:
I disabled replication and distribution on the publisher and distributor
(respectivley) started again.
I was able to start the snapshot agent.
I then received a different error from the snapshot agent:
Invalid object name: syspublications.
Still stuck on this error though.
"Paul Ibison" wrote:

> David,
> have a look at sp_removedbreplication, which should
> remove any lingering system table traces. Have a look for
> any orphaned jobs which are running the snapshot agent.
> Also, consider restarting the sql server service.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>

Error when running Agent in Merge Replication!

Hi All:
I am trying to setup a Merge Replication over Internet. Snapshot runs
successfully, but when it tries to run sycronize the data for ther first
time, it gives the following error in the end:
The Subscription to Publication 'xxxx' is invalid
'xxxx' is the Database Name
The connectivity to the remote DB is working.
One of the reasons for this swich I found was the the remote server's name
was changed after SQL server was installed. Therefore the old name was
dropeed b y using these:
sp_dropserver <server name>
go
sp_addserver <new server name> , LOCAL
go
After doing this, we still get the same message "The Subscription to
Publication 'xxxx' is invalid"
Please suggest the remedy for this.
Thanks,
Anukul
anukul,
Just for grins, check that the publisher is aware of the new server name. If not you can either drop the subscription in both places and re-create or alter the subscription in both places to utilize the new machine name.
Give it a shot. Worst case it doesn't work...|||If you changed the server name after configuring the Subscriber, the
Publisher doesn't know about the new server name. You need to drop and
recreate the subscription at the Subscriber and re-register the Subscriber
with the Publisher, using the following stored procedures:
? sp_dropmergepullsubscription at the Subscriber (only if the Merge Agent
runs at the Subscriber, a pull subscription).
? sp_dropmergesubscription at the Publisher.
? sp_dropsubscriber at the Publisher.
You should also be able to do this from Enterprise Manager.
Then you must re-register the Subscriber using sp_addsubscriber or (from
Enterprise Manager) and recreate the subscription using either Enterprise
Manager or executing sp_addmergesubscription at the Publisher and
sp_addmergepullsubscription (only if the Merge Agent runs at the Subscriber,
a pull subscription).
Best wishes,
Glenn Gailey
SQL Server User Education
This posting is provided "AS IS" with no warranties, and confers no rights.
"Anukul" wrote:

> Hi All:
> I am trying to setup a Merge Replication over Internet. Snapshot runs
> successfully, but when it tries to run sycronize the data for ther first
> time, it gives the following error in the end:
> The Subscription to Publication 'xxxx' is invalid
> 'xxxx' is the Database Name
> The connectivity to the remote DB is working.
> One of the reasons for this swich I found was the the remote server's name
> was changed after SQL server was installed. Therefore the old name was
> dropeed b y using these:
> sp_dropserver <server name>
> go
> sp_addserver <new server name> , LOCAL
> go
> After doing this, we still get the same message "The Subscription to
> Publication 'xxxx' is invalid"
> Please suggest the remedy for this.
> Thanks,
> Anukul
>
>

Error when restoring master database

Dear all,
I'm working on MS SQL 2000.
I stopped the SQL Server and the SQL Agent services.
and from the prompt:
sqlservr.exe -s MyInstanceName -c -m
then from QA, I've entered my MyInstanceName, user: sa and pwd.
and wrote there:
RESTORE DATABASE master FROM DISK = 'c:\master.bak'
I'm getting an error:
RESTORE DATABASE must be used in single user mode when trying to restore the
master database.
what am I missing'
Thanks in advance
joujI've discovered why. :$
I wasn't using the sqlservr.exe from MSSQl$MyInstanceName\Binn.
My problem now is the server version. I think I should install a Service
Pack for that the versions match.
Thanks.
"jouj" wrote:
> Dear all,
> I'm working on MS SQL 2000.
> I stopped the SQL Server and the SQL Agent services.
> and from the prompt:
> sqlservr.exe -s MyInstanceName -c -m
> then from QA, I've entered my MyInstanceName, user: sa and pwd.
> and wrote there:
> RESTORE DATABASE master FROM DISK = 'c:\master.bak'
> I'm getting an error:
> RESTORE DATABASE must be used in single user mode when trying to restore the
> master database.
> what am I missing'
> Thanks in advance
> jouj|||sqlservr.exe -c - m -s {instancename}
"jouj" <jouj@.discussions.microsoft.com> wrote in message
news:C13BA8B2-490A-4365-8591-82C84F2BB0FB@.microsoft.com...
> Dear all,
> I'm working on MS SQL 2000.
> I stopped the SQL Server and the SQL Agent services.
> and from the prompt:
> sqlservr.exe -s MyInstanceName -c -m
> then from QA, I've entered my MyInstanceName, user: sa and pwd.
> and wrote there:
> RESTORE DATABASE master FROM DISK = 'c:\master.bak'
> I'm getting an error:
> RESTORE DATABASE must be used in single user mode when trying to restore
> the
> master database.
> what am I missing'
> Thanks in advance
> jouj

Error when restoring master database

Dear all,
I'm working on MS SQL 2000.
I stopped the SQL Server and the SQL Agent services.
and from the prompt:
sqlservr.exe -s MyInstanceName -c -m
then from QA, I've entered my MyInstanceName, user: sa and pwd.
and wrote there:
RESTORE DATABASE master FROM DISK = 'c:\master.bak'
I'm getting an error:
RESTORE DATABASE must be used in single user mode when trying to restore the
master database.
what am I missing?
Thanks in advance
jouj
I've discovered why. :$
I wasn't using the sqlservr.exe from MSSQl$MyInstanceName\Binn.
My problem now is the server version. I think I should install a Service
Pack for that the versions match.
Thanks.
"jouj" wrote:

> Dear all,
> I'm working on MS SQL 2000.
> I stopped the SQL Server and the SQL Agent services.
> and from the prompt:
> sqlservr.exe -s MyInstanceName -c -m
> then from QA, I've entered my MyInstanceName, user: sa and pwd.
> and wrote there:
> RESTORE DATABASE master FROM DISK = 'c:\master.bak'
> I'm getting an error:
> RESTORE DATABASE must be used in single user mode when trying to restore the
> master database.
> what am I missing?
> Thanks in advance
> jouj
|||sqlservr.exe -c - m -s {instancename}
"jouj" <jouj@.discussions.microsoft.com> wrote in message
news:C13BA8B2-490A-4365-8591-82C84F2BB0FB@.microsoft.com...
> Dear all,
> I'm working on MS SQL 2000.
> I stopped the SQL Server and the SQL Agent services.
> and from the prompt:
> sqlservr.exe -s MyInstanceName -c -m
> then from QA, I've entered my MyInstanceName, user: sa and pwd.
> and wrote there:
> RESTORE DATABASE master FROM DISK = 'c:\master.bak'
> I'm getting an error:
> RESTORE DATABASE must be used in single user mode when trying to restore
> the
> master database.
> what am I missing?
> Thanks in advance
> jouj
sql

Error when restoring master database

Dear all,
I'm working on MS SQL 2000.
I stopped the SQL Server and the SQL Agent services.
and from the prompt:
sqlservr.exe -s MyInstanceName -c -m
then from QA, I've entered my MyInstanceName, user: sa and pwd.
and wrote there:
RESTORE DATABASE master FROM DISK = 'c:\master.bak'
I'm getting an error:
RESTORE DATABASE must be used in single user mode when trying to restore the
master database.
what am I missing'
Thanks in advance
joujI've discovered why. :$
I wasn't using the sqlservr.exe from MSSQl$MyInstanceName\Binn.
My problem now is the server version. I think I should install a Service
Pack for that the versions match.
Thanks.
"jouj" wrote:

> Dear all,
> I'm working on MS SQL 2000.
> I stopped the SQL Server and the SQL Agent services.
> and from the prompt:
> sqlservr.exe -s MyInstanceName -c -m
> then from QA, I've entered my MyInstanceName, user: sa and pwd.
> and wrote there:
> RESTORE DATABASE master FROM DISK = 'c:\master.bak'
> I'm getting an error:
> RESTORE DATABASE must be used in single user mode when trying to restore t
he
> master database.
> what am I missing'
> Thanks in advance
> jouj|||sqlservr.exe -c - m -s {instancename}
"jouj" <jouj@.discussions.microsoft.com> wrote in message
news:C13BA8B2-490A-4365-8591-82C84F2BB0FB@.microsoft.com...
> Dear all,
> I'm working on MS SQL 2000.
> I stopped the SQL Server and the SQL Agent services.
> and from the prompt:
> sqlservr.exe -s MyInstanceName -c -m
> then from QA, I've entered my MyInstanceName, user: sa and pwd.
> and wrote there:
> RESTORE DATABASE master FROM DISK = 'c:\master.bak'
> I'm getting an error:
> RESTORE DATABASE must be used in single user mode when trying to restore
> the
> master database.
> what am I missing'
> Thanks in advance
> jouj

Error trying to execute a sp on a remote server with an SQL agent

Job 'bla' : Step 1, 'execute spbla' : Began Executing 2004-10-13 10:33:13
Msg 7410, Sev 16: Remote access not allowed for Windows NT user activated by
SETUSER. [SQLSTATE 42000]
I get the above error when I try to execute a sp sitting on a remote server
with a SQL Server Agent job.
The sp executes fine if I run it from Query analyser.
Maybe the problem lies with how my linked server is set up, or why does it
try to connect to the remote server with NT security and using SQL
authentication?
Can I force it to connect with SQL Authentication ?
Rgds,
Nico
Nico,
Possibly 811031 PRB: SQL Server Agent Job Fails When the Job Uses a Linked
Server and
http://support.microsoft.com/?id=811031
John Gose
MCDBA
Microsoft SQL Server Support
This posting is provided "AS IS", with no warranties, and confers no rights
Are you secure? For information about the Microsoft Strategic Technology
Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
| Thread-Topic: Error trying to execute a sp on a remote server with an SQL
agent
| thread-index: AcSxAO/Fym/0adp3SrSXr6fzDw/fvQ==
| X-WBNR-Posting-Host: 168.210.90.181
| From: "=?Utf-8?B?Tmljbw==?=" <Nico@.discussions.microsoft.com>
| Subject: Error trying to execute a sp on a remote server with an SQL agent
| Date: Wed, 13 Oct 2004 01:45:05 -0700
| Lines: 15
|
<Snip of Header Stuff>
|
| Job 'bla' : Step 1, 'execute spbla' : Began Executing 2004-10-13 10:33:13
| Msg 7410, Sev 16: Remote access not allowed for Windows NT user activated
by
| SETUSER. [SQLSTATE 42000]
|
| I get the above error when I try to execute a sp sitting on a remote
server
| with a SQL Server Agent job.
| The sp executes fine if I run it from Query analyser.
|
| Maybe the problem lies with how my linked server is set up, or why does
it
| try to connect to the remote server with NT security and using SQL
| authentication?
| Can I force it to connect with SQL Authentication ?
|
| Rgds,
| Nico
|

Error trying to execute a sp on a remote server with an SQL agent

Job 'bla' : Step 1, 'execute spbla' : Began Executing 2004-10-13 10:33:13
Msg 7410, Sev 16: Remote access not allowed for Windows NT user activated by
SETUSER. [SQLSTATE 42000]
I get the above error when I try to execute a sp sitting on a remote server
with a SQL Server Agent job.
The sp executes fine if I run it from Query analyser.
Maybe the problem lies with how my linked server is set up, or why does it
try to connect to the remote server with NT security and using SQL
authentication?
Can I force it to connect with SQL Authentication ?
Rgds,
NicoNico,
Possibly 811031 PRB: SQL Server Agent Job Fails When the Job Uses a Linked
Server and
http://support.microsoft.com/?id=811031
John Gose
MCDBA
Microsoft SQL Server Support
This posting is provided "AS IS", with no warranties, and confers no rights
Are you secure? For information about the Microsoft Strategic Technology
Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
| Thread-Topic: Error trying to execute a sp on a remote server with an SQL
agent
| thread-index: AcSxAO/Fym/0adp3SrSXr6fzDw/fvQ==
| X-WBNR-Posting-Host: 168.210.90.181
| From: "examnotes" <Nico@.discussions.microsoft.com>
| Subject: Error trying to execute a sp on a remote server with an SQL agent
| Date: Wed, 13 Oct 2004 01:45:05 -0700
| Lines: 15
|
<Snip of Header Stuff>
|
| Job 'bla' : Step 1, 'execute spbla' : Began Executing 2004-10-13 10:33:13
| Msg 7410, Sev 16: Remote access not allowed for Windows NT user activated
by
| SETUSER. [SQLSTATE 42000]
|
| I get the above error when I try to execute a sp sitting on a remote
server
| with a SQL Server Agent job.
| The sp executes fine if I run it from Query analyser.
|
| Maybe the problem lies with how my linked server is set up, or why does
it
| try to connect to the remote server with NT security and using SQL
| authentication?
| Can I force it to connect with SQL Authentication ?
|
| Rgds,
| Nico
|

Error starting SQL Agent

Hello,
I cannot start SQL Agent in SQL Server 2000. When I try it, Windows shows
the next message:
"Error 32: The process cannot access the file because it is being used by
another process"
I have checked the Event Log and SLQAgent.out file but haven't saw any
problem.
Moreover, if I try starting Analisys Services, windows shows the same error.
Thank you in advance.
It's seeming that some processes are still using SQLAGENT.OUT file or your
service user don't even have permission on that path or file.
Check if your user services has local administrator and network credentials
to operate and propagate these permissions to all files in sql folder.
Sds!
Krisnamourt
Angel Balaguer wrote:
>Hello,
>I cannot start SQL Agent in SQL Server 2000. When I try it, Windows shows
>the next message:
>"Error 32: The process cannot access the file because it is being used by
>another process"
>I have checked the Event Log and SLQAgent.out file but haven't saw any
>problem.
>Moreover, if I try starting Analisys Services, windows shows the same error.
>Thank you in advance.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200804/1

Error starting SQL Agent

Hello,
I cannot start SQL Agent in SQL Server 2000. When I try it, Windows shows
the next message:
"Error 32: The process cannot access the file because it is being used by
another process"
I have checked the Event Log and SLQAgent.out file but haven't saw any
problem.
Moreover, if I try starting Analisys Services, windows shows the same error.
Thank you in advance.It's seeming that some processes are still using SQLAGENT.OUT file or your
service user don't even have permission on that path or file.
Check if your user services has local administrator and network credentials
to operate and propagate these permissions to all files in sql folder.
Sds!
Krisnamourt
Angel Balaguer wrote:
>Hello,
>I cannot start SQL Agent in SQL Server 2000. When I try it, Windows shows
>the next message:
>"Error 32: The process cannot access the file because it is being used by
>another process"
>I have checked the Event Log and SLQAgent.out file but haven't saw any
>problem.
>Moreover, if I try starting Analisys Services, windows shows the same error.
>Thank you in advance.
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200804/1|||Hi krisnamourt,
Thank you for your answer.
I have checked both options and they are OK.
I have run SQLAgent from the console with the verbose option but SQLAgent
finishes the execution and doesn't display any message.
Could you please give me any idea?
Thank you.
"Krisnamourt via SQLMonster.com" wrote:
> It's seeming that some processes are still using SQLAGENT.OUT file or your
> service user don't even have permission on that path or file.
> Check if your user services has local administrator and network credentials
> to operate and propagate these permissions to all files in sql folder.
>
> Sds!
> Krisnamourt
> Angel Balaguer wrote:
> >Hello,
> >I cannot start SQL Agent in SQL Server 2000. When I try it, Windows shows
> >the next message:
> >
> >"Error 32: The process cannot access the file because it is being used by
> >another process"
> >
> >I have checked the Event Log and SLQAgent.out file but haven't saw any
> >problem.
> >
> >Moreover, if I try starting Analisys Services, windows shows the same error.
> >
> >Thank you in advance.
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200804/1
>