SQL Server Q&A

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
You install Microsoft SQL Server 2008 on a computer that is running Windows XP. Then, you upgrade Windows XP to Windows Vista. When you run a query in SQL Server Management Studio, you receive the following error message:

The type initializer for ‘Microsoft.SqlServer.Management.UI.Grid.ColumnInfo’ threw an exception.However, you can successfully run the query in Windows XP.
Resolution
This problem occurs because the Windows Vista Setup program incorrectly replaces the Mscorlib.dll file of the Microsoft .NET Framework 2.0 Service Pack 1 (SP1). The Mscorlib.dll file of the later version of the file contains the DateTimeOffset data type. This data type does not exist in the earlier version of the Mscorlib.dll file.
When you install SQL Server 2008, SQL Server 2008 installs the .NET Framework 3.5 Service Pack (SP1). The .NET Framework 3.5 SP1 also installs the .NET Framework 2.0 SP1, and this service pack contains the later version of the Mscorlib.dll file. However, the Windows Vista Setup program replaces this version of the Mscorlib.dll file with the earlier version of the Mscorlib.dll file.

Symptoms
When you run a Windows application project that indirectly references the Microsoft.VisualBasic.Compatibility library from Microsoft Visual Studio .NET 2002, the reference lookup fails, and you may receive the following error message:

An unhandled exception of type ‘System.IO.FileNotFoundException’ occurred in system.windows.forms.dll
Additional information: File or assembly name Microsoft.VisualBasic.Compatibility, or one of its dependencies, was not found.
Resolution
To work around the problem, follow these steps: Create an application configuration file that is named App.config for the MyRTMClientApp.exe Windows application project that you create in step 3 of the “More Information” section.
For additional information about how to add the App.config file to the Windows application project, click the following article number to view the article in the Microsoft Knowledge Base:
822752?(http://support.microsoft.com/kb/822752/)PRB: Application configuration file is deleted when you build the solutionAdd the following code to the App.config file:

<?xml version =”1.0″?><configuration><startup><supportedRuntime version=”v1.1.4322″ safemode=”true”/><requiredRuntime version=”v1.1.4322″ safemode=”true”/></startup><runtime><assemblyBinding xmlns=”urn:schemas-microsoft-com:asm.v1″><dependentAssembly><assemblyIdentity name=”Microsoft.VisualBasic.Compatibility” publicKeyToken=”b03f5f7f11d50a3a” culture=”neutral” /><bindingRedirect oldVersion=”7.0.3300.0″ newVersion=”7.0.5000.0″/></dependentAssembly></assemblyBinding></runtime></configuration>Double-click MyRTMClientApp.exe to run the Windows application project.

Symptoms
In Microsoft SQL Server 2008, when you use the Flat File source to enable a package to read data from a text file, or you use the Flat File connection manager to enable a package to extract and load data from a flat file, some rows are parsed incorrectly. Additionally, data may beattributed to the wrong columns in some rows.
This problem occurs for one of the following reasons:The flat file contains comma-separated values (CSV).The flat file contains a different delimiterthat contains a variable number of columns.
Resolution
This problem occurs because the Flat File source and the Flat File connection manager in SQL Server 2008 Integrated Services (SSIS) do not support “Ragged right format” reading of delimited flat files if the files contain a different number of delimiters in the rows.
Note This problem may cause the parser to read ahead and fill the rest of the row with values from the next row.