So you are installing SQL Reporting Services in a 2 or more server farm. And when you go to the service to manage it you’re getting the following error
Application error when access /_admin/ReportServer/ReportingServicesSystemSettings.aspx, Error=The remote server returned an error
If you’re getting this error after you installed the SQL Reporting Services Add-in for SP2013 that means you haven’t installed Reporting Services on a SharePoint 2013 server. You can either install SharePoint on your Reporting Services installed server or install Reporting Services to one of your SharePoint App servers.
Install SQL Server 2012 Reporting Services on a SharePoint application server. In the SQL Server 2012 installation wizard, choose ‘Reporting Services – SharePoint’ on the feature selection page.
For single server installations that you would typically use for your development environment you need minimum 24 GBs of RAM, 4 Cores, and 80 GBs of space.
Based on the MSDN article located at - http://technet.microsoft.com/en-us/library/cc262485.aspx
It’s been a crazy year since I started PwC. I’ve been lucky enough to be working with great people – with world class talent … It has been fun and exciting, but it has been just a super high tempo of traveling around the country transforming tax technology using SharePoint. My team has been waiting for SharePoint 2013 and we’ve been working on creating a solution for Tax Departments using the new SharePoint 2013 functionality. I’m looking forward to sharing with you some of our best practices and findings with our SharePoint 2013 implementations. Let the blogging begin!
This year in SPSVB 2011 I spoke on two topics.
- SharePoint 2010 Records Management Capabilites
- SharePoint 2010 Workflows
Below are the links to the slides, please feel free to contact me I always welcome your feedback!
I’m pretty excited about SharePoint Saturday Virginia Beach 2011. Last year around this time I met a lot of great people in this event and this year I look forward meeting all of you who are coming to the event this weekend. This year I’ll be representing West Monroe Partners and I’ll be speaking on Records Management and Workflows. Click Here to see the schedule!
Did the configuration wizard not complete properly? And now you are getting the following error when you’re running the Farm Configuration Wizard
“Operations started by an earlier run of the Farm Configuration Wizard are still in progress. You must wait for those operations to complete before running the wizard again. You can monitor the status of these operations by looking at the “Farm Configuration Wizard” timer job on the Timer Job Status page in the Monitoring section of Central Administration.”
To get rid of the error message you will need to delete the Job Definition for the Farm Configuration Wizard.
Go to – Central Administration > Monitoring > Job Definitions
Then find Farm Configuration Wizard. Once you click on the job definition you’ll see the Edit Timer Job screen where you will click on Delete
After you delete the job definition for the Farm Configuration Wizard you can now go the wizard page and you should see the following farm configuration wizard.
If you get the following error in your App Log -
Load control template file /_controltemplates/TaxonomyPicker.ascx failed: Could not load type ‘Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker’ from assembly ‘Microsoft.SharePoint.Portal, Version=220.127.116.11, Culture=neutral, PublicKeyToken=71e9bce111e9429c’.
Check out this blog post on how to fix it – http://todd-carter.com/post/2010/05/03/Help-Wanted-Taxonomy-Picker.aspx
You might get an error when you’re trying to move publishing sites to SharePoint 2010.
“Provisioning did not succeed. Details: Failed to provision all permission settings.”
Resolution: When your’re copying the site bring it over as a team site. Once it’s created, then enable the publishing feature. After you enable the feature then copy over the content to avoid this problem.