> Sweet! Learn something new everyday, now I need to check our SQL to see
> what hidden version we have :) I Googled and could not find the
> information about the versions on a Microsoft site.
>
> Cheers,
>
> Rod
>
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://www.msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> http://msmvps.com/clustering/archive/2005/07/20/58233.aspx NYC Clustering
> class
>
>
> "Geoff N. Hiten" <SQLCraftsman@gmail.com> wrote in message
> news:eqhts9orFHA.2876@TK2MSFTNGP12.phx.gbl...
>> Umm, Rodney, there IS a SQL 2000a version, although it is not widely
>> publicized.
>>
>> SQL 2000a is the original disk of SQL 2000 with one DLL replaced to
>> protect against the Slammer worm. Windows 2003 doesn't like installing
>> the original version and prefers SQL 2000a. The easy way to tell is that
>> one or more of the folders in the root of the CD are now show a date in
>> 2003 instead of in 2000.
>>
>> Any version downloaded via MSDN or any of the licensing fulfilment
>> programs will be SQL 2000a. If you have an older version, contact
>> whomever you purchased the license from to obtain a new media kit.
>>
>> You are correct about the SQL_Latin1_General. That refers to the server
>> collation and is the US English default collation.
>>
>> There will be a detailed log in the root of youw Windows folder on each
>> cluster node. You will need both log files to determine why the install
>> didn't work. Post them back here and someone will offer a helpful
>> suggestion or two.
>>
>> Geoff N. Hiten
>> Senior Database Adminsitrator
>> Microsoft SQL Server MVP
>>
>> "Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote in
>> message news:eyBv8torFHA.1204@TK2MSFTNGP15.phx.gbl...
>>> You have both users the cluster and sql services accounts in the local
>>> admins group?
>>>
>>> There is no 2000a version. Though you will need sp3a or sp4 after the
>>> install actually works.
>>>
>>> SQL_Latin1_General is normal and nothing to worry about.
>>>
>>> Have you tried installing from the other node?
>>>
>>> In the SQL logs do you have any other error messages? Anything pop up on
>>> the screen? Are you trying to install an instance or the default?
>>>
>>> Have you looked at
>>> http://support.microsoft.com/default.aspx?scid=kb;en-us;815431?
>>>
>>> Cheers,
>>>
>>> Rod
>>>
>>> MVP - Windows Server - Clustering
>>> http://www.nw-america.com - Clustering Website
>>> http://msmvps.com/clustering - Blog
>>> http://www.clusterhelp.com - Cluster Training
>>> http://msmvps.com/clustering/archive/2005/07/20/58233.aspx NYC
>>> Clustering class
>>>
>>> "Chris" <cdsuperg@hotmail.com> wrote in message
>>> news:%23EX%23RUmrFHA.1788@tk2msftngp13.phx.gbl...
>>>> Hello all,
>>>>
>>>> I have been trying to install a single node cluster on Win2003 for
>>>> about a
>>>> week with pretty much the same results as I have seen all over the web.
>>>> "Setup failed to perform required operations on the clustered nodes"
>>>> I have a CD in front of me labeled "Part No. 810-01148" and the
>>>> readme.txt
>>>> from 2000.
>>>> I have checked the computer name for all lower case and simple
>>>> characters
>>>> I have no terminal services or remote desktop
>>>> my administrator account seems good and I have it's temp and tmp going
>>>> to
>>>> c:\temp
>>>> I have copied all the CD files to a local drive
>>>> default instance
>>>> per seat licensing
>>>> default locations
>>>> the windows cluster seems to work fine
>>>>
>>>> a few questions,
>>>> Is there a SQL 2000a version of EE and if so how do I know if I have it
>>>> and
>>>> if not how do I get it?
>>>> Why do the logs say SQL_Latin1_General when the CD is English?
>>>> and finally, is there any hope that I can install this?
>>>>
>>>> Any ideas, I am at the end of my rope.
>>>>
>>>> Chris
>>>>
>>>> here are my logs
>>>>
>>>> CThreadPool::RunUntilCompleteHlpr create thread, index=0
>>>> CThread::Run thread [0x40] created for execution.
>>>> CThreadPool::RunUntilCompleteHlpr start thread [0x40],index=0
>>>> CThread::Process [0x40]
>>>> Running '\\EMPDB35\D$\sql-inst\x86\setup\setupsql.exe k=Nb k=Rm
>>>> k=Cl -SMS -s -f "\\EMPDB35\D$\sql-inst\x86\setup\setup.ins" -f1
>>>> \\EMPDB35\admin$\EMPDB35_MSSQLSERVER.iss -f2
>>>> "\\EMPDB35\admin$\setup.log" -e
>>>> "stpsilnt._ex" -b -x "c:\temp\"' (EMPDB35) ...
>>>> CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
>>>> CThreadPool::RunUntilCompleteHlpr the operation timed out.
>>>> CThreadPool::RunUntilComplete returned 1460
>>>> CThreadPool::RunUntilComplete execution level=1, need execution: 0
>>>> One or more errors occurred while running the remote/unattended setups.
>>>> Disconnecting from remote machine (EMPDB35)...
>>>> Service removed successfully.
>>>> Remote files could not be removed.
>>>> #### SQL Server Remote Setup - Stop Time 08/30/05 13:50:14 ####
>>>> 13:50:14 End Action : Run setup on cluster nodes
>>>> 13:50:14 One or more errors occurred while running remote setup on the
>>>> clustered machines.
>>>> 13:51:00 Setup failed to perform required operations on the cluster
>>>> nodes.
>>>> 13:51:00 Begin Action : ClusterErrorCleanup
>>>> 13:51:00 End Action : ClusterErrorCleanup
>>>> 13:51:00 End Action : ClusterSetupHelper
>>>>
>>>> and
>>>>
>>>> 13:21:01 C:\Program Files\Microsoft SQL
>>>> er\80\Tools\Binn\cnfgsvr.exe -F
>>>> "C:\WINDOWS\sqlstp3.log" -I MSSQLSERVER -V 1 -M 0 -Q
>>>> "SQL_Latin1_General_CP1_CI_AS" -H 459326 -U sa -P
>>>> ###############################################################################
>>>> Starting Service ...
>>>> SQL_Latin1_General_CP1_CI_AS
>>>> -m -Q -T4022 -T3659
>>>> 13:51:33 Process Exit Code: (1)
>>>> 13:51:33 Setup failed to configure the server. Refer to the server
>>>> error
>>>> logs and C:\WINDOWS\sqlstp3.log for more information.
>>>> 13:51:33 Action CleanUpInstall:
>>>> 13:51:33 c:\temp\SqlSetup\Bin\scm.exe -Silent 1 -Action 4 -Service
>>>> SQLSERVERAGENT
>>>> 13:51:33 Process Exit Code: (2) The system cannot find the file
>>>> specified.
>>>> 13:51:33 c:\temp\SqlSetup\Bin\scm.exe -Silent 1 -Action 4 -Service
>>>> MSSQLSERVER