Installing MSDE

Being new to setting up MSDE, we are currently testing crystal reports
and Microsoft Sharepoint services. We want to install these on a
seperate server and see that they use MSDE. We also have a server
currently installed with MSDE for Altiris deployment images and HP
insite manager. Is it a good practice to link to the existing MSDE
server or house this instance of MSDE on the new test server.
Thanks
John
hi John,
JohnC wrote:
> Being new to setting up MSDE, we are currently testing crystal reports
> and Microsoft Sharepoint services. We want to install these on a
> seperate server and see that they use MSDE. We also have a server
> currently installed with MSDE for Altiris deployment images and HP
> insite manager. Is it a good practice to link to the existing MSDE
> server or house this instance of MSDE on the new test server.
usually it's considered a good practice to separate the database server from
the application server both for security reasons and performance reasons, in
order to have a "dedicated" machine for each task...
just a caveat.. Sharepoint usually requires a lot of database space and
ships with a dedicated MSDE version, known as WMSDE, which has been modified
by Microsoft to remove the 2gb limit for each database.. WMSDE is shipped
only with Sharepoint and can only be (legally) used by it...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea for your info, looking at the big picture and future
expansion. Taking on board your info about a dedicated database server,
are we better off having an sql server and all are database accessing
software linking up to it like Altiris, sharepoint, crystal reports,
and our own web site which at the moment is linked to mysql.
Regards
John

Installation to Sharepoint server

