March 26, 2014 at 8:05 am
tlally (3/26/2014)
Would a proxy account help?
If it is a permission issue, yes.
Give the proxy account the required permissions on the folder and you're good to go.
An easy check is to make the proxy account use the user account that was used to develop the package in BIDS.
If it works, it was a permission issue with the SQL Server Agent account.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 26, 2014 at 8:25 am
Tried it with a proxy no joy. But thanks for all your help you have been great.
March 26, 2014 at 8:26 am
Try to write to a file on a local disk. See if that works.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 26, 2014 at 9:11 am
No problem on the local disk so it looks definitely like a permissions issue. How to solve it is the issue as the proxy did not work?
March 26, 2014 at 1:26 pm
tlally (3/26/2014)
No problem on the local disk so it looks definitely like a permissions issue. How to solve it is the issue as the proxy did not work?
It simply means that either you didn't give the proxy enough permissions, or that the folder is not accessible from the server.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 26, 2014 at 11:33 pm
Koen Verbeeck (3/26/2014)
tlally (3/26/2014)
No problem on the local disk so it looks definitely like a permissions issue. How to solve it is the issue as the proxy did not work?It simply means that either you didn't give the proxy enough permissions, or that the folder is not accessible from the server.
+1, so any luck on this one ?
March 27, 2014 at 4:38 am
Thanks Koen
I finally found the issue, the sql server agent service account did not have permissions to the drive.This was further complicated by the fact that the drive I was trying to link to and the SQL server are on 2 different domains.
After I solved the permissions issues it still would not run but I did some research and the in the path in the package you need to use the UNC instead of the mapped drive. All working now. Thanks .
However I have another issue I am now trying to pull an excel file into a sql table same scenario it works in VS but will not work in the agent. Error below:
Started: 10:28:43
Error: 2014-03-27 10:28:44.42
Code: 0xC001000E
Source: ExcelDims
Description: The connection "{EFC6889A-D312-4A9E-B251-877C7A67B8DF}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error
Error: 2014-03-27 10:28:44.45
Code: 0xC001000E
Source: ExcelDims
Description: The connection "{EFC6889A-D312-4A9E-B251-877C7A67B8DF}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error
Error: 2014-03-27 10:28:44.45
Code: 0xC001000E
Source: ExcelDims
Description: The connection "{EFC6889A-D312-4A9E-B251-877C7A67B8DF}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error
Error: 2014-03-27 10:28:44.45
Code: 0xC00291EB
Source: TruncateDimTables Execute SQL Task
Description: Connection manager "{EFC6889A-D312-4A9E-B251-877C7A67B8DF}" does not exist.
End Error
Error: 2014-03-27 10:28:44.45
Code: 0xC0024107
Source: TruncateDimTables
Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 10:28:43
Finished: 10:28:44
Elapsed: 0.609 seconds
March 27, 2014 at 4:43 am
Are you deleting connection managers?
These types of errors occur when a connection manager is deleted, but it is still referenced by a task or component.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 27, 2014 at 5:17 am
Koen Verbeeck (3/27/2014)
Are you deleting connection managers?These types of errors occur when a connection manager is deleted, but it is still referenced by a task or component.
Another possibility that your ssis package is pointing to some other connection which might have been deleted or renamed .Try opening the SSIS compoenents and point to the correct connection which are there in your connection manager. It happens when we copy the SSIS package components to create a new package or because of renaming the connections or there may be still components which are using the old connection.
Hope it helps
March 27, 2014 at 8:48 am
I recreated the package from the beginning new connection managers but I am still getting the same error.
The connection "{EFC6889A-D312-4A9E-B251-877C7A67B8DF}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
March 27, 2014 at 11:27 am
tlally (3/27/2014)
I recreated the package from the beginning new connection managers but I am still getting the same error.The connection "{EFC6889A-D312-4A9E-B251-877C7A67B8DF}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
Search for the GUID in the XML of the package and see where it is referenced. Maybe it's somewhere hidden, such as in the logging.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 6, 2014 at 3:30 pm
Are you using file system for your deployment? If so, the project connection managers are not supported. Try deploying the SSIS package to the SSIS Catalog and execute the SSIS package through the SQL Agent using SSIS Catalog rather than file system.
Hope this helps.
August 13, 2014 at 1:37 am
Try using the server name rather than L:\ in your Connection Manager
If that doesn't work then try setting up a Proxy Credential that has got access to write to the destination server. Here's an article on the subject http://www.codeproject.com/Articles/28918/SQL-Server-Agent-Proxy
December 26, 2014 at 9:03 am
Searching for a solution for this very same issue...I ran across an older post that seems to be dead on. Now, just need a fit....other than moving the connection to package level.
"I'm a little late to the party, but I ran across this thread while experiencing the same errors and found a different resolution.
When creating an SSIS 2012 package, in the Solution Explorer window you will see the Connection Managers folder at the project level. This seems like the most logical place to create a connection, and should be used when creating a connection that can be used by any package in the project. It is included at the project level, and not the package level.
When running my dtsx package using dtexec, I received the same errors shown above. This is because the connection is not included in the package (just the project). My solution was to go into the package designer, and then in the Connection Manager window, right click the project level connection (which is shown using the "(project)" prefix) and choose "Convert to Package Connection". This will embed the connection in the actual dtsx package. This alleviated my problem." - jhughs answered Jun 25 at 22:28
October 22, 2015 at 9:13 am
Post deleted and transferred under 2012 general
Viewing 15 posts - 16 through 30 (of 30 total)
You must be logged in to reply to this topic. Login to reply