error during SQL Server 2005 Express help...

The "Setup Progress" window displays the selected components to be configured.

After completion, the window displays a red x beside Reporting Services.

On all the other results, you can click and view a log generated during installation.

Clicking on the "Reporting Services" (that didn't install) does not display the log file.

Any help is appreciated.

Thanks,

Trint

You can get the setup logs from here - %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files. Look for the RS log that looks something like SQLSetup0001_<machinename>_RS.log

Thanks,

Sharmila

error during SQL Server 2005 Express help...

The "Setup Progress" window displays the selected components to be
configured.
After completion, the window displays a red x beside Reporting
Services.
On all the other results, you can click and view a log generated
during installation.
Clicking on the "Reporting Services" (that didn't install) does not
display the log file.
Any help is appreciated.
Thanks,
TrintOn Feb 16, 12:11 pm, "trint" <trinity.sm...@.gmail.com> wrote:
> The "Setup Progress" window displays the selected components to be
> configured.
> After completion, the window displays a red x beside Reporting
> Services.
> On all the other results, you can click and view a log generated
> during installation.
> Clicking on the "Reporting Services" (that didn't install) does not
> display the log file.
> Any help is appreciated.
> Thanks,
> Trint
I had this occur in the past, you can try to see if the reason for the
error appeared in the Event Viewer. I would suggest uninstalling SQL
Server 2005 Express and reinstalling it and of course, make sure that
you have all trial versions uninstalled before reinstalling it (where
applicable). Hope this helps.
Regards,
Enrique Martinez
Sr. SQL Server Developer|||On Feb 18, 7:26 pm, "EMartinez" <emartinez...@.gmail.com> wrote:
> On Feb 16, 12:11 pm, "trint" <trinity.sm...@.gmail.com> wrote:
> > The "Setup Progress" window displays the selected components to be
> > configured.
> > After completion, the window displays a red x beside Reporting
> > Services.
> > On all the other results, you can click and view a log generated
> > during installation.
> > Clicking on the "Reporting Services" (that didn't install) does not
> > display the log file.
> > Any help is appreciated.
> > Thanks,
> >Trint
> I had this occur in the past, you can try to see if the reason for the
> error appeared in the Event Viewer. I would suggest uninstalling SQL
> Server 2005 Express and reinstalling it and of course, make sure that
> you have all trial versions uninstalled before reinstalling it (where
> applicable). Hope this helps.
> Regards,
> Enrique Martinez
> Sr. SQL Server Developer
Enrique,
I did that and also on two different machines (same problem).
Thanks,
Trint

Error after installing sp1

I started getting this after installing sp1 on my workstation and trying to deploy to rtm machines. The components giving this error are the data readers in the data flow.

TITLE: Microsoft Visual Studio

Component with name "<name>" and class ID "{BF01D463-7089-41EE-8F05-0A6DC17CE633}" could not be created because an error was encountered during its upgrade to the current version.
Contact information:
Extracts data from a relational database by using a .NET provider.;Microsoft Corporation;Microsoft SqlServer v9; ? 2004 Microsoft Corporation; All Rights Reserved; http://www.microsoft.com/sql/support;2

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.Design.SR&EvtID=ComponentUpgradeFailed&LinkId=20476

BUTTONS:

OK

See Component Changes - http://wiki.sqlis.com/default.aspx/SQLISWiki/SP1.html|||That's just wonderful considering I installed it on my workstation as a test and now I can't roll out a lot of my packages. Ugh, I didn't think they could make management and deployment any more of a headache but they succeeded. How about they let you write the release notes from now on :)|||As a side note, it appears that even if I edit the xml as you suggest I still cannot deploy it from my workstation or it will readd those properties.|||Maybe you are using the built in deployment utility? I'm working in a file copy style deployment so it works fine as a workaround. Failing that roll out SP1!|||

Yeah I am. I suppose it calls that upgrade method before it uploads it to the server. *sigh*

We'd like to roll out sp1 if the install would quit crashing :)