Assume that you have some SQL Server Integration Services (SSIS) packages that contain Execute Package Tasks (EPTs). You run these packages by using SQL Server Agent jobs in Microsoft SQL Server 2012. In this situation, the packages fail intermittently, and you receive the following error message:
Additionally, the following error messages are logged in the Application log:
Faulting application name: ISServerExec.exe, version: 11.0.3000.0, time stamp: 0x5081b8ff
Faulting module name: clr.dll, version: 4.0.30319.296, time stamp: 0x50483916
Exception code: 0xc0000005
Fault offset: 0x0000000000179a3f
Faulting process id: 0x3154
Faulting application start time: 0x01cdf4ed4154ea0a
Faulting application path: SystemDrive:\Program Files\Microsoft SQL Server\110\DTS\Binn\ISServerExec.exe
Faulting module path: SystemDrive:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 82e939b4-60e0-11e2-98cc-6431504cbc78
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEF8AD9A3F (000007FEF8960000) with exit code 80131506.
Cumulative update information
Cumulative Update 4 for SQL Server 2012 SP1
The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to go to the article in the Microsoft Knowledge Base:
Cumulative update 4 for SQL Server 2012 SP1
Given that 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 2012 SP1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to go to the article in the Microsoft Knowledge Base:
The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note
If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note
The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To apply this hotfix, you must have SQL Server 2012 installed.
You do not have to restart the computer after you apply the hotfix.
The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone
tab in the Date and Time
item in Control Panel.
Collapse this imageExpand this image
Collapse this tableExpand this table
|File name||File version||File size||Date||Time||Platform|
Collapse this imageExpand this image
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.