Microsoft SQL Server 2005 install problem.........

when i install the SQL server 2005, it occured the follow message:

Product: Microsoft SQL Server 2005 CTP -- Error 29628. The setup has
encountered an unexpected error in datastore. The action is
PrepareUpgradeDialog. The error is :Failed to find property "langId"
{"SetupStateScope", "", ""} in cache
No collector registered for scope: "SetupStateScope"

--
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/General-Dis...pict248148.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=859943pinos (UseLinkToEmail@.dbForumz.com) writes:
> when i install the SQL server 2005, it occured the follow message:
> Product: Microsoft SQL Server 2005 CTP -- Error 29628. The setup has
> encountered an unexpected error in datastore. The action is
> PrepareUpgradeDialog. The error is :Failed to find property "langId"
> {"SetupStateScope", "", ""} in cache
> No collector registered for scope: "SetupStateScope"

Please post SQL 2005 questions in the SQL 2005 newsgroups, as these are
monitored by Microsoft staff. Access info here:
http://go.microsoft.com/fwlink/?linkid=31765.

Please also make sure that you have the latest build:
http://www.microsoft.com/sql/2005/productinfo/ctp.mspx.

For setup issues, it might even be better to file bugs at
http://lab.msdn.microsoft.com/ProductFeedback/, since the MS presence
in the setup groups have been spotty lately. However, you need to include
much more information. You get a hold bunch of logs with the SQL setup,
although I don't remember exactly where they are located. At a minimum,
you should include in which phase of the installtion this happens.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Microsoft SQL Server 2005 CTP Setup - Could not open a connection to SQL Server [2]

Hi,
Here is the error that I get during install. Does anyone have an idea how to solve this?
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

TITLE: Microsoft SQL Server 2005 CTP Setup
-

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2]. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&ProdVer=9.00.1116&EvtSrc=setup.rll&EvtID=29545&EvtType=lib%5Codbc_connection.cpp@.Do_sqlScript@.OdbcConnection::connect@.x80070002

-
BUTTONS:

&Retry
Cancel
-

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
In the log file I can see the folowing information at the bottom:

Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Thu Jun 16 08:15:46 2005
Service MSSQLSERVER with parameters '-m -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Thu Jun 16 08:15:46 2005
SQL service MSSQLSERVER started successfully waiting for SQL service to accept client connections
Service MSSQLSERVER started at Thu Jun 16 08:16:10 2005
Loaded DLL:
C:\WINDOWS\system32\Odbc32.dll
Version:
3.525.1117.0

SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=08001, level=-1, state=-1, native_error=2, msg=[Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2].
sqlstate=08001, level=-1, state=-1, native_error=2, msg=[Microsoft][SQL Native Client]Client unable to establish connection
sqlstate=HYT00, level=-1, state=-1, native_error=0, msg=[Microsoft][SQL Native Client]Login timeout expired
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.
Source File Name: lib\odbc_connection.cpp
Compiler Timestamp: Fri Mar 18 08:21:13 2005
Function Name: OdbcConnection::connect
Source Line Number: 140

- Context --

Connecting to SQL Server
ExecuteSqlCommands
Originial error was 80070002 (2)
lScript
SqlScriptHlpr

Error Code: 2
MSI (s) (DC!54) [08:16:43:920]: Product: Microsoft SQL Server 2005 CTP -- Error 29545. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2]. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
Error 29545. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2]. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Thu Jun 16 08:16:43 2005
Service MSSQLSERVER with parameters '-m -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Thu Jun 16 08:16:43 2005
Attempt to start service when it is already running
SQL service MSSQLSERVER started successfully waiting for SQL service to accept client connections
Service MSSQLSERVER started at Thu Jun 16 08:16:43 2005
Loaded DLL:
C:\WINDOWS\system32\Odbc32.dll
Version:
3.525.1117.0

SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=08001, level=-1, state=-1, native_error=2, msg=[Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2].
sqlstate=08001, level=-1, state=-1, native_error=2, msg=[Microsoft][SQL Native Client]Client unable to establish connection
sqlstate=HYT00, level=-1, state=-1, native_error=0, msg=[Microsoft][SQL Native Client]Login timeout expired
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.
Source File Name: lib\odbc_connection.cpp
Compiler Timestamp: Fri Mar 18 08:21:13 2005
Function Name: OdbcConnection::connect
Source Line Number: 140

