Has anyone seen this before? Anyone know how to fix it? I'm getting pretty
desperate and have found no info about this on any of several web searches.

Sql Server 2005 SP 2 is running on Windows Server 2003, SP 1.
When I installed SQL Server 2005 SP 2, all installations succeeded including
SSIS.

When I try to start the SQL Server Integration Services Service, it fails
with a message that it started and then stopped immediately.
Because Integration Services is not starting, this causes the installation
of Team Foundation Server RTM to fail.

I have tried running the service under the NETWORK SERVICE account, and also
with several domain accounts, all with local Admin privs on the server and
also with Domain Admin group membership. These make no difference.

In the Application event log, I have an error with the following text:
Event Type: Error
Event Source: SQLISService
Event Category: Service Control
Event ID: 260
Date: 12/29/2006
Time: 4:20:21 PM
User: N/A
Computer: <servername>
Description:
Microsoft SSIS Service failed to start.
Error: Method 'GetTaskInfos' in type
'Microsoft.SqlServer.Dts.Server.DtsServer'
from assembly 'MsDtsSrvr, Version=9.0.242.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91'
does not have an implementation.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

[As with most error events I've experienced, clicking the provided link
leads to a page apologizing for the absence of any KB info or explanation.]



ALSO:

SQL Server 2005 Management studio produces an error when trying to establish
an Integration Services connection, with the following detail:


===================================

Cannot connect to <servername>.

===================================

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

------------------------------
For help, click:
http://go.microsoft.com/fwlink?ProdN...r&LinkId=20476

------------------------------
Program Location:

at Microsoft.SqlServer.Management.Smo.Enumerator.Proc ess(Object
connectionInfo, Request request)
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.ObjectExplorer.ValidateConnection(UIC onnectionInfo
ci, IServerType server)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Co nnector.ConnectionThreadUser()

===================================

Connect to SSIS Service on machine "<servername>" failed:
Server execution failed
..


------------------------------
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.GetSer verInfo(String
server, String& serverVersion)
at Microsoft.SqlServer.Dts.SmoEnum.DTSEnum.GetData(En umResult erParent)
at Microsoft.SqlServer.Management.Smo.Environment.Get Data()
at Microsoft.SqlServer.Management.Smo.Environment.Get Data(Request req,
Object ci)
at Microsoft.SqlServer.Management.Smo.Enumerator.GetD ata(Object
connectionInfo, Request request)
at Microsoft.SqlServer.Management.Smo.Enumerator.Proc ess(Object
connectionInfo, Request request)

===================================

Connect to SSIS Service on machine "<servername>" failed:
Server execution failed
..


------------------------------
Program Location:

at
Microsoft.SqlServer.Dts.Runtime.Wrapper.Applicatio nClass.GetServerInfo(String
bstrMachineName, String& serverVersion)
at Microsoft.SqlServer.Dts.Runtime.Application.GetSer verInfo(String
server, String& serverVersion)

I thought SQL 2005 SP2 was only in CTP and SP1 was the only service pack
released so far. Have you tried un-installing SP2?

--
Todd Chittenden


"Tom Murphy" wrote:

Todd is right. SP2 is CTP 3 at the moment.

I would be looking to install SP1 on a new SQL Server 2005 installation
and certainly on a system I did not class as "Dev"



--


Allan Mitchell
http://wiki.sqlis.com | http://www.sqlis.com | http://www.sqldts.com |
http://www.konesans.com




"Todd C" <ToddC (AT) discussions (DOT) microsoft.com> wrote

Thanks for responding. I reinstalled the whole SQL Server and it worked.



"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote