Error: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.


Error: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

Description: There can be many reason.

  1. The request to SQL Server or query is taking a long time to execute.
  2. The result is returning large amount of records.
  3. Slow network connection issue.
  4. SQL Command connection timeout is not configured properly.
  5. Badly made SQL statements

Solution:

  1. Check the network connectivity is up and running.
  2. Check the SQL Statements, if required tuned and optimize it.
  3. Check the result size.
  4. Configure Connection Timeout property, by default it’s 15 seconds.

Error: Unknown Host. Unable to locate the server named “” — the server does not have a DNS entry.


Error: Unknown Host. Unable to locate the server named “” — the server does not have a DNS entry.

Description:  An SSRS error, unable to locate the server named “” — the server does not have a DNS entry. Perhaps there is a misspelling in the server name, or the server no longer exists. Double-check the name and try again. This error shows when we run the Report Manager or deployed server URL.

Solution: Open Internet Explorer, go to Tools menu then Internet Options, click on Connections tab and then LAN Settings and uncheck Use a proxy server for your LAN. Now rerun the URL again.

Error: The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. The request failed with HTTP status 404: Not Found.


Error: The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. The request failed with HTTP status 404: Not Found.

Description: An SSRS related bug, when we try to access a Report Server which is not correctly configured due to wrong or invalid URL then this error shows up.

Solution: The ReportServerUrl property of ServerReport server control should have a valid URL.

<ServerReport ReportPath=”ReportProject1/Report1″ ReportServerUrl=”http://server name/ReportServer” />

Error: The path of the item ” is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. (rsInvalidItemPath)


Error: The path of the item ” is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. (rsInvalidItemPath)

Description: An SSRS related bug, when the Report path given to ServerReport web control is wrong this error shows up.

<ServerReport ReportPath=”ReportProject1/Report1″ ReportServerUrl=”http://server name/ReportServer” />

Solution: Correct the ReportPath by giving valid deployed folder path. In above tag one forward slash was missing from the ReportPath property.

<ServerReport ReportPath=”/ReportProject1/Report1″ ReportServerUrl=”http://server name/ReportServer” />