Hi,
 For information.
 It looks like the SQL Reporting Services install doesn't work properly
 if you have followed Microsoft's advice and have stored the server's
 .net credentials (in the machine.config <processModel> element) in the
 registry using aspnet_setreg. (You would do this to remove the plain
 text entries from the machine.config file).
 I have tried this several times and each time, the install just reads
 the username and password entries as text, and can't deal with the
 fact that these entries are actually pointing to the registry for the
 credentials.
 When you get to the Service Account screen on the install wizard, the
 section entitled "The Report Server Web service will run under the
 following account:" shows the following:
 registy:HKLM\SOFTWARE\...\ASPNET_SETREG,userName
 (or whatever the location is to your encrypted machine.config
 settings).
 The install starts after you've completed all of the screens in the
 wizard, but then can't start the ReportServer web service
 (unsurprisingly!).
 The only way that I can see to get round this is to change the
 machine.config processModel section before the SQL Reporting Services
 install so that the userName and password entries are present in
 plaintext in the file. This isn't great - particularly if your
 entries have been stored in the registry because it's impossible to
 find out what the password is if you haven't got a note of it (and
 maybe only the Security team were allowed to have the password, etc.).
 It also means that there's a possibility that .net things will stop
 working on your server while you're doing the install (ie. just
 because you don't really want to have to change those entries, for
 risk of typos, etc.).
 I hope these comments are useful.
 Regards,
 Rich WFor info, the same is true for when you install SQL Reporting Services
SP1 - ie. you have to change the machine.config processModel username
and password attributes so that they are not being read from the
registry.
Regards,
Rich
Subscribe to:
Post Comments (Atom)
 
No comments:
Post a Comment