Tuesday, November 5, 2013

Mapping User Login and Database Roles to Existing User

Error: User, group, or role 'xxx' already exists in the current database. (.Net SqlClient Data Provider) Explanation: This error happens when you try to add user mapping to the server logins using username which already exists in the database to be assigned. In my case, the user exists in both server logins and database logins, but the user mapping...
Share:

Current Transaction Cannot be Committed

Error: The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. This error occurs when you try to perform other operations when any transaction fails in try catch section, soon after it goes to catch section. Solution: You have to ROLLBACK first on the catch section before doing...
Share:

Directory Lookup Failed on SQL Server

When executing script on SQL server, this error occurs: Directory lookup for the file <filepath> failed with the operating system error 2(The system cannot find the file specified.) Directory lookup for the file <filepath> failed with the operating system error 3(The system cannot find the path specified.) Solution: Check...
Share:

Wednesday, July 3, 2013

Parameter Sniffing

Parameter sniffing has a weird symptom which can take your hours to find out what actually is happening. The stored procedure you created is running on one side, but when you deploy it on another machine or server, it never ends executing despite the fact that everything is the same. This problem usually occurs when the query contains LIKE condition....
Share:

Thursday, May 30, 2013

Error Converting Data Type Int to Nvarchar

Error: Error converting data type int to nvarchar This error occurs when a stored procedure which returns a value is used. e.g CREATE PROCEDURE [dbo].[spr_SP1] @ColA INT, @AutoID INT OUTPUT AS BEGIN INSERT INTO TableA ( ColA ) VALUES ( @ColA ) SELECT @AutoID = SCOPE_IDENTITY(); END When adding the parameter to the command on the code, usually...
Share:

Monday, April 8, 2013

An Error Occurred While Parsing EntityName

Error: An Error occurred while parsing EntityName. Line 17, position 211. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Xml.XmlException: An error occurred while parsing...
Share:

You may be intersted in

Related Posts

Updating Table Containing Xml Column via LinkedServer

If you are trying to update a table containing XML column via Linked Server in SQL Server, and you are not able to, you are not alone. There...

About Me

My photo
Is an ordinary man, with a little knowledge to share and high dreams to achieve. I'd be glad if I can help others, 'coz the only thing for the triumph of evil is for a good man to do nothing.

About Blog

You can find a lot of debugging and deploying problems while developing applications in .NET and Visual Basic here. There are also some querying tips in SQL and typical source codes which might be useful shared here.

Popular Posts

Blogroll

Followers

Leave a Message