Repost: Security level already for "RosettaMgr"

As an MSDN subscriber, I though I was supposed to get a guaranteed response
here. I am reposting this since no one responded to my 1st inquiry.
Out of the blue this morning our Report Server stopped working with the
following error:
Configuration Error
...
Parser Error Message: Security Level already defined for RosettaMgr
Source Error:
Line 22: <securityPolicy>
Line 23: <trustlevel name="RosettaMgr"
policyFile="rsmgrpolicy.config" />
Line 24: </securityPolicy>
line 24: <trust level="RosettaMgr" originUrl="" />
Removing the offending lines from web.config resolved the problem but I'm
unclear why this happened suddenly. I'm also leery of removing these
settings without fully understanding the implications. If anyone has any
insight as to the cause of this error or can intelligently explain the
<securityPolicy> and <trust level> settings I sure would appreciate a little
feedback.
Thanks,
Rich BakosHi Rich,
Sorry that you're encountering trouble. Not sure where your expectation was
set regarding guaranteed response If you could let me know that would be
very helpful. AFAIK, MS doesn't guarantee responses on this newsgroup -
you're actually talking with many folks on the product team directly. Though
we'd love to answer all questions, we're also trying to ship an awesome
product as part of SQL Server 2005. I'm sure you understand our quandry
:-).
Now your question:
Report Manager ships with a default security group called RosettaMgr.
Removing this line is not desired. The relevant section of the file reads:
<securityPolicy>
<trustLevel name="RosettaMgr" policyFile="rsmgrpolicy.config"/>
</securityPolicy>
<trust level="RosettaMgr" originUrl=""/>
What this line does is it ensure that the report manager loads code, that it
assigns the code the correct permission defined in the rsmgrpolicy.config
file.
This is a shot in the dark but the web.config file included with an
application follows a hierarchy based on other web.config files that come
before it. You can read up on this here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/secmod/html/secmod92.asp
Are you running another application that also uses ASP.Net on the same
server? Has any web.config changed on your server shortly before your
application started to fail?
One other questions - did you move/copy the report manager virtual
directory?
-Lukasz
"Richard Bakos" <bakos@.nospam.nospam> wrote in message
news:%23PAol8DGFHA.444@.TK2MSFTNGP15.phx.gbl...
> As an MSDN subscriber, I though I was supposed to get a guaranteed
> response
> here. I am reposting this since no one responded to my 1st inquiry.
> Out of the blue this morning our Report Server stopped working with the
> following error:
> Configuration Error
> ...
> Parser Error Message: Security Level already defined for RosettaMgr
>
> Source Error:
> Line 22: <securityPolicy>
> Line 23: <trustlevel name="RosettaMgr"
> policyFile="rsmgrpolicy.config" />
> Line 24: </securityPolicy>
> line 24: <trust level="RosettaMgr" originUrl="" />
> Removing the offending lines from web.config resolved the problem but I'm
> unclear why this happened suddenly. I'm also leery of removing these
> settings without fully understanding the implications. If anyone has any
> insight as to the cause of this error or can intelligently explain the
> <securityPolicy> and <trust level> settings I sure would appreciate a
> little
> feedback.
> Thanks,
> Rich Bakos
>
>|||Lukasz Pawlowski [MSFT] wrote:
Hi Lukasz.
Thanks for you response.
> Sorry that you're encountering trouble. Not sure where your
> expectation was set regarding guaranteed response If you could let
> me know that would be very helpful.
My mistake, the page says a "commitment" to respond rather than a guarantee.
http://msdn.microsoft.com/newsgroups/managed/
> <securityPolicy>
> <trustLevel name="RosettaMgr" policyFile="rsmgrpolicy.config"/>
> </securityPolicy>
> <trust level="RosettaMgr" originUrl=""/>
Yes. Those are the offending lines and the server will not run with those
elements defined. To add to the problem, we can not move reports to
different folders or update definitions since removing the offending
elements. Everything else appears to work correctly.
Here is the exact text of the error:
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.
Parser Error Message: Security level already defined for 'RosettaMgr'.
Source Error:
Line 21: <httpRuntime executionTimeout="9000"/>
Line 22: <securityPolicy>
Line 23: <trustLevel name="RosettaMgr" policyFile="rsmgrpolicy.config"/>
Line 24: </securityPolicy>
Line 25: <trust level="RosettaMgr" originUrl=""/>
Source File: C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager\web.config Line: 23
----
Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
Version:1.1.4322.573
> What this line does is it ensure that the report manager loads code,
> that it assigns the code the correct permission defined in the
> rsmgrpolicy.config file.
Thanks for the explaination but this doesn't explain why I'm getting a parse
error complaining that a Security level is already defined. My web.config
files had not been changed until the day I removed the offending elements.
> Are you running another application that also uses ASP.Net on the same
> server?
No. However, the web.config for the report server also contains the elements
sin question.
>Has any web.config changed on your server shortly before
> your application started to fail?
No.
> One other questions - did you move/copy the report manager virtual
> directory?
No.
Any other insight you might have certainly would be helpful.
Thanks,
Rich Bakos|||Richard Bakos wrote:
> No. However, the web.config for the report server also contains the
> elements sin question.
My mistake. The element definitions are not identical. Once defines
RosettaMgr while the other defines RosettaSrv.
Rich|||The solution to your problem is to install the ASP.Net hotfix for a
canonicalization issue. You can do this from the following KB article:
http://support.microsoft.com/kb/887787
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Richard Bakos" <bakos@.nospam.nospam> wrote in message
news:uYe6DZKGFHA.560@.TK2MSFTNGP15.phx.gbl...
> Richard Bakos wrote:
>> No. However, the web.config for the report server also contains the
>> elements sin question.
> My mistake. The element definitions are not identical. Once defines
> RosettaMgr while the other defines RosettaSrv.
> Rich
>|||Lukasz Pawlowski [MSFT] wrote:
Hi Lukasz,
> The solution to your problem is to install the ASP.Net hotfix for a
> canonicalization issue. You can do this from the following KB
> article:
That made no difference. The problem still exists.
Rich Bakos