Showing posts with label default. Show all posts
Showing posts with label default. Show all posts

Thursday, March 29, 2012

Failed to script out Dropping Default Constraint script for table columns

I used the following code to script out Creating default constraints. It works fine. But if I change so.ScriptDrops = true to script Dropping default constraints, it always fails with

Exception: {"Script failed for DefaultConstraint 'DF_Employee_VacationHours'. "}

InnerException: {"Object reference not set to an instance of an object."}

Can anyone shred some light on it? Thanks in advance.

using System;

using System.Collections.Generic;

using System.Collections.Specialized;

using System.Text;

using Microsoft.SqlServer.Management.Smo;

using Microsoft.SqlServer.Management.Common;

namespace Test2

{

class Program

{

static void Main(string[] args)

{

Server s = new Server(".");

StringCollection sc;

ScriptingOptions so=new ScriptingOptions();

so.ScriptDrops = false;

s.ConnectionContext.SqlExecutionModes = SqlExecutionModes.CaptureSql;

foreach (Table t in s.Databases["Adventureworks"].Tables)

{

foreach (Column c in t.Columns)

{

if (c.DefaultConstraint!=null)

{

Console.WriteLine(string.Format("{0},{1}", t.Name, c.Name));

sc=c.DefaultConstraint.Script(so);

foreach (string st in sc)

{

Console.WriteLine(string.Format("{0}", st));

}

sc = null;

}

}

}

return;

}

}

}

Hi,

Thank you for reporting this issue. This is a defect in SMO, and we're filing a bug report. We will try to fix it for the next release of the product.

Friday, March 23, 2012

Failed to enumerate changes in the filtered articles. Incorrect syntax near '-'.

Thanks Kestutis,
the only hotfix I'm aware of that might be relevant is
http://support.microsoft.com/default.aspx?scid=kb;en-
us;810072
There is a completish list at
http://www.aspfaq.com/show.asp?id=2160 so one could wade
through it to see if there is anything relevant, but the
format of the list means that this'll take ages -
definitely one for Hilary's secret contact.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
I think description of the problem and MS supported fix for it can be found
at http://support.microsoft.com/default...b;en-us;814916 but as I
mentioned you can get this fix only by contacting PSS. And also I was unable
to find "a success story" on the web from someone who applied this fix... I
was only able to find a short message from someone, that he applied the fix
and replication was working afterwards - no details, whatsoever..
Thanks for the link to SQL Server versions list, that's a really good
collection.
Would also be interesting to know which of those fixes do changes on
"database side" - I mean not fixing some executables or dll's, but making
changes to system SP's or table schema's (the area, where we can also make
some modifications). But I'm afraid we have to gather such information by
ourselves.
Regards,
Kestutis Adomavicius
Consultant
UAB "Baltic Software Solutions"
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:236001c4dd48$1e32b540$a301280a@.phx.gbl...
> Thanks Kestutis,
> the only hotfix I'm aware of that might be relevant is
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;810072
> There is a completish list at
> http://www.aspfaq.com/show.asp?id=2160 so one could wade
> through it to see if there is anything relevant, but the
> format of the list means that this'll take ages -
> definitely one for Hilary's secret contact.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>

Monday, March 19, 2012

Failed in installation, ERROR:29503

Hi, Folks

My story is a bit of similar to some of the fellows. During the default installation, it failed at the last section which is "SQL server database service" because it cannot start the SQL service.

The difference of my story is this is not the first time I install it on my computer or any upgrade from whatever other version. I'd installed it for a couple of weeks working perfectly before my computer seemingly infected by an adware. Since then SQL Server stopped working, then I decided to re-install it after I had the adware removed.

So it shouldn't be the limitation of either CPU or memory, I think. I hope I could get an answer to it before I have to re-install the whole OS, PAINFULLY.

CONTENT OF SUMMARY.LOG


Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Mon Jul 10 22:53:32 2006
Machine : YANG
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SQLSupport_1.log
--
Machine : YANG
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SQLNCLI_1.log
--
Machine : YANG
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SqlWriter_1.log
--
Machine : YANG
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_MSXML6_1.log
--
Machine : YANG
Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How

to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
--
Machine : YANG
Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How

to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
--
Machine : YANG
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SQL.log
Last Action : InstallFinalize
Error String : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How

