<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rss/1.0/modules/syndication/" xmlns:dc="https://purl.org/dc/elements/1.1/" xmlns:content="https://purl.org/rss/1.0/modules/content/" xmlns:wfw="https://wellformedweb.org/CommentAPI/" xmlns:slash="https://purl.org/rss/1.0/modules/slash/"
  version="2.0">
  <channel>
    <title>Chris's SQL Developer Support Blog</title>
    <atom:link
      href="https://docs.microsoft.com/archive/blogs/calton/feed.xml"
      rel="self"
      type="application/rss+xml" />
    <link>https://docs.microsoft.com/archive/blogs/calton/feed.xml</link>
    <description>Intermittent posts regarding SQL Developer Support topics focusing on Reporting Services and SharePoint integration.</description>
    <lastBuildDate>Wed, 17 Apr 2019 03:41:27 GMT</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>Reporting Services Integration with SharePoint Troubleshooting white paper</title>
      <link>https://docs.microsoft.com/archive/blogs/calton/reporting-services-integration-with-sharepoint-troubleshooting-white-paper</link>
      <pubDate>Thu, 20 Aug 2009 09:50:00 GMT</pubDate>
      <dc:creator><![CDATA[calton]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/calton/2009/08/20/reporting-services-integration-with-sharepoint-troubleshooting-white-paper/</guid>
      <description><![CDATA[After an extremely long time I have finished my white paper on troubleshooting the Reporting...]]></description>
      <content:encoded><![CDATA[<P>After an extremely long time I have finished my white paper on troubleshooting the Reporting Services integration with SharePoint. It details almost all of the problems I have seen when working on these types of cases and will hopefully help you resolve the issues you have getting it configured.</P>
<P>&nbsp;You can find the article here:</P>
<P><A href="https://msdn.microsoft.com/en-us/library/ee384252.aspx">https://msdn.microsoft.com/en-us/library/ee384252.aspx</A></P>]]></content:encoded>
    </item>
    <item>
      <title>How to fix the error "Value does not fall within expected range" from SRS Integration with SharePoint</title>
      <link>https://docs.microsoft.com/archive/blogs/calton/how-to-fix-the-error-value-does-not-fall-within-expected-range-from-srs-integration-with-sharepoint</link>
      <pubDate>Sat, 09 May 2009 18:59:00 GMT</pubDate>
      <dc:creator><![CDATA[calton]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/calton/2009/05/09/how-to-fix-the-error-value-does-not-fall-within-expected-range-from-srs-integration-with-sharepoint/</guid>
      <description><![CDATA[I have written a tool that will help you fix the following error you can receive&nbsp;from Central...]]></description>
      <content:encoded><![CDATA[<P>I have written a tool that will help you fix the following error you can receive&nbsp;from Central Administration-&gt;Application Management-&gt;Reporting Services (section header)-&gt;Set Server Defaults.&nbsp;This tool is only meant to fix the error when you receive it from this location. If you receive this error when clicking on a report or other Reporting Services item in a Document Library this is caused when the report item location and the URL you are accessing the SharePoint site by differ. To resolve that issue you will need to either delete and redeploy your reports, change the public URL of the site back to what it was when you deployed the reports or access the SharePoint site using the same URL you used when you deployed the report.</P>
<P>The error from&nbsp;"Set Server Defaults"&nbsp;will usually look like this:</P>
<P class=MsoNormal style="MARGIN: 0in 0in 10pt"><FONT face=Calibri size=3>“</FONT><FONT size=3><FONT face=Calibri><B style="mso-bidi-font-weight: normal">System.Web.Services.Protocols.SoapException: An internal error occurred on the <BR>report server. See the error log for more details.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>---&gt; Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An <BR>internal error occurred on the report server. See the error log for more details.<BR>---&gt; System.ArgumentException: <SPAN style="mso-bidi-font-weight: bold">Value does not fall within the expected range</SPAN></B>."</FONT></FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 10pt"><U>Cause:</U></P>
<P class=MsoNormal style="MARGIN: 0in 0in 10pt">This is can be caused by the following things:</P>
<P class=MsoNormal style="MARGIN: 0in 0in 10pt">1. You have more than one WFE that has the Central Administration role and the server that currently has that role is not the first one in the list of Central Admin servers.</P>
<P class=MsoNormal style="MARGIN: 0in 0in 10pt">2. You have moved the Central Administration&nbsp;URL (different port etc) after it was created.</P>
<P class=MsoNormal style="MARGIN: 0in 0in 10pt"><U>Resolution:</U></P>
<P class=MsoNormal style="MARGIN: 0in 0in 10pt">1. Give only one server in the farm the Central Administration role rather than multiple. This alone may not resolve the issue since the Central Administration URL might not be removed correctly from the SharePoint database object. If it does not use the resolution for #2 below.</P>
<P class=MsoNormal style="MARGIN: 0in 0in 10pt">2. Use the tool attached to this blog post. The instructions on how to use it are included in the .zip file.</P>
<p><a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Components.PostAttachments/00/09/59/97/55/SharePointTool.zip" original-url="https://blogs.msdn.com/cfs-file.ashx/__key/communityserver-components-postattachments/00-09-59-97-55/SharePointTool.zip">SharePointTool.zip</a></p>]]></content:encoded>
    </item>
  </channel>
</rss>