SSIS job was working fine from sql server agent with local sytem account. it is started failing since the account is changed from local system account to a domain account. the new domail account is also added into administrators group in that server. 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 10.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." windows account also has all the permissions as mentioned here. http://technet.microsoft.com/en-us/library/ms143504.aspx#Review_windows_permissions

Have you checked the FAQ : http://support.microsoft.com/kb/918760.Happy to help! Thanks. Regards and good Wishes, Deepak. In a revamp of my Blog!

SSIS job was working fine from sql server agent with local sytem account. it is started failing since the account is changed from local system account to a domain account. the new domail account is also added into administrators group in that server. 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 10.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." windows account also has all the permissions as mentioned here. http://technet.microsoft.com/en-us/library/ms143504.aspx#Review_windows_permissions You are using the SQL Server Destination, right? Take a read of this: http://consultingblogs.emc.com/jamiethomson/archive/2006/08/14/4344.aspx it explains the extra permissions required to use the SQL Server Destination. Another option would be to stop using the SQL Server Destination and use the OLE DB Destination instead. In fact, even if you weren't getting this error I would recommend doing that. There used to be a very good reason for using SQL Server Destination (it was the quickest way to get data into a SQL Server database) but approximately 5 years ago Microsoft made some improvements to OLE DB Destination that meant this was no longer the case. Hence, there are now zero reasons to use the SQL Server Destination and I always ALWAYS recommend to never use it. @jamiet http://sqlblog.com/blogs/jamie_thomson/ | @jamiet | About me

I tried this method, but didn't work. then changed to OLEDB destination.