to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated

unexpectedly.
Error Number : 29503
--

SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup

Bootstrap\LOG\Summary.txt.


Time : Mon Jul 10 22:57:30 2006


List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SQLSupport_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SQLNCLI_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SqlWriter_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_MSXML6_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SQL.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SNAC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SCC.log
c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

|||

CONTENT OF ERROR.LOG

2006-07-10 22:56:35.05 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

2006-07-10 22:56:35.05 Server (c) 2005 Microsoft Corporation.
2006-07-10 22:56:35.05 Server All rights reserved.
2006-07-10 22:56:35.05 Server Server process ID is 504.
2006-07-10 22:56:35.05 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2006-07-10 22:56:35.05 Server Registry startup parameters:
2006-07-10 22:56:35.05 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-07-10 22:56:35.05 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-07-10 22:56:35.05 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-07-10 22:56:35.05 Server Command Line Startup Parameters:
2006-07-10 22:56:35.05 Server -m SqlSetup
2006-07-10 22:56:35.05 Server SqlSetup
2006-07-10 22:56:35.05 Server -Q
2006-07-10 22:56:35.05 Server -q Chinese_PRC_CI_AS
2006-07-10 22:56:35.05 Server -T 4022
2006-07-10 22:56:35.05 Server -T 3659
2006-07-10 22:56:35.05 Server -T 3610
2006-07-10 22:56:35.05 Server -T 4010
2006-07-10 22:56:35.44 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2006-07-10 22:56:35.44 Server Detected 1 CPUs. This is an informational message; no user action is required.
2006-07-10 22:56:35.47 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2006-07-10 22:56:35.55 Server Database Mirroring Transport is disabled in the endpoint configuration.
2006-07-10 22:56:35.56 spid5s Warning ******************
2006-07-10 22:56:35.56 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required.
2006-07-10 22:56:35.56 spid5s Starting up database 'master'.
2006-07-10 22:56:35.79 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2006-07-10 22:56:36.44 spid5s SQL Trace ID 1 was started by login "sa".
2006-07-10 22:56:36.50 spid5s Starting up database 'mssqlsystemresource'.
2006-07-10 22:56:37.25 Server Error: 26011, Severity: 16, State: 1.
2006-07-10 22:56:37.25 Server The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security.dll exists on the system.
2006-07-10 22:56:37.25 Server Error: 17182, Severity: 16, State: 1.
2006-07-10 22:56:37.25 Server TDSSNIClient initialization failed with error 0x139f, status code 0x80.
2006-07-10 22:56:37.25 Server Error: 17182, Severity: 16, State: 1.
2006-07-10 22:56:37.25 Server TDSSNIClient initialization failed with error 0x139f, status code 0x1.
2006-07-10 22:56:37.25 Server Error: 17826, Severity: 18, State: 3.
2006-07-10 22:56:37.25 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2006-07-10 22:56:37.25 Server Error: 17120, Severity: 16, State: 1.
2006-07-10 22:56:37.25 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

|||OMG, guess what... It's installed SUCCESSFULLY again just now while I tried to figure out in which part it had failed. I sware I haven't done anything specially tonight. Well, difference, tonight I'm thinking seriously of re-install my Windows XP rather than looking for solutions as what I was doing in last few nights. Oh...don't juggle with me. I don't know who, Windows XP or SQL server 2005 express edition.|||

There certainly seemed to be some problems with the installation based on your log, but if it's installed and working that's probably well enough. Tought to say if your adware incident was the cause of this, or if the problems you're seeing are related to it.

I'd say leave it be for a week to see what happens before you consider re-install of Windows, but that's your call.

Mike

|||

Hi Mike

Thanks for your eye on my topic.

The service stopped again and refused being stared manually. I checked Configuration Manager, and both SQL Server and SQL Server Browser stopped.

The ERRORLOG has same content as above.

Then I changed login account in both services from Network Service to Local System, now they are running.

Monday, March 12, 2012

Failed in installatio, ERROR:29503

Hi, Folks

My story is a bit of similar to some of the fellows. During the default installation, it failed at the last section which is "SQL server database service" because it cannot start the SQL service.

The difference of my story is this is not the first time I install it on my computer or any upgrade from whatever other version. I'd installed it for a couple of weeks working perfectly before my computer seemingly infected by an adware. Since then SQL Server stopped working, then I decided to re-install it after I had the adware removed.

