|
Replies:
13
-
Pages:
1
-
Last Post:
Apr 28, 2005 3:53 AM
by: tlachev
|
|
|
Posts:
13
From:
Sydney
Registered:
12/7/04
|
|
|
|
Problem Loading Dataset Data Processing Extension
Posted:
Dec 7, 2004 4:35 AM
|
|
Dear Tao,
I just got my boss to go and buy your book, I need some help desperately. I really need to use datasets for my reports as I want to use my code generated .net database code that uses datasets. I have done all this before with crystal so I am finding this all rather frustrating. I easily did all that was required to compile and deploy your DPE, I could see it in the designer but I am not able to use it. When I try and use your dataset extension in the designer I get the error
"A connection can not be made to the database set and test the connection string"
The problem is that the DPE assembly is not being loaded as I am not able to debug Visual Studio .net with another Visual Studio .net ide. The debugger breakpoints are always ? marked.
Then when I try and run the DPE with a report that references a datasource that is a DPE I get the error shown below, again showing that the DPE could not be loaded as it was not registered correctly.
I have copied the DPE into the proper location in the
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\bin\AWC.RS.Extensions.dll
I have also used the ListExtensions function in the web service and I do not see the DPE there.
Any help at all greatly appreciated or we can pay you.
My boss wants to use reporting services.
NB I have also changed the security policy in the web.config for the ReportServer as explained by other people on the web. I also tried creating my own machine code group with the .net config tool and cut and pasted this into the rssvrpolicy.config file.
<httpRuntime executionTimeout = "9000" />
<securityPolicy>
<trustLevel name="AWCExtensionsCodeGroup" policyFile="rssrvpolicy.config" />
</securityPolicy>
Regards,
Alistair
General Information
*********************************************
Additional Info:
ExceptionManager.MachineName: WRWCSYDD005
ExceptionManager.TimeStamp: 7/12/2004 2:08:55 PM
ExceptionManager.FullName: Microsoft.ApplicationBlocks.ExceptionManagement, Version=1.0.1780.18926, Culture=neutral, PublicKeyToken=86de2ad39c4080c7
ExceptionManager.AppDomainName: Raywood.DTC.Cashering.exe
ExceptionManager.ThreadIdentity:
ExceptionManager.WindowsIdentity: RAYWOOD\arigney
1) Exception Information
*********************************************
Exception Type: Raywood.RaywoodException
Severity: Severe
MachineName: WRWCSYDD005
CreatedDateTime: 7/12/2004 2:08:55 PM
AppDomainName: Raywood.DTC.Cashering.exe
ThreadIdentityName:
WindowsIdentityName: RAYWOOD\arigney
Message: WriteReportAsPDF::Failed to write report '\TestReport.PDF' An error has occurred during report processing.
TargetSite: NULL
HelpLink: NULL
Source: NULL
2) Exception Information
*********************************************
Exception Type: System.Web.Services.Protocols.SoapException
Actor: http://localhost/ReportServer/ReportService.asmx
Code: http://schemas.xmlsoap.org/soap/envelope/:Client
Detail: System.Xml.XmlElement
Message: System.Web.Services.Protocols.SoapException: An error has occurred during report processing. ---> Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.Diagnostics.Utilities.DataExtensionNotFoundException: An attempt has been made to use a data extension 'DATASET' that is not registered for this report server.
at Microsoft.ReportingServices.ReportProcessing.s.a()
at Microsoft.ReportingServices.ReportProcessing.s.a(Object A_0)
--- End of inner exception stack trace ---
at Microsoft.ReportingServices.ReportProcessing.b.c()
at Microsoft.ReportingServices.ReportProcessing.z.af()
at Microsoft.ReportingServices.ReportProcessing.bb.a(ParameterInfoCollection A_0, Boolean A_1, GetReportChunk A_2)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.a(Report A_0, ProcessingContext A_1, Boolean A_2, GetReportChunk A_3, ax A_4, DateTime A_5, z& A_6)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(DateTime executionTimeStamp, GetReportChunk getCompiledDefinitionCallback, ProcessingContext pc, RenderingContext rc)
at Microsoft.ReportingServices.Library.RSService.RenderAsLive(CatalogItemContext reportContext, ItemProperties properties, ParameterInfoCollection effectiveParameters, Guid reportId, ClientRequest session, String description, ReportSnapshot intermediateSnapshot, DataSourceInfoCollection thisReportDataSources, Boolean cachingRequested, Warning[]& warnings, ReportSnapshot& resultSnapshotData, DateTime& executionDateTime, RuntimeDataSourceInfoCollection& alldataSources, UserProfileState& usedUserProfile)
at Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(CatalogItemContext reportContext, ClientRequest session, Warning[]& warnings, ParameterInfoCollection& effectiveParameters)
at Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext reportContext, ClientRequest session, Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]& secondaryStreamNames)
at Microsoft.ReportingServices.Library.RenderFirstCancelableStep.Execute()
at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
--- End of inner exception stack trace ---
at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
at Microsoft.ReportingServices.Library.RenderFirstCancelableStep.RenderFirst(RSService rs, CatalogItemContext reportContext, ClientRequest session, JobTypeEnum type, Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]& secondaryStreamNames)
at Microsoft.ReportingServices.WebServer.ReportingService.Render(String Report, String Format, String HistoryID, String DeviceInfo, ParameterValue[] Parameters, DataSourceCredentials[] Credentials, String ShowHideToggle, Byte[]& Result, String& Encoding, String& MimeType, ParameterValue[]& ParametersUsed, Warning[]& Warnings, String[]& StreamIds)
--- End of inner exception stack trace ---
at Microsoft.ReportingServices.WebServer.ReportingService.Render(String Report, String Format, String HistoryID, String DeviceInfo, ParameterValue[] Parameters, DataSourceCredentials[] Credentials, String ShowHideToggle, Byte[]& Result, String& Encoding, String& MimeType, ParameterValue[]& ParametersUsed, Warning[]& Warnings, String[]& StreamIds)
TargetSite: System.Object[] ReadResponse(System.Web.Services.Protocols.SoapClientMessage, System.Net.WebResponse, System.IO.Stream, Boolean)
HelpLink: NULL
Source: System.Web.Services
StackTrace Information
*********************************************
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Raywood.DTC.ReportUtilities.ReportService.ReportingService.Render(String Report, String Format, String HistoryID, String DeviceInfo, ParameterValue[] Parameters, DataSourceCredentials[] Credentials, String ShowHideToggle, String& Encoding, String& MimeType, ParameterValue[]& ParametersUsed, Warning[]& Warnings, String[]& StreamIds) in c:\windowsbase\dtcfleetmanager\raywood.dtc.reportutilities\web references\reportservice\reference.cs:line 653
at Raywood.DTC.ReportUtilities.ReportGenerator.GenerateReportAsPDF(String reportName, String sOutputPath, ParameterValue[] parameters) in c:\windowsbase\dtcfleetmanager\raywood.dtc.reportutilities\reportgenerator.cs:line 136
|
|
Posts:
687
From:
Atlanta, GA
Registered:
3/26/04
|
|
|
|
Re: Problem Loading Dataset Data Processing Extension
Posted:
Dec 7, 2004 8:34 PM
in response to:
Alistair
|
|
Copying the dll is one part of the game. Next, you need to register it in the rssrvpolicy.config file. See the sample cofiguration file I included in the books source code.
To debug the extension:
1. Add the custom dataset extension project to your Business Intelligence solution in Visual Studio.NET.
2. Set the StartItem setting of your Business Intelligence project to the name of the report which uses the extension.
3. Set breakpoints in the data extension code.
4. Run the report in Debug mode (F5). Once you press the ViewReport button, your breakpoints should be hit.
|
|
Posts:
13
From:
Sydney
Registered:
12/7/04
|
|
|
|
Re: Problem Loading Dataset Data Processing Extension
Posted:
Dec 8, 2004 9:59 AM
in response to:
tlachev
|
|
Thanks Heaps Tao,
Yes I know that I have to copy the dll and set the rssrvpolicy and rspreviewpolicy files. I am smelling that I am getting there but when I debug the report (as you specified) I get the error.
"Error while loading and setting security policy"
(Similar error as I get when I try and run a report as I showed you before).
The version of your sample code with the config files (I was using the version that did not have them).
does not have the CodeGroup for the AWCExtensionsCodeGroup.
The code group that you give in the documentation (repeated below ) is not in the rssrvpolicy file.
<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Name="AWCExtensionsCodeGroup">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url ="C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\bin\AWC.RS.Extensions.dll”/>
</CodeGroup>
Hence I have been trying with 3 attempts.
1. With the above entry only.
2. With the above entry and an entry (specifying a string name) as shown below
<CodeGroup class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Name="RaywoodReportingServices"
Description="">
<IMembershipCondition class="StrongNameMembershipCondition"
version="1"
PublicKeyBlob="0024000004800000940000000602000000240000525341310004000001000100FB44FB0506645FD9569AB319B5B2FEF19332EDE58C73246C043051190A58BEE6F107CB9C086423E90F88DE01233DBEC0C85899989501B44D3F614E0B4BBE3D56037FFCF8EA63973F548C9DA1E89ED805E0DF215F3674B8D8B57C29445F172D5BE2217994BC4467AB82541C2FACF2D5068793BBE81A7E01F366BAE11F79FB58AD"
Name="AWC.RS.Extensions"
AssemblyVersion="1.0.1801.31671"/>
</CodeGroup>
3. Just this CodeGroup with the strong name as shown above.
So do you need just the code group showing the dll location and/or the codegroup specifying the strong name.
I even tried removing the check for the assembly version but no luck.
All generate the same error.
I have spent so much time on this, should I have just read all the book first?
I also had to change the security policy setting in the web.config file from the default.
<securityPolicy>
<trustLevel name="RosettaSrv" policyFile="rssrvpolicy.config" />
</securityPolicy>
<trust level="RosettaSrv" originUrl="" />
To
<securityPolicy>
<trustLevel name="AWCExtensionsCodeGroup" policyFile="rssrvpolicy.config" />
</securityPolicy>
Otherwise you get a strong name exception problem.
Regards,
Alistair
|
|
Posts:
687
From:
Atlanta, GA
Registered:
3/26/04
|
|
|
|
Re: Problem Loading Dataset Data Processing Extension
Posted:
Dec 8, 2004 1:56 PM
in response to:
Alistair
|
|
Hi,
You need the following group only.
<CodeGroup class="UnionCodeGroup" version="1" PermissionSetName="FullTrust" Name="AWCExtensionsCodeGroup">
<IMembershipCondition class="UrlMembershipCondition" version="1" Url="C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\bin\AWC.RS.Extensions.dll"/>
</CodeGroup>
Please verify your setup again as per the setup instructions in the readme file. Many folks complain about setting the custom data extension, but at the end it always turns out to be a configuration issue.
|
|
Posts:
13
From:
Sydney
Registered:
12/7/04
|
|
|
|
Re: Problem Loading Dataset Data Processing Extension
Posted:
Dec 9, 2004 8:18 AM
in response to:
tlachev
|
|
Thanks Tao,
I finally got my extension to work (which had a new name and namespace etc) but could not get the AWC one to work.
But now I have another problem that the dataset fields are not appearing in list of fields for the dataset (in the report designer). I get the fields appearing along the bottom of the data source window ok (after I specify the schema using the datasource parameter).
I must have the path and file name correct as the fields are correct but they are not appearing in the designer list.
Looking forward to getting this right! so close.
Regards,
Alistair
|
|
Posts:
13
From:
Sydney
Registered:
12/7/04
|
|
|
|
Re: Problem Loading Dataset Data Processing Extension
Posted:
Dec 9, 2004 8:21 AM
in response to:
Alistair
|
|
Again Thanks Tao,
I found the problem, I just needed to hit the refresh button on the datasouce dataset and presto the fields are there!! Drag and drop is king.
Regards,
Alistair
|
|
Posts:
13
From:
Sydney
Registered:
12/7/04
|
|
|
|
Re: Problem Loading Dataset Data Processing Extension
Posted:
Apr 22, 2005 3:05 AM
in response to:
Alistair
|
|
Hi Again Tao,
Very sorry to bother you again but I had to rebuild my machine and now I am getting problems again running ReportingServices.
I am unable to browse to the http://localhost/ReportServer default page. I am getting the strong name error again, as shown here.
Security Exception
Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.
Exception Details: System.Security.SecurityException: Request for the permission of type System.Security.Permissions.StrongNameIdentityPermission, mscorlib, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 failed.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[SecurityException: Request for the permission of type System.Security.Permissions.StrongNameIdentityPermission, mscorlib, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 failed.]
Microsoft.ReportingServices.WebServer.Global..cctor() +0
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032
I have the ReportServer web.config file setup as shown here. I am using
<identity impersonate="true" userName="RAYWOOD\devtest" password="raywood" />
as the web service needs access to the ReportServer database as an SSI user.
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<configSections>
<section name="RStrace" type="Microsoft.ReportingServices.Diagnostics.RSTraceSectionHandler,Microsoft.ReportingServices.Diagnostics" />
</configSections>
<system.diagnostics>
<switches>
<!-- 1 = error, 2 = warning, 3 = info, 4 = verbose -->
<add name="DefaultTraceSwitch" value="3" />
</switches>
<assert assertuienabled="false" />
</system.diagnostics>
<RStrace>
<add name="FileName" value="ReportServer_" />
<add name="FileSizeLimitMb" value="32" />
<add name="KeepFilesForDays" value="14" />
<add name="Prefix" value="tid, time" />
<add name="TraceListeners" value="debugwindow, file" />
<add name="TraceFileMode" value="unique" />
<add name="Components" value="all,RunningJobs:3" />
</RStrace>
<system.web>
<authentication mode="Windows" />
<identity impersonate="true" userName="RAYWOOD\devtest" password="raywood" />
<compilation defaultLanguage="c#" debug="false">
<assemblies>
<clear />
<add assembly="ReportingServicesWebServer" />
</assemblies>
</compilation>
<trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true" />
<sessionState mode="Off" />
<httpHandlers>
<add verb="*" path="Reserved.ReportServer" type="Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler, ReportingServicesWebServer" />
</httpHandlers>
<httpModules></httpModules>
<globalization requestEncoding="utf-8" responseEncoding="utf-8" />
<httpRuntime executionTimeout = "9000" />
<securityPolicy>
<trustLevel name="RosettaSrv" policyFile="rssrvpolicy.config" />
</securityPolicy>
<trust level="RosettaSrv" originUrl="" />
</system.web>
</configuration>
I have the following entry in the ReportServer rssrvpolicy.config file
<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Name="RaywoodReportingServicesCodeGroup">
<IMembershipCondition
class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\bin\Raywood.DTC.ReportingServices.DataSetExtension.dll”
/>
</CodeGroup>
I also have added the following entry in the Data section of
the RSReportServer.config file
<Data>
....other extensions etc...
<Extension Name="DATASET" Type="Raywood.DTC.ReportingServices.DataSetExtension.DSXConnection,Raywood.DTC.ReportingServices.DataSetExtension"/>
</Data>
I have also strong named ALL my assemblies (but not my application assemblies) and I am still getting this error.
I have also given all the access to the folders by the devtest user that the ASP.NET user is impersonating.
I am really getting totally exasperated again. Admittedly I am a newbie to code access security.
Regards,
Alistair
|
|
Posts:
687
From:
Atlanta, GA
Registered:
3/26/04
|
|
|
|
Re: Problem Loading Dataset Data Processing Extension
Posted:
Apr 22, 2005 4:19 AM
in response to:
Alistair
|
|
Can you debug the extension at all or this happens when the extension is being loaded? You may want to name the assembly weakly-named and give it a try.
|
|
Posts:
13
From:
Sydney
Registered:
12/7/04
|
|
|
|
Re: Problem Loading Dataset Data Processing Extension
Posted:
Apr 22, 2005 9:27 AM
in response to:
tlachev
|
|
Good question mate, no I can't debug at all when I set the report as the startup object and click debug I get this error.
Regards,
Alistair
|
|
Posts:
13
From:
Sydney
Registered:
12/7/04
|
|
|
|
Re: Problem Loading Dataset Data Processing Extension
Posted:
Apr 22, 2005 9:29 AM
in response to:
Alistair
|
|
The assembly depends on a bunch of other assemblies as well, why do you want me to turn this off? Surely making all the assemblies strongly named means that I should be less likely to have problems?
Regards,
Alistair
|
|
Posts:
687
From:
Atlanta, GA
Registered:
3/26/04
|
|
|
|
Re: Problem Loading Dataset Data Processing Extension
Posted:
Apr 23, 2005 2:46 AM
in response to:
Alistair
|
|
I "think" a strong-named assembly must be marked as AllowPartiallyTrustedCode (or similar attribute) to allow weakly named assemblies to call it.
For the sake of trying open the C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\rssrvpolicy.config and locate the following element:
<CodeGroup
class="FirstMatchCodeGroup"
version="1"
PermissionSetName="Execution"
Description="This code group grants MyComputer code Execution permission. ">
<IMembershipCondition
class="ZoneMembershipCondition"
version="1"
Zone="MyComputer" />
Change PermissionSetName to FullTrust and see if it works.
|
|
Posts:
13
From:
Sydney
Registered:
12/7/04
|
|
|
|
Re: Problem Loading Dataset Data Processing Extension
Posted:
Apr 26, 2005 2:48 AM
in response to:
tlachev
|
|
Thanks Teo,
Yes I am using the FullTrust attribute as you suggest, I am looking into the AllowPartiallyTrusted code. We had a holiday yesterday.
Regards,
Alistair
|
|
Posts:
13
From:
Sydney
Registered:
12/7/04
|
|
|
|
Re: Problem Loading Dataset Data Processing Extension
Posted:
Apr 26, 2005 3:28 AM
in response to:
Alistair
|
|
Hi Teo,
I found this paper in the MSDN that tells me what what you were saying about having to set full trust or
i.e to use strongly named assemblies in ReportingServices
do either 1 or 2.
1. Allow your strong-named assembly to be called by partially trusted code using the assembly attribute
2. AllowPartiallyTrustedCallersAttribute.
Grant FullTrust security permission to report expressions in Reporting Services.
Except I can't find any mention of ReportExpressions in the .config files which is what I have to add or change.
Regards,
Alistair
Reporting Services - Reporting Services Programming
Using Strong-Named Assemblies
A strong name is made up of information used to identify an assembly and includes the assembly's text name, four-part version number, culture information (if provided), a public key, and a digital signature stored in the assembly's manifest.
Strong names provide unique identification of an assembly to the common language runtime (CLR). In addition, adding a strong name ensures binary integrity. By default, strong-named custom assemblies are not supported in Reporting Services. In order for your strong-named custom assembly to function properly in Reporting Services, you must do one of the following:
Allow your strong-named assembly to be called by partially trusted code using the assembly attribute AllowPartiallyTrustedCallersAttribute.
Grant FullTrust security permission to report expressions in Reporting Services.
Using the AllowPartiallyTrustedCallersAttribute
You can use the AllowPartiallyTrustedCallersAttribute to allow strong-named assemblies to be called by Report Designer or the report server in report expressions. If a custom assembly that you or a third-party create is strong-named, using the AllowPartiallyTrustedCallersAttribute is the recommended way in which strong-named assemblies can be incorporated into your reports.
Security Note Before deploying an assembly that contains the AllowPartiallyTrustedCallersAttribute to your report server, you should review what operations and resources its public members can access. Always perform a security review before deploying custom assemblies to your report server.
To allow strong-named assemblies to be called by partially trusted code
In your assembly attribute file, add the following assembly-level attribute:
[Visual Basic]
<assembly:AllowPartiallyTrustedCallers>
[C#]
[assembly:AllowPartiallyTrustedCallers]
AllowPartiallyTrustedCallersAttribute is only effective when applied by a strong-named assembly at the assembly level. For more information about applying attributes at the assembly level, see "Applying Attributes" in the Microsoft .NET Framework SDK documentation.
Caution The presence of this assembly-level attribute prevents the default behavior of placing FullTrust LinkDemand security checks, making the assembly callable from any other partially trusted assembly.
When the AllowPartiallyTrustedCallersAttribute is present, all other security checks function as intended, including any class-level or method-level declarative security attributes that are present. This attribute blocks only the implicit fully trusted caller demand.
Using the FullTrust Permission Set
You can give full trust to report expressions to enable strong-named custom assemblies in Reporting Services. You should not use this method of granting access to strong-named custom assemblies unless you are sure that all of the strong-named assemblies that you or third-parties create and all embedded report code should run as fully trusted. Granting full trust to report expressions gives full trust to all possible code that is executed in a report including custom assembly and embedded code. If this is a concern, it is highly recommended that you use the AllowPartiallyTrustedCallersAttribute on an assembly-by-assembly basis. For more information about embedded code, see Writing Custom Code.
To grant the FullTrust permission set to report expressions
Open the configuration files RSReportServer.config and RSReportDesigner.config in Visual Studio .NET or a simple text editor. The default location of RSReportServer.config is C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer. The default location of RSReportDesigner.config is C:\Program Files\Microsoft SQL Server\80\Tools\Report Designer.
Replace the ReportExpressions element in the configuration files with the following entry:
<ReportExpressions>
<PermissionSet class="System.Security.NamedPermissionSet"
version="1"
Unrestricted="true"
Name="FullTrust"
Description="Allows full access to all resources"/>
</ReportExpressions>
See Also
Using Custom Assemblies with Reports
©1988-2004 Microsoft Corporation. All Rights Reserved.
|
|
Posts:
687
From:
Atlanta, GA
Registered:
3/26/04
|
|
|
|
Re: Problem Loading Dataset Data Processing Extension
Posted:
Apr 28, 2005 3:53 AM
in response to:
Alistair
|
|
I think this should be where Execution needs to be replaced with FullTrust.
<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="Execution"
Name="Report_Expressions_Default_Permissions"
Description="This code group grants default permissions for code in report expressions and Code element. ">
<IMembershipCondition
class="StrongNameMembershipCondition"
version="1"
PublicKeyBlob="0024000004800000940000000602000000240000525341310004000001000100512C8E872E28569E733BCB123794DAB55111A0570B3B3D4DE3794153DEA5EFB7C3FEA9F2D8236CFF320C4FD0EAD5F677880BF6C181F296C751C5F6E65B04D3834C02F792FEE0FE452915D44AFE74A0C27E0D8E4B8D04EC52A8E281E01FF47E7D694E6C7275A09AFCBFD8CC82705A06B20FD6EF61EBBA6873E29C8C0F2CAEDDA2"
/>
</CodeGroup>
|
|
|
Legend
|
|
Gold: 300
+
pts
|
|
Silver: 100
- 299
pts
|
|
Bronze: 25
- 99
pts
|
|
Manning Author
|
|
Manning Staff
|
|
