Groups | Blog | Home
all groups > sql server clustering > january 2004 >

sql server clustering : Setup Failed


Fred Jean
1/26/2004 11:15:38 AM
Hi,

I'm trying to install a second instance of SQL Server on a
clustered node, from Node B. I had to cancel the first
execution of setup installation program for different
reasons. After that, we haven't been able to delete /Binn
directory of that instance on Node B (sharing access
violation messages). It seems to be causing the following
errors on Node B (source installation). On Node A,
installation is successful.

Here is part of the log :
15:25:46 End Action: Locked Connectivity Files Check
15:25:46 Setup is installing Microsoft Data Access
Components (MDAC) ...
15:25:46 G:\x86\Other\sqlredis.exe /q:a
15:26:09 ExitCode: 0
15:26:09 InstallMSSearch instance: MSPRODTMA
15:26:09 Software\Microsoft\Search\Install:Version :
9.107.5512
15:26:09 MSSearch 2.0 or greater version check returned 1
15:26:09 Setup is installing the Microsoft Full-Text
Search Engine ...
15:26:09 "G:\x86
\FullText\MSSearch\Search\SearchStp.exe" /s /a:SQLServer$MS
PRODTMA
15:26:09 Process Exit Code: (0)
15:26:09 /Q:A /T:C:\WINNT\TEMP\ixp001.tmp
15:26:09 Setup is installing HTML Help ...
15:26:09 HTML Help installer exit code: 0
15:26:30 End Action InstallPkgs
15:26:30 Begin Action MoveFileData:
15:26:30 Enabled SELFREGISTERBATCH
15:26:30 Enabled CORECOMPONENTHANDLING
15:26:30 ComponentMoveData exit code: -115
15:26:30 ComponentMoveData: -115
15:26:30 The specified file cannot be opened as write.
Ensure the file is not in use and restart setup.

File: C:\Program Files\Microsoft SQL
Server\MSSQL$MSPRODTMA\Binn\vswitch.exe

15:26:31 Begin Action: MoveFileDataSpecial
15:26:31 An error occurred copying the file xpadsi.exe.
Setup will continue. You can copy this file manually from
the CD.
15:26:31 An error occurred copying the file sqlctr.ini.
Setup will continue. You can copy this file manually from
the CD.
15:26:31 An error occurred copying the file ssmsgnet.dll.
Setup will continue. You can copy this file manually from
the CD.
15:26:31 End Action: MoveFileDataSpecial
15:26:31 Action CleanUpInstall:
15:26:31 StatsGenerate returned: 2
15:26:31 StatsGenerate
(0x0,0x1,0xf00000,0x400,1033,303,0x0,0x1000000a,0,0,0
15:26:31 StatsGenerate -1,administrator)
15:26:31 Installation Failed.

Can you help or suggest me something ?

Thanks,

Fred.
cgross NO[at]SPAM online.microsoft.com
1/28/2004 6:41:55 PM
* Are the files marked as readonly?
* Does something have them locked (maybe backup software or a virus
scanner)?
* Does a reboot of the node help?
* Can you try installing to a different directory? That doesn't help you
clean up the files from the second install, but it may get you past the
error.
* Does a manual delete of the files or directory give a more descriptive
error?

You may also want to try doing a thorough cleanup of the failed install:
290991 HOW TO: Manually Remove SQL Server 2000 Default, Named, or Virtual
http://support.microsoft.com/?id=290991

Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
FRED JEAN
1/29/2004 8:01:40 AM
Hi Cindy,

thank you for answer.
In fact, we did reboot both nodes and restarted the
cluster. From there, I was able to delete the directory
and proceed with successful installation. In conclusion, I
think what was causing these errors was that some files
and directories were marked as opened by the cluster or
nodeB after we cancelled the first installation.

Thanks,

Fred.

[quoted text, click to view]
AddThis Social Bookmark Button