So it shouldn't be the limitation of either CPU or memory, I think. I hope I could get an answer to it before I have to re-install the whole OS, PAINFULLY.

CONTENT OF SUMMARY.LOG


Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Mon Jul 10 22:53:32 2006
Machine : YANG
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SQLSupport_1.log
--
Machine : YANG
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SQLNCLI_1.log
--
Machine : YANG
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SqlWriter_1.log
--
Machine : YANG
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_MSXML6_1.log
--
Machine : YANG
Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How

to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
--
Machine : YANG
Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How

to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
--
Machine : YANG
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SQL.log
Last Action : InstallFinalize
Error String : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How

to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated

unexpectedly.
Error Number : 29503
--

SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup

Bootstrap\LOG\Summary.txt.


Time : Mon Jul 10 22:57:30 2006


List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SQLSupport_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SQLNCLI_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SqlWriter_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_MSXML6_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SQL.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SNAC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0022_YANG_SCC.log
c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

|||

CONTENT OF ERROR.LOG

2006-07-10 22:56:35.05 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

2006-07-10 22:56:35.05 Server (c) 2005 Microsoft Corporation.
2006-07-10 22:56:35.05 Server All rights reserved.
2006-07-10 22:56:35.05 Server Server process ID is 504.
2006-07-10 22:56:35.05 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2006-07-10 22:56:35.05 Server Registry startup parameters:
2006-07-10 22:56:35.05 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-07-10 22:56:35.05 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-07-10 22:56:35.05 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-07-10 22:56:35.05 Server Command Line Startup Parameters:
2006-07-10 22:56:35.05 Server -m SqlSetup
2006-07-10 22:56:35.05 Server SqlSetup
2006-07-10 22:56:35.05 Server -Q
2006-07-10 22:56:35.05 Server -q Chinese_PRC_CI_AS
2006-07-10 22:56:35.05 Server -T 4022
2006-07-10 22:56:35.05 Server -T 3659
2006-07-10 22:56:35.05 Server -T 3610
2006-07-10 22:56:35.05 Server -T 4010
2006-07-10 22:56:35.44 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2006-07-10 22:56:35.44 Server Detected 1 CPUs. This is an informational message; no user action is required.
2006-07-10 22:56:35.47 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2006-07-10 22:56:35.55 Server Database Mirroring Transport is disabled in the endpoint configuration.
2006-07-10 22:56:35.56 spid5s Warning ******************
2006-07-10 22:56:35.56 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required.
2006-07-10 22:56:35.56 spid5s Starting up database 'master'.
2006-07-10 22:56:35.79 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2006-07-10 22:56:36.44 spid5s SQL Trace ID 1 was started by login "sa".
2006-07-10 22:56:36.50 spid5s Starting up database 'mssqlsystemresource'.
2006-07-10 22:56:37.25 Server Error: 26011, Severity: 16, State: 1.
2006-07-10 22:56:37.25 Server The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security.dll exists on the system.
2006-07-10 22:56:37.25 Server Error: 17182, Severity: 16, State: 1.
2006-07-10 22:56:37.25 Server TDSSNIClient initialization failed with error 0x139f, status code 0x80.
2006-07-10 22:56:37.25 Server Error: 17182, Severity: 16, State: 1.
2006-07-10 22:56:37.25 Server TDSSNIClient initialization failed with error 0x139f, status code 0x1.
2006-07-10 22:56:37.25 Server Error: 17826, Severity: 18, State: 3.
2006-07-10 22:56:37.25 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2006-07-10 22:56:37.25 Server Error: 17120, Severity: 16, State: 1.
2006-07-10 22:56:37.25 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

|||OMG, guess what... It's installed SUCCESSFULLY again just now while I tried to figure out in which part it had failed. I sware I haven't done anything specially tonight. Well, difference, tonight I'm thinking seriously of re-install my Windows XP rather than looking for solutions as what I was doing in last few nights. Oh...don't juggle with me. I don't know who, Windows XP or SQL server 2005 express edition.|||

There certainly seemed to be some problems with the installation based on your log, but if it's installed and working that's probably well enough. Tought to say if your adware incident was the cause of this, or if the problems you're seeing are related to it.

