sql error 15138: appears

Showing posts with label appears. Show all posts

Tuesday, March 27, 2012

Error 17883 The Scheduler 0 appears to be hung:add information

After installing the 8.00.0818 patch i receive this error messages in the log
trying to schedule the backups at night, it occurs after approx three minutes
1. Error 17883 The Scheduler 0 appears to be hung
2.Time out occurred while waiting for buffer latch type 2,bp 0xe501c0, page
1:15), stat 0xb, object ID 2:1:2, EC 0x36F094E8 : 0, waittime 300. Not
continuing to wait.
3.Waiting for type 0x2, current count 0x2a, current owning EC 0x3CD3D570.
any suggestions
Best wishes
Hi
There was an issue with 818 see
http://support.microsoft.com/default.aspx?scid=kb;[LN];Q826161 try patch to
819 or 878 http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
although I don't think this is necessarily causing your problem.
Check out http://support.microsoft.com/default...b;en-us;309093
Check the event log for any hardware related problems, particularly disc
errors. Look at perfmon for high disc queue lengths.
Try running DBCC CHECKDB.
John
"Mats" wrote:

> After installing the 8.00.0818 patch i receive this error messages in the log
> trying to schedule the backups at night, it occurs after approx three minutes
> 1. Error 17883 The Scheduler 0 appears to be hung
> 2.Time out occurred while waiting for buffer latch type 2,bp 0xe501c0, page
> 1:15), stat 0xb, object ID 2:1:2, EC 0x36F094E8 : 0, waittime 300. Not
> continuing to wait.
> 3.Waiting for type 0x2, current count 0x2a, current owning EC 0x3CD3D570.
> any suggestions
> --
> Best wishes

Error 17883 The Scheduler 0 appears to be hung:add information

After installing the 8.00.0818 patch i receive this error messages in the lo
g
trying to schedule the backups at night, it occurs after approx three minute
s
1. Error 17883 The Scheduler 0 appears to be hung
2.Time out occurred while waiting for buffer latch type 2,bp 0xe501c0, page
1:15), stat 0xb, object ID 2:1:2, EC 0x36F094E8 : 0, waittime 300. Not
continuing to wait.
3.Waiting for type 0x2, current count 0x2a, current owning EC 0x3CD3D570.
any suggestions
--
Best wishesHi
There was an issue with 818 see
http://support.microsoft.com/defaul...scid=kb;[LN];Q826161 try patch
to
819 or 878 http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
although I don't think this is necessarily causing your problem.
Check out http://support.microsoft.com/defaul...kb;en-us;309093
Check the event log for any hardware related problems, particularly disc
errors. Look at perfmon for high disc queue lengths.
Try running DBCC CHECKDB.
John
"Mats" wrote:

> After installing the 8.00.0818 patch i receive this error messages in the
log
> trying to schedule the backups at night, it occurs after approx three minu
tes
> 1. Error 17883 The Scheduler 0 appears to be hung
> 2.Time out occurred while waiting for buffer latch type 2,bp 0xe501c0, pag
e
> 1:15), stat 0xb, object ID 2:1:2, EC 0x36F094E8 : 0, waittime 300. Not
> continuing to wait.
> 3.Waiting for type 0x2, current count 0x2a, current owning EC 0x3CD3D570.
> any suggestions
> --
> Best wishes

Error 17883 The Scheduler 0 appears to be hung

I get this message every time i try to take a backup. Both manually and via
the Scheduler. What is the problem?
--
Best wishesSee if these help:
http://support.microsoft.com/kb/815056
http://support.microsoft.com/kb/810885
-oj
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>I get this message every time i try to take a backup. Both manually and via
> the Scheduler. What is the problem?
> --
> Best wishes|||Well I do not know. The funny thing is that I get the same message if I
reboot the system ansd take a manual backup. The system get stuck takes
almost all of the processor power. I have then to kill enterprise manager.
Then the process lies there with the backup and I can not kill it. It
diseappears only with reboot.The reboot at that time is also extremely
difficult you have to shut off by the power button as the whole machine is
stucked. I then see the message in the error log.
If I take the backup via the scheduler nothing happends it only adds
processes until next reboot and then I see the message.
The system ran fine for over a month and then this suddenly happened. The
machine by the way is a two processor Dell.
"oj" wrote:

> See if these help:
> http://support.microsoft.com/kb/815056
> http://support.microsoft.com/kb/810885
>
> --
> -oj
>
> "Mats" <Mats@.discussions.microsoft.com> wrote in message
> news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>
>|||Backups should not spike your CPUs. My guess is that you have another
problem on this server and it's hanging SQL. You should engage MS support
and have them review 17883 minidumps. You need to be on build 818 (MS03-031
patch) or higher to generate good minidumps.
Adrian
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:3EB13F27-EDF3-47E6-9CBB-94A8960CAC20@.microsoft.com...[vbcol=seagreen]
> Well I do not know. The funny thing is that I get the same message if I
> reboot the system ansd take a manual backup. The system get stuck takes
> almost all of the processor power. I have then to kill enterprise manager.
> Then the process lies there with the backup and I can not kill it. It
> diseappears only with reboot.The reboot at that time is also extremely
> difficult you have to shut off by the power button as the whole machine is
> stucked. I then see the message in the error log.
> If I take the backup via the scheduler nothing happends it only adds
> processes until next reboot and then I see the message.
> The system ran fine for over a month and then this suddenly happened. The
> machine by the way is a two processor Dell.
> "oj" wrote:
>|||I have just installed 818. How do I do a minidump then?
"Adrian Zajkeskovic" wrote:

> Backups should not spike your CPUs. My guess is that you have another
> problem on this server and it's hanging SQL. You should engage MS support
> and have them review 17883 minidumps. You need to be on build 818 (MS03-03
1
> patch) or higher to generate good minidumps.
> Adrian
>
> "Mats" <Mats@.discussions.microsoft.com> wrote in message
> news:3EB13F27-EDF3-47E6-9CBB-94A8960CAC20@.microsoft.com...
>
>|||Backups should not cause this but could trigger behavior that you don't
expect.
Perhaps this will help.
The 17883 is a generic message (often referred to as the service engine
light) indicating that the UMS scheduling mechanism has detected a
worker that is not properly yielding to other workers within SQL Server.
The message was added in SQL 2000 SP3 but a later build (8.00.818
Security patch) is required to get extended diags. When the error is
first encountered a mini-dump is generated capturing the state of the
non-yielding thread. The mini-dump can be used by SQL support to
determine where in the code the SQL Server is non-yielding.
Since SP3 Microsoft has corrected or protected the engine in approx 25
places in the SQL Server code base that may not yield to other workers
properly, diminishing concurrency of the database engine. That is why
you find so many references to upgrade to a later QFE. I generally
recommend going to 8.00.997 to obtain the majority of these corrections
if you have encountered the 17883 on SP3 (8.00.760) where the mini dump
is not generated so the cause can not be determined.
Future versions of SQL Server are working to make these mini-dumps
Watson enabled so they can be directly submitted to the Watson site and
automated responses generated.
The problems have ranged from SQL Server bugs to getting stuck in API
calls that should return quickly but from time to time do not. For
example if we make a call to a security API and the PDC/BDC does not
return a response for 60 seconds (unusual and unexpected) the worker
ties up the specific UMS scheduler.
Do not be mislead, the worker is still an NT thread or fiber and must
honor NT scheduling. The design of SQL Server (UMS scheduling) is such
that only a single worker on a given scheduler can be scheduled by the
OS at any point in time. As each completes major phases or work
(natural yield points) the UMS scheduler coordinates the scheduling of
another worker on the same scheduler. It is rather simple, each worker
does a WaitForSingleObject with in INFINITE timeout so NT does not see
them as a viable worker to schedule. When a the active worker finishes
the unit of work it signals the next worker and waits on its event and
the cycle continues. Without going into more detail in this thread it
is a very simplistic non-preemptive system inside the SQL Server setup
to maximize resource usage and increase scalability. There is not need
for a lock waiter to do anything until the lock owner signals it to
execute so use the CPU for something more meaningful.
Bob Dorr
Microsoft SQL Server Escalation Support - Senior EE
*** Sent via Developersdex http://www.codecomments.com ***sql

