"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2)"

In SQL Server Management Studio this error appears as:

"Cannot connect to ."

"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2)"

From sqlcmd, possible timeout errors include:

"SQL Network Interfaces: Error Locating Server/Instance Specified"

"Sqlcmd: Error: Microsoft SQL Server Native Client : Client unable to establish connection."

"Sqlcmd: Error: Microsoft SQL Server Native Client : Login timeout expired."

"Could not open a connection to SQL Server"

"An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections."

resolution link:
============================
http://msdn.microsoft.com/en-us/library/ms190181.aspx

how many SSIS packages can run in parallel

http://blogs.msdn.com/sqlperf/archive/2008/02/27/etl-world-record.aspx
http://msdn.microsoft.com/en-us/library/dd537533.aspx

best practices for SSIS package performance

http://blogs.msdn.com/michen/archive/2007/04/24/sqlperf-blog-on-ssis-performance.aspx

The performance turning videos here may also be helpful:

http://sqlcat.com/presentations/archive/2009/05/02/designing-and-tuning-for-performance-your-ssis-packages-in-the-enterprise-sql-video-series.aspx

Importing Excel Cell data via SSIS

check this blog

Dougbert.com blog post

(http://dougbert.com/blogs/dougbert/archive/2008/06/18/excel-in-integration-services-part-2-of-3-tables-and-data-types.aspx )

SSIS Packages Running slow

The workaround is to place this entry into the ‘hosts’ file on the Windows Server 2003 machine :

<<<<<
#Fix for slow running SSIS packages
127.0.0.1 crl.microsoft.com


If you're using 2005, this might have something to do with the certificate revocation list.

In 2008 its modified the dtexec configuration to not check the list. The customer could do the same for 2005 by manually editing the file.

See Michael's blog post for more information:

http://blogs.msdn.com/michen/archive/2008/03/14/configuring-net-for-running-ssis-packages-from-custom-applications.aspx

best practices surrounding team development with SSIS

http://blogs.conchango.com/jamiethomson/archive/2007/08/06/SSIS_3A00_-Team-Development-Experiences.aspx

"Exception from HRESULT: 0xC0010014" Foreach Loop Container SSIS

If we create a new Integration Services Project on the servers BI Visual Studio,
chose the Foreach Loop Container,
click edit on it
and click on the three dots on Expressions under Collection we get an error message saying:

"Exception from HRESULT: 0xC0010014".

Resolution:
============================
issue was resolved by registering ‘ForEachFileEnumerator.dll’ using regsvr32.exe:

c:\program files (x86)\microsoft sql server\90\dts\foreachenumerators\ForEachFileEnumerator.dll

As per this link:

http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/8cf03f7d-f170-40db-98fa-af151d5b5269

Microsoft Connectors for Oracle and Teradata by Attunity

http://www.microsoft.com/downloads/details.aspx?FamilyID=d9cb21fe-32e9-4d34-a381-6f9231d84f1e&DisplayLang=en


Oracle Provider for OLE DB
http://www.oracle.com/technology/tech/windows/ole_db/index.html

"The timeout period elapsed prior to completion of the operation or the server is not responding"

SQL SERVER: 2005
when running a view or query with very long execution time, you may see the
following error message from Management Studio.

---------------------------
Microsoft SQL Server Management Studio
---------------------------
SQL Execution Error.
--
Error Source: .Net SqlClient Data Provider
Error Message: Timeout expired. The timeout period elapsed prior to completion of
the operation or the server is not responding.
---------------------------
OK Help
---------------------------


From Query Analyzer:

Msg -2, Level 11, State 0, Line 0
Timeout expired. The timeout period elapsed prior to completion of the operation
or the server is not responding.

Resolution:
====================
1. Please check the Execution time-out Settings first. Make sure those are 0.
a. Open SSMS (SQL SERVER Management Studio). Tools->Options->Query Execution->SQL
SERVER->General: Execution time-out. Set to 0.
b. Open a new Query window from SSMS. Query->Query Options->Execution->General:
Execution time-out. Set to 0.
c. On SSMS, File->new->Database Engine Query->Options->[Connection
Properties]->Execution time-out. Set to 0.

d. Please reopen SSMS.
e. If issue persists - go to step 2:

2. Please open sqlcmd connection and try to execute the same query. Based on the
error message you receive there you may continue troubleshooting further. It may
involve collecting PSSDIAG / trace / dumps as per the requirement.

"no such interface supported" and SSIS

When we try to connect to SQL Server 2005 Integration services using SQL Server
Management Studio, we get an error -

Connect to SSIS Service on machine failed:
No such interface supported


Full technical Details:
=================

Cannot connect to MySSISServer.

===================================

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

------------------------------
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

------------------------------
Program Location:

at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo,
Request request)
at
Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.Valida
teConnection(UIConnectionInfo ci, IServerType server)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

