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
This article describes one possible reason as to why a Data Transformation Services (DTS) package created in Microsoft Visual Basic code may fail with an access violation (AV) error message.
When you create a DTS package by using the WITHEVENTS keyword, and you then run the DTS package from within Microsoft Visual Basic code, the package fails with an access violation and the following error message occurs:

Microsoft dts package provider generated code execution exception;
exception access violation 2147221499.Need to run the object to
perform this operation.
Resolution
The following five events are associated with a DTS package when the DTS package is created by using the WITHEVENTS clause:

Private Sub <object>_OnError(ByVal EventSource As String, _ByVal ErrorCode As Long, _ByVal Source As String, _ByVal Description As String, _ByVal HelpFile As String, _ByVal HelpContext As Long, _ByVal IDofInterfaceWithError As String, _ByRef pbCancel As Boolean)Private Sub <object>_OnFinish(ByVal EventSource As String)Private Sub <object>_OnProgress(ByVal EventSource As String, _ByVal ProgressDescription As String, _ByVal PercentComplete As Long, _ByVal ProgressCountLow As Long, _ByVal ProgressCountHigh As Long)Private Sub <object>_OnQueryCancel(ByVal EventSource As String, _ByRef pbCancel As Boolean)Private Sub <object>_OnStart(ByVal EventSource As String)If code for these events is not present, the error message described in the “Symptoms” section occurs.
For more information about these events, please see the following article in the Microsoft Knowledge Base:
221193?(http://support.microsoft.com/kb/221193/) How to install Data Transformation Services (DTS) event handlers in Visual Basic

Symptoms
When you try to add a configuration to a Microsoft SQL Server 2005 Integration Services .dtsx package, you receive the following error message:

An error occurred while a new configuration was being added.
Additional information
The path is not of a legal form. (mscorlib)
Resolution
This problem occurs because the .dtsx package is not associated with a business intelligence solution.

Symptoms
This article describes one possible reason why a Data Transformation Services (DTS) package created in Microsoft Visual Basic code may fail with an error message and an access violation (AV).
When you create a DTSTransferObjectsTask task in a DTS package and specify the WITHEVENTS keyword, and you then run the DTS package from Microsoft Visual Basic code, the package may fail with the following error message:

ErrorCode: -2147221499
Source: Microsoft Data Transformation Services (DTS) Package
Description: Need to run the object to perform this operation After you set a breakpoint at the beginning of the OnProgress procedure, and you single step through your OnProgress code in Visual Basic, you will see the underlying access violation (AV):

Package failed error: x80040005, x80040000 + 5
Provider generated code execution exception: EXCEPTION_ACCESS_VIOLATION Then, Dr. Watson shows an error message similar to the following:

The instruction at “0×0fa9183f” referenced memory at “0×00000001″. The memory could not be “read”. When you run the Visual Basic application under the debugger WinDbg you will see a first chance exception of type access violation in OLEAUT32!SysAllocStringByteLen.
NOTE: This article is specifically about the OnProgress event of a DTSTransferObjectsTask!
The most common causes for the error message and access violation when you use DTS in Visual Basic applications are described in the following Microsoft Knowledge Base article:
271889?(http://support.microsoft.com/kb/271889/EN-US/) PRB: Error Message: “Exception Access Violation 2147221499.Need to run the object to perform this operation” Occurs When You Run a DTS Package in Microsoft Visual Basic Code
Resolution
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211?(http://support.microsoft.com/kb/290211/EN-US/) INF: How To Obtain the Latest SQL Server 2000 Service PackNOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.
The English version of this fix should have the following file attributes or later:

DateTimeVersionSizeFile name————————————————————–06-Jan-200220:238.00.5661,901,120 bytesDtspkg.dll NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.

Symptoms
SummarySymptomsResolution
Service pack information
Hotfix information
Prerequisites
Restart information
Hotfix file informationWorkaroundStatusMore Information
Stack information
Resolution
This article describes the following about this hotfix release:The issues that are fixed by this hotfix package.The prerequisites for installing the hotfix package.Whether you must restart your computer after you install the hotfix package.Whether the hotfix package is replaced by any other hotfix package.Whether you must make any registry changes. The files that are contained in the hotfix package.

Symptoms
This article describes the following about this hotfix release: The issues that are fixed by this hotfix package.The prerequisites for installing the hotfix package.Whether you must restart your computer after you install the hotfix package.The files that are contained in the hotfix package.
Resolution
When you open a database in Microsoft SQL Server 2000, you notice that a user database is marked as suspect. Also, an error message that is similar to the following is logged in the SQL Server 2000 error log:

<Date> <Time> spid9 Recovery of database ‘UserDatabaseName’ (5) is 2% complete (approximately 185 more seconds) (Phase 3 of 3).
<Date> <Time> spid9 Using ‘dbghelp.dll’ version ‘4.0.5′ *Dump thread – spid = 9, PSS = 0×80178098, EC = 0×801783c0
<Date> <Time> spid9 The exception information has been submitted to Watson error reporting.
<Date> <Time> spid9 Stack Signature for the dump is 0×986D5509
<Date> <Time> spid9 SQL Server Assertion: File: <page.cpp>, line=3430 Failed Assertion = ‘m_freeCnt + emptySlots * sizeof (Slot) >= spaceNeed’.
<Date> <Time> spid9 Location: page.cpp:3430 Expression: m_freeCnt + emptySlots * sizeof (Slot) >= spaceNeed