SQL Reporting Services App

Hi,
I have successfully (I think!) configured SQL Server Reporting Services on my SharePoint 2013 Enterprise farm. However, when I create a new app of type Report Library as /Reports, it succeeds, but when I navigate to it through the quick link on the left
(/Reports/Forms/current.aspx), it fails because the file does not exist. It does work, however, by navigating to /Reports, it shows a Reporting Services-style user interface, not the usual UI that I would expect from SharePoint.
Is this a known problem, or is it OK? Anything I can do about it - except, of course, change the quick link URL?
Thanks!
RP

Hi  ,
For your issue, it can be caused by that the URL
http://ServerName/Reports/Pages/Folder.aspx 
is the Report Manager URL. As you named the Report Library “Reports”, its path is conflict with Report Manager default Virtual Directory “Reports”. You can go to Reporting Services Configuration Manager -> Report Manager URL to verify it:
You can delete the Report Library “Reports” and recreate a new Report Library (such as “My Reports”, not name it “Reports”).
Reference:http://www.codeproject.com/Articles/88285/Integrating-Sharepoint-and-SQL-Reporting-Serv
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Eric Tao
TechNet Community Support

Similar Messages

  • Workflows 2013 and SQL Report Services: Configure on Independent Servers or Existing App Servers?

    Currently, my SharePoint 2013 Farm has Workflows 2013 and SQL Report Services installed on app servers, along with other applications. Workflows 2013 isn't working correctly (installed prior to my coming on board with the organization), I'm assuming it
    is a configuration issue, but rather than re-configure, I've read that is recommended to be a standalone server. It was also recommended by a MSFT rep that our report services have its own independent server. Currently, Report Services is also installed on
    an app server that runs other applications on the farm.
    Has anyone had any experience with installing Workflows 2013 and/or SQL Report Services on independent vs. existing application servers?
    Additionally, my existing application servers have 24 GB of RAM (I believe the recommendation for SharePoint production environments is 12 GB), should I plan for the potentially new servers (Workflows and Report Services) to also have 24 GB of RAM? Not really
    sure if it will be needed if they have dedicated tasks.
    Thanks for any input you can provide!

    It entirely depends on load. WFM will work just fine installed on servers in the SharePoint farm. SSRS preferably should go on the end-user facing servers for better performance.
    The questions you're asking are all "it depends" :)
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Installed SQL Reporting Services 2012 on SharePoint 2013 Server. SQL Reporting Service not available In the list of runnning services or new service applications

    Hi I'm trying to setup SQL reporting services in a SharePoint 2013 farm consisting of:
    4 WFE's
    4 App Servers (NLB Central Admin x 4 servers)
    4 App Severs for SSRS (Light limited SharePoint services running)
    I've installed SSRS 2012 SP1 by following the guide (http://msdn.microsoft.com/en-us/library/gg492276.aspx) on one of the SSRS SharePoint 2013 servers and ensuring Reporting Services - SharePoint and Reporting Services Add-in for SharePoint Products is selected.
    All completed without errors and I have even upgraded to SP2 for troubleshooting but no joy.
    I've then gone into SharePoint Central Admin and I cannot see SQL Reporting Service available In the list of runnning services on the server I have just installed SSRS on and going to manage service applications I cannot see in the new dropdown menu SQL
    Reporting Services.
    I have ran the following commands in the SHarePoint management shell:
    Install-SPRSService and Install-SPRSSeviceProxy
    and
    get-spserviceinstance -all |where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance
    The reply was that the service was already online on the server.
    So in powershell all seems ok but it does not appear in central administration.
    I have also moved Central Administration to the SSRS SharePoint server too.
    Any other suggestions? Here is the same problem but in SP2010 (http://social.technet.microsoft.com/Forums/office/en-US/6a21cc05-1f9b-49ad-a9bb-44aa5b3ce312/action?threadDisplayName=after-installing-sql-reporting-services-service-for-sharepoint-2012-service-is-not-in-the-list-of)
    In my lab environment of a 4 server SP2013 farm it worked immediately when i installed it on the app server (CA host) so I dont think it is my install strategy.
    I guess my next attempt is to install SSRS on an app server with central administration hosted.
    Thanks

    I had the same issue on 2 different environments.
    I had 2 application servers. One had Central Administration. I installed SSRS on the other one and it never appeared in the Service Applications in SharePoint.
    When I also provisioned Central Administration on the other application server and went to the service applications using Central Admin on that server, the SSRS service application was there.
    Since then I always install SSRS on the server which hosts Central Admin. No issues then.

  • Sql reporting services stops every 24 hours for a short time then restarts

    I have noticed that recently in sccm 2012 sp1 the sql reporting services stops every morning at 7:58 am and restarts after a minute or two.  The only entry in the event logs is when it stops.  I don't see anything tied in with it that stops or
    starts at the same time and there are no tasks or anything like that which would point to this time frame.  I just thought I would throw this out there to see if anyone had any ideas.  Usually with something of this nature there are some corresponding
    log entries that go beyond the service stopping, but in this case there isn't.  Thanks for any help you can provide.

    I think I found out what was going on.  I approached this from a different angle and was directed to the sql reporting services logs and found information on the reporting web server stopping.  Researching that yielded the following information. 
    It appears that this is a result of the SSRS Web Server recycling the App Domain, which is supposed to be a pretty normal process.  In fact, the configuration file for this process defaults to recycling the app domain twice daily.  This lines up
    with the time frame that the reporting service is stopping.  It restarts it in less that two minutes and logs the recyling in the reporting services log twice daily so why I'm not seeing this entry in the event logs twice daily or even every day must
    be a timing thing.  I think if it takes an extra millisecond or two to recycle the app domain, it dumps an entry into the windows event logs and the sccm component status monitoring.
    http://ask.sqlservercentral.com/questions/97176/reporting-web-server-stopped.html

  • Sharepoint SQL Reporting Services Add-In

    Hi,
    I have installed the Sharepoint SQL reporting services Add-in in one of my application servers and when I call the sites created from the application server itself they show the add-in feature in them in the "site features "list. But when I call
    the same site from a WFE in the farm with no add-in installed the the site doesn't show the add-in feature in the "site Feature" list.
    This is not supposed to happen as I have tried the same in another farm and the add-in was needed to be installed only in the application server and it would automatically be shown in sites even when they are called from a WFE or anywhere.

    SSRS in SharePoint Integrated mode requires the installation of two components.  SSRS in SharePoint Integrated mode only needs to be installed on one App server.  But the SSRS SharePoint Add-in needs to be installed on all the WFEs and the app
    server where SSRS in SharePoint Integrated mode is installed.  Not sure how you got it to work in the other farm.  Take a look at the following article:
    https://msdn.microsoft.com/en-us/library/hh479775.aspx
    You will note in the diagram that the Add-in is installed on each WFE.
    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

  • How to Convert MM/DD/YYYY to YYYY/MM/DD in SQL Reporting Services

    i am having difficulty of converting a parameter field, called @startdate, on sql reporting services report to YYYY/MM/DD format.  the parameter @Startdate was set to Data/Time.  @Startdate is 6/1/2014 12:00:00 and I want to convert it
    to 2014/06/01.  I want to compare @Startdate with a column in database called Begindate which is in format of YYYY/MM/DD hh:mm:ss.  I tried the followings
    select * from Atable where cast(Atable.Begindate as date) >= cast(@Startdate as date)
    select * from Atable where cast(Atable.Begindate as date >= cast(convert(datetime, @Startdate) as date)
    SQL Reporting Services only gives me Text, Boolean, Date/Time, Integer and Float.
    Regards,

    Hi Elmucho,
    Sorry for the delay. I tested with the sample data you provided, however everything works well in-house. Could you please creste a new report and check the result. Here are the steps I performed:
    1.  Create a table and insert the following data:
    Name (varchar(50))    Begindate (datetime, not null)    
    Lastdate (datetime, not null)
    bob                          
    2008-01-01 08:08:08.000      2010-10-10  
    10:10:10.000
    alice                         
    2010-10-10 10:10:10.00       2011-11-11
      11:11:11.000
    smith                       
    2011-11-11 11:11:11.00       2012-12-12   
    12:12:12.000    
    2. Open SQL Server Data Tools, create the data source and add the dataset with the below query:
    SELECT     Name, Begindate, Lastdate
    FROM         [tablename ]
    WHERE     (CAST(Begindate AS date) >= CAST(@Startdate AS date)) AND (CAST(Lastdate AS date) <= CAST(@Enddate AS date))
    3. Then, click execute button, it prompts for inputting the parameter value.
    @Startdate        
    6/1/2008
    @Enddate          
    5/1/2014
    Enter the date and press OK.
    4. Here is the result in the query designer:
    Insert a table and fields. Save the report and preview:
    Thanks.
    Tracy Cai
    TechNet Community Support

  • Upgrade 2010 to 2013 with SQL Reporting Services

    I'm getting ready to upgrade to 2013.
    When I run the Test-SPContentDatabase I get:
    Category : MissingWebPart
    Error : True
    UpgradeBlocking : False
    Message : WebPart class [ab6d9dad-e23c-ce4f-ff98-f6575a1ccf4c] (class [
    Microsoft.ReportingServices.SharePoint.UI.WebParts.ReportView
    erWebPart] from assembly
    [Microsoft.ReportingServices.SharePoint.UI.WebParts,
    Version=10.0.0.0, Culture=neutral,
    PublicKeyToken=89845dcd8080cc91]) is referenced [24] times
    in the database [is-sharepoint], but is not installed on the
    current farm. Please install any feature/solution which
    contains this web part.
    Remedy : One or more web parts are referenced in the database
    [is-sharepoint], but are not installed on the current farm.
    Please install any feature or solution which contains these
    web parts.
    Locations :
    Category : MissingAssembly
    Error : True
    UpgradeBlocking : False
    Message : Assembly
    [Microsoft.ReportingServices.SharePoint.UI.ServerPages,
    Version=10.50.0.0, Culture=neutral,
    PublicKeyToken=89845dcd8080cc91] is referenced in the
    database [is-sharepoint], but is not installed on the
    current farm. Please install any feature/solution which
    contains this assembly.
    Remedy : One or more assemblies are referenced in the database
    [is-sharepoint], but are not installed on the current farm.
    Please install any feature or solution which contains these
    assemblies.
    Locations :
    Category : Configuration
    Error : False
    UpgradeBlocking : False
    Message : The [is.photomask.com] web application is configured with
    claims authentication mode however the content database you
    are trying to attach is intended to be used against a
    windows classic authentication mode.
    Remedy : There is an inconsistency between the authentication mode of
    target web application and the source web application.
    Ensure that the authentication mode setting in upgraded web
    application is the same as what you had in previous
    SharePoint 2010 web application. Refer to the link
    "http://go.microsoft.com/fwlink/?LinkId=236865" for more
    information.
    Locations :
    The first two have to do with reporting services.  I'm trying to workout how to go about getting these errors to go away.  I don't want to remove SQL reporting or migrate a broken site and fix it later.  FYI it does migrate but reporting services
    is of course broken.
    So what I was wanting to do was to upgrade SQL Reporting Services for SharePoint 2010 from 2008 SQL to 2014 SQL first.  This would be in the hopes that it would make the migration to SharePoint 2013 work as the assemblies would change to the proper
    version.
    Can anyone elaborate on my upgrade path?
    I'm still looking up the "Claims Based" authentication thing.  I've found an article on how to migrate it so not a big deal.  I do wonder however if this is tied to the issue I saw with default.aspx and home.aspx being denied to all users
    after I did migrate a content db.
    David Jenkins

    Hi David,
    The following sections describe the basic steps needed to upgrade or migrate from 2008 versions of Reporting Services SharePoint mode to 2014 version.
    SQL Server 2008 R2 to SQL Server 2014
    Starting environment: SQL Server 2008 R2, SharePoint 2010.
    Ending environment: SQL Server 2014, SharePoint 2010.
    In-place upgrade is supported and there is no down time for your SharePoint environment.
    Install the SQL Server 2014 version of the Reporting Services add-in for SharePoint on each web front-end in the farm. You can install the add-in by using the SQL Server 2014 installation wizard or by downloading the add-in.
    Run SQL Server 2014 installation to upgrade SharePoint mode for each “report server”. The SQL Server installation wizard will install the Reporting Services Service and create a new Service application.
    If you also want the ending environment to run SharePoint 2013, you need to complete a database-attach upgrade of the SharePoint 2010 to SharePoint 2013.
    For more scenarios information, please refer to:
    http://msdn.microsoft.com/en-us/library/ms143747.aspx#bkmk_sharePoint_scenarios
    Per the supported combinations of SharePoint and Reported Services Components, I’d recommend you firstly upgrade Reporting Services to 2014, then upgrade SharePoint to 2013.
    For more information:
    http://msdn.microsoft.com/en-us/library/gg492257.aspx
    The link below is the reference for migrating a Reporting Services:
    http://msdn.microsoft.com/en-us/library/hh759331.aspx
    Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected] .
    Rebecca Tu
    TechNet Community Support

  • FQDN or NetBIOS for SQL Reporting Services Point installation in a cluster

    Hi Folks
    We have a SQL cluster for config mgr database & SQL reporting services installed on nodes because it is not cluster aware. During SCCM 2012 installation, we mentioned the details of SQL cluster only & it got installed successfully. When we checked
    in console, it is showing 3 site servers  related to SQL. SQL cluster is having site system role only & site database role moved under 2 nodes. Only NetBIOS names of the SQL nodes are being displayed in console.
    Now when I installed reporting service point role by selecting one of the node, wizard picks the FQDN of this node automatically & role installed successfully.
    Now in the console, I have another site server listed publishing the FQDN of the same node which I selected during installation which means one SQL node (site database role present at this) is displaying with NetBIOS name & the same SQL node
    (reporting services point role at this) is displaying with FQDN.
    My concerns is that - 
    Is there any issue if same SQL node displaying 2 times in SCCM console i.e. with NetBIOS name & with FQDN name?
    Why reporting services point role not placed under the node which is already there with NetBIOS name?
    I hope I explained my issue properly however If you guys need any more information regarding this, then let me know. 
    Cheers | Navdeep Sidhu

    This is the default behavior when installing site DB on cluster - all nodes will be visible as NetBIOS.
    I face a problem in two separate environments with SQL cluster when configuring Auto client push for servers, you will get the following error message in CCM.log in site server:
    SQL Server Native Client 11.0][SQL Server]Invalid length parameter passed to the LEFT or SUBSTRING function. : sp_CP_CheckNewAssignedMachine
    AND
    Failed to execute SQL cmd exec [sp_CP_CheckNewAssignedMachine]
    I believe this is a bug in the product.
    There is a workaround FIX editing the SP in SQL DB but it is UNSUPPORTED.
     

  • Service Manager data warehouse SQL Reporting Services server is currently unavailable

    I keep getting this error when I launch my SCSM Console. Take a look at the event log > operation manager and saw this error message below. 
    Tried to google around but unable to find any solution to it. Anybody can enlighten me on this issue that I am encountering? Thanks
    Cannot connect to SQL Reporting Services Server. Message= An unexpected error occured while connecting to SQL Reporting Services server: System.Net.WebException: The request failed with HTTP status 404: Not Found.
    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 Microsoft.EnterpriseManagement.Reporting.ReportingService.ReportingService2005.FindItems(String Folder, BooleanOperatorEnum BooleanOperator, SearchCondition[] Conditions)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.FindItems(String searchPath, IList`1 criteria, Boolean And)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.FindItems(String itemPath)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.FindItem(String itemPath, ItemTypeEnum[] desiredTypes)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.GetFolder(String path)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReportingGroup.Initialize()
    at Microsoft.EnterpriseManagement.Reporting.ServiceManagerReportingGroup..ctor(DataWarehouseManagementGroup managementGroup, String reportingServerURL, String reportsFolderPath, NetworkCredential credentials)
    at Microsoft.EnterpriseManagement.Reporting.ServiceManagerReportingGroup..ctor(DataWarehouseManagementGroup managementGroup, String reportingServerURL, String reportsFolderPath)
    at Microsoft.EnterpriseManagement.UI.SdkDataAccess.ManagementGroupServerSession.TryConnectToReportingManagementGroup() Remediation = Please contact your Administrator.
    Jeron

    Hi,
    This may occur when there is a mismatch between the Report Server URL entered on the SSRS Server Location window for the Report Deployment Wizard and the SSRS Web Service Virtual Directory for the Reporting
    Services Configuration Manager.
    Use the following steps to resolve the issue:
    Launch the Reporting Services Configuration Manager on the server hosting SSRS
    Select Web Service URL
    Copy the value entered in the Virtual Directory textbox
    Paste it after the last forward slash in the Report Server URL textbox in the Report Deployment Wizard
    Continue on with the deployment
    In addition, we may need to check you default web server IP is 'all unassigned', and ping the machine and see what default ip it has assigned.
    Regards,
    Yan Li
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • Cannot consume SQL Reporting Services 2005 webservice

    Hello all,
    I have seen some other postings on this subject, but no
    answers anywhere.
    I am trying to run SQL Reporting Services from a CF
    application. The wsdl file is at
    http://172.XX.XX.XX/reportserver/reportservice.asmx
    When I point my browser to that page, I see the XML, so I
    know the URL is correct.
    When I try to consume the webservice, by either CFINVOKE or
    CFSCRIPT , I get the following error:
    "Could not generate stub objects for web service invocation"
    We are running CF MX on Windows 2003 server.
    Any ideas, references, or resources would be greatly
    appreciated!
    Thanks,
    Kathryn

    Ken,
    Thanks. I do exactly that, ctrl-c to copy, ctrl-v to paste. I
    can Preview the message and see the attached code, but when I click
    'Reply to Topic' to post the message, I get the "page not found"
    error....sigh...Thanks for trying to help....
    Kathryn

  • Service manager console can't connect to Service manager data warehouse SQL reporting services

    When I start Service manager console, it gives this kind of error:
    The Service Manager data warehouse SQL Reporting Services server is currently unavailable. You will be unable to execute reports until this server is available. Please contact your system administrator. After the server becomes available please close your
    console and re-open to view reports.
    Also in EventViewer says:
    cannot connect to SQL Reporting Services Server. Message= An unexpected error occured while connecting to SQL Reporting Services server: System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
    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 Microsoft.EnterpriseManagement.Reporting.ReportingService.ReportingService2005.FindItems(String Folder, BooleanOperatorEnum BooleanOperator, SearchCondition[] Conditions)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.FindItems(String searchPath, IList`1 criteria, Boolean And)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.FindItems(String itemPath)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.FindItem(String itemPath, ItemTypeEnum[] desiredTypes)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReporting.GetFolder(String path)
    at Microsoft.EnterpriseManagement.Reporting.EnterpriseReportingGroup.Initialize()
    at Microsoft.EnterpriseManagement.Reporting.ServiceManagerReportingGroup..ctor(DataWarehouseManagementGroup managementGroup, String reportingServerURL, String reportsFolderPath, NetworkCredential credentials)
    at Microsoft.EnterpriseManagement.Reporting.ServiceManagerReportingGroup..ctor(DataWarehouseManagementGroup managementGroup, String reportingServerURL, String reportsFolderPath)
    at Microsoft.EnterpriseManagement.UI.SdkDataAccess.ManagementGroupServerSession.TryConnectToReportingManagementGroup() Remediation = Please contact your Administrator.
    We have a four server set-up where SCSM, SCDW, and sqls for both are on different servers. Also I have red that this could be a SPN problem, but this has  been worked on last week without the SPNs.

    On the computer you get the "SQL Reporting Services server is currently unavailable" message please open the Internet Explorer and try to connect to the URL <a href="http:///reports">http://<NameOfReportingServer>/reports
    This should open the reporting website in IE. If this isn't working you should check the proxy settings in IE. If the URL doesn't work in IE it won't work in the SCSM console as well (and vice versa).
    Andreas Baumgarten | H&D International Group
    Actually I can't access to the reporting website. It asks me credentials 3 times and then return a blank page. Also error message comes to the EventViewer System log with id 4 and source Security-Kerberos.
    The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server "accountname".
    The target name used was HTTP/"reporting services fqn". This indicates that the target server failed to decrypt the ticket provided by the client.
    This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using.
    Ensure that the target SPN is only registered on the account used by the server.
    This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service.
    Ensure that the service on the server and the KDC are both configured to use the same password.
    If the server name is not fully qualified, and the target domain (domain.com) is different from the client domain (domain.com), check if there are identically named server accounts in these two domains,
    or use the fully-qualified name to identify the server.
    I can access the website directly from the server which hosts Reporting Services.
    Also I query "setspn -Q HTTP/"reporting services fqn" whit result NO SUCH SPN FOUND.

  • Remove Corrupted Sharepoint SQL Reporting Services

    Hi,
    I had my sharepoint 2013 foundation with sharepoint-SQL reporting services integrated removed from my server 2012. And I removed my sharepoint folders and regedit files for sharepoint manually to ensure complete uninstallation of sharepoint from my server.
    But now I did a reisntall of sharepoint and it works completely fine, but when I tried to install the reporting services again I cant as it says it is already installed but the service is not listed in my sharepoint Services list and when i tried removing
    the reporting service using the SQL installer from control panel it exits with an error
    Action required:
    Use the following information to resolve the error, and then, try to uninstall this feature again.
    Feature failure reason:
    An error occurred during the setup process of the feature.
    Error details:
    § Error installing SQL Server Reporting Services
    There was an error attempting to remove the configuration of the product which prevents any other action from occuring.  The current configuration of the product is being cancelled as a result.
    Error code: 25012
    Log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150220_144131\sql_rsshp_Cpu64_1.log
    Visit http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sql_rsshp.msi%40Sqlmsirc_NotifyFeatureStates_64%4025012 to get help on troubleshooting.
    § Error installing SQL Server Reporting Services
    Install-SPRSServiceProxy : The term 'Install-SPRSServiceProxy' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.At
    line:1 char:35+ & {$DebugPreference = 'Continue'; Install-SPRSServiceProxy -uninstall}+                                  
    ~~~~~~~~~~~~~~~~~~~~~~~~    + CategoryInfo          : ObjectNotFound: (Install-SPRSServiceProxy:String) [], CommandNotFoundException    + FullyQualifiedErrorId : CommandNotFoundException
    Error code: 0x80131500
    Visit http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x6A1944E2%400xC68B78F0&EvtType=0x6A1944E2%400xC68B78F0 to get help on troubleshooting

    Install the sharepoint reporting services add-in to the exact same drive where you installed it before using the MSSQL installation file, now uninstall the add-in and the reporting service feature from the control panel. This will remove the corrupted
    files completely and now do a fresh installation

  • Group box vs SQL Reporting Services Bookmark box

    <p style="margin: 0cm 0cm 0pt" class="MsoNormal"><font face="Times New Roman" size="3">Hi,</font></p><p style="margin: 0cm 0cm 0pt" class="MsoNormal"><font face="Times New Roman" size="3">My name is Peter Mead. I have started a job where they have a bunch of Reports written using SQL Reporting Services. My job is to convert these reports in to Crystal Reports to be used in an Enterprise Reporting methodology.</font></p><font face="Times New Roman" size="3"> </font> <p style="margin: 0cm 0cm 0pt" class="MsoNormal"><font face="Times New Roman" size="3">The first problem I have is that SQL Reporting Services viewer has a Bookmark box down the left hand side. This Bookmark box looks like a Group box but does not function in the same way. SQL Reporting Services designer allows for the creation of any definable bookmark to be placed in this Bookmark box. </font></p><font face="Times New Roman" size="3"> </font> <p style="margin: 0cm 0cm 0pt" class="MsoNormal"><font face="Times New Roman" size="3">How can I replicate or emulate this Bookmark box?</font></p><font face="Times New Roman" size="3"> </font> <p style="margin: 0cm 0cm 0pt" class="MsoNormal"><font face="Times New Roman" size="3">Thanks in Advance,</font></p><p style="margin: 0cm 0cm 0pt" class="MsoNormal"><font face="Times New Roman" size="3">Peter Mead</font></p>

    In the grouping dialog, there is an option to create "Specified Groups". This should allow you to emulate that bookmark idea.Â
         - Kathryn Webster (Report Design Consultant)
               Kat&#39;s News: http://diamond.businessobjects.com/blog/279

  • SAP and SQL Reporting Services.

    Hi,
    I'm trying to implement a few reports using MS SQL Reporting Services.  I don't think that SAP (we are currently on 4.6C, and BW is not an option for now) has anything nearly as cool.  The problem is that SQL RS can only create queries against ODBC and OleDB providers.  One of the solutions would be to create a view in SAP DB and query against it, but the logic behind is just too complicated for a view that you can create in SAP.  Is there another way that I can interface SAP real time to SQL RS?  Anyone had experience with that, or is there a solution from SAP with similar capabilities?
    Thanks,
    Leon

    Hi Leon,
    maybe you can use the SAP.NET Connector and save the results in SQL-SERVER-Tables or use the OLEDB Provider for SAP from NSX software.
    Greetings,
    Andreas Rohr

  • PS2013 / SQL 2012 - A SQL Reporting Services Report with more than one filter connection looses connection in a site template

    Hi,
    I created in a sub site not linked to a project to become a site template. I inserted two SQL Reporting Services reports web part that require the same two dates for an interval and the name of the project in a page of the site and connected
    to three filters, two for date and one for text and I got the page below (only one of the reports shown).
    Look that all parameters needed by the report are linked to the filters above the report.
    Then I save the site as template with all contentes and assign it to the EPTs and create a new project or replace the site of existing project site. What I got is:
    Look that the filter connection of the dates are lost (in both reports) and the order of the filters changed.
    I deleted and retried to connect the filters in diferent order and language, but I did not get any success.
    The BI Central Data Connectivity resource is activated in the template site and in the site collection.
    Is there any solution for this?
    Best regards, Ricardo Segawa - Segawas Projetos / Microsoft Partner

    Hi,
    Correction: this happens only with "Date Filter" web part!
    Best regards, Ricardo Segawa - Segawas Projetos / Microsoft Partner

Maybe you are looking for