Error 17883 The Scheduler 0 appears to be hung

I get this message every time i try to take a backup. Both manually and via
the Scheduler. What is the problem?
Best wishes
See if these help:
http://support.microsoft.com/kb/815056
http://support.microsoft.com/kb/810885
-oj
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>I get this message every time i try to take a backup. Both manually and via
> the Scheduler. What is the problem?
> --
> Best wishes
|||Well I do not know. The funny thing is that I get the same message if I
reboot the system ansd take a manual backup. The system get stuck takes
almost all of the processor power. I have then to kill enterprise manager.
Then the process lies there with the backup and I can not kill it. It
diseappears only with reboot.The reboot at that time is also extremely
difficult you have to shut off by the power button as the whole machine is
stucked. I then see the message in the error log.
If I take the backup via the scheduler nothing happends it only adds
processes until next reboot and then I see the message.
The system ran fine for over a month and then this suddenly happened. The
machine by the way is a two processor Dell.
"oj" wrote:

> See if these help:
> http://support.microsoft.com/kb/815056
> http://support.microsoft.com/kb/810885
>
> --
> -oj
>
> "Mats" <Mats@.discussions.microsoft.com> wrote in message
> news:289BEB45-7BDF-47DD-937F-0425DB689549@.microsoft.com...
>
>
|||Backups should not spike your CPUs. My guess is that you have another
problem on this server and it's hanging SQL. You should engage MS support
and have them review 17883 minidumps. You need to be on build 818 (MS03-031
patch) or higher to generate good minidumps.
Adrian
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:3EB13F27-EDF3-47E6-9CBB-94A8960CAC20@.microsoft.com...[vbcol=seagreen]
> Well I do not know. The funny thing is that I get the same message if I
> reboot the system ansd take a manual backup. The system get stuck takes
> almost all of the processor power. I have then to kill enterprise manager.
> Then the process lies there with the backup and I can not kill it. It
> diseappears only with reboot.The reboot at that time is also extremely
> difficult you have to shut off by the power button as the whole machine is
> stucked. I then see the message in the error log.
> If I take the backup via the scheduler nothing happends it only adds
> processes until next reboot and then I see the message.
> The system ran fine for over a month and then this suddenly happened. The
> machine by the way is a two processor Dell.
> "oj" wrote:
|||I have just installed 818. How do I do a minidump then?
"Adrian Zajkeskovic" wrote:

> Backups should not spike your CPUs. My guess is that you have another
> problem on this server and it's hanging SQL. You should engage MS support
> and have them review 17883 minidumps. You need to be on build 818 (MS03-031
> patch) or higher to generate good minidumps.
> Adrian
>
> "Mats" <Mats@.discussions.microsoft.com> wrote in message
> news:3EB13F27-EDF3-47E6-9CBB-94A8960CAC20@.microsoft.com...
>
>
|||Backups should not cause this but could trigger behavior that you don't
expect.
Perhaps this will help.
The 17883 is a generic message (often referred to as the service engine
light) indicating that the UMS scheduling mechanism has detected a
worker that is not properly yielding to other workers within SQL Server.
The message was added in SQL 2000 SP3 but a later build (8.00.818
Security patch) is required to get extended diags. When the error is
first encountered a mini-dump is generated capturing the state of the
non-yielding thread. The mini-dump can be used by SQL support to
determine where in the code the SQL Server is non-yielding.
Since SP3 Microsoft has corrected or protected the engine in approx 25
places in the SQL Server code base that may not yield to other workers
properly, diminishing concurrency of the database engine. That is why
you find so many references to upgrade to a later QFE. I generally
recommend going to 8.00.997 to obtain the majority of these corrections
if you have encountered the 17883 on SP3 (8.00.760) where the mini dump
is not generated so the cause can not be determined.
Future versions of SQL Server are working to make these mini-dumps
Watson enabled so they can be directly submitted to the Watson site and
automated responses generated.
The problems have ranged from SQL Server bugs to getting stuck in API
calls that should return quickly but from time to time do not. For
example if we make a call to a security API and the PDC/BDC does not
return a response for 60 seconds (unusual and unexpected) the worker
ties up the specific UMS scheduler.
Do not be mislead, the worker is still an NT thread or fiber and must
honor NT scheduling. The design of SQL Server (UMS scheduling) is such
that only a single worker on a given scheduler can be scheduled by the
OS at any point in time. As each completes major phases or work
(natural yield points) the UMS scheduler coordinates the scheduling of
another worker on the same scheduler. It is rather simple, each worker
does a WaitForSingleObject with in INFINITE timeout so NT does not see
them as a viable worker to schedule. When a the active worker finishes
the unit of work it signals the next worker and waits on its event and
the cycle continues. Without going into more detail in this thread it
is a very simplistic non-preemptive system inside the SQL Server setup
to maximize resource usage and increase scalability. There is not need
for a lock waiter to do anything until the lock owner signals it to
execute so use the CPU for something more meaningful.
Bob Dorr
Microsoft SQL Server Escalation Support - Senior EE
*** Sent via Developersdex http://www.codecomments.com ***

Error 17883 - Scheduler appears to be hung - related to linked server or HT??

We have been getting the following errors on our production environment
lately.
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x021B55C0
It appears that this error shows whenever we run a query with a linked
server. This error appears concurrently with an application popup on the
SQL server.
Application popup: SQL Server OLEDB provider support error : Unable to load
SQL Server OLEDB provider resource DLL. The application cannot continue.
We had this issue earlier with another machine which had parallelization
turned on. We turned it off because we believed the Hyperthreading w/
Parallelization was confusing this. Our old servers never had these issues
and were not HT enabled. The one box that was experiencing the problems
was/is behaving normally. However another box (same CPU, same no
parallelization settings) is having the issue when running a query using a
linked server to another SQL Server.
Our servers are SQL Server 2000 SP3, on Windows2000 SP4. With 2 3.2Ghz, HT
Enabled and 1.5GB RAM.
Thanks,
DanWe've seen the 17883 happen for a variety of reasons and symptoms.
It almost always comes down to disk i/o - contention issues. We had a
msde show this after being bombarded with query requests and with an 8
concurrent query limit.
Check to make sure that SQL Server is the ONLY one messing with
its' files. Make sure that on-access virus scan is off. As well as
backups or anything that might be going after the data and log files.
The last time this happened was because of virus scan and a policy set
that kept re-enabling on access scan.
Frankm
dan wrote:
> We have been getting the following errors on our production environment
> lately.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x021B55C0
> It appears that this error shows whenever we run a query with a linked
> server. This error appears concurrently with an application popup on the
> SQL server.
> Application popup: SQL Server OLEDB provider support error : Unable to load
> SQL Server OLEDB provider resource DLL. The application cannot continue.
> We had this issue earlier with another machine which had parallelization
> turned on. We turned it off because we believed the Hyperthreading w/
> Parallelization was confusing this. Our old servers never had these issues
> and were not HT enabled. The one box that was experiencing the problems
> was/is behaving normally. However another box (same CPU, same no
> parallelization settings) is having the issue when running a query using a
> linked server to another SQL Server.
> Our servers are SQL Server 2000 SP3, on Windows2000 SP4. With 2 3.2Ghz, HT
> Enabled and 1.5GB RAM.
> Thanks,
> Dan
>|||Hey Dan,
Your problem is almost exactly what we are facing.
I did not know you had posted your question when I posted
mine ( I usually do a search before posting questions, but
I missed doing it this time). Check out 'my' thread on the
21st & 22nd with 17883 in the subject line.
Did you resolve your problem?
Did you go through any of the suggestions in my thread?
Hotfix to get a more precise indication?
Thanks very much.
Sam
>--Original Message--
>We have been getting the following errors on our
production environment
>lately.
>Error: 17883, Severity: 1, State: 0
>The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS
Context 0x021B55C0
>It appears that this error shows whenever we run a query
with a linked
>server. This error appears concurrently with an
application popup on the
>SQL server.
>Application popup: SQL Server OLEDB provider support
error : Unable to load
>SQL Server OLEDB provider resource DLL. The application
cannot continue.
>We had this issue earlier with another machine which had
parallelization
>turned on. We turned it off because we believed the
Hyperthreading w/
>Parallelization was confusing this. Our old servers
never had these issues
>and were not HT enabled. The one box that was
experiencing the problems
>was/is behaving normally. However another box (same CPU,
same no
>parallelization settings) is having the issue when
running a query using a
>linked server to another SQL Server.
>Our servers are SQL Server 2000 SP3, on Windows2000 SP4.
With 2 3.2Ghz, HT
>Enabled and 1.5GB RAM.
>Thanks,
>Dan
>
>.
>

