Showing posts with label timeout. Show all posts
Showing posts with label timeout. Show all posts

Wednesday, March 21, 2012

Enterprise Manager Tape Backup issue

I have multiple failed backups jobs through the enterprise manager. I have an
event id 9 "\device\scis\aic78u21 did not respond within the timeout period"
and event id 15 "\device\tape0 is not ready for access yet." The aic78u21 is
the scsi controller and only appeared once. Since then, I have had multiple
event id 15. However I did boot up into the scsi utility and teh dlt tape
device is listed in the utility with scsi id 3, and the controler listed as
scsi id 7. I then ran a ntbackup job on a new media set and it ran fine.
However the scheduled jobs within enterprise manager still will not run. Our
SQL admin is no longer with us, and myself and another have been tasked with
the SQL admin, so we are both leery of making any changes that might have bad
reprecussions later. I thought about deleting and adding the tape device back
into the enterprise manager, but I'm wondering if it is a media set issue.
What do you think?
I forgot to mention that the device does show up in device manager with the
questions marks in the other devices category. Is this due to the device
running off of the scsi controller drivers?
"sigm" wrote:

> I have multiple failed backups jobs through the enterprise manager. I have an
> event id 9 "\device\scis\aic78u21 did not respond within the timeout period"
> and event id 15 "\device\tape0 is not ready for access yet." The aic78u21 is
> the scsi controller and only appeared once. Since then, I have had multiple
> event id 15. However I did boot up into the scsi utility and teh dlt tape
> device is listed in the utility with scsi id 3, and the controler listed as
> scsi id 7. I then ran a ntbackup job on a new media set and it ran fine.
> However the scheduled jobs within enterprise manager still will not run. Our
> SQL admin is no longer with us, and myself and another have been tasked with
> the SQL admin, so we are both leery of making any changes that might have bad
> reprecussions later. I thought about deleting and adding the tape device back
> into the enterprise manager, but I'm wondering if it is a media set issue.
> What do you think?
sql

Enterprise Manager Tape Backup issue

I have multiple failed backups jobs through the enterprise manager. I have a
n
event id 9 "\device\scis\aic78u21 did not respond within the timeout period"
and event id 15 "\device\tape0 is not ready for access yet." The aic78u21 is
the scsi controller and only appeared once. Since then, I have had multiple
event id 15. However I did boot up into the scsi utility and teh dlt tape
device is listed in the utility with scsi id 3, and the controler listed as
scsi id 7. I then ran a ntbackup job on a new media set and it ran fine.
However the scheduled jobs within enterprise manager still will not run. Our
SQL admin is no longer with us, and myself and another have been tasked with
the SQL admin, so we are both leery of making any changes that might have ba
d
reprecussions later. I thought about deleting and adding the tape device bac
k
into the enterprise manager, but I'm wondering if it is a media set issue.
What do you think?I forgot to mention that the device does show up in device manager with the
questions marks in the other devices category. Is this due to the device
running off of the scsi controller drivers?
"sigm" wrote:

> I have multiple failed backups jobs through the enterprise manager. I have
an
> event id 9 "\device\scis\aic78u21 did not respond within the timeout perio
d"
> and event id 15 "\device\tape0 is not ready for access yet." The aic78u21
is
> the scsi controller and only appeared once. Since then, I have had multipl
e
> event id 15. However I did boot up into the scsi utility and teh dlt tape
> device is listed in the utility with scsi id 3, and the controler listed a
s
> scsi id 7. I then ran a ntbackup job on a new media set and it ran fine.
> However the scheduled jobs within enterprise manager still will not run. O
ur
> SQL admin is no longer with us, and myself and another have been tasked wi
th
> the SQL admin, so we are both leery of making any changes that might have
bad
> reprecussions later. I thought about deleting and adding the tape device b
ack
> into the enterprise manager, but I'm wondering if it is a media set issue.
> What do you think?

Enterprise Manager Tape Backup issue

