Showing posts from October, 2011

Enterprise Single Sign-On Service Error:0x80131700

ESSO service cannot start and giving  error message,
Windows could not start the Enterprise Single Sign-On Service service on Local Computer. Error 0x80131700: 0x80131700

This is happens after installing .net 4.0 framework. This is known known issue and there is a hotfix to install.

The URL* is, Update for Microsoft Enterprise Single Sign-On v4 (KB2252691)

* last access: 2011-10-31 11:45AM

For more details

MS SQL Server Backups & Restore: Steps explained

Yes I know, there are lots of articles and posts about this topic. But I want to show, what are things to be known to recover the database to specific point-in-time. Backup As you know there are 3 recovery models supported in MS SQL server.
Simple Automatically clear the log file. Only allows  recover to end of a backup. No log backupsFull Requires log backups No work is lost, if data (.mdf) file get damaged/lost Can recover to a specific point-in-time.Bulk-logged Requires log backups Use minimal logging for bulk operations, thereby reducing the log space Point-in-time recovery is not supported. In a mission critical environment, Full recovery model is the most recommended. In this post I’m paying attention to this model and simply explain point-in-time recovery. From your SQL server database you can take, 3 back up types.
Full Differential Transaction Log In Full recovery model, applicability of above types can be depicted in following way.

Figure 1 You can see in the Figu…


To Shrink the database log file I’ve used to,
1: 2:DUMPTRAN <DatabaseName> WITH TRUNCATE_ONLY 3:GO 4: 5:USE <DatabaseName> 6:DBCC SHRINKFILE (<DatabaseName>_log, 100); 7:GO 8:

This is not work in SQL 2008, as DUMP is discontinued. Otherwise we have to use BACKUP.

To shrink the log file in SQL 2008,
Back up the database in “SIMPLE” recovery mode. then run above line no 6.
Refer this ( for discontinued functionalities in SQL 2008.

WPF Application Crashes in Windows XP (System.IO.FileFormatException)

BackgroundWindows XP users are keep complaining me about  crashes of WPF application as soon I released it.  I was wandered, why all Windows 7 users don’t have that. My team mate did couple of enhancements plus adding new application’s window icon. The error message they receive is (crashing message !),ProblemSince everything working perfectly on Windows 7, something wrong with XP to what we did lastly. That is replacing the icon. But I have no proof for that, but  got a clue from the following screen.Hm…., I change the icon to a very classic one and try it. WOW, it is working fine in XP. Now I want to find out what is the different between this icon and the my icon. I found that my icon containing additional two image types (256x256, 32bit,PNG), which you can be seen from the Visual Studio Icon editor.SolutionI removed these two image types from the icon file using Visual Studio Icon Editor, added to the application and  it’s work fine.To justify the situation, I found this (accessed…