error 17883

Monday, March 26, 2012

error 17883

Im getting
The Scheduler 0 appears to be hung. SPID 6, ECID 0, UMS Context 0x03D15418.
Error: 17883, Severity: 1, State: 0
Dont know about other compliants and no performance issues so far.
The server is mssql 2000,multiinstance&multidatabase on w2k3. One of dbs is
ARCServe
In most of the cases this error appears just after the start&finish of
ARCServe jobs. Ideas how to fix the problem will be appreciated. Thanks.What service pack/hotfix level?
Please run Select @.@.versionin Query Analyzer and post back
--
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Eli Milkova" <EliMilkova@.discussions.microsoft.com> wrote in message
news:5C63197D-3BB5-4140-97A8-02A5B6CA5278@.microsoft.com...
> Im getting
> The Scheduler 0 appears to be hung. SPID 6, ECID 0, UMS Context
> 0x03D15418.
> Error: 17883, Severity: 1, State: 0
> Dont know about other compliants and no performance issues so far.
> The server is mssql 2000,multiinstance&multidatabase on w2k3. One of dbs
> is
> ARCServe
> In most of the cases this error appears just after the start&finish of
> ARCServe jobs. Ideas how to fix the problem will be appreciated. Thanks.
>|||all instances there are with SP3a 8.00.760. Not all dbs on the server are SP4
compliant.
I dont know what exactly to expect in future...problem escalation?!?
"Kevin3NF" wrote:
> What service pack/hotfix level?
> Please run Select @.@.versionin Query Analyzer and post back
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
> "Eli Milkova" <EliMilkova@.discussions.microsoft.com> wrote in message
> news:5C63197D-3BB5-4140-97A8-02A5B6CA5278@.microsoft.com...
> > Im getting
> > The Scheduler 0 appears to be hung. SPID 6, ECID 0, UMS Context
> > 0x03D15418.
> > Error: 17883, Severity: 1, State: 0
> > Dont know about other compliants and no performance issues so far.
> > The server is mssql 2000,multiinstance&multidatabase on w2k3. One of dbs
> > is
> > ARCServe
> > In most of the cases this error appears just after the start&finish of
> > ARCServe jobs. Ideas how to fix the problem will be appreciated. Thanks.
> >
>
>|||SP4
!!!! only fix!!!!
If you are enterprise using AWE memory, be sure to install the memory
hotifx.
d.
"Eli Milkova" <EliMilkova@.discussions.microsoft.com> wrote in message
news:5C63197D-3BB5-4140-97A8-02A5B6CA5278@.microsoft.com...
> Im getting
> The Scheduler 0 appears to be hung. SPID 6, ECID 0, UMS Context
0x03D15418.
> Error: 17883, Severity: 1, State: 0
> Dont know about other compliants and no performance issues so far.
> The server is mssql 2000,multiinstance&multidatabase on w2k3. One of dbs
is
> ARCServe
> In most of the cases this error appears just after the start&finish of
> ARCServe jobs. Ideas how to fix the problem will be appreciated. Thanks.
>|||sp4 fix the issue completely
"d" wrote:
> SP4
> !!!! only fix!!!!
> If you are enterprise using AWE memory, be sure to install the memory
> hotifx.
> d.
> "Eli Milkova" <EliMilkova@.discussions.microsoft.com> wrote in message
> news:5C63197D-3BB5-4140-97A8-02A5B6CA5278@.microsoft.com...
> > Im getting
> > The Scheduler 0 appears to be hung. SPID 6, ECID 0, UMS Context
> 0x03D15418.
> > Error: 17883, Severity: 1, State: 0
> > Dont know about other compliants and no performance issues so far.
> > The server is mssql 2000,multiinstance&multidatabase on w2k3. One of dbs
> is
> > ARCServe
> > In most of the cases this error appears just after the start&finish of
> > ARCServe jobs. Ideas how to fix the problem will be appreciated. Thanks.
> >
>
>|||Hi Eli,
Did installing SQL 2000 SP4 fix your issue? WE have SP4 installed on
all of our databases and still getting database corruption.
Thanks!
Louise.
Eli Milkova wrote:
> sp4 fix the issue completely
> "d" wrote:
> > SP4
> > !!!! only fix!!!!
> >
> > If you are enterprise using AWE memory, be sure to install the memory
> > hotifx.
> >
> > d.
> > "Eli Milkova" <EliMilkova@.discussions.microsoft.com> wrote in message
> > news:5C63197D-3BB5-4140-97A8-02A5B6CA5278@.microsoft.com...
> > > Im getting
> > > The Scheduler 0 appears to be hung. SPID 6, ECID 0, UMS Context
> > 0x03D15418.
> > > Error: 17883, Severity: 1, State: 0
> > > Dont know about other compliants and no performance issues so far.
> > > The server is mssql 2000,multiinstance&multidatabase on w2k3. One of dbs
> > is
> > > ARCServe
> > > In most of the cases this error appears just after the start&finish of
> > > ARCServe jobs. Ideas how to fix the problem will be appreciated. Thanks.
> > >
> >
> >
> >