===================================

Connect to SSIS Service on machine "MySSISServer" failed:
No such interface supported
.


------------------------------
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.GetServerInfo(String server,
String& serverVersion)
at Microsoft.SqlServer.Dts.SmoEnum.DTSEnum.GetData(EnumResult erParent)
at Microsoft.SqlServer.Management.Smo.Environment.GetData()
at Microsoft.SqlServer.Management.Smo.Environment.GetData(Request req, Object
ci)
at Microsoft.SqlServer.Management.Smo.Enumerator.GetData(Object connectionInfo,
Request request)
at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo,
Request request)

===================================

Connect to SSIS Service on machine "MySSISServer" failed:
No such interface supported
.


------------------------------
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.GetServerInfo(String
bstrMachineName, String& serverVersion)
at Microsoft.SqlServer.Dts.Runtime.Application.GetServerInfo(String server,
String& serverVersion)


Solution:
=========================
Root Cause:
==========
We may get the above error if the DLL MsDtsSrvrUtil.dll, located under Installation Folder>\90\DTS\Binn\MsDtsSrvrUtil.dll is not Registered successfully
on the machine (SSIS Server).

The most common cause of this error is -

SQL Server 2005 Service pack or CU setup failed to re-register the above DLL (we
can review the setup logs to verify)

During setup of a SQL Server 2005 Service pack or CU, setup tries to unregister and
re-register relevant DLLs on the machine and we have seen certain cases when this
DLL (and other DLLs) was not re-registered successfully.


Resolution:
==========

Re-register the DLL MsDtsSrvrUtil.dll and DTS.dll like below -

regsvr32.exe "\90\DTS\Binn\MsDtsSrvrUtil.dll"

We don't require SSIS service restart or to re-open SSMS. After re-registering it
starts working.

"SQL Server specified in SSIS Service configuration is not present"

PROBLEM: After connecting to SSIS (SQL Server Integration Services) from SSMS (SQL
Server Management Studio), when you expand MSDB under Stored Packages to see list
of stored packages, you may get below error.




ERROR MESSAGE:

TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
The SQL server specified in SSIS service configuration is not present or is not
available. This might occur when there is no default instance of SQL Server on the
computer. For more information, see the topic "Configuring the Integration Services
Service" in Server 2005 Books Online.

Login timeout expired
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that under
the default settings SQL Server does not allow remote connections.
SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
(MsDtsSrvr)
------------------------------
Login timeout expired
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that under
the default settings SQL Server does not allow remote connections.
SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
(Microsoft SQL Native Client)
------------------------------
BUTTONS:
OK
------------------------------

Resolution:
====================
CAUSE: This problem may happen because below multiple reasons.

1. Registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTS\ServiceConfigFile" not
existing or not pointing to correct path of the file MsDtsSrvr.ini.xml. Default
path of this file is "%ProgramFiles%\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml".

2. The content of file MsDtsSrvr.ini.xml typically looks like below.


xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
true


MSDB
.


File System
..\Packages




If the Packages folder path specified between StorePath tags above is incorrect,
you may get the same error.

3. If the ServerName specified between ServerName tags above is incorrect, you may
get the same error. If the SQL is in cluster, specify the virtual name.

RESOLUTION: In our case, we replaced '.' with the netbios name of the server and it
resolved the issue.

