From: mrceolla on
Hello again,

Well, that error hasn't happened in a few days. My wild guess is that
adding RAM to the machine (went from 4 to 12) must have changed
something. And the only reason I attribute it to the RAM is because
the day after I added the RAM is when the errors stopped. Of course
it could've been something else I did but I hadn't performed any
additional troubleshooting steps between the last time I got the error
and when I put the RAM in. Oh well. At least it's gone.

Thanks again for all of your help/advise.

Have a great day!

Mike

From: Dave Nickason [SBS MVP] on
Interesting. I wonder if the extra performance from the added RAM made the
difference, especially since the original error message referenced a
timeout. Anyway, glad you got it sorted out, and thanks for the update.


"mrceolla" <mrceolla(a)gmail.com> wrote in message
news:cdb88610-c9ee-4be0-819b-f3ab7ba9c776(a)o10g2000yqa.googlegroups.com...
> Hello again,
>
> Well, that error hasn't happened in a few days. My wild guess is that
> adding RAM to the machine (went from 4 to 12) must have changed
> something. And the only reason I attribute it to the RAM is because
> the day after I added the RAM is when the errors stopped. Of course
> it could've been something else I did but I hadn't performed any
> additional troubleshooting steps between the last time I got the error
> and when I put the RAM in. Oh well. At least it's gone.
>
> Thanks again for all of your help/advise.
>
> Have a great day!
>
> Mike
>