Wednesday, March 21, 2012

Error 14258

Hi,
The SQLServerAgent has NOT started properly after a
shutdown/reboot two days ago. If you look at the service
manager, the service appears to have started, but its
really not.
Here is what you have to do:
Stop the SQLServerAgent (Not SQL Server)
Restart the service (make no errors are recorded)
Here is something else you may have not noticed, since
this error has been occurring, your scheduled jobs have
not run. You might want to backup your databases and run
any other jobs you may have.
hth
DeeJay
>--Original Message--
>For the last two days I've been getting this error
whenever I click on a Job
>in Enterprise Manager:
>Error 14258: Cannot perform this operation while
SQLServerAgent is starting.
>Try again later.
>Any idea what is causing this? Agent appears to be
running - it is
>performing the assigned tasks on schedule.
>
>.
>
OK I've stopped and restarted the service several times. Event Viewer claims
the service started succesfully. Where else can I look for errors? The SQL
Server logs show no errors with the Agent. But you are correct - the jobs
are NOT running! Any other sugggestions on where to look for the problem?
"DeeJay Puar" <deejaypuar@.Yahoo.com> wrote in message
news:393601c48f89$d0181ff0$a501280a@.phx.gbl...[vbcol=seagreen]
> Hi,
> The SQLServerAgent has NOT started properly after a
> shutdown/reboot two days ago. If you look at the service
> manager, the service appears to have started, but its
> really not.
> Here is what you have to do:
> Stop the SQLServerAgent (Not SQL Server)
> Restart the service (make no errors are recorded)
> Here is something else you may have not noticed, since
> this error has been occurring, your scheduled jobs have
> not run. You might want to backup your databases and run
> any other jobs you may have.
> hth
> DeeJay
> whenever I click on a Job
> SQLServerAgent is starting.
> running - it is

