SQL Server 2016 SSIS package fails with "Unexpected Termination" - sql-server

I have an Integration Services project deployed to SQL Server 2016.
In this project I am extracting data from an old Oracle database using Oracle provider for OLEDB.
the extract package basically truncates a table in the destination (SQL Server 2016) database, and then uses a data flow task to extract a table of about 300,000 rows and about 80 columns (basically just creating a copy on the SQL Server).
when running the package using Visual studio we never ran into any problem. but when running the package from SSISDB, about half the times, the package fails with an "unexpected error". nothing appears in the SSIS log.
Looking into the events log finds the following error:
Faulting application name: ISServerExec.exe, version: 13.0.4457.0, time stamp: 0x5a0384d1
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18666, time stamp: 0x58f32841
Exception code: 0xc0000005
Fault offset: 0x00015608
Faulting process id: 0x37e8
Faulting application start time: 0x01d36de21b43d295
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\ISServerExec.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: 71f91df2-d9d5-11e7-80d7-005056a12e2d
Faulting package full name:
Faulting package-relative application ID:
I have found notes of this problem in SQL Server 2012 with a hotfix by Microsoft, but none for SQL Server 2016.
Things I have tried:
update sql server 2016 to the latest version
change the sql server agent user to a local admin.
change the buffer size and rows
change the max concurrent executions from -1 to 1 (I don't run more than 1 package at a time here)
I also noticed that the failure sometimes happens after about 40 seconds (which is also the time it takes it to run successfully) and sometimes it lingers for about 8-10 minutes, even though the error is logged about 40 seconds from when it started.
Thanks for any help.
Update
I think it was a performance issue. when I reduced the number of rows loaded from 330K to 20K it worked 100% of the time.
So I Changed it to load incrementally (for a single package I didn't think it's a good idea to add RAM).
Thank you all.

Related

SQL Server 2014 crash on Linked Server query

I've been having a recurring issue when attempting to query large results from a linked server. I am using SQL Server 2014 and have a POSTGRESQL Server setup as a Linked Server. I have no problem querying against the Linked server on basic/small results or functions. But on the larger jobs the query will attempt to run for a few minutes and eventually the SQL Server will crash and SSMS will produce this error:
A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)
Here is the version of SQL Server 2014 that I am currently on. I have found that there was a bug regarding this or at least something similar in Windows Server 2012 and had a hotfix but that doesn't apply to my build (Attempted to apply anyways). The OS being used is Windows Server 2016.
Microsoft SQL Server 2014 (SP1-GDR) (KB4019091) - 12.0.4237.0 (X64)
Jul 5 2017 22:03:42
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 14393: ) (Hypervisor)
Has anyone else had this issue? I have TCP/IP, Named Pipes, and Shared Memory enabled in my SQL Server Configuration Manager already and my Linked Server Provider currently has these options enabled: Dynamic parameter, Allow inprocess, Non transacted updated.
UPDATED INFORMATION:
I have checked through some additional potential causes including 32-bit registry key issues and local user issues. I am still encountering this same issue after these changes as well.
Date 8/28/2017 2:32:24 PM
Log Windows NT (Application)
Source Application Error
Category (100)
Event 1000
Computer DBM
Message
Faulting application name: sqlservr.exe, version: 2014.120.4237.0, time stamp: 0x595e7459
Faulting module name: ntdll.dll, version: 10.0.14393.1532, time stamp: 0x5965abad
Exception code: 0xc0000374
Fault offset: 0x00000000000f8363
Faulting process id: 0x13c0
Faulting application start time: 0x01d32034049e1344
Faulting application path: E:\Microsoft SQL Server\MSSQL12.ESCENTRAL\MSSQL\Binn\sqlservr.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 3489af8e-639f-4a54-ac3e-fda719cf75dc
Faulting package full name:
Faulting package-relative application ID:
This is the application error that I am seeing in my SQL Logs when the crash occurs

Error during replication from Oracle to SQL Server 2014

I am implementing a replication from Oracle 12c server to SQL Server 2014 Enterprise Edition.
I have set up the Publisher successfully. .
I am bringing in 2 table elements into SQL Server. These contain date fields
Refer Date Field Mapping done on Publisher
The Subscription gets created fine and when the replication agent runs for the first time, I am facing following error:
Replication-Replication Distribution Subsystem: agent ServerName-TNSNAME-PublisherName-1 failed. The process could not bulk copy into table '"dbo"."Destinationtable"'.
The SQL Logs at C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log contain the minidump of the process when it failed. They mention that SQLSERVR.exe faced a fatal exception
Dump File: SQLDump0004.mdmp : C:\LOgs\SQLDump0004.mdmp
Last Write Time: 5/12/2016 11:02:15 PM
Process Name: sqlservr.exe : C:\Program Files\Microsoft SQL
Exception Code: 0xC0000005 Exception Information: The thread tried to
read from or write to a virtual address for which it does not have the
appropriate access. SqlDumpExceptionHandler: Process 66 generated
fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
Need help going past this error.

SQL Agent: The Package Execution Failed

