installation problems with W2003/WSS

I have not been able to install SRS onto a W2003 server that hosts Windows
Sharepoint, and (briefly) had the .NET 2.0 beta framework installed. I
believe this is due to the "unclean" removal of 2.0 (the aspnet_admin and
aspnet_state services still seem to point at the 2.0 directory, which has no
remaining executables).
The "ReportingService" is not installed / instantiated, although according
to BOL it should be. I have attempted to use the command-line tool as
suggested in the readme.htm file with the installation, but again, no luck.
I haven't been able to ascertain where the install log might be parked.
Funny, this installation went pretty smoothly on my XP box. I guess I may
have to rebaseline this puppy at some point, due to mistakenly attempting to
run the 2.0 fx with WSS.
ANY help at all appreciated.Should pass along the following log snippet as well, apparently playing with
the "Default" IIS instance ain't cricket:
<EndFunc Name='PerformDetections' Return='0' GetLastError='0'>
<Prerequisite Name="IsIISInstalled" Checked="Metabase"
Item="/LM/W3SVC/1/1016" Found="Can not read value" Expected="No error"
Result="Fail" />
Machine = ALMO, Article = IIS, Result = 60350 (0xebbe)
Machine = ALMO, Article = VSNET, Result = 0 (0x0)
Machine = ALMO, Article = ASPNET, Result = 0 (0x0)
Machine = ALMO, Article = MDAC, Result = 0 (0x0)
Machine = ALMO, Article = DTC, Result = 0 (0x0)
Machine = ALMO, Article = SERVEROS, Result = 0 (0x0)
<Prerequisite Name="IsSharePointNotInstalled" Checked="Registry"
Item="HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\6.0"
Found="Key" Expected="No Key" Result="Fail" />
Machine = ALMO, Article = SHAREPOINT, Result = 60356 (0xebc4)
Machine = ALMO, Article = AUTHZ, Result = 0 (0x0)
Machine = ALMO, Article = RSACCOUNTS, Result = 0 (0x0)
"AlexM" <amondale@.nopsam.yahoo.nopsam.com> wrote in message
news:OqaGegs0EHA.1860@.TK2MSFTNGP15.phx.gbl...
> I have not been able to install SRS onto a W2003 server that hosts Windows
> Sharepoint, and (briefly) had the .NET 2.0 beta framework installed. I
> believe this is due to the "unclean" removal of 2.0 (the aspnet_admin and
> aspnet_state services still seem to point at the 2.0 directory, which has
no
> remaining executables).
> The "ReportingService" is not installed / instantiated, although according
> to BOL it should be. I have attempted to use the command-line tool as
> suggested in the readme.htm file with the installation, but again, no
luck.
> I haven't been able to ascertain where the install log might be parked.
> Funny, this installation went pretty smoothly on my XP box. I guess I may
> have to rebaseline this puppy at some point, due to mistakenly attempting
to
> run the 2.0 fx with WSS.
> ANY help at all appreciated.
>|||I had a similar problem with FX2. I had to re-register ASP.NET 1.1 with IIS
by running :
<windows>\Microsoft.NET\Framework\<your 1.1 dir>\aspnet_regiis -i
RS installed fine afterwards.
hth
"AlexM" <amondale@.nopsam.yahoo.nopsam.com> wrote in message
news:OqaGegs0EHA.1860@.TK2MSFTNGP15.phx.gbl...
>I have not been able to install SRS onto a W2003 server that hosts Windows
> Sharepoint, and (briefly) had the .NET 2.0 beta framework installed. I
> believe this is due to the "unclean" removal of 2.0 (the aspnet_admin and
> aspnet_state services still seem to point at the 2.0 directory, which has
> no
> remaining executables).
> The "ReportingService" is not installed / instantiated, although according
> to BOL it should be. I have attempted to use the command-line tool as
> suggested in the readme.htm file with the installation, but again, no
> luck.
> I haven't been able to ascertain where the install log might be parked.
> Funny, this installation went pretty smoothly on my XP box. I guess I may
> have to rebaseline this puppy at some point, due to mistakenly attempting
> to
> run the 2.0 fx with WSS.
> ANY help at all appreciated.
>|||Thanks, Chris!
I have managed to get by this hurdle, basically by finding (%TEMP%) the
logs, the location of which isn't relly well documented, and discovering
that the script is hardcoded to look for LMSVC3/1 specifically. This meant
removing and then re-adding the role for "Application Server" in 2003
Server.
Having gotten past this, however, I have now discovered that the NT
AUTHORITY\NETWORK SERVICE won't start the "Report Server" service up during
installation, again causing the setup to fail. I believe this problem may be
documented somewhere, but I haven't yet found it. It is not logged in any
way I can figure out.
Anybody have any ideas on this issue? All help greatly appreciated.
Alex
"Chris Ashworth" <cashworth@.gmail.com> wrote in message
news:O#JD50u0EHA.1392@.tk2msftngp13.phx.gbl...
> I had a similar problem with FX2. I had to re-register ASP.NET 1.1 with
IIS
> by running :
> <windows>\Microsoft.NET\Framework\<your 1.1 dir>\aspnet_regiis -i
> RS installed fine afterwards.
> hth
> "AlexM" <amondale@.nopsam.yahoo.nopsam.com> wrote in message
> news:OqaGegs0EHA.1860@.TK2MSFTNGP15.phx.gbl...
> >I have not been able to install SRS onto a W2003 server that hosts
Windows
> > Sharepoint, and (briefly) had the .NET 2.0 beta framework installed. I
> > believe this is due to the "unclean" removal of 2.0 (the aspnet_admin
and
> > aspnet_state services still seem to point at the 2.0 directory, which
has
> > no
> > remaining executables).
> >
> > The "ReportingService" is not installed / instantiated, although
according
> > to BOL it should be. I have attempted to use the command-line tool as
> > suggested in the readme.htm file with the installation, but again, no
> > luck.
> > I haven't been able to ascertain where the install log might be parked.
> >
> > Funny, this installation went pretty smoothly on my XP box. I guess I
may
> > have to rebaseline this puppy at some point, due to mistakenly
attempting
> > to
> > run the 2.0 fx with WSS.
> >
> > ANY help at all appreciated.
> >
> >
>|||Still unable to install on Win2003 server. When the setup program attempts
to start the windows service, the following is looged to the app event log:
The encrypted value for Dsn in the RSReportServer.config file cannot be
decrypted.
and
Service cannot be started.
Microsoft.ReportingServices.Diagnostics.Utilities.FailedToDecryptConfigInfor
mationException: The encrypted value for configuration setting Dsn cannot be
decrypted. -->
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details.
at
Microsoft.ReportingServices.Diagnostics.DataProtectionLocal.UnprotectData(By
te[] data, Int32 dwFlags)
at
Microsoft.ReportingServices.Diagnostics.DataProtectionLocal.LocalUnprotectDa
ta(Byte[] data)
at
Microsoft.ReportingServices.Diagnostics.DataProtectionLocal.LocalUnprotectDa
ta(String data)
at
Microsoft.ReportingServices.Diagnostics.RSConfiguration.DecryptCatalogData(S
tring encryptedData, String element)
-- End of inner exception stack trace --
at
Microsoft.ReportingServices.Diagnostics.RSConfiguration.DecryptCatalogData(S
tring encryptedData, String element)
at
Microsoft.ReportingServices.Diagnostics.RSConfiguration.get_ConnectionString
()
at
Microsoft.ReportingServices.Library.ServiceAppDomainController.StartRPCServe
r()
at Microsoft.ReportingServices.Library.ServiceAppDomainController.Start()
at Microsoft.ReportingServices.NTService.ReportService.OnStart(String[]
args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"AlexM" <amondale@.nopsam.yahoo.nopsam.com> wrote in message
news:#56qdxw0EHA.1564@.TK2MSFTNGP09.phx.gbl...
> Thanks, Chris!
> I have managed to get by this hurdle, basically by finding (%TEMP%) the
> logs, the location of which isn't relly well documented, and discovering
> that the script is hardcoded to look for LMSVC3/1 specifically. This meant
> removing and then re-adding the role for "Application Server" in 2003
> Server.
> Having gotten past this, however, I have now discovered that the NT
> AUTHORITY\NETWORK SERVICE won't start the "Report Server" service up
during
> installation, again causing the setup to fail. I believe this problem may
be
> documented somewhere, but I haven't yet found it. It is not logged in any
> way I can figure out.
> Anybody have any ideas on this issue? All help greatly appreciated.
> Alex
>
> "Chris Ashworth" <cashworth@.gmail.com> wrote in message
> news:O#JD50u0EHA.1392@.tk2msftngp13.phx.gbl...
> > I had a similar problem with FX2. I had to re-register ASP.NET 1.1 with
> IIS
> > by running :
> >
> > <windows>\Microsoft.NET\Framework\<your 1.1 dir>\aspnet_regiis -i
> >
> > RS installed fine afterwards.
> >
> > hth
> >
> > "AlexM" <amondale@.nopsam.yahoo.nopsam.com> wrote in message
> > news:OqaGegs0EHA.1860@.TK2MSFTNGP15.phx.gbl...
> > >I have not been able to install SRS onto a W2003 server that hosts
> Windows
> > > Sharepoint, and (briefly) had the .NET 2.0 beta framework installed. I
> > > believe this is due to the "unclean" removal of 2.0 (the aspnet_admin
> and
> > > aspnet_state services still seem to point at the 2.0 directory, which
> has
> > > no
> > > remaining executables).
> > >
> > > The "ReportingService" is not installed / instantiated, although
> according
> > > to BOL it should be. I have attempted to use the command-line tool as
> > > suggested in the readme.htm file with the installation, but again, no
> > > luck.
> > > I haven't been able to ascertain where the install log might be
parked.
> > >
> > > Funny, this installation went pretty smoothly on my XP box. I guess I
> may
> > > have to rebaseline this puppy at some point, due to mistakenly
> attempting
> > > to
> > > run the 2.0 fx with WSS.
> > >
> > > ANY help at all appreciated.
> > >
> > >
> >
> >
>