We're running SQL Server 2K sp3a on 2003 Server. Our user databases are on
an HP SAN. During heavy data warehouse ETL DTS operations we occasionally
get I/O errors such as:
DTSRun OnError: DTSStep_DTSExecuteSQLTask_2, Error = -2147467259 (80004005)
Error string: I/O error (bad page ID) detected during read at offset
0x0000020a472000 in file 'W:\SQLServer\Data\ColleagueRaw_Data.MDF'.
Running DBCC CHECKDB after a processing failure sometimes shows consistency
errors with the table associated with the I/O failure. Running DBCC again
without the REPAIR_REBUILD option will then not show any errors.
Running SQLIOStress fails with stale read errors such as:
ERROR: Stale read check failure. Page image returned does not match
previous write.
Running SQLIOStress on different boxes against the SAN results in the same
errors. Write caching is not enabled on the SAN.
Does anyone have any ideas'
Thanks much!whit wrote:
> We're running SQL Server 2K sp3a on 2003 Server. Our user databases
> are on an HP SAN. During heavy data warehouse ETL DTS operations we
> occasionally get I/O errors such as:
> DTSRun OnError: DTSStep_DTSExecuteSQLTask_2, Error = -2147467259
> (80004005) Error string: I/O error (bad page ID) detected during
> read at offset 0x0000020a472000 in file
> 'W:\SQLServer\Data\ColleagueRaw_Data.MDF'.
> Running DBCC CHECKDB after a processing failure sometimes shows
> consistency errors with the table associated with the I/O failure.
> Running DBCC again without the REPAIR_REBUILD option will then not
> show any errors.
> Running SQLIOStress fails with stale read errors such as:
> ERROR: Stale read check failure. Page image returned does not match
> previous write.
> Running SQLIOStress on different boxes against the SAN results in the
> same errors. Write caching is not enabled on the SAN.
> Does anyone have any ideas'
Looks like a MS PSS (http://support.microsoft.com) case, they should be able
to help you.
You may also want to read this:
PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O
Problems
http://support.microsoft.com/defaul...kb;en-us;826433
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label heavy. Show all posts
Showing posts with label heavy. Show all posts
Sunday, March 11, 2012
Friday, March 9, 2012
Error 444 - Permission denied.
OK, I'm at a complete loss. Any advice on the following would be greatly
appreciated. What I've got is multiple reports that are heavy process
intensive(multiple datasets, multiple joins, etc). Reports usually take
between 25 and 35 minutes. All was fine until yesterday. Now the reports seem
to run forever. Then finally after an hour we get a 444 error and a
permission denied dialog box. These reports have been running for months
without issue. We've even gone so far as to switch to a new server and still
get the same errors.
Any suggestions?Can you launch SQL Profiler and run a trace and see what connection
credentials are being presented to the dataserver and what the
queries/sprocs are? After capturing the trace you should be able to open
the trace and replay it. My guess is that it is not a SQL issue but this
will help confirm that.
I tried to do some looking up on what error 444 means, is that from MS SQL,
or DB2? or from IIS? Also can you open the Add/Remove Programs, check the
'show updates' box and look for updates installed around the same time as
when the problem started occuring. I've been keeping our machines up to
date and haven't had issue, so not much help here, sorry.
Steve MunLeeuw
"dbutler" <dbutler@.discussions.microsoft.com> wrote in message
news:52C330E6-AEBE-4B59-91C6-99F4E8FD5574@.microsoft.com...
> OK, I'm at a complete loss. Any advice on the following would be greatly
> appreciated. What I've got is multiple reports that are heavy process
> intensive(multiple datasets, multiple joins, etc). Reports usually take
> between 25 and 35 minutes. All was fine until yesterday. Now the reports
> seem
> to run forever. Then finally after an hour we get a 444 error and a
> permission denied dialog box. These reports have been running for months
> without issue. We've even gone so far as to switch to a new server and
> still
> get the same errors.
> Any suggestions?|||I'd also use the RS 2005 Configuration tool to check what accounts are used,
and if they have had a password change or expire. Maybe it's a private key
backup issue...grasping at straws.
Steve MunLeeuw
"dbutler" <dbutler@.discussions.microsoft.com> wrote in message
news:52C330E6-AEBE-4B59-91C6-99F4E8FD5574@.microsoft.com...
> OK, I'm at a complete loss. Any advice on the following would be greatly
> appreciated. What I've got is multiple reports that are heavy process
> intensive(multiple datasets, multiple joins, etc). Reports usually take
> between 25 and 35 minutes. All was fine until yesterday. Now the reports
> seem
> to run forever. Then finally after an hour we get a 444 error and a
> permission denied dialog box. These reports have been running for months
> without issue. We've even gone so far as to switch to a new server and
> still
> get the same errors.
> Any suggestions?|||Thanks Steve. It ended up being exactly that. We switched to a new server,
but our network guy swapped one of the harddrives so it was still 'linked' to
the old server. Once we updated a few keys and played around with RS, we got
it back to working.
"Steve MunLeeuw" wrote:
> I'd also use the RS 2005 Configuration tool to check what accounts are used,
> and if they have had a password change or expire. Maybe it's a private key
> backup issue...grasping at straws.
> Steve MunLeeuw
> "dbutler" <dbutler@.discussions.microsoft.com> wrote in message
> news:52C330E6-AEBE-4B59-91C6-99F4E8FD5574@.microsoft.com...
> > OK, I'm at a complete loss. Any advice on the following would be greatly
> > appreciated. What I've got is multiple reports that are heavy process
> > intensive(multiple datasets, multiple joins, etc). Reports usually take
> > between 25 and 35 minutes. All was fine until yesterday. Now the reports
> > seem
> > to run forever. Then finally after an hour we get a 444 error and a
> > permission denied dialog box. These reports have been running for months
> > without issue. We've even gone so far as to switch to a new server and
> > still
> > get the same errors.
> >
> > Any suggestions?
>
>
appreciated. What I've got is multiple reports that are heavy process
intensive(multiple datasets, multiple joins, etc). Reports usually take
between 25 and 35 minutes. All was fine until yesterday. Now the reports seem
to run forever. Then finally after an hour we get a 444 error and a
permission denied dialog box. These reports have been running for months
without issue. We've even gone so far as to switch to a new server and still
get the same errors.
Any suggestions?Can you launch SQL Profiler and run a trace and see what connection
credentials are being presented to the dataserver and what the
queries/sprocs are? After capturing the trace you should be able to open
the trace and replay it. My guess is that it is not a SQL issue but this
will help confirm that.
I tried to do some looking up on what error 444 means, is that from MS SQL,
or DB2? or from IIS? Also can you open the Add/Remove Programs, check the
'show updates' box and look for updates installed around the same time as
when the problem started occuring. I've been keeping our machines up to
date and haven't had issue, so not much help here, sorry.
Steve MunLeeuw
"dbutler" <dbutler@.discussions.microsoft.com> wrote in message
news:52C330E6-AEBE-4B59-91C6-99F4E8FD5574@.microsoft.com...
> OK, I'm at a complete loss. Any advice on the following would be greatly
> appreciated. What I've got is multiple reports that are heavy process
> intensive(multiple datasets, multiple joins, etc). Reports usually take
> between 25 and 35 minutes. All was fine until yesterday. Now the reports
> seem
> to run forever. Then finally after an hour we get a 444 error and a
> permission denied dialog box. These reports have been running for months
> without issue. We've even gone so far as to switch to a new server and
> still
> get the same errors.
> Any suggestions?|||I'd also use the RS 2005 Configuration tool to check what accounts are used,
and if they have had a password change or expire. Maybe it's a private key
backup issue...grasping at straws.
Steve MunLeeuw
"dbutler" <dbutler@.discussions.microsoft.com> wrote in message
news:52C330E6-AEBE-4B59-91C6-99F4E8FD5574@.microsoft.com...
> OK, I'm at a complete loss. Any advice on the following would be greatly
> appreciated. What I've got is multiple reports that are heavy process
> intensive(multiple datasets, multiple joins, etc). Reports usually take
> between 25 and 35 minutes. All was fine until yesterday. Now the reports
> seem
> to run forever. Then finally after an hour we get a 444 error and a
> permission denied dialog box. These reports have been running for months
> without issue. We've even gone so far as to switch to a new server and
> still
> get the same errors.
> Any suggestions?|||Thanks Steve. It ended up being exactly that. We switched to a new server,
but our network guy swapped one of the harddrives so it was still 'linked' to
the old server. Once we updated a few keys and played around with RS, we got
it back to working.
"Steve MunLeeuw" wrote:
> I'd also use the RS 2005 Configuration tool to check what accounts are used,
> and if they have had a password change or expire. Maybe it's a private key
> backup issue...grasping at straws.
> Steve MunLeeuw
> "dbutler" <dbutler@.discussions.microsoft.com> wrote in message
> news:52C330E6-AEBE-4B59-91C6-99F4E8FD5574@.microsoft.com...
> > OK, I'm at a complete loss. Any advice on the following would be greatly
> > appreciated. What I've got is multiple reports that are heavy process
> > intensive(multiple datasets, multiple joins, etc). Reports usually take
> > between 25 and 35 minutes. All was fine until yesterday. Now the reports
> > seem
> > to run forever. Then finally after an hour we get a 444 error and a
> > permission denied dialog box. These reports have been running for months
> > without issue. We've even gone so far as to switch to a new server and
> > still
> > get the same errors.
> >
> > Any suggestions?
>
>
Subscribe to:
Posts (Atom)