SQL Server Q&A

Symptoms
Consider the following scenario. In Microsoft SQL Server 2005, you try to run a SQL Server Integration Services (SSIS) package. The SSIS package transfers data between two instances of SQL Server 2005. In this scenario, you may receive an access violation error message. When this problem occurs, the Microsoft Windows Application log contains an event that documents the system error message. The system error message resembles the following:

DTExec.EXE – Application ErrorThe exception unknown software exception (0×40000015) occurred in the application at location 0×7ee8bd9e.Note This problem occurs when Lookup transformations that are in the SSIS package are executed in parallel.This problem does not occur when Lookup transformations that are in the SSIS package are executed sequentially.
Resolution
This problem occurs when Lookup transformations from multiple data flow tasks share the same cache area.Lookup transformations may share the same cache area when the textin the SQLCommand property of one Lookup transformationthat isin a data flow taskis the same asthe textin the SQLCommand property of a Lookup transformationthat is in another data flow task.

Symptoms
After you uninstall Microsoft SQL Server 2005 from a computer that has Microsoft SQL Server 2008 installed, the Microsoft ActiveX Script task in a SQL Server Integration Services package does not run.Additionally, when you try to add an ActiveX Script Task to a new package in BIDS, the task will show a validation error pointing ScriptHost can’t be instantiated.
Resolution
This problem occurs because the Axscphst.dllfile is deleted or is unregistered after you uninstall SQL Server 2005. The Axscphst.dllfile is in the following location:
%SystemRoot0%\Program Files\Microsoft SQL Server\100\COMNote SQL Server 2005 and SQL Server 2008 use the Axscphst.dll file.

Symptoms
Consider the following scenario. In Microsoft SQL Server 2005, you try to run a SQL Server Integration Services (SSIS) package. The SSIS package transfers data between two instances of SQL Server 2005. In this scenario, you may receive an access violation error message. When this problem occurs, the Microsoft Windows Application log contains an event that documents the system error message. The system error message resembles the following:

DTExec.EXE – Application ErrorThe exception unknown software exception (0×40000015) occurred in the application at location 0×7ee8bd9e.Note This problem occurs when Lookup transformations that are in the SSIS package are executed in parallel.This problem does not occur when Lookup transformations that are in the SSIS package are executed sequentially.
Resolution
This problem occurs when Lookup transformations from multiple data flow tasks share the same cache area.Lookup transformations may share the same cache area when the textin the SQLCommand property of one Lookup transformationthat isin a data flow taskis the same asthe textin the SQLCommand property of a Lookup transformationthat is in another data flow task.

Symptoms
Consider the following scenario: You run a SQL Server Integration Services (SSIS) package in SQL Server 2005 or in SQL Server 2008. The SSIS package contains a data flow task. You run the SSIS package on a computer that has low available memory.The low-memory condition may occur temporarily or intermittently. When you run the SSIS package, data buffers are written to disk because of the low-memory condition.In this scenario, you may experience one or more of the following symptoms:
Symptom 1Data is damaged before the data reaches the data flow destination. You find that the data in the data flow destination becomes the following values unexpectedly.”" : NULL, blank, or empty string values0 : Zero value or zero value that has higher precision and scale.0-0-0 0:0:0: Dashed zero date valueNote You will not receive an error message when you experience this symptom.
Symptom 2You receive one of the following data type conversion error messages:
Error message 1

DTS_E_OLEDBERROR.An OLE DB error has occurred. Error code: 0×80004005.
An OLE DB record is available.Source: “Microsoft SQL Native Client”Hresult: 0×80004005Description: “Invalid character value for cast specification”.
Error message 2

DTS_E_COLUMNSTATUSERROR. There was an error with input column “ColumnName” (IDnumber) on input “OLE DB Destination Input” (IDNumber). The column status returned was: “Conversion failed because the data value overflowed the specified type.”.
Symptom 3You receive the following constraint violation error message:

DTS_E_OLEDBERROR.An OLE DB error has occurred. Error code: 0×80004005.
An OLE DB record is available.Source: “Microsoft SQL Native Client”Hresult: 0×80004005Description: “The statement has been terminated.”.
An OLE DB record is available.Source: “Microsoft SQL Native Client”Hresult: 0×80004005Description: “Violation of PRIMARY KEY constraint ‘PrimaryKeyName’. Cannot insert duplicate key in object ‘TableName’.”.
Additionally, if you run the same SSIS package again when memory is available, this issue does not occur.
Resolution
When a low-memory-resource notification is sent to the data flow engine, the data flow engine writes data buffers to disk temporarily.This issue occurs because data values are set to NULL or zero incorrectly when the data flow engine writes data buffers to disk. Therefore, when the data flow engine reads data from data buffers and then writes data to the data flow destination, the data flow destination will contain damaged data values. The damaged data values may also result in data type conversion errors or constraint violation errors.

Symptoms
Consider the following scenario: In Microsoft SQL Server 2008, you use the DTExec.exe or DTExecUi.exe utility to run a SQL Server Integration Services (SSIS) package. You specify a configuration file by using the /ConfigFile option when you run the DTExec.exe or DTExecUi.exe utilities. The configuration file contains many configurations for objects in the package. However, the paths of the objects that are referenced in the configuration file do not exist in the current package. For example, you use a shared configuration file for many packages. However, some variables, connection managers, tasks, or other objects that are referenced in the shared configuration file are not contained in all packages. In this scenario, when you run the command, you receive the following error message:

Code: 0×80012017
Source: Package
Description: The package path referenced an object that cannot be found: “Path”. This occurs when an attempt is made to resolve a package path to an object that cannot be found.
DTExec: Could not import the configuration file Configuration File.
Additionally, if you specify the shared configuration file in Business Intelligence Design Studio (BIDS) when you design the SSIS package, instead of specifying the shared configuration file by using the /ConfigFile option, the package can run successfully. The SupressConfigurationWarnings package setting does not affect this issue.
Note This issue does not occur in SQL Server 2005 Integration Services. In SQL Server 2005 Integration Services, the command provides warning messages as expected for the invalid values. However, the command can run successfully.
Resolution
The fix for this issue was first released in Cumulative Update4 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
973602?(http://support.microsoft.com/kb/973602/LN/) Cumulative update package 4 for SQL Server 2008 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365?(http://support.microsoft.com/kb/970365/LN/) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was releasedMicrosoft SQL Server 2008hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Symptoms
Consider the following scenario.In Microsoft SQL Server 2008, you create a SQL Server Integration Services (SSIS) package.You use the SQL Server configuration type to create a configuration table for the package. In the configuration table, there is an invalid package path in the PackagePath column. For example, a package path does not exist. The package path can be for a connection manager, for an event handler, or for a log provider.In this scenario, when you run the package in SQL Server Business Intelligence Development Studio (BIDS), you receive the following error message:

Error at Package: The connection “Connection Name” is not found. This error is thrown by Connections collection when the specific connection element is not found.
(Microsoft.DataTransformationServices.VsIntegration)
This issue is likely to occur when you use a shared configuration table in multiple packages. In these packages, the configuration filter values in the configuration table are the same for each package. For example, an object, such as a connection manager, does not exist in all packages. Therefore, you experience this issue when you run packages that do not have this object in SQL Server BIDS.
Note This issue does not occur in SQL Server 2005 Integration Services.
Resolution
SQL Server 2008 Service Pack 1Important You must install this fix if you are running SQL Server 2008 Service Pack 1.
The fix for this issue was first released in Cumulative Update5 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
975977?(http://support.microsoft.com/kb/975977/LN/) Cumulative update package 5 for SQL Server 2008 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365?(http://support.microsoft.com/kb/970365/LN/) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was releasedMicrosoft SQL Server 2008hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.