B
bernardl
I'm sure that anyone who uses Outlook with Exchange has seen this error
before. I have an Exchange2k server with a mix of WinXP and Win2k
workstations running Outlook XP.
We get these messages often and they seem to be getting worse. I thought it
may be too much stress on the server since it runs as on SBS but the cpu%
runs normally. Any ideas? I don't know if I should target the server or the
rest of the network.
before. I have an Exchange2k server with a mix of WinXP and Win2k
workstations running Outlook XP.
We get these messages often and they seem to be getting worse. I thought it
may be too much stress on the server since it runs as on SBS but the cpu%
runs normally. Any ideas? I don't know if I should target the server or the
rest of the network.