SQL Server Management Studio to SSIS with 'Error loading type library/DLL'

TITLE: Connect to Server
------------------------------
Cannot connect to xxxx.
------------------------------
ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
Connect to SSIS Service on machine "xxxx" failed:
Error loading type library/DLL.
-----------------------------
Connect to SSIS Service on machine "xxxx" failed:
Error loading type library/DLL.
------------------------------
BUTTONS:
OK
------------------------------


TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
Library not registered. (Exception from HRESULT: 0x8002801D
(TYPE_E_LIBNOTREGISTERED)) (Microsoft.SqlServer.DTSRuntimeWrap)
------------------------------
Library not registered. (Exception from HRESULT: 0x8002801D
(TYPE_E_LIBNOTREGISTERED)) (Microsoft.SqlServer.DTSRuntimeWrap)
------------------------------
BUTTONS:
OK
------------------------------

Solution:
======================
We Need to Un-Register both 32Bit and 64Bit of Dts.dll and Un-Register both
32Bit and 64Bit of MsDtsSrvrUtil.dll and Re-Register both 32Bit and 64Bit of
Dts.dll and both 32Bit and 64Bit of MsDtsSrvrUtil.dll

==================
In another issue of 32-bit SQL Server installation on a 32-bit windows 2003, we were
getting exactly the same error.

Resolution: Resolution in that issue was also same as the above.

Registering the Dts.dll and MsDtsSrvrUtil.dll from %PROGRAM FILES%\Microsoft SQL
Server\90\DTS\Binn folder.

=================
Cause: During each service pack setup, we unregister the older versions of these
DLLs (along with a lot of others), copy the new ones and re-register them. The
registering phase may have failed on these files. The installation log of the
service pack can confirm us that.

"Failed to retrieve data for this request" "Error loading type library dll"

Component Registration
To resolve error loading typelibrary error when connecting to SSIS from Management
Studio we did following on both nodes of the cluster

1. Run following commands to make sure 32bit and 64bit versions of
MsDtsSrvrUtil.dll are registered properly.

regsvr32 /u C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvrUtil.dll
regsvr32 /u C:\Program Files (x86)\Microsoft SQL
Server\90\DTS\Binn\MsDtsSrvrUtil.dll
regsvr32 C:\Program Files (x86)\Microsoft SQL
Server\90\DTS\BINN\MsDtsSrvrUtil.dll
regsvr32 C:\Program Files\Microsoft SQL Server\90\DTS\Binn\ MsDtsSrvrUtil.dll

2. Run following commands to make sure 32bit and 64bit versions of DTS.dll are
registered properly.

regsvr32 /u C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll
regsvr32 /u C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTS.dl
regsvr32 C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTS.dll
regsvr32 C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll

Enabling Users to Connect SSIS from Remote Computers
By default you cannot connect to SSIS service from a remote computer running
Management Studio. To be able to connect SSIS from remote computer, we did
following:

1. Open Component Services\Computers\My Computer\Properties\Default Properties,
make sure the option “Enable Distributed COM on this
computer” is checked.

2. Open Component Services\Computers\My Computer\DCOM Config\MsDtsServer
Properties. In the security page verify that under “Launch and Activate
Permissions”, Remote Launch and Remote Activation are enabled for all users who
will be connecting SSIS service remotely.

3. Open Computer Management\Local Users and Groups\Groups and make sure all users
who will be connecting SSIS service remotely are added into “Distributed COM users”
group.

4. If there’s a firewall between the client computer where you run Management
Studio and SSIS server you also need to make sure the firewall is configured for
DCOM. Refer to below article for more information on this.

Using Distributed COM with Firewalls
http://msdn.microsoft.com/library/en-us/dndcom/html/msdn_dcomfirewall.asp

Setting the backend SQL Server for SSIS
By default SSIS tries to use the local default instance as backend server. If your
SQL Server has a different name, you need to reconfigure SSIS to connect to your
SQL Server instance. We did following on both nodes of the cluster to configure
same SQL Server instance as the backend database for both SSIS service on both
nodes.

