Tag Archives: error

Microsoft Outlook Out of Office (OOF) – Server is Currently Unavailable

When you try and use the Out of Office feature in Microsoft Outlook you may recieve the following error message:

Your automatic reply settings cannot be displayed because the server is currently unavailable.  Try again later.

 

 

 

 

 

 

When you look at the Application Event Log on you Exchange Server you will see Event ID 1310 logged from Source ASP.NET 2.0.50727.0

 

 

 

 

 

Exception information:

Exception type: ConfigurationErrorsException

Exception message: The value for the property ‘maxRequestLength’ is not valid. The error is: The value must be inside the range 0-2097151. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config line 2376)

We need to modify the “web.config” file which can be found here “C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\” you need to open the “web.config” file using Notepad and then use the “find” feature in notepad to quickly locate the following line in the file

<system.web>

<httpRuntime maxRequestLength=”52428800″ />

The default value is to high “52428800” so you need to change it as follows

<system.web>

<httpRuntime maxRequestLength=”2066661″ />

The final step in resolving the issue is to save the changes you have made to the “web.config” file and restarting the “Default Website” under IIS Manager (Administrative Tools)

Watchguard XTM 1050, XTM 2050, XTM 2 Series, XTM 3 Series, XTM 5 Series, XTM 8 Series – Fireware XTM OS 11.6.1 – Build # 346666

Watchguard XTM 1050, XTM 2050, XTM 2 Series, XTM 3 Series, XTM 5 Series, XTM 8 Series – Fireware XTM OS 11.6.1 – Build # 346666

11.6.1 – Build # 346666 Provides some new features and resolves the following issues:

• This release introduces support for the new high-performance XTM 5 Series models 515, 525, 535, and 545

• Provides an update to our localized user interfaces and documentation

• An XTM device configured in bridge mode can now pass VLAN traffic between 802.1Q switches or bridges

• FireCluster support for XTM 25, 26, and 33 wired models

• Several issues have been resolved in this release that caused XTM devices to crash when configured to use Application Control or IPS [66937, 65426, 65636, 67312, 66135, 67159, 67399, 67310]

• An issue was resolved that caused some XTM device processes to crash when running Mu Dynamics default published vulnerability test [66490]

• An issue was resolved that caused a kernel crash and device reboot [67329]

• The XTM 2 Series device can now handle a large file transfer without interface instability [67367]

• A problem that caused incorrect data to display on the XTM 5 Series LCD screen has been resolved [67197]

• Policy Manager now displays the correct VLAN limits for XTM 5 Series models 505, 510, 520, and 530 with a standard Fireware XTM feature key (not Pro) [67780]

• You can now successfully configure and apply Traffic Management actions for XTM 2 and 3 Series devices from the Web UI [67221, 66645]

• Firebox X Edge e-Series devices can now be successfully managed with templates [67658]

• The notification message sent when a local Log or Report database is down now correctly shows the host IP address instead of “???” [41731]

• The Log Server can now handle backup files greater than 2GB in size without generating an error message: “Error (8199), Exception during backup of oldest log data: File is not a zip file” exception” [66811]

• The DHCP lease activity report now works correctly [66062]

• Log Collector now handles XTM device log data that spans multiple SSL/TLS records without crashing [66347]

• A problem has been resolved that caused poor performance on XTM 2 Series models 25 and 26 because of an incorrect memory allocation for security subscription signatures [67240]

• A deny message is now correctly sent to the web browser in most cases when Application Control blocks content in the Web/Web 2.0 category [66201]

• The WebBlocker automatic database update time is no longer off by one hour when daylight savings time is in effect on the host server’s timezone [67551]

• If you use PPPoE or DHCP for an external interface on an XTM device configured to use multi-WAN, the XTM device no longer loses the default routes for external interfaces after the external interface reconnects [67424, 67520]

• A problem has been resolved that caused a static route to fail after an external interface configured to use PPPoE is disconnected, then reconnected [67520]

• Tagged VLAN traffic is now correctly recognized when an XTM device is configured in Bridge mode [64355]

• The CLl command “restore factory default all” now successfully restores a device to its factory default settings [66240]

• An issue has been resolved that caused Policy Manager to incorrectly display an interface IP address as 0.0.0.0/24 when you viewed a FireCluster configuration for a cluster in drop-in mode [63551]

• The Mobile VPN with SSL process no longer crashes during a FireCluster failover [66118]

You can download 11.6.1 – Build # 346666 from the Watchguard website

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

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

