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)