RS2005 Crashed After Editing and Restoring Config Files

Dear Anyone,

Here's what happened. We backed up the web.config and the rsreportserver.config. We messed around with it trying to make an assumption worked. When we finally gave up, we deleted these files and renamed back the web.config and the rsreportserver.config files. To our surprise when we tried to open our report manager, the error below showed up. We tried to reconfigure the report server using the reporting services configuration tool to no avail.

Any insights to what had happened and how to resolve it?

Thanks,
Joseph

Error message:

The report server is not responding. Verify that the report server is running and can be accessed from this computer.

check that reportserver service is running|||Yup, report service is running.|||

Hi Joseph,

I have seen something similar if the xml in the config files were mal formed. Open the config file in IE and see if there is a tag missing or something.

David

|||

Thanks for the reply. I have been told that one of the config files is not really an xml file. We've verified this with all of our reporting services installations. Aparently they have some sort of an encrypted data within it. I wonder if this is really true?

|||

We rely on ASP.NET and CLR Security to parse config files (rsReportServer.Config and rssrvpolicy.config).
Unfortunately these things use simplified xml parsers that may not properly handle some of xml features. It is a known fact that rssrvpolicy.config does not handle xml comments.
So whenever you modify config file make sure it is well formed.

RSReportServer.Config contains credentials for connecting to the RS Catalog database. These credentials are encrypted. To change them use Reporting Services Configuration Manager.

RS on the Internet

Im tring to gte my report server to work on the Internet.
It works fine locally but when I add the ReportServerExternalURL to the
config file as documented it fails saying ;
The configuration file contains an element that is not valid. The
ReportServerExternalURL element is not a configuration file element.
I am using Win2003 and RsSp1. Does anyone know what I am doing wrong?
NickIt must be something like
<Configuration>
<UI>
<ReportServerUrl>http://www.MyRSServer.com/ReportServer</ReportServerUrl>
</UI>
in RSWebApplication.config. I think ReportServerExternalURL is the wrong
property tag for this.
Hope this helps.
Regards
"Nick Jacobs" <news@.winman.co.uk> wrote in message
news:#A2Ff9tAFHA.1188@.tk2msftngp13.phx.gbl...
> Im tring to gte my report server to work on the Internet.
> It works fine locally but when I add the ReportServerExternalURL to the
> config file as documented it fails saying ;
> The configuration file contains an element that is not valid. The
> ReportServerExternalURL element is not a configuration file element.
> I am using Win2003 and RsSp1. Does anyone know what I am doing wrong?
> Nick
>
>|||You may be modifiying the wrong Config file. This change should be
made to the "RSWebApplication.config" file which is usually located at
the following path:
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager
The new node will go within the UI element, alongside the
ReportServerUrl element. The value should be the fully-qualified
domain name for the external address.
<Configuration>
<UI>
<ReportServerUrl>http://localhost/ReportServer</ReportServerUrl>
<ReportServerExternalURL>reports.adventure-works.com</ReportServerExternalURL>
</UI>
...
NOTE: Be careful because, all elements are case-sensitive and this one
has "URL" capitalized instead of Pascal cased. Improper case can also
cause this to fail.
For more details, see MSDN:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0h9e.asp
I hope this helps,
Lance Hunt
http://weblogs.asp.net/lhunt/|||I have
<Configuration>
<UI>
<ReportServerUrl>http://COMSRV/ReportServer</ReportServerUrl>
<ReportServerExternalURL>http://remote.mydomain.co.uk/ReportServer</ReportServerExternalURL>
</UI>
In the RSWebApplication.config
Isn't this supposed to work?
Nick
"Lance" <lancehunt@.gmail.com> wrote in message
news:1106665173.525554.327200@.z14g2000cwz.googlegroups.com...
> You may be modifiying the wrong Config file. This change should be
> made to the "RSWebApplication.config" file which is usually located at
> the following path:
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportManager
> The new node will go within the UI element, alongside the
> ReportServerUrl element. The value should be the fully-qualified
> domain name for the external address.
> <Configuration>
> <UI>
> <ReportServerUrl>http://localhost/ReportServer</ReportServerUrl>
> <ReportServerExternalURL>reports.adventure-works.com</ReportServerExternalURL>
> </UI>
> ...
>
> NOTE: Be careful because, all elements are case-sensitive and this one
> has "URL" capitalized instead of Pascal cased. Improper case can also
> cause this to fail.
> For more details, see MSDN:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0h9e.asp
> I hope this helps,
> Lance Hunt
> http://weblogs.asp.net/lhunt/
>|||You were half right Lance. It is the case of the element but it's the MSDN
documentation that is wrong.
The element should read ReportServerExternalUrl not ReportServerExternalURL.
Thanks for pointing me in the right direction.
Nick
"Lance" <lancehunt@.gmail.com> wrote in message
news:1106665173.525554.327200@.z14g2000cwz.googlegroups.com...
> You may be modifiying the wrong Config file. This change should be
> made to the "RSWebApplication.config" file which is usually located at
> the following path:
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportManager
> The new node will go within the UI element, alongside the
> ReportServerUrl element. The value should be the fully-qualified
> domain name for the external address.
> <Configuration>
> <UI>
> <ReportServerUrl>http://localhost/ReportServer</ReportServerUrl>
> <ReportServerExternalURL>reports.adventure-works.com</ReportServerExternalURL>
> </UI>
> ...
>
> NOTE: Be careful because, all elements are case-sensitive and this one
> has "URL" capitalized instead of Pascal cased. Improper case can also
> cause this to fail.
> For more details, see MSDN:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0h9e.asp
> I hope this helps,
> Lance Hunt
> http://weblogs.asp.net/lhunt/
>|||Sorry about that. I usually test my suggestions locally before
posting, but I wasnt at my Dev PC when I posted that info. Now that
you mention it, I seem to recall this documentation mistake.
Regardless, I'm glad you worked it out.
Lance
http://weblogs.asp.net/lhunt/

