I run the SSIS 2012 package and got following error. SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E14. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80040E14 Description: "Could not bulk load because SSIS file mapping object 'Global\DTSQLIMPORT ' could not be opened. Operating system error code 5(Access is denied.). Make sure you are accessing a local server via Windows security." I saw similar posts. The solution would be - set Local Security Policy - "create global objects". I run the package by 'Administrator' user that permitted the "create global objects". In the Connection manager, the authentication is SQL Server Authentication and specified sa user. It is not remote environment. Run the package on the Server machine. If I changed to Windows Authentication in the connection manager, it works fine. If I switched OLD DB destination, the package works fine. Any idea to solve this issue to keep 'SQL Server destination' and 'SQL Server authentication'?

Don't use the SQL Server Destination. As you noticed, it is buggy, you need to have too much permission to use it and it has too much restrictions. The OLE DB Destination with Fast Load is most of the times as good as the SQL Server Destination. Even the SSIS development team discourages the use of the SQL Server Destination. MCTS, MCITP - Please mark posts as answered where appropriate.

Hi yoshik_ss, Users who execute packages that include the SQL Server destination require the "Create global objects" permission. You can grant this permission to users by using the Local Security Policy tool opened from the Administrative Tools menu. If you receive an error message when executing a package that uses the SQL Server destination, make sure that the account running the package has the "Create global objects" permission. Please refer to: http://msdn.microsoft.com/en-us/library/ms141095.aspx Thanks, Eileen

Hi Eileen, I have already set the permission to the user executed the packages. Is there any other check point? Y

Why are you so determined to use this component? It is established by the SSIS development team theirselves that with the most recent versions of SSIS, there's practically no performance gain over the OLE DB Destination with Fast Load. In fact, in some cases it's even slower than the OLE DB Destination. And last but not least, it's not portable. If someday the server becomes remote, you'll have to change the package. Save yourself some misery and switch to the OLE DB Destination.MCTS, MCITP - Please mark posts as answered where appropriate.