So interesting problem that I ran into with regards to maintenance plans and SQL Server 2012/2014.
The test case for this is on a clustered Windows 2012 R2 environment install SQL of your choice without SSIS installed. Create a maintenance plan that just does "select 1" and it will run fine via SQL Agent. Now, install SSIS, and the job now fails due to:
Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection.
Even when uninstalling SSIS, the package still fails when being run through SQL Agent. In all cases, the package can be run via the command line or through Integration Services directly.
The connection string is:
Data Source=instance\name;Integrated Security=True;Pooling=False;MultipleActiveResultSets=False;Packet Size=4096;Application Name="Microsoft SQL Server Management Studio";
It seems like SSIS changes some type of reference to the package but I can't narrow down what is causing this to fail. I've compared registry keys as well with other instances and there isn't anything would would reference '.\name' or anything to that effect that would black hole it.
Named pipes, shared memory, and TCP/IP are all enabled and firewall rules both outbound and inbound are open as well. Also, @@servername returns as expected.
Thoughts on what to check for next?