"Stingray" wrote:

> I hope this is the correct forum for this question. We have been having
> problems for several months, getting progressively worse, with Oulook 2003
> users reporting connection problems with our Exchange 2000 server (Outlook is
> retrieving data from the Microsoft Exchange Server).
>
> We started troubleshooting that issue via the Knowledgebase and have made a
> few changes to the Exchange server such as moving some applications that were
> running on the same drive as the Transaction Logs to a different disk. We
> were still having problems though so we started looking at the Exchange
> server and running some Perfmon logging to track down the problem.
>
> The perfmon logs show that the LSASS service is pegging utilization
> frequently, sometimes for a moment and sometimes for longer and it appears
> that our Outlook connectivity issues occur when the utilization stays at 100%
> for a significant length of time.
>
> So far we've tried adjusting the Exchange IS Maintenance schedules to run
> only after hours and we've tried turning off our email virus scanning (Trend
> ScanMail version 7) for a few minutes and tracking the CPU utilization. Even
> with Trend off, we still see the same spikes in utilization and Outlook
> hangups.
>
> I wondered if anyone out there has seen anything like this or has any tips
> on how to figure out what is causing the LSASS service to hog the CPU? I've
> run out of ideas and thought I'd try here before I pay for the call to PSS.

"Dave Allonby" wrote:

> Hi Stingray,
> What is your server operating system?
>
> Cheers
> Dave Allonby
>
> "Stingray" wrote:
>
> > I hope this is the correct forum for this question. We have been having
> > problems for several months, getting progressively worse, with Oulook 2003
> > users reporting connection problems with our Exchange 2000 server (Outlook is
> > retrieving data from the Microsoft Exchange Server).
> >
> > We started troubleshooting that issue via the Knowledgebase and have made a
> > few changes to the Exchange server such as moving some applications that were
> > running on the same drive as the Transaction Logs to a different disk. We
> > were still having problems though so we started looking at the Exchange
> > server and running some Perfmon logging to track down the problem.
> >
> > The perfmon logs show that the LSASS service is pegging utilization
> > frequently, sometimes for a moment and sometimes for longer and it appears
> > that our Outlook connectivity issues occur when the utilization stays at 100%
> > for a significant length of time.
> >
> > So far we've tried adjusting the Exchange IS Maintenance schedules to run
> > only after hours and we've tried turning off our email virus scanning (Trend
> > ScanMail version 7) for a few minutes and tracking the CPU utilization. Even
> > with Trend off, we still see the same spikes in utilization and Outlook
> > hangups.
> >
> > I wondered if anyone out there has seen anything like this or has any tips
> > on how to figure out what is causing the LSASS service to hog the CPU? I've
> > run out of ideas and thought I'd try here before I pay for the call to PSS.

"Stingray" wrote:

> Windows 2000 SP4
> Exchange 2000 SP3
>
>
> "Dave Allonby" wrote:
>
> > Hi Stingray,
> > What is your server operating system?
> >
> > Cheers
> > Dave Allonby
> >
> > "Stingray" wrote:
> >
> > > I hope this is the correct forum for this question. We have been having
> > > problems for several months, getting progressively worse, with Oulook 2003
> > > users reporting connection problems with our Exchange 2000 server (Outlook is
> > > retrieving data from the Microsoft Exchange Server).
> > >
> > > We started troubleshooting that issue via the Knowledgebase and have made a
> > > few changes to the Exchange server such as moving some applications that were
> > > running on the same drive as the Transaction Logs to a different disk. We
> > > were still having problems though so we started looking at the Exchange
> > > server and running some Perfmon logging to track down the problem.
> > >
> > > The perfmon logs show that the LSASS service is pegging utilization
> > > frequently, sometimes for a moment and sometimes for longer and it appears
> > > that our Outlook connectivity issues occur when the utilization stays at 100%
> > > for a significant length of time.
> > >
> > > So far we've tried adjusting the Exchange IS Maintenance schedules to run
> > > only after hours and we've tried turning off our email virus scanning (Trend
> > > ScanMail version 7) for a few minutes and tracking the CPU utilization. Even
> > > with Trend off, we still see the same spikes in utilization and Outlook
> > > hangups.
> > >
> > > I wondered if anyone out there has seen anything like this or has any tips
> > > on how to figure out what is causing the LSASS service to hog the CPU? I've
> > > run out of ideas and thought I'd try here before I pay for the call to PSS.