Error when installing SQL server 200 on SBS 2003 in Windows Small Business Server 2003

Hi,
I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the SBS
2003 server Premium).
I installed the OS lately and made all the Microsoft update.
I am now trying to install the SQL 2000 server and get this error message:
(It is the english translation of what I get on my screen)
Error message: "A previous installation program created operation files
waiting for Installtion on your computer. You have to reboot it before
executing the installation."
Of course I rebooted my server, but nothing happened.
Any idea of what to do ?
Thank you for your helpDid you try installing again after the reboot? Was there an error code
listed?
From KB Article 257716:
Q. What should I do if the installation of SQL Server 2000 is unsuccessful?
A. If you have an unsuccessful installation, you can examine two files to
help determine what went wrong. The Sqlstp.log file, which is located in the
Windows directory, gives detailed information on what setup is doing and
contains all errors encountered during setup. Reviewing this file will give
you a better understanding of where setup fails and why.
During the configuration portion of setup, SQL Server setup runs an
application called Cnfgsvr.exe to configure the SQL Server. This application
starts SQL Server, connects to it, and then runs the initial installation
scripts. Any error encountered during this process is also written to the
Sqlstp.log file; however, you should also review the SQL Server error log,
named "Errorlog" with no file extension, located by default in the Program
Files\Microsoft SQL Server\Mssql\Log directory. This error log contains
errors that SQL Server encounters when setup attempts to start SQL Server,
which may provide further insight into the failure.
If you cannot determine the cause of the Setup failure, save the two files
just mentioned and call Microsoft Product Support Services (PSS) to speak to
a SQL Server Support Professional who will help you to resolve your problem.
Note that when the Setup application fails, it rolls back all changes to the
file system, which includes removing any copied files and changes that were
made to the registry.
HTH
Jerry
"Alambiki" <alambiki@.yahoo.com> wrote in message
news:dj5qnl$ok9$1@.reader1.imaginet.fr...
> Hi,
> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
> SBS
> 2003 server Premium).
> I installed the OS lately and made all the Microsoft update.
> I am now trying to install the SQL 2000 server and get this error message:
> (It is the english translation of what I get on my screen)
> Error message: "A previous installation program created operation files
> waiting for Installtion on your computer. You have to reboot it before
> executing the installation."
> Of course I rebooted my server, but nothing happened.
> Any idea of what to do ?
> Thank you for your help
>|||Yes I tried to reinstall after reboot.
I found the Sqlstp.log file, but am not able to understand it.
If someone has an idea...
"Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
> Did you try installing again after the reboot? Was there an error code
> listed?
> From KB Article 257716:
> Q. What should I do if the installation of SQL Server 2000 is
> unsuccessful?
> A. If you have an unsuccessful installation, you can examine two files to
> help determine what went wrong. The Sqlstp.log file, which is located in
> the Windows directory, gives detailed information on what setup is doing
> and contains all errors encountered during setup. Reviewing this file will
> give you a better understanding of where setup fails and why.
> During the configuration portion of setup, SQL Server setup runs an
> application called Cnfgsvr.exe to configure the SQL Server. This
> application starts SQL Server, connects to it, and then runs the initial
> installation scripts. Any error encountered during this process is also
> written to the Sqlstp.log file; however, you should also review the SQL
> Server error log, named "Errorlog" with no file extension, located by
> default in the Program Files\Microsoft SQL Server\Mssql\Log directory.
> This error log contains errors that SQL Server encounters when setup
> attempts to start SQL Server, which may provide further insight into the
> failure.
> If you cannot determine the cause of the Setup failure, save the two files
> just mentioned and call Microsoft Product Support Services (PSS) to speak
> to a SQL Server Support Professional who will help you to resolve your
> problem. Note that when the Setup application fails, it rolls back all
> changes to the file system, which includes removing any copied files and
> changes that were made to the registry.
>
> HTH
> Jerry
> "Alambiki" <alambiki@.yahoo.com> wrote in message
> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>|||What were the last few successful entries? Do you have an installation that
WAS successful that you can compare it to?
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356ae9a$0$4336$626a54ce@.news.free.fr...
> Yes I tried to reinstall after reboot.
> I found the Sqlstp.log file, but am not able to understand it.
> If someone has an idea...
> "Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
> enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
>|||I already installed SBS + SQL on this server. It is the second time I
install it on this server. The only thing that changes is that I updated
with the latest ms update + installed symantec lifestate...
here is the log of SQLstp.log
19:00:30 Begin Setup
19:00:30 8.00.194
19:00:30 Mode = Normal
19:00:30 ModeType = NORMAL
19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
19:00:30 ValueFTS returned: 1
19:00:30 ValuePID returned: 1
19:00:30 ValueLic returned: 1
19:00:30 System: Small Business Server
19:00:30 SQL Server ProductType: Standard Edition [0x2]
19:00:30 Begin Action: SetupInitialize
19:00:30 End Action SetupInitialize
19:00:30 Begin Action: SetupInstall
19:00:30 Reading Software\Microsoft\Windows\CurrentVersio
n\CommonFilesDir
...
19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
19:00:30 Windows Directory=C:\WINDOWS\
19:00:30 Program Files=C:\Program Files\
19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Te
mp\1\
19:00:30 Begin Action: SetupInstall
19:00:30 Begin Action: CheckFixedRequirements
19:00:30 Platform ID: 0xf000
19:00:30 Version: 5.2.3790
19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
19:00:31 End Action: CheckFixedRequirements
19:00:31 Begin Action: ShowDialogs
19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
19:00:31 Begin Action ShowDialogsHlpr: 0x1
19:00:31 Begin Action: DialogShowSdWelcome
19:00:32 End Action DialogShowSdWelcome
19:00:32 Dialog 0x1 returned: 1
19:00:32 End Action ShowDialogsHlpr
19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
19:00:32 Begin Action ShowDialogsHlpr: 0x2
19:00:32 Begin Action: DialogShowSdMachineName
19:01:07 ShowDlgMachine returned: -1
19:01:07 ShowDlgMachine: GetLastError returned: 0
19:01:07 Opration russie.
19:01:07 End Action DialogShowSdMachineName
19:01:07 End Action ShowDialogs
19:01:07 Action CleanUpInstall:
19:01:07 StatsGenerate returned: 2
19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
19:01:07 StatsGenerate -1,)
19:01:07 Installation Failed.
"Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
> What were the last few successful entries? Do you have an installation
> that WAS successful that you can compare it to?
> "aLAMBIKI" <alambiki@.yahoo.com> wrote in message
> news:4356ae9a$0$4336$626a54ce@.news.free.fr...
>|||I'm sure one of the MS guys will jump in here somewhere and give you more
than I can. Can you remove the Symantic product as a test?
HTH
Jerry
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356c190$1$4337$626a54ce@.news.free.fr...
>I already installed SBS + SQL on this server. It is the second time I
>install it on this server. The only thing that changes is that I updated
>with the latest ms update + installed symantec lifestate...
> here is the log of SQLstp.log
> 19:00:30 Begin Setup
> 19:00:30 8.00.194
> 19:00:30 Mode = Normal
> 19:00:30 ModeType = NORMAL
> 19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
> 19:00:30 ValueFTS returned: 1
> 19:00:30 ValuePID returned: 1
> 19:00:30 ValueLic returned: 1
> 19:00:30 System: Small Business Server
> 19:00:30 SQL Server ProductType: Standard Edition [0x2]
> 19:00:30 Begin Action: SetupInitialize
> 19:00:30 End Action SetupInitialize
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Reading Software\Microsoft\Windows\CurrentVersio
n\CommonFilesDir
> ...
> 19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
> 19:00:30 Windows Directory=C:\WINDOWS\
> 19:00:30 Program Files=C:\Program Files\
> 19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Te
mp\1\
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Begin Action: CheckFixedRequirements
> 19:00:30 Platform ID: 0xf000
> 19:00:30 Version: 5.2.3790
> 19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
> 19:00:31 End Action: CheckFixedRequirements
> 19:00:31 Begin Action: ShowDialogs
> 19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
> 19:00:31 Begin Action ShowDialogsHlpr: 0x1
> 19:00:31 Begin Action: DialogShowSdWelcome
> 19:00:32 End Action DialogShowSdWelcome
> 19:00:32 Dialog 0x1 returned: 1
> 19:00:32 End Action ShowDialogsHlpr
> 19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
> 19:00:32 Begin Action ShowDialogsHlpr: 0x2
> 19:00:32 Begin Action: DialogShowSdMachineName
> 19:01:07 ShowDlgMachine returned: -1
> 19:01:07 ShowDlgMachine: GetLastError returned: 0
> 19:01:07 Opration russie.
> 19:01:07 End Action DialogShowSdMachineName
> 19:01:07 End Action ShowDialogs
> 19:01:07 Action CleanUpInstall:
> 19:01:07 StatsGenerate returned: 2
> 19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
> 19:01:07 StatsGenerate -1,)
> 19:01:07 Installation Failed.
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> a crit dans le message de news:
> OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
>