Error when installing SQL Server Express

Hi All,

I have a problem when installing SQL Server Express Advanced Edition

It crash when installing Database Services, the log file contains this message

.....

<Func Name='GetSkuIt'>
GetServiceUserGroup failed for SQLEXPRESS, 5
Error Code: 0x80070534 (1332)
Windows Error Text: Le mappage entre les noms de compte et les ID de scurit n'a pas t effectu.
Source File Name: sqlca\sqlcax.cpp
Compiler Timestamp: Fri Feb 9 22:35:05 2007
Function Name: SetInstanceProperty
Source Line Number: 1223

Error Code: 1332
MSI (s) (E0!E8) [10:34:39:288]: Produit : Microsoft SQL Server 2005 -- Erreur 29528. Le programme d'installation a rencontr une erreur inattendue pendant Dfinition des proprits internes. L'erreur est : Erreur irrcuprable lors de l'installation.

Erreur 29528. Le programme d'installation a rencontr une erreur inattendue pendant Dfinition des proprits internes. L'erreur est : Erreur irrcuprable lors de l'installation.

<EndFunc Name='LaunchFunction' Return='1332' GetLastError='203'>
Fin de l'action 10:34:39 : SetInstanceProperty.D20239D7_E87C_40C9_9837_E70B8D4882C2. Valeur renvoye : 3.
Fin de l'action 10:34:39 : INSTALL. Valeur renvoye : 3.
.......

Can someone help me ?

Thx

Hi,

this might helps http://support.microsoft.com/default.aspx/kb/925976.

|||

No, it won't.

Maybe my windows was in a bad state.

I've see that there is no group in local group ..... and a lot of bad news.

I format .........

Thx for your help.

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 help
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...
> 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\CurrentVersion\CommonFi lesDir
...
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\Temp\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\CurrentVersion\CommonFi lesDir
> ...
> 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\Temp\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...
>

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...
>

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...
>> 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
>|||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...
>> 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...
>> 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
>>
>|||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\CurrentVersion\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\Temp\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 Opération réussie.
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...
>> 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...
>> 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
>>
>>
>|||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\CurrentVersion\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\Temp\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 Opération réussie.
> 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...
>> 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...
>> 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
>>
>>
>>
>sql

Error when installing SQL 2000 clustering

See error below
"An error occurred while creating virtual server
resources for clustering. The system cannot find the file
specified."
The failure occured during the creation of the virtual server resources (which this error indicates). You must view Cluster.log (in the WINNT\Cluster folder) or Sqlclstr.log (or both). At this stage, you are past the
unattended setup processes, so you will typically see the "Installation Succeeded" messages in the Sqlstp<N>.log files.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Error when installing Reporting Services in Virtual PC 2004

When I tried installing Reporting Services in Windows Server 2003 under
Virtual PC 2004 it displays a message "Error!". I have already installed
VS.NET 2003 and SQL Server 2000 with SP3. Please help.Hi Randy:
I've installed RS on a couple VPCs, so I don't think it would be a
general problem with VPC. I'm wondering what the problem could be. Do
you have 2003 configured as an application server (IIS, ASP.NET
enabled) before the install?
--
Scott
http://www.OdeToCode.com/blogs/scott/
On Wed, 3 Nov 2004 19:23:02 -0800, "Randy Gadingan" <Randy
Gadingan@.discussions.microsoft.com> wrote:
>When I tried installing Reporting Services in Windows Server 2003 under
>Virtual PC 2004 it displays a message "Error!". I have already installed
>VS.NET 2003 and SQL Server 2000 with SP3. Please help.|||Hi Scott:
I have configured Windows Server 2003 as an application server before
installing VS NET 2003 and SQL Reporting Services.
"Scott Allen" wrote:
> Hi Randy:
> I've installed RS on a couple VPCs, so I don't think it would be a
> general problem with VPC. I'm wondering what the problem could be. Do
> you have 2003 configured as an application server (IIS, ASP.NET
> enabled) before the install?
> --
> Scott
> http://www.OdeToCode.com/blogs/scott/
> On Wed, 3 Nov 2004 19:23:02 -0800, "Randy Gadingan" <Randy
> Gadingan@.discussions.microsoft.com> wrote:
> >When I tried installing Reporting Services in Windows Server 2003 under
> >Virtual PC 2004 it displays a message "Error!". I have already installed
> >VS.NET 2003 and SQL Server 2000 with SP3. Please help.
>

Error when installing MSDE

Hello Everyone

I have worked a little with MSDE mainly for the purpose of a tutorial book.

Right now I have just switched to an XP pc, and i am trying to install it once more, However I am experiencing severe problems when doing so, and i cannot find the correct answer, despite trawling thru these forums.

I am running the command prompt and

cd \sql2ksp3
then cd msde, followed by
Setup SAPWD=password SecurityMode=SQL
It then begins installing, and as it reaches the conclusion i get an error

Setup Failed to configure the server ,refer to the server error logs and the setup error logs for more information.

I just cannot work out what is causing this, i have plenty space on my pc, i am running winXP It seems so many people are having problems with MSDE

is there any way i can install it without a command prompt? or does anyone have a link to a proper installation guide.

Or maybe somone can help me with this problem

Thanks so much in advance

RaphaelIt seems like the Security Mode=SQL causes trouble. Try to install it with just SAPWD=password, I did and it worked

Error when installing

Iv'e searched other forums and websites for this, but I cant solve it.

When I try to install SQL 2000 I get an error about Low Registry Quota.

Any idea on how to solve this?

Doing a quick search, I found this suggestion which helped a few people fix this problem. Can you check if this might be your problem?

Thanks,
Sam

<snip>

I have never ever had the following error message before during the
installation of SQL Server Developer Edition 2000 on a client running
Windows XP Pro SP2 using an account with administrator privileges:
"An error occurred while creating one or more registry entries. Please see
C:\Windows\sqlstp.log for details. The problem could be caused by a low
registry quota condition."

Looking on the internet I have only found several people who had the same
problem but nobody gave a solution. What I have done to find the cause for
this problem was to run the Registry Monitor tool which can be found on
sysinternals.com to monitor what was causing this "Registry error".

I saw that I got several access denies to the following registry key:
HKEY_CLASSES_ROOT\.col

In RegEdit I noticed that the permissions for this key were set to
read-only. I have changed this for the Administrator to full-control and the
installation of SQL Server worked fine.

</snip>

|||Yeah, Iv'e tried that one already. Ill try it again. Thanks :)|||Didnt work :'(

Error when installing

i'm trying to install MS server 2000 components and I continuously get the same error. "A previous program installation created pending file operations on the installation machine. You must restart the computer before running setup." I've rebooted 100 times, turned the machine on and off, installed other programs, etc. and stil I get the error ONLY when I try to install the components.

Please Help!!!!

Thanks.

Moved to the setup group for a better chance of a response.|||

try...

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q290/9/91.asp&NoWebContent=1

|||

Hi, this should help:

http://support.microsoft.com/default.aspx?scid=kb;en-us;312995

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

sql

Error when installing

i'm trying to install MS server 2000 components and I continuously get the same error. "A previous program installation created pending file operations on the installation machine. You must restart the computer before running setup." I've rebooted 100 times, turned the machine on and off, installed other programs, etc. and stil I get the error ONLY when I try to install the components.

Please Help!!!!

Thanks.

Moved to the setup group for a better chance of a response.|||

try...

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q290/9/91.asp&NoWebContent=1

|||

Hi, this should help:

http://support.microsoft.com/default.aspx?scid=kb;en-us;312995

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Error when attempting to use SQL Server Import and Export Wizard

I'm unable to use SSIS packages after installing SQL Server 2005. Specifically when I first loaded a new Integration Services project in SQL Server Business Intelligence Development Studio the default SSIS package could not load, I get Package.dtsx in my tabbed document view but in the body of this window is a error message: "Microsoft Visual Studio is unable to load this document. QI for IEnumVARIANT failed on the unmanaged server."

If I try to use the SQL Server Import and Export Wizard shortly after the window to select your data source I get a pop-up error message:

This wizard will close because it encountered the following error:

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.SqlServer.Management.UI.WizardFrameworkErrorSR&EvtID=UncaughtException&LinkId=20476

ADDITIONAL INFORMATION:

QI for IEnumVARIANT failed on the unmanaged server. (CustomMarshalers)

Anyone have any ideas on how I can resolve this?

I have experienced the same problem. Have you found a solution yet?

I found other users experiencing similar problems, but apparently not the same issue. I tried the fix at http://groups-beta.google.com/group/microsoft.public.dotnet.framework.setup/browse_thread/thread/a2ed96d68cb349f3/db810a1bcf8f66e4?q=qi+ienumvariant&_done=%2Fgroups%3Fhl%3Den%26lr%3Dlang_en%26safe%3Doff%26c2coff%3D1%26q%3Dqi+ienumvariant%26qt_s%3DSearch+Groups%26&_doneTitle=Back+to+Search&&d#db810a1bcf8f66e4

but had no luck.

Error when attempting to use SQL Server Import and Export Wizard

I'm unable to use SSIS packages after installing SQL Server 2005. Specifically when I first loaded a new Integration Services project in SQL Server Business Intelligence Development Studio the default SSIS package could not load, I get Package.dtsx in my tabbed document view but in the body of this window is a error message: "Microsoft Visual Studio is unable to load this document. QI for IEnumVARIANT failed on the unmanaged server."

If I try to use the SQL Server Import and Export Wizard shortly after the window to select your data source I get a pop-up error message:

This wizard will close because it encountered the following error:

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.SqlServer.Management.UI.WizardFrameworkErrorSR&EvtID=UncaughtException&LinkId=20476

ADDITIONAL INFORMATION:

QI for IEnumVARIANT failed on the unmanaged server. (CustomMarshalers)

Anyone have any ideas on how I can resolve this?

I have experienced the same problem. Have you found a solution yet?

I found other users experiencing similar problems, but apparently not the same issue. I tried the fix at http://groups-beta.google.com/group/microsoft.public.dotnet.framework.setup/browse_thread/thread/a2ed96d68cb349f3/db810a1bcf8f66e4?q=qi+ienumvariant&_done=%2Fgroups%3Fhl%3Den%26lr%3Dlang_en%26safe%3Doff%26c2coff%3D1%26q%3Dqi+ienumvariant%26qt_s%3DSearch+Groups%26&_doneTitle=Back+to+Search&&d#db810a1bcf8f66e4

but had no luck.

Error when "Open Table" in SQL Server Management Studio

I get the following error when I try and open a table in SQL Server Management Studio. Installing SP1 did not fix as I hoped it might. What can I do about this - I can't see my data?

===================================

Unspecified error
(MS Visual Database Tools)

Program Location:

at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.VirtualProject.Microsoft.SqlServer.Management.UI.VSIntegration.Editors.ISqlVirtualProject.CreateDesigner(Urn origUrn, DocumentType editorType, DocumentOptions aeOptions, IManagedConnection con)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.ISqlVirtualProject.CreateDesigner(Urn origUrn, DocumentType editorType, DocumentOptions aeOptions, IManagedConnection con)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.VsDocumentMenuItem.CreateDesignerWindow(IManagedConnection mc, DocumentOptions options)

I have the exact same problem.
Did you happen to solve it in any way? Can't find any good information about this failure :(

Error Uninstalling CTP

I am trying to uninstall SQL Server 2005 CTP version before installing Beta version and keep getting an ARP Wrapper Error message that states "Registry Enumeration Failed". I ran Registry Mechanic, etc, but there are no indications of a problem.

Any ideas?

Thanks in advance,

dinzana

I'm getting this error too. Totally annoying.

Error Uninstalling CTP

I am trying to uninstall SQL Server 2005 CTP version before installing Beta version and keep getting an ARP Wrapper Error message that states "Registry Enumeration Failed". I ran Registry Mechanic, etc, but there are no indications of a problem.

Any ideas?

Thanks in advance,

dinzana

I'm getting this error too. Totally annoying.

Error starting svc at end of install

I get this error right at the end of installing the server
components.
Product: Microsoft SQL Server 2000 Reporting Services
Developer Edition -- Error 1920. Service 'ReportServer'
(ReportServer) failed to start. Verify that you have
sufficient privileges to start system services.
I am logged in as Administrator. It then decides to
rollback the install. My machine is Win2k2003 with IIS6.
Any ideas?
Thanks,
DaveOk, so i did a complete uninstall and reinstall and it
works. I guess if you do a client only install and then
try to install the service components you don't get any
prompts to select which account the reportservice runs
under.
>--Original Message--
>I get this error right at the end of installing the
server
>components.
>Product: Microsoft SQL Server 2000 Reporting Services
>Developer Edition -- Error 1920. Service 'ReportServer'
>(ReportServer) failed to start. Verify that you have
>sufficient privileges to start system services.
>I am logged in as Administrator. It then decides to
>rollback the install. My machine is Win2k2003 with IIS6.
>Any ideas?
>Thanks,
>Dave
>.
>

Error Starting Report Manager with Beta 2005 Dec CTP

I et the following error trying to start Report Manager after installing
SQL2005 beta December CTP. I installed side-by-side with a full SQL2000
implementation on Windows 2003 Server:
Server Error in '/Reports$SQL2005' Application
----
Unable to find a helper module that supports ISessionIDModule
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Web.HttpException: Unable to find a helper module
that supports ISessionIDModule
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[HttpException (0x80004005): Unable to find a helper module that supports
ISessionIDModule]
System.Web.SessionState.SessionStateModule.InitModuleFromConfig(HttpApplication app, SessionStateSection config) +3517537
System.Web.SessionState.SessionStateModule.Init(HttpApplication app) +256
System.Web.HttpApplication.InitModules() +210
System.Web.HttpApplication.InitInternal(HttpContext context,
HttpApplicationState state, MethodInfo[] handlers) +1283
System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext
context) +414
System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext
context) +99
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +186
----
Version Information: Microsoft .NET Framework Version:2.0.40903.27; ASP.NET
Version:2.0.40903.27I think this may be related to an ASP.Net 2.0 beta problem - The ASP Admin
service does not start and errors with "Error 2: The system cannot find the
file specified."
"Mark" wrote:
> I et the following error trying to start Report Manager after installing
> SQL2005 beta December CTP. I installed side-by-side with a full SQL2000
> implementation on Windows 2003 Server:
> Server Error in '/Reports$SQL2005' Application.
> ----
> Unable to find a helper module that supports ISessionIDModule
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information about
> the error and where it originated in the code.
> Exception Details: System.Web.HttpException: Unable to find a helper module
> that supports ISessionIDModule
> Source Error:
> An unhandled exception was generated during the execution of the current web
> request. Information regarding the origin and location of the exception can
> be identified using the exception stack trace below.
> Stack Trace:
>
> [HttpException (0x80004005): Unable to find a helper module that supports
> ISessionIDModule]
> System.Web.SessionState.SessionStateModule.InitModuleFromConfig(HttpApplication app, SessionStateSection config) +3517537
> System.Web.SessionState.SessionStateModule.Init(HttpApplication app) +256
> System.Web.HttpApplication.InitModules() +210
> System.Web.HttpApplication.InitInternal(HttpContext context,
> HttpApplicationState state, MethodInfo[] handlers) +1283
> System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext
> context) +414
> System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext
> context) +99
> System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +186
>
>
> ----
> Version Information: Microsoft .NET Framework Version:2.0.40903.27; ASP.NET
> Version:2.0.40903.27

Error SQL server 2005 installing

first I installed SQL 2005 beta 2 the I uninstall it , but still I receive this error msg:

SQL Server 2005 setup has detected incompatible components from beta version of visual studio, .Net Framework , or SQL server 2005 .

is there any suggestion to solve this problem

thanks for your reply

no one knows ,,

or no one care , I wonder what's the porpose of this forum

|||If you first installed beta products you have to clean your system from all installed version of the beta software, client tools, .NET framework, SNAC, SQL Server etc. There is a uninstall software which cleans the installation, it can be downloaded here:

http://lab.msdn.microsoft.com/vs2005/uninstall/preRTMuninstall/default.aspx
http://lab.msdn.microsoft.com/vs2005/uninstall/default.aspx

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

error- shared memory sql server doesnt........

Hi evryone

I have installed SQL server as local system account and mixmode authorization.

After installing when i try to connect to database using sa account.

it gives error like Microsoft ODBC sql server driver - shared memory- sql server doesnt exist or access denied.

I unistalled sql server and again i installed. but same error facing.

Please reply.

Regards,

What name did you give the SQL Server when you installed it, which SQL Server was it?

If this is SQL Express then the connection string you need ot use is .\sqlexpress

Error running script: sp1_serv_uni.sql(1), while installing SP3(sql2ksp3)

Thanks for the reply.
The link which you have given me, I went to that page but
the solution they gave is to install the latest service
pack or a work around solution, I was trying to install
the latest service pack itself not the service pack 1,the
solution they gave is for servive pack 1 not for service
pack 3, so do you have any idea what I should do.
Please mail me a response.
Regards,
Jyotshna.
--Original Message--
this error may occur if the master database files have
been moved from the
orignal installation location.
check the following link:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;Q308753
regards,
Harsh.
"Jyotshna Vonguru" <jyotshna.vonguru@.icn.siemens.com>
wrote in message
news:568701c3e51c$aefe4410$a401280a@.phx.gbl...
Hello,
I am getting an error called:
Error running script: sp1_serv_uni.sql(1), while
installing service pack 3(sql2ksp3).
Could anybody tell me, how to correct this.
Is there anyway.
Please give me a quick solution.
Thank you,
Jyotshna.Please find the corresponding *.out file to see a detailed error mesage.
Thanks,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.|||I too am getting the same problem.
The *.out file says (1 row affected)
Thats it.
This is driving me made, as I have 3 x 2003 Servers I am building with SQL 2000 on them, and am getting exactly the same error on all 3.|||I'm having the exact same problem.
No one has been able to help me.
Would I be correct in guessing that this is on a Windows 2003 Server, and
its a fresh install of SQL 2000.
Dave.|||What does the sqlstp.log say?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.