1. Open the configuration file C:\Program Files\Microsoft SQL
Server\90\DTS\Binn\MsDtsSrvr.ini.xml in notepad.

2. Find following piece of information in the file


MSDB
.


3. Change the server name value (between tags) to point to the actual
SQL Server name you will use.

4. Restart SSIS Service.

Clustering SSIS Service
By default SSIS service is installed on individual nodes and runs as a separate
service on both nodes. If you want clustering capabilities (failover etc.) you may
configure SSIS service to be a clustered resource. Please follow steps in the BOL
link below to configure SSIS on a cluster.

Installing SQL Server 2005 Components > Installing SQL Server Components How-to
Topics > Integration Services Installation How-to Topics > How to: Configure
Integration Services on a Cluster
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/223c3a59-84c3-4f60-be98-a8daf69e9473.htm

SSIS packages that are currently running may unexpectedly stop responding when you restart the SSIS service in SQL Server 2005

CAUSE

This behavior may occur because of an incorrect node setting in the SSIS service configuration file. Every time that the SSIS service starts, the service reads the SSIS configuration file. One of the nodes in the SSIS configuration file determines how the SSIS service will handle packages that may be running if the SSIS service stops responding. If this node is set incorrectly, the service issues a stop request to the SSIS runtime as soon as the SSIS service stops responding. When this behavior occurs, each package that is running is stopped.

RESOLUTION

To resolve this behavior, you must modify the SSIS service configuration file to enable packages to continue to run even if the SSIS service stops responding. The name of the SSIS service configuration file is MsDtsSrvr.ini.xml. By default, the MsDtsSrvr.ini.xml file is located in the Program Files\Microsoft SQL Server\90\DTS\Binn folder.

To modify the SSIS service configuration file, follow these steps. 1. In Notepad, open the MsDtsSrvr.ini.xml file.
2. Locate the following node: TRUE

3. In the node that you located in step 2, change TRUE to FALSE , so that the node appears as follows: FALSE

4. Save and then close the MsDtsSrvr.ini.xml file.
Note After you have modified the SSIS service configuration file, restart the SSIS service to apply updated service configuration.

How to import ODBC settings from 32 bit OS to 64 bit OS

Try registry import/export.

System DSN:

1. Export all entries under HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI into a file SysDsn.reg
2. Use notepad to open SysDsn.reg and replace all occurrences of "HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources" with "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources"
3. Save the file and copy it to the new machine
4. Import the SysDsn.reg into the registry of the new machine

User DSN:

1. Export all entries under HKEY_CURRENT_USER\Software\ODBC\ODBC.INI into a file UserDsn.reg
2. You don't need to change the content of the reg as above for system DSN
3. Copy the file to the new machine
4. Import the UserDsn.reg into the registry of the new machine

