|
Home > Archive > MS SQL Server > October 2006 > SQL 2000 - Scheduled Job causes system errors
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SQL 2000 - Scheduled Job causes system errors
|
|
| Andrew 2006-10-24, 6:38 pm |
| I have a scheduled job that is causing errors in the System Event Log, and I
don't know why.
The job is a DTS package that has two steps -- first step connects to our
AS400 and copies down data, the second step takes that data an formats it
for later use. Whether running the DTS manually, or letting it run as a
scheduled job, it completes just fine, all data is there, no errors in the
SQL Server error logs, all peachy. When the DTS package is run as a
scheduled job, during _only_ the first step, the System Event Log starts
rapid fire spitting out the following error:
Source: Disk
Type: Warning
Category: None
Event ID: 51
User: N/A
Description: An error was detected on device \Device\Harddisk1 during a
paging operation.
The error shows up 20 to 30 times per second every 3 to 4 seconds for the
duration of only the first step of the job. Again, this is only when the
job runs as a scheduled job... no errors appear if I run the DTS package
manually from the DTS designer.
And regardless - scheduled, manually - the job finishes just fine.
I literally have no idea why, what, how this is happening. Has anyone run
into this behavior or issue?
Our SQL Server box:
Microsoft SQL Server 2000 (SP3)
Microsoft Windows Server 2003 Standard Edition (SP1)
Dual 3GHz Intel Xeon Procs
4GB RAM
130GB on O/S drive (100+ free)
550GB on Data drive (300+ free)
-- Andrew
| |
| John Bell 2006-10-24, 6:38 pm |
| Hi Andrew
What account is SQL Agent running under and are you logged in as that
account when you manually run the package?
John
"Andrew" wrote:
> I have a scheduled job that is causing errors in the System Event Log, and I
> don't know why.
>
> The job is a DTS package that has two steps -- first step connects to our
> AS400 and copies down data, the second step takes that data an formats it
> for later use. Whether running the DTS manually, or letting it run as a
> scheduled job, it completes just fine, all data is there, no errors in the
> SQL Server error logs, all peachy. When the DTS package is run as a
> scheduled job, during _only_ the first step, the System Event Log starts
> rapid fire spitting out the following error:
>
> Source: Disk
> Type: Warning
> Category: None
> Event ID: 51
> User: N/A
> Description: An error was detected on device \Device\Harddisk1 during a
> paging operation.
>
> The error shows up 20 to 30 times per second every 3 to 4 seconds for the
> duration of only the first step of the job. Again, this is only when the
> job runs as a scheduled job... no errors appear if I run the DTS package
> manually from the DTS designer.
>
> And regardless - scheduled, manually - the job finishes just fine.
>
> I literally have no idea why, what, how this is happening. Has anyone run
> into this behavior or issue?
>
> Our SQL Server box:
> Microsoft SQL Server 2000 (SP3)
> Microsoft Windows Server 2003 Standard Edition (SP1)
> Dual 3GHz Intel Xeon Procs
> 4GB RAM
> 130GB on O/S drive (100+ free)
> 550GB on Data drive (300+ free)
>
> -- Andrew
>
>
>
| |
| Andrew 2006-10-24, 6:38 pm |
| SQL Server Agent Properties
- General Tab shows the Service startup account is set to "System Account".
- Connection Tab shows the SQL Server connection account is set to "Use
Windows Authentication".
I am not logged in under this account, I am logged in under my own account
when I run the DTS package. But again, the job runs fine, there is no
errors anywhere within SQL Server, only the "disk" errors in the Event
Viewer - System Event Log when run as a scheduled job, and no errors of any
kind anywhere when I run the DTS package manually.
-- Andrew
"John Bell" < jbellnewsposts@hotma
il.com> wrote in message
news:C59C8E17-D53D-40FD-8424- 5B7A69162276@microso
ft.com...[color=darkred]
> Hi Andrew
>
> What account is SQL Agent running under and are you logged in as that
> account when you manually run the package?
>
> John
>
>
>
> "Andrew" wrote:
>
| |
| John Bell 2006-10-24, 6:38 pm |
| Hi Andrew
Change the account to be a domain account for SQL 2000 see
http://msdn.microsoft.com/library/d...nsetup_9ann.asp
for SQL 2005 see http://msdn2.microsoft.com/en-us/library/ms143504.aspx (I
would not use the network service account either).
John
"Andrew" wrote:
> SQL Server Agent Properties
> - General Tab shows the Service startup account is set to "System Account".
> - Connection Tab shows the SQL Server connection account is set to "Use
> Windows Authentication".
>
> I am not logged in under this account, I am logged in under my own account
> when I run the DTS package. But again, the job runs fine, there is no
> errors anywhere within SQL Server, only the "disk" errors in the Event
> Viewer - System Event Log when run as a scheduled job, and no errors of any
> kind anywhere when I run the DTS package manually.
>
> -- Andrew
>
>
> "John Bell" < jbellnewsposts@hotma
il.com> wrote in message
> news:C59C8E17-D53D-40FD-8424- 5B7A69162276@microso
ft.com...
>
>
>
| |
| Andrew 2006-10-24, 6:38 pm |
| Thanks for the suggestion, and the MSDN link to how, but it leaves me
begging the question... why? Why is running it the way I have on numerous
other boxes now not the way I should?
-- Andrew
"John Bell" < jbellnewsposts@hotma
il.com> wrote in message
news:4F26F807-6401-4332-B234- 8C613AC4CE20@microso
ft.com...[color=darkred]
> Hi Andrew
>
> Change the account to be a domain account for SQL 2000 see
> http://msdn.microsoft.com/library/d...nsetup_9ann.asp
> for SQL 2005 see http://msdn2.microsoft.com/en-us/library/ms143504.aspx (I
> would not use the network service account either).
>
> John
>
> "Andrew" wrote:
>
| |
| John Bell 2006-10-24, 6:38 pm |
| Hi Andrew
Have you check the SQL Agent Proxy Account using xp_sqlagent_proxy_ac
count?
John
"Andrew" wrote:
> Thanks for the suggestion, and the MSDN link to how, but it leaves me
> begging the question... why? Why is running it the way I have on numerous
> other boxes now not the way I should?
>
> -- Andrew
>
> "John Bell" < jbellnewsposts@hotma
il.com> wrote in message
> news:4F26F807-6401-4332-B234- 8C613AC4CE20@microso
ft.com...
>
>
>
| |
| Andrew 2006-10-24, 6:38 pm |
| The result from EXEC master.dbo. xp_sqlagent_proxy_ac
count N'GET' is nothing.
I'm not sure what you're getting at, but ask the question again... why would
I want to change the account SQL Server Agent runs under from the default
account when the server was installed, and is the same setup on all our
other boxes that run just fine?
"John Bell" < jbellnewsposts@hotma
il.com> wrote in message
news:FB31120E-F17D-4237-9D3C- 928510F0A2AD@microso
ft.com...[color=darkred]
> Hi Andrew
>
> Have you check the SQL Agent Proxy Account using
> xp_sqlagent_proxy_ac
count?
>
> John
>
> "Andrew" wrote:
>
| |
| John Bell 2006-10-24, 6:38 pm |
| Hi Andrew
The most likely cause is that this server is not quite the same, therefore
you will need to try and find out what is different. I may not even be the
SQL Server configuration that is different.
John
"Andrew" wrote:
> The result from EXEC master.dbo. xp_sqlagent_proxy_ac
count N'GET' is nothing.
>
> I'm not sure what you're getting at, but ask the question again... why would
> I want to change the account SQL Server Agent runs under from the default
> account when the server was installed, and is the same setup on all our
> other boxes that run just fine?
>
> "John Bell" < jbellnewsposts@hotma
il.com> wrote in message
> news:FB31120E-F17D-4237-9D3C- 928510F0A2AD@microso
ft.com...
>
>
>
| |
| Andrew 2006-10-24, 6:38 pm |
| I have tried changing the account the SQL Server Agent runs under, changed
the schedule so it would run, and there is no difference in that I still get
errors even under the new account.
There is no difference between this SQL Server and any other here. They are
all the same server model, all have the same hardware, same SQL Server
version, service pack, even installed from the same CD.
While I thank you for your suggestions, I can't help but think you are
missing the main issue: Why are we getting Disk errors in the Windows Server
System Event Log (*not* SQL Server's log) when a DTS package is executed
from the Scheduled Jobs but no errors when the *same* DTS package is run
manually from within the DTS Designer?
There are no errors of any kind in the SQL Server Log. The Job completes,
every step of the DTS package executes and does what it is supposed to. All
data is there at the end. Other DTS packages and Scheduled Jobs run fine
with no errors anywhere.
I don't know what else to say, how to say it differently. How can a
scheduled SQL Server job create Operating System errors, while leaving no
errors within SQL Server itself, regardless of the user/system account it
executes under?
We have run hardware and software diagnostics on the server itself and there
are no issues or problems of any kind.
Again, I appreciate the help, but the suggestion of changing the account for
Agent didn't solve the problem, and there is no discernable difference
between this and any other SQL Server box. Is there, are there, any other
items I should check or look at?
-- Andrew
"John Bell" < jbellnewsposts@hotma
il.com> wrote in message
news:F148319B-F02A-44FD-B4A9- 6F4DFCB686FA@microso
ft.com...
> Hi Andrew
>
> The most likely cause is that this server is not quite the same, therefore
> you will need to try and find out what is different. I may not even be the
> SQL Server configuration that is different.
>
> John
>
| |
| John Bell 2006-10-24, 6:38 pm |
| Hi Andrew
But you get no other disc errors at any other time? I assume that you have
checked the hardware? What is harddisk1 and what is on it? Have you tried
other means of re-creating the message such as copying large files around?
Have you checked firmware levels? Also look at:
http://support.microsoft.com/?kbid=834910
http://support.microsoft.com/?kbid=835473
John
"Andrew" wrote:
> I have tried changing the account the SQL Server Agent runs under, changed
> the schedule so it would run, and there is no difference in that I still get
> errors even under the new account.
>
> There is no difference between this SQL Server and any other here. They are
> all the same server model, all have the same hardware, same SQL Server
> version, service pack, even installed from the same CD.
>
> While I thank you for your suggestions, I can't help but think you are
> missing the main issue: Why are we getting Disk errors in the Windows Server
> System Event Log (*not* SQL Server's log) when a DTS package is executed
> from the Scheduled Jobs but no errors when the *same* DTS package is run
> manually from within the DTS Designer?
>
> There are no errors of any kind in the SQL Server Log. The Job completes,
> every step of the DTS package executes and does what it is supposed to. All
> data is there at the end. Other DTS packages and Scheduled Jobs run fine
> with no errors anywhere.
>
> I don't know what else to say, how to say it differently. How can a
> scheduled SQL Server job create Operating System errors, while leaving no
> errors within SQL Server itself, regardless of the user/system account it
> executes under?
>
> We have run hardware and software diagnostics on the server itself and there
> are no issues or problems of any kind.
>
> Again, I appreciate the help, but the suggestion of changing the account for
> Agent didn't solve the problem, and there is no discernable difference
> between this and any other SQL Server box. Is there, are there, any other
> items I should check or look at?
>
> -- Andrew
>
> "John Bell" < jbellnewsposts@hotma
il.com> wrote in message
> news:F148319B-F02A-44FD-B4A9- 6F4DFCB686FA@microso
ft.com...
>
>
|
|
|
|
|