I'd say leave it be for a week to see what happens before you consider re-install of Windows, but that's your call.

Mike

|||

Hi Mike

Thanks for your eye on my topic.

The service stopped again and refused being stared manually. I checked Configuration Manager, and both SQL Server and SQL Server Browser stopped.

The ERRORLOG has same content as above.

Then I changed login account in both services from Network Service to Local System, now they are running.

Fail to uninstall SQLServer 2005

I can't uninstall a default instance of SQLServer 2005.

i have instaled a MSDE2000 then i uninstall it and when a try to uninstall the default instance of SQLServer2005 a have a error the log following:

--

Instance Name = MSSQLSERVER
Trying to find install through Instance Name
Install Type = 1
If possible, determine action
Failed to determine installSkuId due to property load failure.SKU is set to SKU_EXPRESS.
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:20 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "InstallSku" {"SetupStateScope", "", ""} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupStateScope.InstallSku
Source Line Number: 44
-
No collector registered for scope: "SetupStateScope"
Machine = EMILIO, Article = WMIServiceWin32OSWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceReadRegWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceCIMDataWorking, Result = 0 (0x0)
Machine = EMILIO, Article = XMLDomDocument, Result = 0 (0x0)
Failed to determine installSkuId due to property load failure.SKU is set to SKU_EXPRESS.
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:20 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "InstallSku" {"SetupStateScope", "", ""} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupStateScope.InstallSku
Source Line Number: 44
-
No collector registered for scope: "SetupStateScope"
Machine = EMILIO, Article = Processor, Result = 0 (0x0)
Machine = EMILIO, Article = PhysicalMemory, Result = 0 (0x0)
Machine = EMILIO, Article = DiskFreeSpace, Result = 0 (0x0)
Machine = EMILIO, Article = OSVersion, Result = 0 (0x0)
Machine = EMILIO, Article = OSServicePack, Result = 0 (0x0)
Machine = EMILIO, Article = OSType, Result = 0 (0x0)
Machine = EMILIO, Article = AdminShare, Result = 0 (0x0)
Machine = EMILIO, Article = PendingReboot, Result = 0 (0x0)
Machine = EMILIO, Article = IEVersion, Result = 0 (0x0)
Machine = EMILIO, Article = DriveWriteAccess, Result = 0 (0x0)
Machine = EMILIO, Article = COMPlus, Result = 0 (0x0)
Machine = EMILIO, Article = ASPNETVersionRegistration, Result = 0 (0x0)
Machine = EMILIO, Article = MDAC25Version, Result = 0 (0x0)
Machine = EMILIO, Article = SKUUpgrade, Result = 0 (0x0)

HOW I CAN RESOLVED THE PROBLEM THKS,

Emilio Ferreira

How are you trying to uninstall? Through Add/Remove Programs or through command line? If it is command line, can you share out your cmd line call?

Thanks,
Samuel Lester (MSFT)

|||

i try Through Add/Remove Programs.

Thks,

Emilio Ferreira

(MCAD.NET)

|||

I have the same problem when using Add/Remove programs on a customer computer. Any idea on how to get it to unisntall?

Eric Renken

|||Hi,

Did anyone find a fix for this as we are experiencing the same error here?

"Failed to determine installSkuId due to property load failure."

Any help is much appreciated

Iain

|||

You can try to manually uninstall SQL Server 2005. Detail steps please refer to "How to uninstall an instance of SQL Server 2005 manually http://support.microsoft.com/kb/909967".

Fail to uninstall SQLServer 2005

I can't uninstall a default instance of SQLServer 2005.

i have instaled a MSDE2000 then i uninstall it and when a try to uninstall the default instance of SQLServer2005 a have a error the log following:

--