- Context --

Connecting to SQL Server
ExecuteSqlCommands
Originial error was 80070002 (2)
Do_sqlScript
SqlScriptHlpr

Error Code: 2

Probably better to ask this in the Setup/Upgrade group...

However, do you have SQL 2000 installed? If so are named pipes enabled in cli config? If not enable them and re-run setup.

-Euan|||Hey Edwin.

I just had this very same problem.

The way that I got around it was to run the SQL server install, and when it came up with this error I went into my services MMC snapin and restarted the SQL Server (MSSQLSERVER) service.

Then I pressed retry in the install window and it worked.

See if that helps

Cheers
Beric Holt
e-Media Ltd
Dunedin
New Zealand|||Hi Beric

work around suggested by you worked for me as well.thanks.|||

I had the similar issues, and this has been resolved by running command Setup\sqlncli.msi REINSTALL=ALL REINSTALLMODE=omus /qb.
More informations is available on link :http://download.microsoft.com/download/E/1/1/E1196B19-DE92-4AB2-BAFD-5B5AD26E67B4/AprilCTPNotes.mht
Thanks!

Microsoft Releases Synchronization Services CTP

The Microsoft Synchronization Services for ADO.NET v1.0 CTP release appeared without fanfare on January 22, 2006. The release contains "v1.0 early CTP" bits for the sync framework and SQL Server 2005 Compact Edition (SSCE) v3.5, the Orcas successor to the SSCE v3.1 RTM bits, which Microsoft released on January 11, 2006. The current code name for Sync Services is OCS (for Occasionally Connected Systems).

Seems to me to resemble a "stealth release."

For more, see http://oakleafblog.blogspot.com/2007/01/microsoft-releases-synchronization.html.

Oops. Make that January 11, 2007!

--rj

Metadata Issues

I am experiencing something really bazaar. The package I created usign SQL2K5 Sept. CTP Builds and functions just fine in one domain. When I deployed to another machine & new domain, we get Metadata errors within dataflow that was modified. We had encountered this earlier but by rebuilding the package it has solved the problem. This time, rebuild is not helping. How can metadata for data flow of a package get corrupted from one environment to another. Also, what's the purpose of building a package when the package is in XML (Text). I don't see any binary code for script tasks.

What exactly is the message? My favourite at present when moving between environments is the encyrption error for passwords (or any sensitive propertry), since the default protection uses the user key, so obviously changing domains changes accounts and therefore the decyption fails. Setting don't save sensitive information and use configurations to apply passwords again helps somewhat.|||Thanks for your reply Darren. I have already cross the hurdle of Package Protection level issue. Current settings are "Don't save sensitive" info. I am curious to see if they modify this default setting in RTM rel.
|||Using the RTM release now available to MSDN subscribers, the default is User Key still.|||Great!!. By the way, what does a Build functionality do for a package when script tasks within either control flow or data flow are set not to compile on save. If I don't build the package, it still works so why build it?
|||

Scripts can be compiled or not. If compiled then they run faster since there is no compilation overhead each time the package is run. I wasn't aware that this was linked to the package build, I assumed it happened within the script editor itself and VSA. Only downside of pre-compiled scripts is they are processor specific, so x86 to x64 deployments for example will fail.

|||You'd be better of ignoring me and just reading Books Online. The package Save induces the compilation.

From ScriptTask.PreCompile

Property Value

true if the VSA script is compiled when the package is saved; otherwise, false. The default value is true.

Remarks

VSA scripts must be compiled before the package runs. The Script task includes the option to pre-compile script into binary code when the package is saved. When script is precompiled, the language engine is not loaded at run time and the package runs more quickly; however, compiled binary files consume significant disk space. Script that is not precompiled is compiled at run time, which slows package execution but consumes less disk space. When storing large packages is not a problem, you should pre-compile your VSA scripts.

|||

DarrenSQLIS wrote:

Only downside of pre-compiled scripts is they are processor specific, so x86 to x64 deployments for example will fail.

Not really. The script is precompiled to MSIL (.NET intemediary language) which is platform-independent. It will be JIT-ed to process-specific code at runtime.