Susan
Fri Jul 11 14:52:09 CDT 2003
That's SBS's TS/Exchange falling over themselves and it seems to be a byproduct of SP4. It's not caused by
SP4 per se...I've just been seeing a fair number of happenings of it post SP4 install ...doesn't happen
100% of the time either...but it's one of those ...oh my gosh what have I just done to my SBS box sort of
issues that once we know that it's normal the heartbeat goes down accordingly....
If it's working now...IMHO don't fix it but just file it in the back of your mind....
Mark Adams wrote:
> Well, actually I notice that SP4 is installed. I don't really remember
> doing it, but then HFNetchk seems to do all this stuff for me nowadays.
>
> Incidentally, I re-ran the ICW and it seems to have resolved the problem --
> I can connect via term services once again. Now, in your opinion, do I need
> to implement Q154596?
>
> And how about those Exchange stores mysteriously shutting down?
>
> Thanks!
>
> Mark
>
> "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@pacbell.net>
> wrote in message news:3F0DC30A.F6728C49@pacbell.net...
> > Terminal Server keeps indicating that the TS server is busy?:
> >
>
http://www.smallbizserver.net/SBS2000/Terminal_Server_keeps_indicating_that_the_TS_server_is_busy.aspx
> >
> > Lemme guess...you recently applied SP4?
> >
> > Mark Adams wrote:
> >
> > > Lots of peculiar stuff. Yesterday I had to reset the Linksys router and
> > > manually restart the Exchange mailbox and Public Folder stores. Today,
> I
> > > had to manually restart the stores again (the checkbox in their
> properties
> > > setting them not to restart automatically is not, repeat not, checked).
> > > Just for good measure I rebooted the machine.
> > >
> > > When the machine came back up, I couldn't connect my terminal services
> > > client. There is nothing in the event log that indicates any obvious
> > > problem with either the Exchange server or terminal services, but when I
> try
> > > the connection I get the error message, "The client could not connect to
> the
> > > Terminal Server. The server may be too busy. Please try connecting
> later."
> > > Of course, waiting until later hasn't helped.
> > >
> > > I found MSKB article 260746, but it dosn't seem to be any help. The IP
> > > address of the server resolves just fine. I even reinstalled term.
> services
> > > and created a new connection just out of curiousity.
> > >
> > > Any help here? I really need term services back and I want to know why
> > > these stores keep shutting down.
> > >
> > > Thanks.
> > >
> > > Mark
> >