Tag Archives: delays

Rpcrt4.dll – Pre Service Pack 2 Revision History for Windows 7 SP1, Windows Server 2008 R2 SP1 and Windows Small Business Server 2011 (SBS 2011)

Rpcrt4.dll – Pre Service Pack 2 Revision History for Windows 7 SP1, Windows Server 2008 R2 SP1 and Windows Small Business Server 2011 (SBS 2011)

24-Dec-2013 – 6.1.7601.22550 – Rpcrt4.dll – x86/x64 – http://support.microsoft.com/kb/2916915 – Outlook may take two to three minutes to connect to an Office 365 mailbox

09-Jul-2013 – 6.1.7601.22380 – Rpcrt4.dll – x86/x64 – http://support.microsoft.com/kb/2849470 – MS13-062: Vulnerability in remote procedure call could allow elevation of privilege: August 13, 2013

09-Jul-2013 – 6.1.7601.18205 – Rpcrt4.dll – x86/x64 – http://support.microsoft.com/kb/2849470 – MS13-062: Vulnerability in remote procedure call could allow elevation of privilege: August 13, 2013

11-Jul-2012 – 6.1.7601.22054 – Rpcrt4.dll – x86/x64 – http://support.microsoft.com/kb/2734410 – RPC client application stops responding on a computer that is running Windows Server 2008 R2 or Windows 7

05-Nov-2011 – 6.1.7601.21855 – Rpcrt4.dll – x86/x64 – http://support.microsoft.com/kb/2619234 – A hotfix is available to enable the Association Cookie/GUID that is used by RPC over HTTP to also be used at the RPC layer in Windows 7 and in Windows Server 2008 R2

29-Oct-2011 – 6.1.7601.21849 – Rpcrt4.dll – x86/x64 – http://support.microsoft.com/kb/2637692 – RPC threads may stop responding in Windows 7 or in Windows Server 2008 R2

06-Jan-2011 – 6.1.7601.21635 – Rpcrt4.dll – x86/x64 – http://support.microsoft.com/kb/2457402 – You experience delays with an application or service that uses NTDSA APIs for passing changes from RWDC data centers to RODC data centers

Watchguard XTM Firewall and UTM Appliance – High CPU Usage in the GAV (gateway anti-virus) scand process causes lag and typing delay in Remote Desktop Sessions (RDP) and SIP or VoIP latency issues

Watchguard XTM Firewall and UTM Appliance – High CPU Usage in scand process causes lag and typing delay in Remote Desktop Sessions (RDP).  You may find that remote users report a lag with Remote Desktop Sessions, freezing sessions, black screen and random disconnections.  At around the same time users report these issues you may find that the CPU usage of the scand process on your Watchguard has increased to 100% and the majority of the activity is attributed to the scand process.  You may be able to recreate this issue by browsing websites that utilise lots of Adobe Flash or Media Content as GAV will need to scan all these elements of the web page.  Login to the Watchguard System Manager and then open Firebox System Manager click on Status Report and scroll down the report until you find the Process List (Screenshot Below).  This information will automatically update every 30 seconds so you can see the %CPU column will change and update every 30 seconds.  The top value system shows the overall CPU utilisation and if you look further down you can see which sub processes are actually occupying the CPU time and making up the overall system usage.  In the screenshot below we can see that system is showing 100 % CPU Usage and then further down we can see that the scand process is accounting for 90.99% of this.  When the CPU Usage reaches 100% on the Watchguard unit it may stop forwarding other traffic and this accounts for the lag and jitter we see within the Remote Desktop Session.  Other time sensitive traffic such as VoIP or SIP traffic may also be affected by this issue as the packets are delayed whilst the Firewall recovers from the resource exhaustion.  Users may also report that web pages are slow to load at the time these issues occur where the GAV process is still dealing with the other requests.

Resolution/Workaround:

You can try disabling the GAV (gateway antivirus) for the HTTP and FTP Proxy to ensure that this is the actual cause of your issues, if the problem subsides then you may need to consider updating the XTM OS to the latest release i.e. 11.5.2 and/or adjusting the GAV policy so that it does not scan some content i.e. Images/Text within websites.  You may also need to consider opening a support case with Watchguard to make them aware of this issue, if you have a large number of users then you may even need to consider upgrading your XTM appliance to a larger unit i.e. XTM 23 to XTM 505 or XTM 22 to XTM330 to provide additional processing power (CPU) and system resources to cope with the additional anti-virus scanning requirements.

Watchguard XTM High CPU Usage scand
Watchguard XTM High CPU Usage scand

Windows Vista, Windows Server 2008 and SBS 2008 with Service Pack 2 – You may find that applications stop responding, delays occur during resume from standby and/or files may become corrupt when the computer goes to sleep/hibernate and/or poor AMD processor/chipset performance

A variety of issue exist post service pack 2 with Windows Vista, Windows Server 2008 and Small Business Server 2008, a variety of hotfixes have been released since 2008 to address these issues but you only need to apply the latest to ensure that all subsequent issues are addressed.

 

You should only need to apply the hotfix from KB 980080 to ensure that all the issues below are addressed as this contains the latest versions of the affected files, this can be obtained from http://support.microsoft.com/kb/980080

 

KB 980080 – Files may be corrupted when a computer that is running Windows Vista or Windows Server 2008 enters the sleep mode or the hibernate mode

Info: http://support.microsoft.com/kb/980080

KB 977323 – After you change the SATA mode of disk devices to use the AHCI specification on a Windows Server 2008-based or Windows Vista-based computer, the computer or certain applications randomly stop responding for 60 seconds or longer

Info: http://support.microsoft.com/kb/977323

KB 974073 – An update for the Msahci.sys driver has been released for AMD chipsets

Info: http://support.microsoft.com/kb/974073

KB 971390 – A minor delay occurs when Windows Vista or Windows Server 2008 resumes from sleep if the hard disk is attached to a secondary ATA port

Info: http://support.microsoft.com/kb/971390

Remote Desktop Sessions Pause Or Exhibit Unresponsiveness – Lag Whilst Typing And Session Will Not Accept Mouse Inputs

Remote Desktop Services can be extremely useful, allowing users to access a terminal server or their company desktop computer from another location.  One very common complaint with RDP sessions is screen refresh delays and a delay when typing or trying to click on items using the mouse cursor.  It will appear to most that the session has become unresponsive for a period of 5-20 seconds, after this delay the session will return to normal for a period of several minutes before once again becoming unresponsive.  You may find that this issue becomes more apparent as more users connect to the specific terminal server in question and if all these users utilise several applications (i.e. Outlook, Word and Excel) together.

Causes for poor user experience when connected via RDP are varied but one of the most common is resource exhaustion or contention.  This in turn causes a delay in processing that appears as a pause or unresponsiveness.

Check that your computer or terminal server has sufficient Memory to cope with the current load.

The next thing to verify by using performance monitor is that the PhysicalDisk\% Idle Time is consistently high, that’s correct this should be 90-100% when the server is not very busy.

It is worth running performance monitor using the PhysicalDisk\% Idle Time counter whilst you are seeing the slowdowns, this will help identify if your hard disk or controller are causing contention and in turn the pausing or unresponsiveness.

If you do find that the “%Idle Time” keeps going very low then it’s time to consider some of the options below to help resolve the issue

  • Install a second drive or mirror set, move the Windows Page File to this second disk/array to reduce the load on the drive/array holding your operating system
  • Install additional memory into the computer or server, this will reduce paging to disk and will generally improve overall system performance
  • Migrate to or upgrade your existing RAID controller to a unit that had a Battery Backed Cache (Fast) or Flash Backed Cache (Newer – Faster) to significantly improve performance and alleviate the system
  • Migrate to faster hard disk drives, 7200, 10,000 or 15,000 RPM drives are amongst the fastest.  The SATA interface is slower than the SAS interface but is cheaper.  Try to invest in the fastest drives that you can to future proof the system and avoid future performance issues if you have to scale for more users.
  • Ensure that you have at least 20-25% free disk space on all partitions/drives
  • Defragment all drives on a regular basis to optimise read and write operations
  • A cheap solution for improving disk performance may be to turn on the Hard Disk Cache using “Device Manager” or in the event that you are using a RAID controller without a battery backed Cache module you will need to open the RAID Array Management Software and then enable Disk Cache within the management software as this feature will not be available within “Device Manager” in this instance.  Please note that this does have some risks and should be used with caution, you may loose data in the event of a sudden/unexpected loss of power to the system.  Consider using this option with a UPS and redundant power supplies to reduce the risk of power loss to the system.  As always ensure you have a reliable backup that is carried out at regular intervals.

Example – HP RAID Array Configuration Utility:

Example – Windows Device Manager: