FYI - for anyone that has a problem installing SP3a for
SQL2k in a clustered W2K3 environment.
The fix for this problem was an invalid path setting for
the temp directory. It seems that W2K3 does not allow for
8.3 filename support "out of the box". This includes
spaces in the path of you temp directory. Is seems that
the SP3a upgrade for SQL2K requires 8.3 file name support.
there are two ways to resolve this problem:
1) remove the space from path of your temp file or
2) modify a registry key in the following manner:
Start Registry Editor.
Locate, and then click the value under the following key
in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\FileSys
tem\NtfsDisable8dot3NameCreation
On the Edit menu, click Modify, type 0, and then click OK.
Quit Registry Editor.
Restart the computer for this registry setting to take
effect.
This is explained in Q328290.
[quoted text, click to view] >-----Original Message-----
>I am trying to upgrade an SQL2K instance to SP3a on a
>Windows W2K3 cluster .... without success.
>
>I am able to sucessfully navigate through the various
>setup screens (using the setup.bat installation), that
>select my virtual SQL instance, sa username and password.
>However after I select OK to proceed with the upgrade an
>error occurs indicating that setup cannot determine the
>state of the SQL server, that I should check that the SQL
>server has started and my sa password is correct.
>
>I have checked the readme file for SP3a and followed
>article 811168 with no success. I could not find any
>dependencies that I could remove. Is there anything else
I
>should be doing to enable this upgrade?? Thanks in
>advance!!
>.
I have run into a similar problem. The easy way around this is to make sure
and log in at least once to each cluster server with the account you are
running the installation under. Specifically, the account you log in to
the host node with to launch the Service Pack Installer. When you log in,
Windows will create the user directory structure, including the temporary
folders.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
[quoted text, click to view] "Owen Thomas" <anonymous@discussions.microsoft.com> wrote in message
news:008601c39fe4$bf1d3c70$a601280a@phx.gbl...
> FYI - for anyone that has a problem installing SP3a for
> SQL2k in a clustered W2K3 environment.
>
> The fix for this problem was an invalid path setting for
> the temp directory. It seems that W2K3 does not allow for
> 8.3 filename support "out of the box". This includes
> spaces in the path of you temp directory. Is seems that
> the SP3a upgrade for SQL2K requires 8.3 file name support.
> there are two ways to resolve this problem:
> 1) remove the space from path of your temp file or
> 2) modify a registry key in the following manner:
>
> Start Registry Editor.
> Locate, and then click the value under the following key
> in the registry:
> HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\FileSys
> tem\NtfsDisable8dot3NameCreation
>
> On the Edit menu, click Modify, type 0, and then click OK.
> Quit Registry Editor.
> Restart the computer for this registry setting to take
> effect.
>
> This is explained in Q328290.
>
> >-----Original Message-----
> >I am trying to upgrade an SQL2K instance to SP3a on a
> >Windows W2K3 cluster .... without success.
> >
> >I am able to sucessfully navigate through the various
> >setup screens (using the setup.bat installation), that
> >select my virtual SQL instance, sa username and password.
> >However after I select OK to proceed with the upgrade an
> >error occurs indicating that setup cannot determine the
> >state of the SQL server, that I should check that the SQL
> >server has started and my sa password is correct.
> >
> >I have checked the readme file for SP3a and followed
> >article 811168 with no success. I could not find any
> >dependencies that I could remove. Is there anything else
> I
> >should be doing to enable this upgrade?? Thanks in
> >advance!!
> >.
> >
