Archive for February, 2013

Posted: February 21, 2013 in Uncategorized

Let us see how IOS fix will help improve Exchange Experience!!

Thoughtsofanidlemind's Blog

It looks like Apple has released iOS 6.1.2 in an attempt to fix the calendar synchronization problem that causes Exchange servers to log a vastly increased number of database transactions and results in more transaction logs being generated, log replication within Database Availability Groups (DAGs) and potentially service disruption if disks fill up.

This problem has lasted for far too long and it follows on other issues with iOS such as calendar hijacking. In fact, dealing with a calendar seems to pose a technical challenge for Apple, possibly because their experience and focus is centered around the development of consumer applications rather than enterprise-ready software.

I don’t know if the latest fix will work or whether some new bugs are lurking and will be exposed when the fix is applied. No one knows how Apple tests their code against Exchange. If we did, we might have more confidence in the…

View original post 133 more words

Advertisements

The web these days is full with people reporting issues while trying to apply SQL Server related Security updates. A lot of answers is around which are helpful but I couldn’t see any touches the actual issue.
First, when you are trying to apply any security updates, security updates usually requires some per-requisites. So you need to make sure first if you are meeting these pre-requisites like having the latest service pack installed, specific updates or previous security update. To make it easier for you, when a security update released by Microsoft, these is a Security Bulletin associated with these updates, go and read the exact description of the update and the pre-requisites associated with it.

In case you are sure that you are doing everything to the litter according to the book, you will need simply to look at the error code the update produced, common error code related to security updates will be 84B200001 “This error code collected with the KB2716440 security update” so what you will need to do next is to repair your SQL Instances. To update the instances is a simple process, you will need the installation media of SQL Server “Make sure you will use the correct one based on the SQL Server version you have”, to know the SQL Server version you are running, run the following query

Select @@version

For the purpose of the security update KB2716440, make sure your version is 10.50.2500 which indicates SQL Server 2008 R2 SP1

Once you identified the correct installation media you should use, simply follow this article to repair the instances, remember, you should update all instances and on all SQL Server nodes if you are using clustering.
Repair SQL Server 2008 R2 Instance

Basically the instance(s) repair will do the following:

1) All missing or corrupt files are replaced.
2) All missing or corrupt registry keys are replaced.
3) All missing or invalid configuration values are set to default values.

Once you are done. Try to install the SQL Server security update, you should be now rocking easily!!

Hope this read is informative for you, thank you for reading!!