I have multiple failed backups jobs through the enterprise manager. I have an
event id 9 "\device\scis\aic78u21 did not respond within the timeout period"
and event id 15 "\device\tape0 is not ready for access yet." The aic78u21 is
the scsi controller and only appeared once. Since then, I have had multiple
event id 15. However I did boot up into the scsi utility and teh dlt tape
device is listed in the utility with scsi id 3, and the controler listed as
scsi id 7. I then ran a ntbackup job on a new media set and it ran fine.
However the scheduled jobs within enterprise manager still will not run. Our
SQL admin is no longer with us, and myself and another have been tasked with
the SQL admin, so we are both leery of making any changes that might have bad
reprecussions later. I thought about deleting and adding the tape device back
into the enterprise manager, but I'm wondering if it is a media set issue.
What do you think?I forgot to mention that the device does show up in device manager with the
questions marks in the other devices category. Is this due to the device
running off of the scsi controller drivers?
"sigm" wrote:
> I have multiple failed backups jobs through the enterprise manager. I have an
> event id 9 "\device\scis\aic78u21 did not respond within the timeout period"
> and event id 15 "\device\tape0 is not ready for access yet." The aic78u21 is
> the scsi controller and only appeared once. Since then, I have had multiple
> event id 15. However I did boot up into the scsi utility and teh dlt tape
> device is listed in the utility with scsi id 3, and the controler listed as
> scsi id 7. I then ran a ntbackup job on a new media set and it ran fine.
> However the scheduled jobs within enterprise manager still will not run. Our
> SQL admin is no longer with us, and myself and another have been tasked with
> the SQL admin, so we are both leery of making any changes that might have bad
> reprecussions later. I thought about deleting and adding the tape device back
> into the enterprise manager, but I'm wondering if it is a media set issue.
> What do you think?

Monday, March 19, 2012

Enterprise Manager results timeout

Hi -
Often when working on a query or viewing a table in Enterprise Manager, I ge
t messages such as "There has been no recent activity in the results pane" a
nd threatening to clear it. Is there any way to get rid of these messages? I
'm capable of determining w
hen too many resources are in use on the server without the help of these me
ssages.
Thanks,
JimNo...other than using Query Analyzer instead.
The behavior is by design. The following article applies to
SQL Server 2000 as well:
PRB: Table Designer Automatically Clears Results Pane When
Idle
http://support.microsoft.com/?id=252434
-Sue
On Wed, 10 Mar 2004 08:46:23 -0800, "Jim S"
<anonymous@.discussions.microsoft.com> wrote:

>Hi -
>Often when working on a query or viewing a table in Enterprise Manager, I get messa
ges such as "There has been no recent activity in the results pane" and threatening
to clear it. Is there any way to get rid of these messages? I'm capable of determini
ng
when too many resources are in use on the server without the help of these messages.darkred">
>Thanks,
>Jim|||Hi Jim.
We share in your frustration. Have you come up with any solutions yet?
-Dan
****************************************
******************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET
resources...

Enterprise manager query timeout

When I check the server's query timeout on the Server properties /
Connections tab in enterprise manager, it is set to 600 seconds.
Yet when I run a complicated query, it times out after 40 seconds.
The same query takes about a minute in OSQL, and succeeds there.
Is there an additional time-out that EM imposes, and can it be changed?
"Lucvdv" <replace_name@.null.net> wrote in message
news:kpjgh1lgjsqe3boeredlvn7iu5ipr3dp2k@.4ax.com...
> When I check the server's query timeout on the Server properties /
> Connections tab in enterprise manager, it is set to 600 seconds.
> Yet when I run a complicated query, it times out after 40 seconds.
> The same query takes about a minute in OSQL, and succeeds there.
> Is there an additional time-out that EM imposes, and can it be
> changed?
I believe this is a known issue. You should use Query Analyzer for all
your querying rather than going through SQL EM. This problem may have
been addressed in the recent SQL Server service pack (not sure). What SP
are you running on the client?
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||On Fri, 2 Sep 2005 10:34:38 -0400, "David Gugick"
<david.gugick-nospam@.quest.com> wrote:

> "Lucvdv" <replace_name@.null.net> wrote in message
> news:kpjgh1lgjsqe3boeredlvn7iu5ipr3dp2k@.4ax.com...
> I believe this is a known issue. You should use Query Analyzer for all
> your querying rather than going through SQL EM. This problem may have
> been addressed in the recent SQL Server service pack (not sure). What SP
> are you running on the client?
Still SP3 on server and client.
I haven't downloaded SP4 yet because it looked like the changes are mostly
intended for 64 bit systems, I decided to wait until I get it through MSDN.
I'll take your advice and use Query Analyzer.
|||First of all the query time-out setting on the connections tab is only
for remote server queries. From what I understand your running a local
query.
The problem is that EM as a client application has it's own timeout
configuration setting which I admit is rather short. Query Analyzer on
the other hand by default waits as long as it needs, so you won't get
any timeout.
M
|||On 5 Sep 2005 01:03:31 -0700, m.bohse@.quest-consultants.com wrote:

> First of all the query time-out setting on the connections tab is only
> for remote server queries. From what I understand your running a local
> query.
> The problem is that EM as a client application has it's own timeout
> configuration setting which I admit is rather short. Query Analyzer on
> the other hand by default waits as long as it needs, so you won't get
> any timeout.
I found the setting, Tools -> Options -> Advanced -> Connection settings,
the default is 0 = infinite (says online help).
Trying to override it (I set it to 600 seconds) makes no difference.
I upgraded to SP4, and it's still the same