Search This Blog

Examples

Monday, November 17, 2014

Microsoft recent security update has resulted in compilation error. After spending some time came across this link. This is a known issue.

Error: Could not load file or assembly 'System.Web.Mvc, Version=4.0.0.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)Cause of Error:Microsoft recent security updateSolution:Install Nuget Package Microsoft.AspNet.Mvc for all the project referencing System.Web.Mvc dllExample: Install-Package Microsoft.AspNet.Mvc

Error:Could not load file or assembly 'WebMatrix.Data, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)Solution:Install Nuget Package Microsoft.AspNet.WebPages.DataExample: Install-Package Microsoft.AspNet.WebPages.Data

Samsung data migration utility CD which comes with SSD Drive hardware is still not compatible with Win 10, so you can either used different software for drive cloning or can degrade to previous version of windows on which samsung data migration utility will works just good.

Few other references you would find useful if run into any such issues:

Monday, July 07, 2014

Update Table from Another Table in SQL Server: A simple scenario demonstrating how we can update Persons table with data from Employees table using update statement. A simple but very effective query which can saves you from creating unnecessary cursor for updating from different tables. By performance wise also Update statement is more efficient compared to creating update cursor.

Json Object String we will be using in following example
@"{'PhotoName':'mypic.jpg','IsModerated':'false'}"Code Snippet
using System;
using System.Collections.Generic;
using Newtonsoft.Json;
using Newtonsoft.Json.Converters;

Json Object String we will be using in following example
@"[
{'PhotoName':'pic1.png','IsModerated':'true'},
{ 'PhotoName':'pic2.jpg','IsModerated':'true'}
]"Code Snippet
using System;
using System.Collections.Generic;
using Newtonsoft.Json;
using Newtonsoft.Json.Converters;

Json Object String we will be using in following example
@"[
{'PhotoName':'pic1.png','IsModerated':'true'},
{ 'PhotoName':'pic2.jpg','IsModerated':'true'}
]"Code Snippet
using System;
using System.Collections.Generic;
using Newtonsoft.Json;
using Newtonsoft.Json.Converters;

Saturday, May 24, 2014

Error: A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Data Provider)

Solution:Step 1: Open SQL Server Configuration Manager

Go to Windows 8 Start screen.

Start typing in SQLServerManager11.msc if you are looking for SQL Server 2012 configuration manager. Type in SQLServerManager10.msc if you are looking for SQL Server 2008 configuration manager.

In the result panel you can see the SQLServerConfiguration Manager.

Click the icon to launch the SQL Server Configuration manager.

The configuration manager will open in MMC.

Step 2: Enable following configuration settings

ensure Shared Memory protocol is enabled

ensure Named Pipes protocol is enabled

ensure TCP/IP is enabled, and s ahead of the Named Pipes in the settings

I was recently facing this error when created a SQL Server login and then try login using that newly created login.

Error: Login failed for user. (Microsoft SQL Server, Error 18456) (.Net SqlClient Data Provider)Please note:
Solution is available on this link, but since microsoft has bad habit of link breaking issue; I have copied and pasted the solution for my reference.http://support.microsoft.com/kb/555332

Cause:Scenario 1: The login may be a SQL Server login but the server only accepts Windows Authentication.Scenario 2: You are trying to connect by using SQL Server Authentication but the login used does not exist on SQL Server.Scenario 3: The login may use Windows Authentication but the login is an unrecognized Windows principal. An unrecognized Windows principal means that Windows can't verify the login. This might be because the Windows login is from an untrusted domain.

Solution:

Scenario 1: Configure SQL Server in Mixed Authentication Mode.

SQL Server 2012, SQL Server 2008, and SQL Server 2005

Open SQL Server Management Studio. To do this, click Start, click All Programs, click Microsoft SQL Server 200x (where x is the version of SQL), and then click SQL Server Management Studio.

Scenario 2: Verify that the SQL Server login exists

If you are trying to connect to the SQL Server by using SQL Server Authentication, and the server is configured for mixed mode authentication, verify that the SQL Server login exists. For more information, see Create a login in SQL Server Books Online.

Scenario 3: The login may use Windows Authentication but the login is an unrecognized Windows principal.

If you are trying to connect to SQL Server by using Windows Authentication, verify that you are logged in to the correct domain.

Most Recent Post

Community Updates

Disclaimers:We have tried hard to provide accurate information, as a user, you agree that you bear sole responsibility for your own decisions to use any programs, documents, source code, tips, articles or any other information provided on this Blog.