RS Install killing me w/ 'NT AUTHORITY\ANONYMOUS LOGON' error

Hi - my config is as follows:
- RS Standard on Windows Server 2003 (server1)
- SQL Server 2000 for repository on a different server server2 (same domain)
- I am logged onto server1 as domain admin (full SQL perms to server2)
- I have successfully installed other RS repositories to server2 (different
db names of course)
Installation fails at the "Configuring Microsoft SQL Server" part with error
message: "SQL Setup failed to connect to the database service for server
configuration. The error was: Login failed for user 'NT Authority\Anonymous
Logon'. "
It appears to be losing my interactively logged on credentials.
Here is info from the log:
SQL_ERROR (-1) in SQLDriverConnectW
sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
user 'NT AUTHORITY\ANONYMOUS LOGON'.
Error 29545. SQL Setup failed to connect to the database service for server
configuration. The error was: Login failed for user 'NT AUTHORITY\ANONYMOUS
LOGON'.
Refer to the Server error logs and setup logs for more detailed information.
MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
Standard Edition -- Error 29545. SQL Setup failed to connect to the database
service for server configuration. The error was: Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'.
Refe
r to the Server error logs and setup logs for more detailed information.
--
Thoughts?
thanksHow are permissions configured for server2? I've had some problems in the
past connecting from a local machine account to a domain sql server
(configured with mixed security). I was attempting SQL authentication. It
started working when I changed the service to run with a domain user
identity rather than a local machine user; then it connected with SQL
authentication just fine. That was odd, because I expected SQL
authentication to work regardless of the windows login identity.
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"ISGADMIN" <isgadmin@.newsgroup.nospam> wrote in message
news:576C839C-156B-4648-B9D2-DE56EB7EA60A@.microsoft.com...
> Hi - my config is as follows:
> - RS Standard on Windows Server 2003 (server1)
> - SQL Server 2000 for repository on a different server server2 (same
> domain)
> - I am logged onto server1 as domain admin (full SQL perms to server2)
> - I have successfully installed other RS repositories to server2
> (different
> db names of course)
> Installation fails at the "Configuring Microsoft SQL Server" part with
> error
> message: "SQL Setup failed to connect to the database service for server
> configuration. The error was: Login failed for user 'NT
> Authority\Anonymous
> Logon'. "
> It appears to be losing my interactively logged on credentials.
> Here is info from the log:
> SQL_ERROR (-1) in SQLDriverConnectW
> sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
> user 'NT AUTHORITY\ANONYMOUS LOGON'.
> Error 29545. SQL Setup failed to connect to the database service for
> server
> configuration. The error was: Login failed for user 'NT
> AUTHORITY\ANONYMOUS
> LOGON'.
> Refer to the Server error logs and setup logs for more detailed
> information.
> MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
> Standard Edition -- Error 29545. SQL Setup failed to connect to the
> database
> service for server configuration. The error was: Login failed for user 'NT
> AUTHORITY\ANONYMOUS LOGON'.
> Refe
> r to the Server error logs and setup logs for more detailed information.
> --
> Thoughts?
> thanks|||Hi Jeff - Just to clarify my understanding of the installation process as a
baseline assumption so we're on the same page - it's the ID of the
interactively logged on user performing the install who the repository
database is created under.
Regarding permissions for server2, the user I am logged onto server1 as is
domainA\userA. This user is a domain admin and has full admin to server1 and
server2, as well as SQL Server on server2.
regards
"Jeff A. Stucker" wrote:
> How are permissions configured for server2? I've had some problems in the
> past connecting from a local machine account to a domain sql server
> (configured with mixed security). I was attempting SQL authentication. It
> started working when I changed the service to run with a domain user
> identity rather than a local machine user; then it connected with SQL
> authentication just fine. That was odd, because I expected SQL
> authentication to work regardless of the windows login identity.
> Cheers,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "ISGADMIN" <isgadmin@.newsgroup.nospam> wrote in message
> news:576C839C-156B-4648-B9D2-DE56EB7EA60A@.microsoft.com...
> > Hi - my config is as follows:
> >
> > - RS Standard on Windows Server 2003 (server1)
> > - SQL Server 2000 for repository on a different server server2 (same
> > domain)
> > - I am logged onto server1 as domain admin (full SQL perms to server2)
> > - I have successfully installed other RS repositories to server2
> > (different
> > db names of course)
> >
> > Installation fails at the "Configuring Microsoft SQL Server" part with
> > error
> > message: "SQL Setup failed to connect to the database service for server
> > configuration. The error was: Login failed for user 'NT
> > Authority\Anonymous
> > Logon'. "
> >
> > It appears to be losing my interactively logged on credentials.
> >
> > Here is info from the log:
> >
> > SQL_ERROR (-1) in SQLDriverConnectW
> > sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
> > user 'NT AUTHORITY\ANONYMOUS LOGON'.
> >
> > Error 29545. SQL Setup failed to connect to the database service for
> > server
> > configuration. The error was: Login failed for user 'NT
> > AUTHORITY\ANONYMOUS
> > LOGON'.
> > Refer to the Server error logs and setup logs for more detailed
> > information.
> > MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
> > Standard Edition -- Error 29545. SQL Setup failed to connect to the
> > database
> > service for server configuration. The error was: Login failed for user 'NT
> > AUTHORITY\ANONYMOUS LOGON'.
> > Refe
> > r to the Server error logs and setup logs for more detailed information.
> >
> > --
> >
> > Thoughts?
> > thanks
>
>|||I had the same problem when I installed RS yesterday. For some reason the
credentials are not passed correctly and I had to run the setup program from
the command line and explicitly pass it credentials with which to run the
setup program. The command to run setup ends up looking something like this:
setup /i "setup\rsrun.msi" RSSETUPACCOUNT=sa RSSETUPPASSWORD=sapwd
I've been told you can use any credentials you want (domain administrator,
etc.), but I just used the sql sa account, and that worked correctly.
I had the same problem when installing sp1. I had to manually extract the
.cab file and run setup from the command line once again:
sp1setup RSSETUPACCOUNT=sa RSSETUPPASSWORD=sapwd
Hope this helps.
David
"ISGADMIN" wrote:
> Hi - my config is as follows:
> - RS Standard on Windows Server 2003 (server1)
> - SQL Server 2000 for repository on a different server server2 (same domain)
> - I am logged onto server1 as domain admin (full SQL perms to server2)
> - I have successfully installed other RS repositories to server2 (different
> db names of course)
> Installation fails at the "Configuring Microsoft SQL Server" part with error
> message: "SQL Setup failed to connect to the database service for server
> configuration. The error was: Login failed for user 'NT Authority\Anonymous
> Logon'. "
> It appears to be losing my interactively logged on credentials.
> Here is info from the log:
> SQL_ERROR (-1) in SQLDriverConnectW
> sqlstate=28000, level=0, state=0, native_error=18456, msg=Login failed for
> user 'NT AUTHORITY\ANONYMOUS LOGON'.
> Error 29545. SQL Setup failed to connect to the database service for server
> configuration. The error was: Login failed for user 'NT AUTHORITY\ANONYMOUS
> LOGON'.
> Refer to the Server error logs and setup logs for more detailed information.
> MSI (s) (F0!E4): Product: Microsoft SQL Server 2000 Reporting Services
> Standard Edition -- Error 29545. SQL Setup failed to connect to the database
> service for server configuration. The error was: Login failed for user 'NT
> AUTHORITY\ANONYMOUS LOGON'.
> Refe
> r to the Server error logs and setup logs for more detailed information.
> --
> Thoughts?
> thanks|||> Installation fails at the "Configuring Microsoft SQL Server" part
with error
> message: "SQL Setup failed to connect to the database service for
server
> configuration. The error was: Login failed for user 'NT
Authority\Anonymous
> Logon'. "
>
Another fix for this - add the 'NT Authority\Anonymous Logon' account
as Local Admin on the SQL Server box and then be sure
Builtin\Administrators has SA access on the SQL Server.
Run the install and then change the dbowner to "sa" and remove the
account.
That's how I finally got it installed on a Win2003 box...
-Annette