Welcome to MSDN Blogs Sign in | Join | Help

July 2008 - Posts

Thursday, July 31, 2008 10:58 AM

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

The Scenario: Sometimes you may get a timeout issue looking something like this: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlConnection.OnError(SqlException
Posted by maspeng | 1 Comments
Filed under:
Friday, July 25, 2008 10:03 AM

Invalid attempt to read when no data is present.

A short one. You are reading data from a data reader, and sometimes you hit: Invalid attempt to read when no data is present. It may seem obvious, but there have been occasions where this error is reported. When checking the code sample below, it is obvious
Posted by maspeng | 0 Comments
Filed under:
Wednesday, July 23, 2008 4:04 PM

Remote debugging of CLR Stored Procedures, two common errors and the reason behind them.

The Scenario: You are attempting to remotely debug a CLR stored procedure from Visual Studio 2008. The Setup: Both debugger (VS 2008) and debugger target (Sql Server) is in the same domain but on different machines, which is a given, otherwise it would
Posted by maspeng | 1 Comments
Filed under: ,
Wednesday, July 23, 2008 10:20 AM

OLE DB provider "MICROSOFT.JET.OLEDB.4.0" for linked server "(null)" returned message "Unspecified error".

The scenario: You want to use a linked server (directly or indirectly) in SQL Server using the OleDb provider. With this provider you wish to use, for example, the OPENROWSET query against a file of some sort, *.txt, *.csv, *.xls, etc. The problem: You
Posted by maspeng | 5 Comments
Filed under: ,
Tuesday, July 22, 2008 10:21 AM

The simplification of JOIN. Simple example of how T-SQL JOIN work

Today I’ll try to explain how Joins work. If you are a DBA or a T-SQL expert, this is no news to you. But I’m not, and I’m sure there is a lot of people out there who are in the same situation. For example, sometimes there may be problems and you need
Posted by maspeng | 1 Comments
Filed under:
Friday, July 18, 2008 4:13 PM

Failed to find or load the registered .Net Framework Data Provider

When using a 3rd party .Net data provider. Or when you dynamically load a .Net provider you may get the following error: Failed to find or load the registered .Net Framework Data Provider There does not seem to be that much information about this and
Posted by maspeng | 1 Comments
Filed under:
Thursday, July 17, 2008 3:18 PM

{"Syntax error in FROM clause."} when using text based datasources

This is also one of the issues that I have seen a few times. What happens here is that customer uses *.csv or *.xls or any text file as a data source and connects to it using .Net and OleDb. The error reported from the framework when issuing a SELECT
Posted by maspeng | 0 Comments
Filed under: ,
Tuesday, July 15, 2008 3:38 PM

Creating a new system DSN: "Faulting application odbcad32.exe, version 3.526.3959.0, faulting module unknown, version 0.0.0.0, fault address 0x5bb312de"

This is an issue that I have seen a few times, so it could be worth mentioning. The error is as follows: When trying to create a new System DSN using the ODBC Data Source Administrator, the odbcad32.exe process goes down. And you will see something like
Posted by maspeng | 1 Comments
Filed under:
Monday, July 14, 2008 10:27 AM

Error/Event 18456 explained

Sometimes you may experience that your application, stand alone or web, can't connect to SQL Server. This error is simply reported as 18456, and the error text is "Login failed for user ‘username'" Well, you already had understood that you could not login
Posted by maspeng | 0 Comments
Filed under:
 
Page view tracker