I have spent the past two days trying to find a solution for this error but I am still struggling to understand the failure.
I am fairly sure the issue is to do with the SQL Agent accessing a Network Drive as I have created identical SSIS packages with the only difference being the location of a flat file, when it runs the version on a Network folder it fails with very little indication of the error.
Its worth pointing out both of the packages run in BIDS, its the SQL Agent that results in the error
I have followed the below link and created a Proxy account and I can confirm the SQL Agent runs under this logon (it says in the Job History)
How do I create a step in my SQL Server Agent Job which will run my SSIS package?
Question is - What is the failure and why? It clearly seems to be something with the network file but I cannot understand what step I am missing?
Thanks

SQL Agent Job failes when trying to execute SSIS package due to some permission issues

I deployed ssis package on sql server 2012. Thereafter scheduled a sql job to run this ssis package weekly.
When I started a job for the first time, it failed with following error.
The job failed. The Job was invoked by User MyDomain\MyUserName. The
last step to run was step 1 (scheduling ssis package).
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server
Execute Package Utility Version 11.0.5058.0 for 64-bit Copyright (C)
Microsoft Corporation. All rights reserved. Started: 2:17:12 PM
Package execution on IS Server failed. Execution ID: 6, Execution
Status:4. To view the details for the execution, right-click on the
Integration Services Catalog, and open the [All Executions] report
Started: 2:17:12 PM Finished: 2:17:17 PM Elapsed: 4.493 seconds.
The package execution failed. The step failed.
I am sure there is some issue with permissions, however I am not able to resolve this.
This package is deleting a content of a folder present on my desktop.
SQL Server instance is running on my machine. I am on a standalone machine.
After searching lot of articles I got an article which helped me identifying actual error :-
Identifying issue
Login sql server instance
Navigate to Integration Service Catalogs
Right Click on your SSISDB catalog and select All Reports -> Standard reports -> All Executions
For your folder, click on All Messages for failed task
Here you will see your error
In my case error was "Access to path 'C:\Users\MyUser\Desktop\Test Folder' is denied". To note there is a section Caller in this report who is trying to access this folder, in my case it was NT SERVICE\SQLSERVERAGENT.
Go to this folder, right click -> Properties -> Security
Under Group/username click Edit -> Inside new pop up Add new user
Now if you are trying to find NT SERVICE\SQLSERVERAGENT user, you won't find since its under a service account which means you will see a user named SERVICE . This is the user you need to add to this folder.
As soon as I added this, my job started running :)
In my case
Identifying issue:
Login sql server instance
Navigate to Integration Service Catalogs
Right Click on your SSISDB catalog and select All Reports -> Standard reports -> All Executions
-check the fail/ red error log report section(overview,all messages,execution performance)
- I went to overview ->clicked execution path -> under error messages clicked view context
this will show you step by step execution. I had a data type mismatch as I reran the sql script in ssms it was giving issue. Once I fixed the data type or removed extra data.
All back to normal
Solution :
I got the same error in SQL agent job ,so I just check SSIS package whether it is running or not then find that package is failing because from proc we are taking input as string and in package I have create a variable datatype object to store the proc input ,When I changed that my SSIS package as well as sql job is running fine now.
I hope this will help you ..
I got the same error while executing the SSIS Job in SQL Agent "Access to the path 'C:\Users\abhis\Documents\Visual Studio 2017\Projects\SSIS\AWS-S3-FileLoad\OracleEmployeeDetails' is denied.".
Solution -
Go to this folder for which you are getting the Access Denied Error,
Go to Folder -> Properties -> Security -> To Change Permission Click
Edit - > Add the user "SERVICE" to the Folder.
\As soon as the "SERVICE" user has been added, Job has executed and completed successfully.\

Not able to connect any remote database server after installing Visual studio 2012

I have a machine which has VS2010 and sql server 2005, 2008 installed.
I were able to connect every remote database server from my application prior to installing VS2012. After installing VS2012 I am getting "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." on code where i have database call.
If i try to connect local database it connects fine.
Also what i tried is connect via server explorer in Visual studio 2010. It connects to local source successfully.
But when i try to connect to remote source it crashes VS2010 and Get following error in Event viewer
Faulting application name: devenv.exe, version: 10.0.40219.1, time stamp: 0x4d5f2a73
Faulting module name: netconfig.dll, version: 1.0.0.5, time stamp: 0x50a60f11
Exception code: 0xc0000005
Fault offset: 0x0000fdac
Faulting process id: 0xb40
Faulting application start time: 0x01ceae0dd4041a18
Faulting application path: C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
Faulting module path: C:\WINDOWS\system32\drivers\imonagent\netconfig.dll
Report Id: 5fec2d1f-1a01-11e3-bf8e-4c001050978f
I have read following post and downloaded utility but it also not indicates any error in my machine
http://social.msdn.microsoft.com/Forums/vstudio/en-US/81e1b380-afe1-46ad-9c91-a588e0a5aa4b/how-to-reenable-remote-sql-server-connections-after-installing-visual-studio-2012
Please help me what to do with this problem
Problem not only occurs while i am debugging but also if somebody trying to view hosted site in my machine which has some remote database server connection
Have a luck via running following command (netsh Winsock reset) from command prompt mentioned in
social.msdn.microsoft.com/Forums/vstudio/en-US/2d11b6f9-3ada-4682-b643-c721a97af4ba/cant-connect-to-database-after-installing-vs-11-pro-beta

Resources