Instance Name = MSSQLSERVER
Trying to find install through Instance Name
Install Type = 1
If possible, determine action
Failed to determine installSkuId due to property load failure.SKU is set to SKU_EXPRESS.
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:20 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "InstallSku" {"SetupStateScope", "", ""} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupStateScope.InstallSku
Source Line Number: 44
-
No collector registered for scope: "SetupStateScope"
Machine = EMILIO, Article = WMIServiceWin32OSWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceReadRegWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceCIMDataWorking, Result = 0 (0x0)
Machine = EMILIO, Article = XMLDomDocument, Result = 0 (0x0)
Failed to determine installSkuId due to property load failure.SKU is set to SKU_EXPRESS.
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:20 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "InstallSku" {"SetupStateScope", "", ""} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupStateScope.InstallSku
Source Line Number: 44
-
No collector registered for scope: "SetupStateScope"
Machine = EMILIO, Article = Processor, Result = 0 (0x0)
Machine = EMILIO, Article = PhysicalMemory, Result = 0 (0x0)
Machine = EMILIO, Article = DiskFreeSpace, Result = 0 (0x0)
Machine = EMILIO, Article = OSVersion, Result = 0 (0x0)
Machine = EMILIO, Article = OSServicePack, Result = 0 (0x0)
Machine = EMILIO, Article = OSType, Result = 0 (0x0)
Machine = EMILIO, Article = AdminShare, Result = 0 (0x0)
Machine = EMILIO, Article = PendingReboot, Result = 0 (0x0)
Machine = EMILIO, Article = IEVersion, Result = 0 (0x0)
Machine = EMILIO, Article = DriveWriteAccess, Result = 0 (0x0)
Machine = EMILIO, Article = COMPlus, Result = 0 (0x0)
Machine = EMILIO, Article = ASPNETVersionRegistration, Result = 0 (0x0)
Machine = EMILIO, Article = MDAC25Version, Result = 0 (0x0)
Machine = EMILIO, Article = SKUUpgrade, Result = 0 (0x0)

HOW I CAN RESOLVED THE PROBLEM THKS,

Emilio Ferreira

How are you trying to uninstall? Through Add/Remove Programs or through command line? If it is command line, can you share out your cmd line call?

Thanks,
Samuel Lester (MSFT)

|||

i try Through Add/Remove Programs.

Thks,

Emilio Ferreira

(MCAD.NET)

|||

I have the same problem when using Add/Remove programs on a customer computer. Any idea on how to get it to unisntall?

Eric Renken

|||Hi,

Did anyone find a fix for this as we are experiencing the same error here?

"Failed to determine installSkuId due to property load failure."

Any help is much appreciated

Iain

|||

You can try to manually uninstall SQL Server 2005. Detail steps please refer to "How to uninstall an instance of SQL Server 2005 manually http://support.microsoft.com/kb/909967".

Fail to uninstall SQLServer 2005

I can't uninstall a default instance of SQLServer 2005.

i have instaled a MSDE2000 then i uninstall it and when a try to uninstall the default instance of SQLServer2005 a have a error the log following:

--

Instance Name = MSSQLSERVER
Trying to find install through Instance Name
Install Type = 1
If possible, determine action
Failed to determine installSkuId due to property load failure.SKU is set to SKU_EXPRESS.
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:20 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "InstallSku" {"SetupStateScope", "", ""} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupStateScope.InstallSku
Source Line Number: 44
-
No collector registered for scope: "SetupStateScope"
Machine = EMILIO, Article = WMIServiceWin32OSWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceReadRegWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceCIMDataWorking, Result = 0 (0x0)
Machine = EMILIO, Article = XMLDomDocument, Result = 0 (0x0)
Failed to determine installSkuId due to property load failure.SKU is set to SKU_EXPRESS.
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:20 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "InstallSku" {"SetupStateScope", "", ""} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupStateScope.InstallSku
Source Line Number: 44
-
No collector registered for scope: "SetupStateScope"
Machine = EMILIO, Article = Processor, Result = 0 (0x0)
Machine = EMILIO, Article = PhysicalMemory, Result = 0 (0x0)
Machine = EMILIO, Article = DiskFreeSpace, Result = 0 (0x0)
Machine = EMILIO, Article = OSVersion, Result = 0 (0x0)
Machine = EMILIO, Article = OSServicePack, Result = 0 (0x0)
Machine = EMILIO, Article = OSType, Result = 0 (0x0)
Machine = EMILIO, Article = AdminShare, Result = 0 (0x0)
Machine = EMILIO, Article = PendingReboot, Result = 0 (0x0)
Machine = EMILIO, Article = IEVersion, Result = 0 (0x0)
Machine = EMILIO, Article = DriveWriteAccess, Result = 0 (0x0)
Machine = EMILIO, Article = COMPlus, Result = 0 (0x0)
Machine = EMILIO, Article = ASPNETVersionRegistration, Result = 0 (0x0)
Machine = EMILIO, Article = MDAC25Version, Result = 0 (0x0)
Machine = EMILIO, Article = SKUUpgrade, Result = 0 (0x0)

