SQL tool for MSDE: sql-dmo

Showing posts with label sql-dmo. Show all posts

Saturday, February 25, 2012

Agent not running?

Hi I am trying to run na backup and when I run the job manually I get
an error SQL-DMO State 42000, Error 200225 SQLServerAgent is currently
not running and cannot be notified. In the event log I get these two,
but the agent is definitely running. Any ideas?
Thanks
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
You do not have sufficient operating system permission to open the
SQLServerAgent status event.
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Alert Engine
The data portion of event 17052 from MSSQLSERVER is invalid.Starting the Agent service?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"hals_left" <cc900630@.ntu.ac.uk> wrote in message
news:1162561943.730620.280980@.h48g2000cwc.googlegroups.com...
> Hi I am trying to run na backup and when I run the job manually I get
> an error SQL-DMO State 42000, Error 200225 SQLServerAgent is currently
> not running and cannot be notified. In the event log I get these two,
> but the agent is definitely running. Any ideas?
> Thanks
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> You do not have sufficient operating system permission to open the
> SQLServerAgent status event.
>
> Event Type: Error
> Event Source: SQLSERVERAGENT
> Event Category: Alert Engine
> The data portion of event 17052 from MSSQLSERVER is invalid.
>|||Well the agent has the Green arrow on the icon in EM and when I right
click it, Start is greyed out and Stop is not. In services
SQLSERVERAGENT has the status of started, so Im confused as to why Im
getting this error.
Tibor Karaszi wrote:
> Starting the Agent service?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "hals_left" <cc900630@.ntu.ac.uk> wrote in message
> news:1162561943.730620.280980@.h48g2000cwc.googlegroups.com...
> > Hi I am trying to run na backup and when I run the job manually I get
> > an error SQL-DMO State 42000, Error 200225 SQLServerAgent is currently
> > not running and cannot be notified. In the event log I get these two,
> > but the agent is definitely running. Any ideas?
> >
> > Thanks
> >
> > Event Type: Error
> > Event Source: MSSQLSERVER
> > Event Category: (2)
> > Event ID: 17052
> > You do not have sufficient operating system permission to open the
> > SQLServerAgent status event.
> >
> >
> > Event Type: Error
> > Event Source: SQLSERVERAGENT
> > Event Category: Alert Engine
> > The data portion of event 17052 from MSSQLSERVER is invalid.
> >|||Did you check Agent for the correct instance? Perhaps you have several instances of SQL Server
installed?
Assuming you did, I'd check SQL Server agent's error log for errors as the next step.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"hals_left" <cc900630@.ntu.ac.uk> wrote in message
news:1162833283.408183.293470@.h54g2000cwb.googlegroups.com...
> Well the agent has the Green arrow on the icon in EM and when I right
> click it, Start is greyed out and Stop is not. In services
> SQLSERVERAGENT has the status of started, so Im confused as to why Im
> getting this error.
>
> Tibor Karaszi wrote:
>> Starting the Agent service?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "hals_left" <cc900630@.ntu.ac.uk> wrote in message
>> news:1162561943.730620.280980@.h48g2000cwc.googlegroups.com...
>> > Hi I am trying to run na backup and when I run the job manually I get
>> > an error SQL-DMO State 42000, Error 200225 SQLServerAgent is currently
>> > not running and cannot be notified. In the event log I get these two,
>> > but the agent is definitely running. Any ideas?
>> >
>> > Thanks
>> >
>> > Event Type: Error
>> > Event Source: MSSQLSERVER
>> > Event Category: (2)
>> > Event ID: 17052
>> > You do not have sufficient operating system permission to open the
>> > SQLServerAgent status event.
>> >
>> >
>> > Event Type: Error
>> > Event Source: SQLSERVERAGENT
>> > Event Category: Alert Engine
>> > The data portion of event 17052 from MSSQLSERVER is invalid.
>> >
>|||Only 1 instance running. It does work on the schedule when not looged
in though, its only when I manually run the job from EM it fails.Will
check the agent error log
Tibor Karaszi wrote:
> Did you check Agent for the correct instance? Perhaps you have several instances of SQL Server
> installed?
> Assuming you did, I'd check SQL Server agent's error log for errors as the next step.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "hals_left" <cc900630@.ntu.ac.uk> wrote in message
> news:1162833283.408183.293470@.h54g2000cwb.googlegroups.com...
> > Well the agent has the Green arrow on the icon in EM and when I right
> > click it, Start is greyed out and Stop is not. In services
> > SQLSERVERAGENT has the status of started, so Im confused as to why Im
> > getting this error.
> >
> >
> >
> > Tibor Karaszi wrote:
> >> Starting the Agent service?
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "hals_left" <cc900630@.ntu.ac.uk> wrote in message
> >> news:1162561943.730620.280980@.h48g2000cwc.googlegroups.com...
> >> > Hi I am trying to run na backup and when I run the job manually I get
> >> > an error SQL-DMO State 42000, Error 200225 SQLServerAgent is currently
> >> > not running and cannot be notified. In the event log I get these two,
> >> > but the agent is definitely running. Any ideas?
> >> >
> >> > Thanks
> >> >
> >> > Event Type: Error
> >> > Event Source: MSSQLSERVER
> >> > Event Category: (2)
> >> > Event ID: 17052
> >> > You do not have sufficient operating system permission to open the
> >> > SQLServerAgent status event.
> >> >
> >> >
> >> > Event Type: Error
> >> > Event Source: SQLSERVERAGENT
> >> > Event Category: Alert Engine
> >> > The data portion of event 17052 from MSSQLSERVER is invalid.
> >> >
> >|||Hi Can anyone suggest what might be goig wrong here?
I have 4 backup jobs, 1 old one and 3 new-ish. All the settings are the
same on the 3 new jobs, the only difference is the time they run. All
fail when manually run with the errors below, the old one still
succeeds on the schedule when no one is logged in.
The strange thing is that the one that succeeds on the schedule is
actually now running at a different time than is defined, yesterday I
changed it from 00:00 to 03:00 and changed the schedule name from
"Schedule 1" to "3AM" yet it still runs at 00:00 and reports "Schedule
1" I also changed one of the step names yet it still reports the old
step name.
It seems the changes being made in EM are not taking effect, and that
SQL Server cannot see that the agent is running.
I have not had this problem before on other SQL 2000 installs, the only
diference is that I installed this folling best practices and set up
sqlservice and sqlagent on diferent windows accounts. ALl jobs login as
Administrator , I have tried changing thois the SQLAgent & SQLService
but it makes no difference.
The only thing thatr has changed on the server is windows updates.
The version is 8.00.2039 Standard Edition on NT5.2 SP1
Thanks
hals_left wrote:
> Only 1 instance running. It does work on the schedule when not looged
> in though, its only when I manually run the job from EM it fails.Will
> check the agent error log
>
> Tibor Karaszi wrote:
> > Did you check Agent for the correct instance? Perhaps you have several instances of SQL Server
> > installed?
> >
> > Assuming you did, I'd check SQL Server agent's error log for errors as the next step.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "hals_left" <cc900630@.ntu.ac.uk> wrote in message
> > news:1162833283.408183.293470@.h54g2000cwb.googlegroups.com...
> > > Well the agent has the Green arrow on the icon in EM and when I right
> > > click it, Start is greyed out and Stop is not. In services
> > > SQLSERVERAGENT has the status of started, so Im confused as to why Im
> > > getting this error.
> > >
> > >
> > >
> > > Tibor Karaszi wrote:
> > >> Starting the Agent service?
> > >>
> > >> --
> > >> Tibor Karaszi, SQL Server MVP
> > >> http://www.karaszi.com/sqlserver/default.asp
> > >> http://www.solidqualitylearning.com/
> > >>
> > >>
> > >> "hals_left" <cc900630@.ntu.ac.uk> wrote in message
> > >> news:1162561943.730620.280980@.h48g2000cwc.googlegroups.com...
> > >> > Hi I am trying to run na backup and when I run the job manually I get
> > >> > an error SQL-DMO State 42000, Error 200225 SQLServerAgent is currently
> > >> > not running and cannot be notified. In the event log I get these two,
> > >> > but the agent is definitely running. Any ideas?
> > >> >
> > >> > Thanks
> > >> >
> > >> > Event Type: Error
> > >> > Event Source: MSSQLSERVER
> > >> > Event Category: (2)
> > >> > Event ID: 17052
> > >> > You do not have sufficient operating system permission to open the
> > >> > SQLServerAgent status event.
> > >> >
> > >> >
> > >> > Event Type: Error
> > >> > Event Source: SQLSERVERAGENT
> > >> > Event Category: Alert Engine
> > >> > The data portion of event 17052 from MSSQLSERVER is invalid.
> > >> >
> > >

Agent Jobs Not Running

Most of our agent jobs are not running on schedule. When we try to start
them manually we get:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Error 22022: Unable to post notification to SQLServerAgent (reason:
MapViewOfFile() returned error 8, 'Not enough storage is available to
process this command.')
No errors in event log, sql server error log, or agent log. This appears to
be a memory issue outside of that allocated to sql server. Has anyone ever
resolved this without rebooting?
Only by finding the other programs on the server that were
using the memory and shutting those down.
But you generally get the error when low on memory.
-Sue
On Thu, 12 Aug 2004 15:08:37 -0500, "michelle"
<michelle@.nospam.com> wrote:

>Most of our agent jobs are not running on schedule. When we try to start
>them manually we get:
>Microsoft SQL-DMO (ODBC SQLState: 42000)
>Error 22022: Unable to post notification to SQLServerAgent (reason:
>MapViewOfFile() returned error 8, 'Not enough storage is available to
>process this command.')
>No errors in event log, sql server error log, or agent log. This appears to
>be a memory issue outside of that allocated to sql server. Has anyone ever
>resolved this without rebooting?
>

Agent Jobs Not Running

Most of our agent jobs are not running on schedule. When we try to start
them manually we get:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Error 22022: Unable to post notification to SQLServerAgent (reason:
MapViewOfFile() returned error 8, 'Not enough storage is available to
process this command.')
No errors in event log, sql server error log, or agent log. This appears to
be a memory issue outside of that allocated to sql server. Has anyone ever
resolved this without rebooting?Only by finding the other programs on the server that were
using the memory and shutting those down.
But you generally get the error when low on memory.
-Sue
On Thu, 12 Aug 2004 15:08:37 -0500, "michelle"
<michelle@.nospam.com> wrote:

>Most of our agent jobs are not running on schedule. When we try to start
>them manually we get:
>Microsoft SQL-DMO (ODBC SQLState: 42000)
>Error 22022: Unable to post notification to SQLServerAgent (reason:
>MapViewOfFile() returned error 8, 'Not enough storage is available to
>process this command.')
>No errors in event log, sql server error log, or agent log. This appears to
>be a memory issue outside of that allocated to sql server. Has anyone ever
>resolved this without rebooting?
>

Agent Jobs Not Running

Most of our agent jobs are not running on schedule. When we try to start
them manually we get:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Error 22022: Unable to post notification to SQLServerAgent (reason:
MapViewOfFile() returned error 8, 'Not enough storage is available to
process this command.')
No errors in event log, sql server error log, or agent log. This appears to
be a memory issue outside of that allocated to sql server. Has anyone ever
resolved this without rebooting?Only by finding the other programs on the server that were
using the memory and shutting those down.
But you generally get the error when low on memory.
-Sue
On Thu, 12 Aug 2004 15:08:37 -0500, "michelle"
<michelle@.nospam.com> wrote:
>Most of our agent jobs are not running on schedule. When we try to start
>them manually we get:
>Microsoft SQL-DMO (ODBC SQLState: 42000)
>Error 22022: Unable to post notification to SQLServerAgent (reason:
>MapViewOfFile() returned error 8, 'Not enough storage is available to
>process this command.')
>No errors in event log, sql server error log, or agent log. This appears to
>be a memory issue outside of that allocated to sql server. Has anyone ever
>resolved this without rebooting?
>

Saturday, February 25, 2012

Agent not running?

Agent not running?

Agent not running?

Agent Jobs Not Running

Agent Jobs Not Running

Agent Jobs Not Running

SQL tool for MSDE

Blog Archive

About Me