Tag Archives: framework

Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later – fixed

“Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later” occurs when trying to access out of office onwith outlook2007. The strange thing is that the out of office functionality through the Outlook Web Access page works as expected.
There are several documented ways to fix this, mainly ensuring that the various autodiscover urls are correct. See Proexchange.be – Your out of office settings cannot be displayed for the best document on this.
Interestingly is that if you enable debugging in outlook and try to access the Out of Office you do see the settings being pulled across in the logfile.

However I was still having this issue. From Microsoft forums on Exchange Server Clients I found that various patches to the dot net framework (oh how I hate thee) being discussed and http://support.microsoft.com/kb/952883 was the first patch that was discussed. Sure enough, installing this patch fixed the problem and what is more I didn’t even have to reboot.

The annoying thing is that the first time I had this problem (on this server) was due to a typo in the autodiscover service, then the .net framework patches were applied and the problem re-occured.

Dynamics SL crashing on startup after installation of .net patches.

Overnight several of the .net patches were pushed out to workstations and now when Dynamics SL  is run I get the following error. “Microsoft Dynamics SL has encountered a problem and needs to close. We are sorry for the inconvenience”

Looking in the event log or the details  I see a .net Runtime 2.0 error, Event 5000. Description EventType clr20r3, P1 msdynamicssl.exe, P2 7.0.0.0, P3 4889f859, P4 solomon.kernel, P5 7.0.0.0, P6 4649b3d9,P7 1b4, P8 0, P9 system.accessviolationexception, P10 NIL

This is then followed by id 5001, Description “Bucket 300554837, bucket table 5, EventType clr20r3, P1 msdynamicssl.exe, P2 7.0.0.0, P3 4889f859, P4 solomon.kernel, P5 7.0.0.0, P6 4649b3d9,P7 1b4, P8 0, P9 system.accessviolationexception, P10 NIL

The cause of this was actually the installation of a .NET Framework 3 patch.

The sorry saga of trying to fix this solution is documented at the dynamics forum but this is a known issue and the patch is available through Customersource or PartnerSource if you have access to this. Alternatively call Microsoft hotfix line on 1 888 456 5570 and request the Dynamics SL hotfix 961802. There is no charge for this hotfix.  Install on your workstation and you should be good to go.

However if you have tried to fix this issue by editing your .NET framework settings then I recommend totally removing .net from the computer, reinstalling v2 and the service pack.  There is a really good tool for removing .NET framework from Aaron Stebner which works a treat.