Hi,
We have a question regarding the installation of RS to a WSS server. We have
used STSADM to exlcude the site, checked the web configs for session state
info present, placed the Report server web site in a separate application
pool from WSS, applied Hotfix 859, and attempted manually activate using
rsactivate.
RS fails to activate and the sites cannot be browsed.
What can we check beyond this?
Thanks
SethWe have had similar difficulties - RS seems to compete with SharePoint
in the default web site. In our situation running an IISRESET had the
effect that whichever application was accessed first (either Report
Manager or SharePoints default web site application) would work, and
the other would throw an error.
In our case, RS had been installed first, so activation was not a
problem. Interestingly, even when Report Manager was 'broken', the
underlying Reporting Services continued to work for reports that had
already been deployed.
Researching provided some updated configuration files from the MSDN web
site (sorry I don't have the link) which got Report Manager to work
(after extracting and reapplying the symmetric key), but left the
sharepoint default web site down.
Luckily we didn't need it at that point, so we never drove to a
resolution. (so I will be tracking this thread!).
I would recommend uninstalling RS, finding the new config files I
mentioned, and starting again.
A copy of 'Hitchhiker's Guide to SQL Server Reporting Services' may be
a good investment - (www.bookpool.com has good pricing, service, and
delivery) I am just starting to work through the book, and feel I got
my money's worth at about page 2...
Putting the two RS applications in the same pool is good - you should
also confirm they are both configured to work with .NET Framework 1.1.
If you have Framework 2.0 on the box, they may have been configured to
work with it instead (and they won't - they also won't work if they are
in an application pool with anything using 2.0 - the other thing will
also break...).
If you can install RS to a place other than the default web site, that
might help (though we have never gone down that road).
Also, if you can get a more recent hotfix, you will overcome some
problems that 859 introduces in the Enterprise Manager (some DDL-type
changes won't work through the GUI, although the equivalent commands
will run in Query Analyzer.)|||Seth,
Did you ever get an answer for this?
Alan
"Seth" <Seth@.discussions.microsoft.com> wrote in message
news:41B01080-6179-4BBE-A343-11F3013836ED@.microsoft.com...
> Hi,
> We have a question regarding the installation of RS to a WSS server. We
> have
> used STSADM to exlcude the site, checked the web configs for session state
> info present, placed the Report server web site in a separate application
> pool from WSS, applied Hotfix 859, and attempted manually activate using
> rsactivate.
> RS fails to activate and the sites cannot be browsed.
> What can we check beyond this?
> Thanks
> Seth

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

Installation Package for XML Filter

Hi,
I need to install the XML Filter on the SQL Server machine.
http://www.microsoft.com/sharepoint/...XML_Filter.asp
The filter will be used by the Indexing Service.
The problem with the filter is that it comes as a dll and involves
registry changes that have to be manually done.
Is there a MSI or exe for the same available from Microsoft or do I
need to write one myself ?
Vinay Bhatia
Hi
I think it is the latter!!
This is described as beta software so installing it may have some potential
risk!
John
"bhatiavinay99@.gmail.com" wrote:

> Hi,
> I need to install the XML Filter on the SQL Server machine.
> http://www.microsoft.com/sharepoint/...XML_Filter.asp
> The filter will be used by the Indexing Service.
> The problem with the filter is that it comes as a dll and involves
> registry changes that have to be manually done.
> Is there a MSI or exe for the same available from Microsoft or do I
> need to write one myself ?
> Vinay Bhatia
>
|||Hi John,
The XML Filter is actually installed when you deploy Sharepoint 2003.
And its a newer version then available on the microsoft site. So I am
truely worried about the beta part...I can take the new version from
the Sharepoint Folder.
But installing XML Filter via Sharepoint 2003 makes only those registry
changes required for Sharepoint Search, not the one used by Indexing
Service.
Also, my Sharepoint and SQL Server are on different boxes..so I need an
installable.
Vinay

Installation Package for XML Filter

Hi,
I need to install the XML Filter on the SQL Server machine.
http://www.microsoft.com/sharepoint/server/techinfo/reskit/XML_Filter.asp
The filter will be used by the Indexing Service.
The problem with the filter is that it comes as a dll and involves
registry changes that have to be manually done.
Is there a MSI or exe for the same available from Microsoft or do I
need to write one myself ?
Vinay BhatiaHi
I think it is the latter!!
This is described as beta software so installing it may have some potential
risk!
John
"bhatiavinay99@.gmail.com" wrote:
> Hi,
> I need to install the XML Filter on the SQL Server machine.
> http://www.microsoft.com/sharepoint/server/techinfo/reskit/XML_Filter.asp
> The filter will be used by the Indexing Service.
> The problem with the filter is that it comes as a dll and involves
> registry changes that have to be manually done.
> Is there a MSI or exe for the same available from Microsoft or do I
> need to write one myself ?
> Vinay Bhatia
>|||Hi John,
The XML Filter is actually installed when you deploy Sharepoint 2003.
And its a newer version then available on the microsoft site. So I am
truely worried about the beta part...I can take the new version from
the Sharepoint Folder.
But installing XML Filter via Sharepoint 2003 makes only those registry
changes required for Sharepoint Search, not the one used by Indexing
Service.
Also, my Sharepoint and SQL Server are on different boxes..so I need an
installable.
Vinay

Installation Package for XML Filter

Hi,
I need to install the XML Filter on the SQL Server machine.
http://www.microsoft.com/sharepoint.../XML_Filter.asp
The filter will be used by the Indexing Service.
The problem with the filter is that it comes as a dll and involves
registry changes that have to be manually done.
Is there a MSI or exe for the same available from Microsoft or do I
need to write one myself ?
Vinay BhatiaHi
I think it is the latter!!
This is described as beta software so installing it may have some potential
risk!
John
"bhatiavinay99@.gmail.com" wrote:

> Hi,
> I need to install the XML Filter on the SQL Server machine.
> http://www.microsoft.com/sharepoint.../XML_Filter.asp
> The filter will be used by the Indexing Service.
> The problem with the filter is that it comes as a dll and involves
> registry changes that have to be manually done.
> Is there a MSI or exe for the same available from Microsoft or do I
> need to write one myself ?
> Vinay Bhatia
>|||Hi John,
The XML Filter is actually installed when you deploy Sharepoint 2003.
And its a newer version then available on the microsoft site. So I am
truely worried about the beta part...I can take the new version from
the Sharepoint Folder.
But installing XML Filter via Sharepoint 2003 makes only those registry
changes required for Sharepoint Search, not the one used by Indexing
Service.
Also, my Sharepoint and SQL Server are on different boxes..so I need an
installable.
Vinay