31-Jul-2013 – 6.1.7601.22407 – Volsnap.sys – x64 – http://support.microsoft.com/kb/2871085 – I/O failures occur when you create a snapshot for a large volume in Windows Server 2012 or Windows Server 2008 R2 SP1

31-Jul-2013 – 6.1.7601.18226 – Volsnap.sys – x64 – http://support.microsoft.com/kb/2871085 – I/O failures occur when you create a snapshot for a large volume in Windows Server 2012 or Windows Server 2008 R2 SP1

18-Oct-2012 – 6.1.7601.22137 – Volsnap.sys – x86/x64 – https://support.microsoft.com/kb/2775511 – An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1

02-Aug-2012 – 6.1.7601.22077 – Volsnap.sys – x64 – http://support.microsoft.com/kb/2727972 – Cluster node freezes when you restart a computer in a Windows Server 2008 R2 environment

02-Aug-2012 – 6.1.7601.17920 – Volsnap.sys – x64 – http://support.microsoft.com/kb/2727972 – Cluster node freezes when you restart a computer in a Windows Server 2008 R2 environment

11-Jul-2012 – 6.1.7601.22054 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/2727941 – “0x00000050” Stop error when you create a volume snapshot in Windows Vista, in Windows Server 2008, in Windows 7 or in Windows Server 2008 R2

01-May-2012 – 6.1.7601.17832 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/2708549 – Stop error when you create a VSS snapshot backup in Windows 7 SP1 or in Windows Server 2008 R2 SP1: “fvevol!FveFilterDeviceControl+1d0”

04-Nov-2011 – 6.1.7601.21854 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/2708549 – Stop error when you create a VSS snapshot backup in Windows 7 SP1 or in Windows Server 2008 R2 SP1: “fvevol!FveFilterDeviceControl+1d0”

04-Nov-2011 – 6.1.7601.21854 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/2632149 – “fvevol!FveFilterDeviceControl+1d0” Stop error when you create a VSS snapshot backup in Windows Server 2008 R2 SP1

04-Nov-2011 – 6.1.7601.21854 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/2627052 – Computer randomly stops responding after you use the VSS software provider in Windows Server 2008 R2 or in Windows 7

14-May-2011 – 6.1.7601.21728 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/2548124 – “0x0000007E” Stop error when you run a VSS-based backup application in Windows 7 or in Windows Server 2008 R2

25-Feb-2011 – 6.1.7601.21668 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/2505454 – The startup process is delayed on a computer that has a large hard disk installed and is running Windows 7 or Windows Server 2008 R2

25-Feb-2011 – 6.1.7601.17567 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/2505454 – The startup process is delayed on a computer that has a large hard disk installed and is running Windows 7 or Windows Server 2008 R2

18-Dec-2010 – 6.1.7601.21624 – Volsnap.sys – x86/x64 – http://support.microsoft.com/kb/2460912 – “0x0000007E” or “0x00000050” Stop error when you create snapshots of a volume in Windows Server 2008 R2 or in Windows 7

Atapi.sys – Pre Service Pack 3 Revision History for Windows Vista SP2, Windows Server 2008 SP2 and Windows Small Business Server 2008 (SBS 2008)

Atapi.sys – Pre Service Pack 3 Revision History for Windows Vista SP2, Windows Server 2008 SP2 and Windows Small Business Server 2008 (SBS 2008)

09-May-2012 – 6.0.6002.22850 – Atapi.sys – x86/x64 – http://support.microsoft.com/kb/2703639 – MMC stops responding when you disable or enable an ATA channel on a Windows Server 2008-based or Windows Server 2008 R2-based computer

17-Mar-2010 – 6.0.6002.22366 – Atapi.sys – x86/x64 – http://support.microsoft.com/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

21-Dec-2009 – 6.0.6002.22291 – Atapi.sys – x86/x64 – http://support.microsoft.com/kb/977890 – The system restarts unexpectedly when OOBE runs, and you receive the following error message: “Failure occurred during online installation”

06-Nov-2009 – 6.0.6002.22260 – Atapi.sys – x86/x64 – http://support.microsoft.com/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

22-Sep-2009 – 6.0.6002.22230 – Atapi.sys – x86/x64 – http://support.microsoft.com/kb/974073 – An update for the Msahci.sys driver has been released for AMD chipsets

20-May-2009 – 6.0.6002.22139 – Atapi.sys – x86/x64 – http://support.microsoft.com/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