C
Calvin Lo
Hi, we have a really intriguing issue that started recently.
Outlook users, when clicking on an item in the Mailbox, will get the message
"Can't open this item. The operation could not be completed because of an
error on the network. Try to log on to the network again, and then repeat
the operation."
The user will click OK, and usually will be able to open the same item in
one or two attempts.
The Envrionment: Ex5.5 SP4, Outlook 2000.
It is ONLY the Windows98 users that is seeing this message, on NT and W2k
stations, there's this occassional hour-glass when we click on an item, but
eventually the item will be open.
My conjecture is that 'inactive' outlook clients will have to re-establish
their connections with the Ex server (via server port 1057 and 1068). And
W98 couldn't tolerate the time needed for the re-establishment and throw up
that message. While NT and W2k just throw up the hour-glass.
Any ideas? Is there a registry value on W98 that I can adjust to make it
more tolerate? Like TcpKeepCnt
If the conjecture above is true, another question is why would this
suddently started to happen? The W98 users does not have that problem since
recently- when our WINS server has to be restarted, and the Master Browser
was a 'bad' candidate -- these were corrected.
We also reapplied SP4 on Ex without running the optimizer- will that cause
issues?
Thnx!
Calvin
Outlook users, when clicking on an item in the Mailbox, will get the message
"Can't open this item. The operation could not be completed because of an
error on the network. Try to log on to the network again, and then repeat
the operation."
The user will click OK, and usually will be able to open the same item in
one or two attempts.
The Envrionment: Ex5.5 SP4, Outlook 2000.
It is ONLY the Windows98 users that is seeing this message, on NT and W2k
stations, there's this occassional hour-glass when we click on an item, but
eventually the item will be open.
My conjecture is that 'inactive' outlook clients will have to re-establish
their connections with the Ex server (via server port 1057 and 1068). And
W98 couldn't tolerate the time needed for the re-establishment and throw up
that message. While NT and W2k just throw up the hour-glass.
Any ideas? Is there a registry value on W98 that I can adjust to make it
more tolerate? Like TcpKeepCnt
If the conjecture above is true, another question is why would this
suddently started to happen? The W98 users does not have that problem since
recently- when our WINS server has to be restarted, and the Master Browser
was a 'bad' candidate -- these were corrected.
We also reapplied SP4 on Ex without running the optimizer- will that cause
issues?
Thnx!
Calvin