HOW I CAN RESOLVED THE PROBLEM THKS,

Emilio Ferreira

How are you trying to uninstall? Through Add/Remove Programs or through command line? If it is command line, can you share out your cmd line call?

Thanks,
Samuel Lester (MSFT)

|||

i try Through Add/Remove Programs.

Thks,

Emilio Ferreira

(MCAD.NET)

|||

I have the same problem when using Add/Remove programs on a customer computer. Any idea on how to get it to unisntall?

Eric Renken

|||Hi,

Did anyone find a fix for this as we are experiencing the same error here?

"Failed to determine installSkuId due to property load failure."

Any help is much appreciated

Iain

|||

You can try to manually uninstall SQL Server 2005. Detail steps please refer to "How to uninstall an instance of SQL Server 2005 manually http://support.microsoft.com/kb/909967".

Fail to uninstall SQLServer 2005

I can't uninstall a default instance of SQLServer 2005.

i have instaled a MSDE2000 then i uninstall it and when a try to uninstall the default instance of SQLServer2005 a have a error the log following:

--

Instance Name = MSSQLSERVER
Trying to find install through Instance Name
Install Type = 1
If possible, determine action
Failed to determine installSkuId due to property load failure.SKU is set to SKU_EXPRESS.
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:20 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "InstallSku" {"SetupStateScope", "", ""} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupStateScope.InstallSku
Source Line Number: 44
-
No collector registered for scope: "SetupStateScope"
Machine = EMILIO, Article = WMIServiceWin32OSWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceReadRegWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0)
Machine = EMILIO, Article = WMIServiceCIMDataWorking, Result = 0 (0x0)
Machine = EMILIO, Article = XMLDomDocument, Result = 0 (0x0)
Failed to determine installSkuId due to property load failure.SKU is set to SKU_EXPRESS.
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:20 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "InstallSku" {"SetupStateScope", "", ""} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupStateScope.InstallSku
Source Line Number: 44
-
No collector registered for scope: "SetupStateScope"
Machine = EMILIO, Article = Processor, Result = 0 (0x0)
Machine = EMILIO, Article = PhysicalMemory, Result = 0 (0x0)
Machine = EMILIO, Article = DiskFreeSpace, Result = 0 (0x0)
Machine = EMILIO, Article = OSVersion, Result = 0 (0x0)
Machine = EMILIO, Article = OSServicePack, Result = 0 (0x0)
Machine = EMILIO, Article = OSType, Result = 0 (0x0)
Machine = EMILIO, Article = AdminShare, Result = 0 (0x0)
Machine = EMILIO, Article = PendingReboot, Result = 0 (0x0)
Machine = EMILIO, Article = IEVersion, Result = 0 (0x0)
Machine = EMILIO, Article = DriveWriteAccess, Result = 0 (0x0)
Machine = EMILIO, Article = COMPlus, Result = 0 (0x0)
Machine = EMILIO, Article = ASPNETVersionRegistration, Result = 0 (0x0)
Machine = EMILIO, Article = MDAC25Version, Result = 0 (0x0)
Machine = EMILIO, Article = SKUUpgrade, Result = 0 (0x0)

HOW I CAN RESOLVED THE PROBLEM THKS,

Emilio Ferreira

How are you trying to uninstall? Through Add/Remove Programs or through command line? If it is command line, can you share out your cmd line call?

Thanks,
Samuel Lester (MSFT)

|||

i try Through Add/Remove Programs.

Thks,

Emilio Ferreira

(MCAD.NET)

|||

I have the same problem when using Add/Remove programs on a customer computer. Any idea on how to get it to unisntall?

Eric Renken

|||Hi,

Did anyone find a fix for this as we are experiencing the same error here?

"Failed to determine installSkuId due to property load failure."

Any help is much appreciated

Iain

|||

You can try to manually uninstall SQL Server 2005. Detail steps please refer to "How to uninstall an instance of SQL Server 2005 manually http://support.microsoft.com/kb/909967".

Friday, March 9, 2012

Fail to remotely connect to SQL 2005 named instance

I have 2 instances on a remote machine:
- SQL Server 2000 - default instance
- SQL Server 2005 Standard - named instance called: SQL2005.
I am able to connect to SQL2005 from within the remote machine itself
(loopback). I am also able to connect to the SQL 2000 engine remotely
(remember - it is in default instance).
I am NOT able to connect to SQL2005 engine remotely. I enter server name:
remote\SQL2005, user name: sa, password: xxx, but I get "SQL Server does not
exist or access denied". Trying from various clients: Management Studio, UDL
file, connection string, etc.
I marked "Local and remote connections" in Surface Area Configuration;
TCP/IP is enabled and I have no problem of port definitions (all standard -
1433).
I have no firewall or other limitation accessing that remote machine at all.
I checked all Microsoft docs about SQL connectivity issues - that didn't
help.
I'd appreciate any help...
OferStart the SQL Browser service or connect to the named instance via the IP
address and port number.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Ofer Zelig" <ofer@.newsgroups.nospam> wrote in message
news:%23GhXSTBVGHA.5852@.TK2MSFTNGP10.phx.gbl...
>I have 2 instances on a remote machine:
> - SQL Server 2000 - default instance
> - SQL Server 2005 Standard - named instance called: SQL2005.
> I am able to connect to SQL2005 from within the remote machine itself
> (loopback). I am also able to connect to the SQL 2000 engine remotely
> (remember - it is in default instance).
> I am NOT able to connect to SQL2005 engine remotely. I enter server name:
> remote\SQL2005, user name: sa, password: xxx, but I get "SQL Server does
> not
> exist or access denied". Trying from various clients: Management Studio,
> UDL
> file, connection string, etc.
> I marked "Local and remote connections" in Surface Area Configuration;
> TCP/IP is enabled and I have no problem of port definitions (all
> standard -
> 1433).
> I have no firewall or other limitation accessing that remote machine at
> all.
> I checked all Microsoft docs about SQL connectivity issues - that didn't
> help.
> I'd appreciate any help...
> Ofer
>|||SQL Browser doesn't work.
About the IP number - which IP should I use? As far as I know, it is the
same 1433 port as in SQL 2000.
What should be the full server name if the machine is called "remote" and
the SQL 2005 instance is called "SQL2005" ? Isn't it: remote\SQL2005 ?
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23cP4edCVGHA.5828@.TK2MSFTNGP10.phx.gbl...
> Start the SQL Browser service or connect to the named instance via the IP
> address and port number.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Ofer Zelig" <ofer@.newsgroups.nospam> wrote in message
> news:%23GhXSTBVGHA.5852@.TK2MSFTNGP10.phx.gbl...
name:[vbcol=seagreen]
>|||Hello Ofer,
May I suggest that we focus on the theard in setup newsgroup? This might be
easier for community to track this issue. Thanks.
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "Ofer Zelig" <ofer@.newsgroups.nospam>
>References: <#GhXSTBVGHA.5852@.TK2MSFTNGP10.phx.gbl>
<#cP4edCVGHA.5828@.TK2MSFTNGP10.phx.gbl>
>Subject: Re: Fail to remotely connect to SQL 2005 named instance
>Date: Sun, 2 Apr 2006 15:13:30 +0200
>Lines: 53
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
>Message-ID: <OLnTq8kVGHA.6084@.TK2MSFTNGP14.phx.gbl>
>Newsgroups:
microsoft.public.sqlserver.setup,microsoft.public.sqlserver.connect
>NNTP-Posting-Host: line134-75.adsl.actcom.co.il 192.115.134.75
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:47287
microsoft.public.sqlserver.setup:76030
>X-Tomcat-NG: microsoft.public.sqlserver.connect
>SQL Browser doesn't work.
>About the IP number - which IP should I use? As far as I know, it is the
>same 1433 port as in SQL 2000.
>What should be the full server name if the machine is called "remote" and
>the SQL 2005 instance is called "SQL2005" ? Isn't it: remote\SQL2005 ?
>
>"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
>news:%23cP4edCVGHA.5828@.TK2MSFTNGP10.phx.gbl...
>name:
does[vbcol=seagreen]
Studio,[vbcol=seagreen]
didn't[vbcol=seagreen]
>
>

Fail to remotely connect to SQL 2005 named instance

I have 2 instances on a remote machine:
- SQL Server 2000 - default instance
- SQL Server 2005 Standard - named instance called: SQL2005.
I am able to connect to SQL2005 from within the remote machine itself
(loopback). I am also able to connect to the SQL 2000 engine remotely
(remember - it is in default instance).
I am NOT able to connect to SQL2005 engine remotely. I enter server name:
remote\SQL2005, user name: sa, password: xxx, but I get "SQL Server does not
exist or access denied". Trying from various clients: Management Studio, UDL
file, connection string, etc.
I marked "Local and remote connections" in Surface Area Configuration;
TCP/IP is enabled and I have no problem of port definitions (all standard -
1433).
I have no firewall or other limitation accessing that remote machine at all.
I checked all Microsoft docs about SQL connectivity issues - that didn't
help.
I'd appreciate any help...
Ofer
Start the SQL Browser service or connect to the named instance via the IP
address and port number.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Ofer Zelig" <ofer@.newsgroups.nospam> wrote in message
news:%23GhXSTBVGHA.5852@.TK2MSFTNGP10.phx.gbl...
>I have 2 instances on a remote machine:
> - SQL Server 2000 - default instance
> - SQL Server 2005 Standard - named instance called: SQL2005.
> I am able to connect to SQL2005 from within the remote machine itself
> (loopback). I am also able to connect to the SQL 2000 engine remotely
> (remember - it is in default instance).
> I am NOT able to connect to SQL2005 engine remotely. I enter server name:
> remote\SQL2005, user name: sa, password: xxx, but I get "SQL Server does
> not
> exist or access denied". Trying from various clients: Management Studio,
> UDL
> file, connection string, etc.
> I marked "Local and remote connections" in Surface Area Configuration;
> TCP/IP is enabled and I have no problem of port definitions (all
> standard -
> 1433).
> I have no firewall or other limitation accessing that remote machine at
> all.
> I checked all Microsoft docs about SQL connectivity issues - that didn't
> help.
> I'd appreciate any help...
> Ofer
>
|||SQL Browser doesn't work.
About the IP number - which IP should I use? As far as I know, it is the
same 1433 port as in SQL 2000.
What should be the full server name if the machine is called "remote" and
the SQL 2005 instance is called "SQL2005" ? Isn't it: remote\SQL2005 ?
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23cP4edCVGHA.5828@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Start the SQL Browser service or connect to the named instance via the IP
> address and port number.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Ofer Zelig" <ofer@.newsgroups.nospam> wrote in message
> news:%23GhXSTBVGHA.5852@.TK2MSFTNGP10.phx.gbl...
name:
>
|||Hello Ofer,
May I suggest that we focus on the theard in setup newsgroup? This might be
easier for community to track this issue. Thanks.
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "Ofer Zelig" <ofer@.newsgroups.nospam>
>References: <#GhXSTBVGHA.5852@.TK2MSFTNGP10.phx.gbl>
<#cP4edCVGHA.5828@.TK2MSFTNGP10.phx.gbl>
>Subject: Re: Fail to remotely connect to SQL 2005 named instance
>Date: Sun, 2 Apr 2006 15:13:30 +0200
>Lines: 53
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
>Message-ID: <OLnTq8kVGHA.6084@.TK2MSFTNGP14.phx.gbl>
>Newsgroups:
microsoft.public.sqlserver.setup,microsoft.public. sqlserver.connect
>NNTP-Posting-Host: line134-75.adsl.actcom.co.il 192.115.134.75
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP14.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:47287
microsoft.public.sqlserver.setup:76030[vbcol=seagreen]
>X-Tomcat-NG: microsoft.public.sqlserver.connect
>SQL Browser doesn't work.
>About the IP number - which IP should I use? As far as I know, it is the
>same 1433 port as in SQL 2000.
>What should be the full server name if the machine is called "remote" and
>the SQL 2005 instance is called "SQL2005" ? Isn't it: remote\SQL2005 ?
>
>"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
>news:%23cP4edCVGHA.5828@.TK2MSFTNGP10.phx.gbl...
>name:
does[vbcol=seagreen]
Studio,[vbcol=seagreen]
didn't
>
>