Can not install - workstation components on Longhorn x86 or x64

Is Katmai supported on Longhorn? I tried both x64 and x86 (development edition) on Longhorn x64 and x86 versions respectively. The workstation components get errors and rolled back. Any fix?

I want to try Lognhorn, Katmai, Orcas, Biztalk R2 (on 32-bit platform first) and then x64. Can someone recommend what stacks are tried/supported ?

(Pingala@.discussions.microsoft.com) writes: > Is Katmai supported on Longhorn? I tried both x64 and x86 (development > edition) on Longhorn x64 and x86 versions respectively. The workstation > components get errors and rolled back. Any fix? The Readme says that Katmai runs on Win2003 SP1 x86/x64 and WinXP SP2 x86/x64. It's silent on Vista, Longhorn and Windows 2000. But I can answer the latter: it does not run on Win2000. I've tried. I guess that if you want to run Katmai on Longhorn, that you will have to wait for a later CTP. -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||

Actually, I postponed x64 tests.

On x86 Longhorn (w2k8), I was successful with Katmai when I installed a) .NET Framework 3.5 and b) windows update.

I also installed Orcas CTP and BizTalk 2006 R2 CTP. However, I did not see the Biztalk projects in VS. I am wondering why. I have to check with Biztalk forum.

|||

Has anyone been able to get reporting services for Katmai running on Longhorn?

Thanks,

Can not install - workstation components on Longhorn x86 or x64

Is Katmai supported on Longhorn? I tried both x64 and x86 (development edition) on Longhorn x64 and x86 versions respectively. The workstation components get errors and rolled back. Any fix?

I want to try Lognhorn, Katmai, Orcas, Biztalk R2 (on 32-bit platform first) and then x64. Can someone recommend what stacks are tried/supported ?

(Pingala@.discussions.microsoft.com) writes: > Is Katmai supported on Longhorn? I tried both x64 and x86 (development > edition) on Longhorn x64 and x86 versions respectively. The workstation > components get errors and rolled back. Any fix? The Readme says that Katmai runs on Win2003 SP1 x86/x64 and WinXP SP2 x86/x64. It's silent on Vista, Longhorn and Windows 2000. But I can answer the latter: it does not run on Win2000. I've tried. I guess that if you want to run Katmai on Longhorn, that you will have to wait for a later CTP. -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||

Actually, I postponed x64 tests.

On x86 Longhorn (w2k8), I was successful with Katmai when I installed a) .NET Framework 3.5 and b) windows update.

I also installed Orcas CTP and BizTalk 2006 R2 CTP. However, I did not see the Biztalk projects in VS. I am wondering why. I have to check with Biztalk forum.

|||

Has anyone been able to get reporting services for Katmai running on Longhorn?

Thanks,

Can not find Microsoft.SqlServer.InstApi when trying to run a SMO trace

I install the follwing components

1.Microsoft SQL Server 2005 Management Objects Collection

2.Microsoft Core XML Services (MSXML) 6.0

3.Microsoft SQL Server Native Client

(available from http://www.microsoft.com/downloads/details.aspx?FamilyID=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&DisplayLang=en)

on a clean machine with no SQL Server 2005 client tools.

I get the following error.

Failed to initialize object as reader.
Could not load file or assembly 'Microsoft.SqlServer.Instapi, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.

A gacutil tells me that this assembly is not installed.

Is there are way to run SMO trace without having to install the 2005 client tools and only the Management Objects Collection and necessary components?

Sample code:

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Text;
using System.Windows.Forms;
using Microsoft.SqlServer.Management.Trace;
using Microsoft.SqlServer.Management.Common;

namespace SMOTraceTestProgram
{
public partial class Form1 : Form
{

public Form1()
{
InitializeComponent();
}

private void bStart_Click(object sender, EventArgs e)
{

TraceServer smoTraceServerReader;

ConnectionInfoBase cInfoBase = new SqlConnectionInfo();
SetupConnectionInfoBase((cInfoBase as SqlConnectionInfo));

smoTraceServerReader = new TraceServer();

try
{
smoTraceServerReader.InitializeAsReader(cInfoBase, "2005NOSPIDFilter.tdf");
smoTraceServerReader.Stop();
MessageBox.Show("Trace Started and stopped successfully");
}
catch (Exception exception)
{
StringBuilder sb = new StringBuilder();
sb.Append(exception.Message);

Exception ex = exception.InnerException;
while(ex != null)
{
sb.Append(ex.Message);
ex = ex.InnerException;
}
MessageBox.Show(sb.ToString());
}

}

private void SetupConnectionInfoBase(SqlConnectionInfo sqlConnectionInfo)
{
sqlConnectionInfo.ServerName = eSeverName.Text;

if (eUserName.Text.Length > 0)
{
sqlConnectionInfo.UserName = eUserName.Text;
sqlConnectionInfo.Password = ePassword.Text;
sqlConnectionInfo.UseIntegratedSecurity = false;
}
else
{
sqlConnectionInfo.UseIntegratedSecurity = true;
}

}

}
}

I have reproduced this issue in house and can confirm that this is a problem with the Microsoft SQL Server 2005 Management Objects Collection. We will consider this issue for inclusion in Service Pack 2.

As for workarounds, I don't have one. I tried Gac'cing the missing DLL, but there is apparently more registration required, as evidenced by the new error message I got. ("Failed to initialize object as reader.Failed to get SQL Tools directory path from InstAPI.")

|||

Thanks James,

Appreciate the feedback. For the time being I will get the users of my profiling tool to install management tools from the SQL Server 2005 Install. This seems to install the necessary components for SMO Trace to work.

Look forward to a fix though, as this installs a lot more than is required.

sql

Can not connect to SQL Server

I installed SQL Server 2005 (server and client components) on Windows Server 2003 with SP1. I can connect to this sql server from any other machine. However, I can not connect from this machine to sql servers on other machines. I have tried named pipe and TCP/IP. Neither of them works. The error message is can not establish connection. Any suggestion?

Thanks,

What is the exact error message ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

Here is the error message:

An error has occured while establishing a connection to server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Cound not open a connection to SQL Server) (Microsoft SQL Server, Error 53)

Had enabled the remote connection from other server and can connect that server from other machines.

Thanks,

|||Is a firewall (Perhaps the WIndows default one) installed and configured on the server ? Perhaps then outgoing traffic on the ports is restricted.

-Jens.|||

Also, if you're connecting to a named instance, make sure that you're either specifying the port number in the connection string or you have SQL Browser running on the server machine.

Thanks,
Il-Sung.

Can I install SQL2005 SP2 to TFS server?

Hi!

We have a TFS server include this components:

windows standard R2 server + SP1

Microsoft SQL Server 2005 + SP1

Microsoft Visual Studio 2005 Team Foundation Server - ENU + SP1

Microsoft Windows SharePoint Services 2.0.

Can I install sql 2005 SP2 without any problem?

Best Regards,

Mihaly Demeczky

To my knowledge, there are no know issues with adding SQL Server 2005 SP2. If your SQL Sevrer is on a VHD, make a copy, otherwise, set a 'SavePoint' -just in case.