September 8, 2015 at 7:36 am
Dear All,
I'm trying to execute a SSIS package via proxy user but I keep getting the following error message regardless of I have tried to do to fix it, I have done the following so far:-
1. Recreated the proxy user
2. Retyped the password, under credentials
Message
Unable to start execution of step 1 (reason: Error authenticating proxy "proxyname", system error: Logon failure: unknown user name or bad password.). The step failed.
Thank you in advance!
September 8, 2015 at 8:16 am
I have something like this
/****** Object: ProxyAccount [proxySSIS] Script Date: 8/09/2015 16:12:43 ******/
IF NOT EXISTS (SELECT name FROM msdb.dbo.sysproxies WHERE name = N'proxySSIS')EXEC msdb.dbo.sp_add_proxy @proxy_name=N'proxySSIS',@credential_name=N'SSISProxyCredentials',
@enabled=1,
@description=N'Proxy used to execute SSIS packages'
GO
EXEC msdb.dbo.sp_grant_proxy_to_subsystem @proxy_name=N'proxySSIS', @subsystem_id=11
GO
EXEC msdb.dbo.sp_grant_login_to_proxy @proxy_name=N'proxySSIS', @login_name=N'MYSSISPOWERUSER'
GO
SSISProxyCredentials maps to a windows login
September 9, 2015 at 2:52 am
Thank you for your reply. I have already tried to recreate the proxy. The only thing which is unusual is that the source data is on another server but the connection is successful, I'm just guessing at the moment as I have tried every possible fix I can think of.
Thank you!
September 9, 2015 at 3:29 am
source data is on another server ?
More like a linked server setup (run package on server A to access data from server B)?
September 9, 2015 at 4:02 am
The package gets data from various servers but the job which I'm trying to create is on a different server.
As I said I'm not sure if that is the problem because the connection test was successful on the package.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply