Optimization job failing

I have scheduled the optimization job to run everyday and sometimes it fails
.
I get this:
Executed as user: test\test. ConnectionCheckForData (CheckforData()).
{SQLSTATE 01000} (Message 10054) General network error. Check your netw
ork
documentation. {SQLSTATE 08S01} (Error 11). The step failed.
It does not fail every night. I had it scheduled to run once a week, but it
was taken a long time to run so I thought I would run it more often to reduc
e
the time.
Also, I notice that when the optimization job is running the transaction log
backup fails.
Any help would be greatly appreciated.
Thank you!Are you having network problems sporadically? Run ping -t all night several
nights in a row (dump to a text file) and see if you have any 'blips" in
connectivity.
"Orn" wrote:

> I have scheduled the optimization job to run everyday and sometimes it fai
ls.
> I get this:
> Executed as user: test\test. ConnectionCheckForData (CheckforData()).
> {SQLSTATE 01000} (Message 10054) General network error. Check your ne
twork
> documentation. {SQLSTATE 08S01} (Error 11). The step failed.
> It does not fail every night. I had it scheduled to run once a week, but
it
> was taken a long time to run so I thought I would run it more often to red
uce
> the time.
> Also, I notice that when the optimization job is running the transaction l
og
> backup fails.
> Any help would be greatly appreciated.
> Thank you!|||ok, i will try that.
Can you tell me what the network would have to do with an optimization job
running locally on the SQL server?
Thank you.
"Donna Lambert" wrote:
[vbcol=seagreen]
> Are you having network problems sporadically? Run ping -t all night sever
al
> nights in a row (dump to a text file) and see if you have any 'blips" in
> connectivity.
>
> "Orn" wrote:
>