Error 14258

Hi,
The SQLServerAgent has NOT started properly after a
shutdown/reboot two days ago. If you look at the service
manager, the service appears to have started, but its
really not.
Here is what you have to do:
Stop the SQLServerAgent (Not SQL Server)
Restart the service (make no errors are recorded)
Here is something else you may have not noticed, since
this error has been occurring, your scheduled jobs have
not run. You might want to backup your databases and run
any other jobs you may have.
hth
DeeJay
>--Original Message--
>For the last two days I've been getting this error
whenever I click on a Job
>in Enterprise Manager:
>Error 14258: Cannot perform this operation while
SQLServerAgent is starting.
>Try again later.
>Any idea what is causing this? Agent appears to be
running - it is
>performing the assigned tasks on schedule.
>
>.
>OK I've stopped and restarted the service several times. Event Viewer claims
the service started succesfully. Where else can I look for errors? The SQL
Server logs show no errors with the Agent. But you are correct - the jobs
are NOT running! Any other sugggestions on where to look for the problem?
"DeeJay Puar" <deejaypuar@.Yahoo.com> wrote in message
news:393601c48f89$d0181ff0$a501280a@.phx.gbl...[vbcol=seagreen]
> Hi,
> The SQLServerAgent has NOT started properly after a
> shutdown/reboot two days ago. If you look at the service
> manager, the service appears to have started, but its
> really not.
> Here is what you have to do:
> Stop the SQLServerAgent (Not SQL Server)
> Restart the service (make no errors are recorded)
> Here is something else you may have not noticed, since
> this error has been occurring, your scheduled jobs have
> not run. You might want to backup your databases and run
> any other jobs you may have.
> hth
> DeeJay
> whenever I click on a Job
> SQLServerAgent is starting.
> running - it is

Monday, March 19, 2012

error 1203 (SQL Server 6.5)

who knows's the cause of error: 'Caller of lock manager is trying to
unlock an unlocked object' . This error appears 200 time per second.
configuration: SQL 6.5 SP 5 / NT 4 SP6Check the article at
http://support.microsoft.com/default.aspx?scid=kb;en-us;175887, I think it
can help you.
--
Dejan Sarka, SQL Server MVP
FAQ from Neil & others at: http://www.sqlserverfaq.com
Please reply only to the newsgroups.
PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"marijn" <mklijs@.ons.nl> wrote in message
news:d35da914.0307280159.7819b3a7@.posting.google.com...
> who knows's the cause of error: 'Caller of lock manager is trying to
> unlock an unlocked object' . This error appears 200 time per second.
> configuration: SQL 6.5 SP 5 / NT 4 SP6

Tuesday, March 27, 2012

Error 17883 The Scheduler 0 appears to be hung:add information

Error 17883 The Scheduler 0 appears to be hung:add information

Error 17883 The Scheduler 0 appears to be hung

Error 17883 The Scheduler 0 appears to be hung

Error 17883 The Scheduler 0 appears to be hung

Error 17883 - Scheduler appears to be hung - related to linked server or HT??

error 17883

Monday, March 26, 2012

error 17883

error 17883

Wednesday, March 21, 2012

Error 14258

Error 14258

Monday, March 19, 2012

error 1203 (SQL Server 6.5)

sql error 15138

Blog Archive

About Me