Hello,
I've a request from a dev team to create a SSIS package where it simply has a Analysis Services Processing task which what it does is to refresh SSAS analysis services database cube.
I've been working with SQL Data Tools project from scratch where I have setup correctly the connection to the SSAS server, the Test Connection works fine, I execute the package via SQL Data Tools, it works fine too.
But when I deploy the package to the SQL server SSIS Catalog, after the deploy I can't execute the package successfully via SQL Server 2014 Management Studio, it simply gives the error "A connection cannot be made. Ensure that the server is running",
but if I create a SQL Agent job and have configure a step with that SSIS package, and run that job manually, it run's fine.
Also I've tried in SSIS package to use impersonation and even tried with the domain administrator account which as permissions as sysadmin in SQL Server and Administrator permissions in SSAS service, and the problem of executing the package manually via SQL
Management Studio still persists.
In SQL Profiler when I start the SSIS package via SQL Agent, appears as started by the configured user proxy "Administrator", when started manually in SSIS Catalog in SQL Studio Management, in SQL Profiler only shows Login and Logout of an Anonymous
User?!
Since this does not make sense this behavior, I think that this might be a bug. Can someone give some help or any ideia in what am I doing wrong?
Notes: This situation happens in a Production environment, but also happens in a test environment using the AdventureWorks DB with the Analysis Services in Multidimensional and Tabular mode with demo projects of AdventureWorks cubes where the error results
are the same.
Notes-2: I've attached to this post print screens of SQL Profiler with Event's filtered by Audit Logons, with logs of the SSIS package working via SQL Agent and another print screen with logs of the same SSIS package started manually via SQL Studio Management
in SSIS Catalog where it gives the error.
Notes-3: This problem is reproducible if trying to execute manually the SSIS package via SQL Management Studio but you must connect to the SQL server remotely, and SQL Engine and SQL Analysis Services must be installed in 2 separated servers in same AD domain
Thanks for your attention,
Best Regards
PS: This situation is also published with print screens in Microsoft Connect - Microsoft SQL Server Feedback:
https://connect.microsoft.com/SQLServer/feedback/details/1391769/ssis-2014-analysis-services-processing-task-connection-cannot-be-made