After completed both steps, all existing applications should expect to work as before. But if some application has migrated from 32-bit to 64-bit and if it is using system DSN, you may need to move the corresponding entries from HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources. (There is no similar problem for user DSN. See a related KB for this issue at: http://support.microsoft.com/kb/942976/en-us).

However, it is not a good idea to move all entries from Wow6432Node to the Native 64-bit registry tree, since this may break some 32-bit applications running under WOW64 mode. Please also note that there is no 64-bit ODBC driver for Excel / Access available currently. Therefore, any application using Excel / Access as data source must not be upgraded to be 64-bit. For those applications, it should still be able to run under WOW64 mode.

"[Microsoft]ODBC Driver Manager]Datasource name not found and no default driver

ACTION:
In Excel, you try to refresh the data imported from an external datasource (Oracle database).

RESULT:
You receive the following error message:
"[Microsoft]ODBC Driver Manager]Datasource name not found and no default driver specified"

CAUSE:
The source was imported from an Oracle database, but Oracle client 9.2.0.6 was missing on the user’s computer.

RESOLUTION:
installed Oracle client 9.2.0.6 on the user's computer and the worksheet is now working.

Creating an instance of the COM component with CLSID

Creating a new OLEDB connection manager in BIDS SSIS project was giving below
error. Right click on Connection Manager and select "New OLE DB Connection" . In
the "Configure
OLE DB Connection Manager" window click on the "New.." button and you will see
below error:

========================================
TITLE: Microsoft Visual Studio
------------------------------

Creating an instance of the COM component with CLSID
{C8B522D0-5CF3-11CE-ADE5-00AA0044773D} from the IClassFactory failed due to the
following error: 8007007e.

------------------------------
BUTTONS:

OK
========================================

RESOLUTION
==============
Reinstalled MDAC components by running MDAC.inf file.

1. Go to the C:\Windows\Inf folder
2. Right-click the Mdac.inf file, and then click Install
3. Point to the Windows Installation CD when prompted
This reinstalled the MDAC components and then the to choose the OLE DB connector.

Parser Error Message: Could not load file or assembly 'Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or on

Parser Error Message: Could not load file or assembly 'Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.

Stack trace
getting error
'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' because it was not specified in Configuration file.
w3wp!library!1!5/24/2007-15:57:03:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to default value of 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' because it was not specified in Configuration file.
w3wp!library!1!5/24/2007-15:57:03:: i INFO: Initializing SecureConnectionLevel to default value of '1' because it was not specified in Configuration file.
w3wp!library!1!5/24/2007-15:57:03:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
w3wp!library!1!5/24/2007-15:57:03:: i INFO: Initializing WebServiceUseFileShareStorage to default value of 'False' because it was not specified in Configuration file.
w3wp!ui!1!5/24/2007-15:57:03:: Unhandled exception: System.Configuration.ConfigurationErrorsException: Could not load file or assembly 'Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified. (c:\inetpub\wwwroot\web.config line 46) ---> System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'
at System.RuntimeTypeHandle._GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, Boolean loadTypeFromPartialName)
at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark)
at System.RuntimeType.PrivateGetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark)
at System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase)
at System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase)
at System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

--- End of inner exception stack trace ---

Cause:
=======================================================================
Still the References to the dll’s of SharePoint exists in the web.config file in c:\inetpub\wwwroot as well as the rssrvpolicy.config file and rsmgrpolicy.config file
So the error is getting thrown while browsing the reportserver and reports

Resolution:
=======================================================================
Manually Removed all the code references pointing to the sharepoint from web.config file of c:\inetpub\wwwroot, rssrvpolicy.config file and rsmgrpolicy.config file
And reset the iis.
Now browsed report server and reports its coming up fine without error.
or
rename the web.config file of c:\inetpub\wwwroot to something like web.config.bak
now restart the iis and try browsing the reportserver and reports

ReportingServicesService!emailextension!4!04/19/2007-17:05:59:: Error sending email. System.Runtime.InteropServices.COMException (0x80040211): The mes

ReportingServicesService!dbpolling!21!04/19/2007-17:05:59:: NotificationPolling finished processing item 0ed42bc8-26ab-4454-819c-db894e68c973
ReportingServicesService!library!4!04/19/2007-17:05:59:: i INFO: Initializing EnableExecutionLogging to 'True' as specified in Server system properties.
ReportingServicesService!emailextension!4!04/19/2007-17:05:59:: Error sending email. System.Runtime.InteropServices.COMException (0x80040211): The message could not be sent to the SMTP server. The transport error code was 0x800ccc15. The server response was not available


A firewall was blocking traffic from the Report Server to the Exchange server. It blocks emails being sent from the server on port 25.
Add an exception for the ReportingServerService.exe Anti virus program
and now emails for data driven subscriptions of reports should fire

OR

CAUSE:
The configuration for the Email service was incorrect.

RESOLUTION:
change the SendEmail setting to 2 and removed the value for
SMTPServerPickupDirectory in the RSReportServer.config file.

Failed to map the path '/ReportServer/App_GlobalResources/' while Trrying to browse the Reporserver and reports.

problem lies in the permissions of the ASP.NET user account.

First step was to delete the ASPNET user account and then run the aspnet_regiis utility in the framework folder:

c:\WINNT\Microsoft.NET\framework\v2.0.50727\aspnet_regiis -i

This will re-register ASP.NET with IIS and re-create the ASPNET account.

Next you need to give permissions to the (nicely refreshed) ASPNET user account to access this folder with Modify permissions:

C:\Documents and Settings\All Users.WINNT\Application Data\Microsoft\Crypto\RSA\MachineKeys

A quick restart of IIS (quick-tip: simply type iisreset in a run dialog to restart your IIS)

OR

giving the ASP.NET user account permissions over the 'C:\Documents and Settings\All Users.WINNT\Application Data\Microsoft\Crypto\RSA\MachineKeys'

OR

click the Security Tab under the Properties of the C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA and add the ASP.NET account with full control.

OR

In the folder --> C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys
... I found a key that was 0 KBytes,
simply deleted it (which is then recreated when accessing the website)

"Could not find file C:\Documents and Settings\username\Local Settings\Temp\xxxxxxx.dll"

Getting below error message when we try to create a Business Intelligence Project[SSIS]

"Could not find file C:\Documents and Settings\username\Local Settings\Temp\xxxxxxx.dll"

Issue seems to be an corruption with Dot Net framework dll.

SQL 2005 uses dotnet framework 2.0
SQL 2008 uses dotnet framework 3.5

Uninstalling and reinstalling the framework Should resolve the issue.

Attempting to install is MS07-009, which corresponds to KB article 927779 and its failing with error.

Before making any changes to registry key do a backup of it.

1.Remove the MDAC Exception component keys from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ExceptionComponents.

2. Re-run the MDAC 2.81 installer (MDAC_TYP.EXE). When the installer runs you should see a few windows coming up showing it copying files.
http://www.microsoft.com/downloads/details.aspx?FamilyID=78CAC895-EFC2-4F8E-A9E0-3A1AFBD5922E&displaylang=en [mdac 2.8 sp1 download]

3. Apply the update again and if need be reboot the machine.

We can ping the IP address of the SQL Server but we can not connect to the SQL

Make sure File and Printer Sharing for Microsoft Networks is installed and is
checked.

Right-click on Network Places, select Properties. Right-click the network we
are using, select properties and make sure that “File and Printer Sharing for
Microsoft Networks” is installed and is checked.

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation.

have a web site and using SQL Server 2000 as my back end DB. The ASP page connect to SQL Server through ODBC connection using DSN configured using TCP/IP protocol. and after couple of windows update website page was showing network errror when it was trying to get the infomation from the SQL Server.

Below is the error message getting displayed


[Microsoft][ODBC SQL Server Driver][DBMSSOCN] General Network error. Check your documentation.
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][DBMSSOCN]ConnectionOpen(connect())
Connection failed:
SQLState: 08001
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation.
Connection failed:
SQLState: 01000
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (connect())

cause: exceeded the default WinsockListenBacklog setting on the computer that is running SQL Server.

A Winsock application accepts connections on a port by calling a Listen() function, which has a backlog parameter specifying the maximum length of the pending-connection queue. The Winsock specification defines the maximum Listen() backlog at five and when it exceeds five, TCP/IP issues a reset.

and due to this we see the below error message

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation.


Solution:

Start Registry Editor (REGEDT32.EXE) and locate the following subkey:

For a default instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib

For a named instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Name\MSSQLServer\SuperSocketNetLib

select the SuperSocketNetLib for SQL Server 2000. On the Edit menu, click Add Value.

Enter the following:

Value Name: WinsockListenBacklog
Data Type: REG_DWORD
Data: Range is 1 to 0xFFFFFFFF

in my case i had set the value of Data:15, that resolved the issue.

Note: The suggested method of testing with this value is to set the value in increments of five and observe the results until the connection reset stops.

once value is set, Restart SQL Server.

Accessing SQL Server Databases with PHP

Applies to: SQL Server 2005 and SQL Server 2008 – all editions

http://msdn.microsoft.com/en-us/library/cc793139.aspx

Troubleshooting Performance Problems in SQL Server 2008

http://msdn.microsoft.com/en-us/library/dd672789.aspx

