May 17, 2011 at 1:35 pm
I have a question regarding running SSIS packages from SQL server agent jobs. I have a package that has a component I got from this website (http://ssissshcomponents.codeplex.com/, it connects to a site and downloads a file via secure ftp (ssh)) It works beautifully from my desktop, and our network admin is able to log onto our sql server and run it manually fine. But when I try to schedule it, I get the following error:
Code: 0xC0014005
Source:
Description: The connection type "SSH" specified for connection manager "name" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
End Error
Has anyone experienced packages running from their desktop but not when scheduled? We have setup a proxy acct and tried the troubleshooting tips on this site (http://support.microsoft.com/kb/918760/en-us)
Any suggestions would be appreciated, thanks
May 17, 2011 at 2:32 pm
When your network admin logged in and ran the package manually on the server did he log in as himself or using the proxy account?
Being that its a third-party component and a proxy account a lot of things could be going wrong.
I would start with:
> Does the proxy account have limited permissions on the server or is it part of the local admin group?
> Is there anything you needed to do to make the SSH connection type usable in your development environment? e.g. like loading Visual Studio and accept some license agreement?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply