Terminal Server - Opening & closing attachment freezes GW

Question

Hello,
we are running a Terminal Server Farm on Windows 2008 R2 with GroupWise 2012 SP2.
All of our users have problems when opening an attachment (PDF, DOC, XLS...) from a mail and closing the opened Application (Word, Acrobat Reader, Excel....). After closing the Application GroupWize freezes for some seconds. If you click anything in GroupWise in this time, GroupWise crashes.
You've to wait up to 10-15 seconds until you can do something in GroupWise.
Our Users are really "nerved" about this situation. This problem still exists an all of our Terminal Servers.
Any Ideas what we can do ?
Regards.

Answer 1

Originally Posted by konecnya
In article <[email protected]>, DavudOeden wrote:[color=blue]
I don't see this on the single Windows 2008 R2 Standard TS with GroupWise
2012 SP2, client build 108211.
This does feel more like a Windows/ Windows app (GW client or other)
issue, so I would certainly check the Windows event logs for any clues.
- If you are at the primary console of any of the servers (i.e. Physically
at the box or vm equivalent), does the same problem still happen?
- Doe the POA logs show anything when this happens? Especially if you turn
up the logging to verbose.
- Try disabling the anti-virus for a test in case it is part of this.
- Make sure the TEMP folders are getting cleared periodically.
- To eliminate the issue of crud collecting in profiles, setup a new user,
both GW and on the Terminal Server, and see if it can be reproduced with
those ID.
[color=blue]
Hello,
thanks for you're reply.
- The Problem still happens on the "physical" console.
- The Windows Event Logs does not show anything. It's only a freeze which
can take up to 10 seconds and more. After this time, GroupWise works fine again.
Most times it takes only a few seconds.
- The Temp Folders are cleaned at logoff ("C:\Users\USERNAME\AppData\Local\Temp\xxxxxxx" ).
There are up to 4 GroupWise Directorys (XPgrpwise, XPGWSync, XpGWViews & XPNotify). They are not roaming.
- I've tested this with an absolutely new created user. Same Problem.
- Tested on an absolute new TerminalServer. Same Problem.
But what I figured out, if there are only a few users connected to the server, the problem is not noticeable.
The more users are connected to the server, the higher the possibility that this freeze problems occur.
I'm going to check the groupwise POA logs, but I dont think that there will be log entrys about this problem.
I've installed yesterday the groupwise client build 112764. I'm going to test today if the newer build
makes the same problem. At the moment there are not enough users logged in to test it.
Kindest regards for your tips,
I hope we're going to figure out the problem :-)
D. Oeden