A new whitepaper covering the topic of performance troubleshooting in SQL Server 2008 has now been released. You can download the paper from the above link.

also u can check the below link

http://blogs.msdn.com/psssql/archive/2009/03/03/troubleshooting-sql-server-2005-2008-performance-counter-collection-problems.aspx

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Named Pipes Provider

Some of solutions which can help you resolve above issue

**********************************************************************************************************************
This is the solutions perscribed in the MS Knowledge Base: http://support.microsoft.com/kb/914277/en-us

1. Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Surface Area Configuration.
2. On the SQL Server 2005 Surface Area Configuration page, click Surface Area Configuration for Services and Connections.
3. On the Surface Area Configuration for Services and Connections page, expand Database Engine, click Remote Connections, click Local and remote connections, click the appropriate protocol to enable for your environment, and then click Apply.

Note Click OK when you receive the following message:
Changes to Connection Settings will not take effect until you restart the Database Engine service.
4. On the Surface Area Configuration for Services and Connections page, expand Database Engine, click Service, click Stop, wait until the MSSQLSERVER service stops, and then click Start to restart the MSSQLSERVER service.


**********************************************************************************************************************


http://blogs.msdn.com/sql_protocols/archive/2005/10/22/sql-server-2005-connectivity-issue-troubleshoot-part-i.aspx



This error message means that the server was not found or not running or can not make Named Pipe connection through the pipe name that client specified. To verify this:



1) From the command line, do "sc query mssqlserver" or "sc query mssql$" to check whether sql instance present. Then open sql server configuration manager -> check the state of the sql service, if it is not running, start it. If server started fail, check event log or server error log, see what happened there.

2) if you are sure the service is running and shared memory/Named Pipe enabled, please try connection if it is local default instance "osql /Snp:\\.\pipe\sql\query"; or try connection "osql /Snp:\\.\pipe\mssql$\sql\query" if it is local named instance. if you still get error 2, then go to step 3).

3) Double check the server is started and listening on named pipe if you enabled Named Pipe. One way is that see the ERRORLOG of the server, search follow keywords:

Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ] or [\\.\pipe\mssql$\sql\query]

Notice that "sql\query" is the default pipe name, so you need to know server is listening on which pipe name. eg: if you specify server pipe name is "sql\query1", then you would see in the errorlog that server listening on [ \\.\pipe\sql\query1 ].

4) See your connection string, whether you explicitly specify the pipe name and does it match the pipe that server is listening on? Or whether you just specify server name( like ".","(local)", etc), but you specify the wrong pipe name on client side Named Pipe configuration.eg, go to SQL Server Configuration Manager, click client Named Pipe properties, see whether the pipe name is same with the one server listening on.

Note: For remote connection, you need to verify step 2) and 3).

**********************************************************************************************************************

http://social.msdn.microsoft.com/forums/en-US/sqldataaccess/thread/5d9e84c2-1c05-449a-aae5-503e2ad6f9ca/

http://groups.google.com/group/microsoft.public.sqlserver.odbc/browse_thread/thread/773da4fece704a57

Named Pipes was not enabled.

**********************************************************************************************************************
When attempting to connect to a SQL Server 2005 Express database with sqlcmd, such as:

sqlcmd -s \SQLEXPRESS
where '' is the name of the pc/server with SQL Server 2005 Express installed. The following error is generated:

HResult 0x2, Level16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections..
Sqlcmd: Error: Microsoft SQL native Client : Login timeout expired

Cause:
When first installed SQL Server 2005 Express Edition does not allow any connections other than via the Shared Memory protocol on the local machine.

This error can also be caused by firewall settings blocking access to SQL Server.

Possible Remedies:

Enabled Named Pipes and TCP/IP protocols on the database server.
Start ? All Programs ? Microsoft SQL Server 2005 ? SQL Server Configuration Manager
In the left hand pane, expand "SQL Server Configuration Manager (Local) ? SQL Server 2005 Network Configuration"
In the left hand pane, highlight "Protocols for SQLEXPRESS"
In the right hand pane, right click "Named Pipes" and select "Enable"
In the right hand pane, right click "TCP/IP", select "Enable" and then select "Properties"
On the "IP Addresses" tab ensure that "Enabled" is set to "Yes" for each network adapter listed.
Click [OK] to close the TCP/IP Properties dialog.
In the left hand pane select "SQL Server 2005 Services"
Right click "SQL Server (SQL EXPRESS)" and select "Restart"
Whilst it is not required for this process, it can make the task of configuring remote access to SQL Server Express easier if you also start the process "SQL Server Browser". You may need to open the properties and on the "Service" tab change the Start Mode from Disabled to Automatic, before you can start the process.

Add SQL Server 2005 Express as an exception to the windows firewall.
You will need to add SQL Server 2005 Express as an exception to any firewall software that is running locally. The following sequence assumes the Windows XP Firewall:

Start ? Control Panel (classic view) ? Windows Firewall
On the Exceptions tab, click "Add Program..."
Browse to "sqlserver.exe" and click [OK]. This is normally located in the folder "Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn"
Repeat for "sqlbrowser.exe" if you have set the "SQL Server Browser" service to run. This is normally located in the folder "Program Files\Microsoft SQL Server\90\Shared"
Click [OK] to close the Windows Firewall dialog.
If you still find that you cannot connect, then try opening TCP Port 1666 in the Windows Firewall:

Start ? Control Panel (classic view) ? Windows Firewall
On the Exceptions tab, click "Add Port..."
The "Name" can be anything, but I suggest something like "TCP Port 1666 for SQL Server". For the "Port number" enter 1666, and ensure that TCP is selected. Click [OK]
Click [OK] to close the Windows Firewall dialog.
For those that are interested, the port number 1666 comes from the "TCP Dynamic Ports" displayed on the "IP Addresses" tab of the "TCP/IP Properties" of the TCP/IP Protocol listed by SQL Server Configuration Manager.

If you get this error when trying to connect using Microsoft SQL Server Management Studio then try opening UDP port 1434.

Ensure that the SQL Server 2005 Express server process is running.
Check this by:

Start ? Control Panel (classic view) ? Administrative Tools ? Services
Scroll down and check that "SQL Server (SQLEXPRESS)" has the status of "Started". Start it if it is not already started.

**********************************************************************************************************************

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125210

The following error is displayed during the setup of SQL Server Database Services:

"SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2]. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online."

There is a retry and cancel button.
After checking the registry value of ProtocolOrder under \HKEY_LOCAL_MACHINE\SOFTWARE\Microsost\MSSQLServer\Client\SNI9.0 the value is correct, and no changes are required: "sm tcp np" or under SQL Server configuration manager "Shared Manager", "TCP/IP" and "Named Pipes" are all enabled.

Installation FailsCommentsWhen SQL Native Client copies over the legacy registry hive it doesn't enable shared memory. During installation of SQL Server 2005 the SQL Setup program uses the SQL Native Client to connect to the newly installed database instance using shared memory. Since shared memory is not enabled setup fails to connect.

Work Around
When setup encounters this error the error dialog contains a "retry" button.
1) Open Regedit
2) Navigate to \HKEY_LOCAL_MACHINE\SOFTWARE\Microsost\MSSQLServer\Client\SNI9.0
3) Open the key ProtocolOrder, you should see the values tcp and np
4) Add "sm" to the begining to the reg key value. The reg key should look like this after editing:
sm
tcp
np
5) Save the changes to the reg key
6) Go back to SQL setup and click "Retry". Setup should finish installing
**********************************************************************************************************************
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=48653

Problem is that named pipes are not enabled by default.
Try this way..
First install the workstation components alone. Then go to sql configuration tool (under configuration tools) and then under sql native client configuration -> Client Protocols, enable all protocols.

**********************************************************************************************************************
http://my.opera.com/yoroshiku/blog/2007/11/06/sql-server-troubleshooting-named-pipes-provider-could-not-open-a-connection

http://www.mydigitallife.info/2007/10/31/error-has-occurred-while-establishing-a-connection-to-sql-server-2005-which-does-not-allow-local-and-remote-connections/