Wednesday, July 18, 2012 5:34 PM
SQL 2008 fully patched with a two node active/passsive cluster. Currently, one named instance has been created. Connecting to the instance with SSMS and drilling down to the MSDB folder, I get an error on any remote machine (including the passive node):
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
The SQL Server instance specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in Server 2008 Books Online.
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. (MsDtsSvr)
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. (Microsoft SQL Server Native Client 10.0)
I've already edited the MsDtsSrv.ini.xml file to contain the full instance name, which seemed to be the most accepted solution in my searching, but my error still remains.
The issue only occurs on remote machines, the active node works fine. Any solution to this?
- Moved by amber zhang Friday, July 20, 2012 1:41 AM (From:SQL Server High Availability and Disaster Recovery)
Wednesday, July 18, 2012 7:02 PMTo add to the issue (may be related) - when you actually try to deploy a package on the active node, it only shows the local node in the server area instead of the full cluster instance path. I do have another cluster at a different location and everything functions fine, so I don't know if something was missed. Does it all come down to not having a default instance?
Thursday, July 26, 2012 10:42 AMModerator
Clustering Integration Services is not recommended because the Integration Services service is not a clustered or cluster-aware service, and does not support failover from one cluster node to another. Therefore, in a clustered environment, Integration Services should be installed and started as a stand-alone service on each node in the cluster.
Although the Integration Services service is not a clustered service, you can manually configure the service to operate as a cluster resource after you install Integration Services separately on each node of the cluster. Please refer to the details in the following article:
Configuring Integration Services in a Cluster: http://msdn.microsoft.com/en-us/library/ms345193(v=sql.105).aspx
If you have any question, please feel free to ask.
Thursday, July 26, 2012 3:05 PMI should have clarified - I understand that Integration Services is not clustered service and it is setup as a non-failover service. I've opened a ticket with Microsoft, but the first few calls have them scratching their heads as they agree everything is setup/configured properly for the funcationality I'm trying to achieve.