SharePoint 2016

SharePoint 2016 installation step by step...

You can follow this site to configure it,,,

http://www.enjoysharepoint.com/Articles/Details/sharepoint-server-2016-installation-step-by-step-21272.aspx

Thanks,

Power Pivot Data Refresh Error Using Power pivot unattended account SharePoint 2013 & Sql 2014

error:

Getting following error while refreshing power pivot data in excel sheet,

we installed power pivot perfectly but somewhere some permission is missing but could not able to find it,

when i check event viewer, found following error though i m able to connect sql server instance from SharePoint box and able to ping,

can some one help me to fix this?

"OLE DB or ODBC error: A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.; 08001; Client unable to establish connection; 08001; Encryption not supported on the client.; 08001."

Solution;

Power pivot has been installed successfully. it was issue with Sql server adventureworks2014 db sample.

I fixed this issue by restoring AdventureWorks2012 database on sql server 2014 and it works now.

it does not work with AdventureWorks2014 db with sql 2014 as of now.

Thanks,

Improvements Announced for SharePoint 2016 – May Ignite 2015 By Bill Baer

“SharePoint 2016 is the most durable version shipped till date.”

Bill Baer today shared and announced some significant changes coming up in SharePoint 2016.

These announcements are very welcoming, not only from a IT admin perspective but also for the end user (file size, list threshold etc.) This might be the best SharePoint version to date.

TOPICS
• Management
• Reliability, performance, scale
• Insights and data
• Cloud accelerated experiences

Management
Convergence
Code base – took a cloud snapshot of SPO. Brought a lot of SPO investments back to on-premises (the one which couldn’t be brought will be covered by cloud accelerators.) Cloud down codebase based on SPO. Backported capabilities for on-premises differentiators

Hardware Reqs
Single – 16-24 memory; x64 processor; 80 GB disk
Farm – 12-16 GB RAM

Pre Requisites
OS
Windows Server 2012 R2, WS 2010

Services
.NET Framework 4.5.2
Windows Server App Fabric
Provides in memory distributed caching
MS Information Protection and Control Client
WCF Data Services – enables creation and consumption of services

Database– 64 bit of SQL 2014
Deployment – unchanged from SP 2013

NOTE: Standalone installations will no longer be supported (Single Server Farm does not include SQL Server Express)

Upgrade – Attach SP 2013 DB to SP 2016. (For SP 2010 scenarios -Upgrade 14.5 mode (SP 2010 mode) site collections to 15 mode)
Migration – Migrate content to SP 2016

NOTE: The services that don’t exist in SPO will be backported to SP 2016 like PerformancePoint

Identity
SAML authentication becomes a first class citizen (default). Normalizes on OAuth and JWT/SAML with WSFED
(Apps will trust Azure AD) (Moving away from windows identity and moving towards cloud based)

SMTP Connection Encryption
Supports sending mail to SMTP servers using STARTTLS connection encryption
No fallback support for unencrypted connections
SMTP can use non-default ports (no more relying on port 25 for mails)

Performance and Reliability

MinRole (Roles and services)
Four discrete roles –
• User services – Any requests coming from the end user will be handled here like sync client; onenote; user profile; page rendering; excel services; sandbox. code; project; subscription settings. These are optimized for low latency
• Robot Services (Application Services) – not end user initiated like provisioning; timer jobs; search. Optimized for high throughput
• Specialized Load – reserved for services that needed to be isolated from other services like 3rd party
• Caching Services – supports for distributed cache (load balances request from end user)

New Role Screen -Specify Server Role (in config wizard) like special load role (third party solutions); web front load role; search; application; distributed cache

NOTE: For automated deployments – use -IsLocalServerRole <RoleName> from PSConfig commandlets to assign role to a server
NOTE: Chose specialty load role for assigning multiple roles to a server

Role Enforcement and Health
Health rule will scan each server in the farm daily (except special load)

Central Administration
New columns in the “servers in farm”- Role; In Compliance (yes or no) with fix button (in cases where one server is assigned multiple roles

PATCHING
Zero downtime patching – 2 MSI’s per service and 1 MSI’s per language pack. Smaller update footprint.
You can install patches middle of day online w/o stopping services.

Boundaries (HUGE HUGE)
Content DB – probably sizing into TB’s
Site Collection per Content DB – 100,000 site collections per content DB
List threshold – well beyond 5000
File Size -10 GB and removed character restrictions
Indexed items – 2x increase in search scale to 500 million items

Performance
Download – byte range HTTP Gets
Upload – BITS specific block-based upload protocol
*Moving away from file sync
Fast site creation – simply copies site collections with SPSite. Copy from already created templated site collections. Mitigation of feature activation.

User profile service
Removed built in FIM service and supports external FIM service.

Durable Links (BIG)
Renaming or moving files in earlier versions broke the link. With SP 2016 links will use Resource ID based URL’s. URL remains intact with rename and move. Enables discrete Url on visibility. Moving between site collections or sites will not change the URL

Insights and Data
Real time telemetry – real user monitoring for Services, Actions, Usage, Engagement, Diagnostics

Compliance
Classification ID – complex query based on complex predicate. 51 classification ID’s OOB provided for SSN, license #, etc.
You can now use Azure RMS and eDiscovery for on-premises SharePoint.

Search Service Application
New application will provide support for Office Graph/Delve. Unifies on-premises and cloud indexes.

Extranet
Site publishing – leverages Office 365 Identity federation services

Team Sites
Hybrid scenarios – Be inclusive of both online and on-premises. e.g. when you follow documents online you should be able to see the same on-premises too.

SSRS SharePoint 2013 installation and Configuration Step By Step

Configuration steps for SSRS with SQL server 2014 and SharePoint 2014

https://msdn.microsoft.com/en-us/library/JJ219068(v=sql.120).aspx

 Setup accounts

This section describes the accounts and permissions used for the primary deployment steps of Reporting Services in SharePoint mode.

Installation and registering the Reporting Services Service:
* The current account during the installation (referred to as the ‘setup’ account) of Reporting Services in SharePoint mode needs to have administrative rights in the local computer. If you are installing Reporting Services after SharePoint is installed and the ‘setup’ account is also a member of the SharePoint farm administrators group, the Reporting Services installation will register the Reporting Services service for you. If you install Reporting Services before SharePoint is installed or the ‘setup’ account is not a member of the farm administrators group, you register the service manually. See the section Step 2: Register and Start the Reporting Services SharePoint Service.

Creating Reporting Services Service Applications
* Following installation and registering the Reporting Services service, create one or more Reporting Services service applications. The “SharePoint farm service account “ needs to temporarily be a member of the local administrators group so the Reporting Services service application can be created. For more information on SharePoint 2013 account permissions, see Account permissions and security settings in SharePoint 2013(http://technet.microsoft.com/library/cc678863.aspx).
It is security best practice that SharePoint farm administrator accounts are not also local operating system administrator accounts. If you add a farm admin account to the local administrators group as part of your installation process, it is recommended you remove the account from the local administrators group after installation is complete.

 Step 1: Install Reporting Services Report Server in SharePoint mode

This step installs a Reporting Services report server in SharePoint mode and the Reporting Services add-in for SharePoint products. Depending on what is already installed on your computer, you may not see some of the installation pages described in the following steps.
1. Run the SQL Server Installation Wizard (Setup.exe).
2. Click Installation in the left side of the wizard and then click New SQL Server stand-alone installation or add features to an existing installation.
3. Click OK on the Setup Support Rules page, assuming all rules passed.
4. Click Install on the Setup Support Files page. Depending on what is already installed on your computer, you might see the following message:
o “One or more affected files have operations pending. You must restart your computer after the setup process is completed.”
o Click Ok.
5. Click Next after the support files have completed installing and the Support Rules pages show a status ofPassed. Review any warnings or blocking issues.
6. On the Installation Type page, click Add features to an existing instance of SQL Server 2014. Select the correct instance in the drop-down list and click Next.
7. If you see the Product Key page, type your key or accept the default of the ‘Enterprise Evaluation’ edition.
Click Next.
8. If you see the License terms page, review and accept the license terms. Microsoft appreciates you clicking to agree to send feature usage data to help improve product features and support.
Click Next.
9. If you see the Setup Role page, select SQL Server Feature Installation
Click Next

1.     Select the following on the Feature Selection page:

o    Reporting Services – SharePoint

o    Reporting Services add-in for SharePoint Products.

The installation wizard option for installing the add-in is new with the SQL Server 2014 release.

o    If you do not already have an instance of SQL Server Database Engine, you could also select Database Engine Services and Management Tools Complete for a complete environment.

Click Next.

1.     If you see the Installation Rules page. Review any warnings or blocking issues. Then click Next

2.     If you selected the Database Engine services, accept the default instance of MSSQLSERVER on the Instance Configuration page and click Next.

The Reporting Services SharePoint service architecture is not based on a SQL Server "instance" as was the previous Reporting Services architecture.

3.     Review the Disk Space Requirements page and click Next.

4.     If you see the Server Configuration page type appropriate credentials. If you want to use the Reporting Services data alerting or subscription features, you need to change the Startup Type for SQL Server Agent toAutomatic. You may not see the Server Configuration page, depending on what is already installed on the computer.

Click Next.

5.     If you selected the Database Engine services, you will see the Database Engine Configuration page, add appropriate accounts to the list of SQL Administrators and click Next.

6.     On the Reporting Services Configuration page you should see the Install only option is selected. This option installs the report server files, and does not configure the SharePoint environment for Reporting Services.

Note

When the SQL Server installation is complete, follow the other sections of this topic to configure the SharePoint environment. This Includes installing the Reporting Services shared service and creating Reporting Services service applications.

1.     Help Microsoft improve SQL Server features and services by clicking the check box to send error reports on theError Reporting page.

Click Next.

2.     Review any warnings and then click Next on the Installation Configuration Rules page.

3.     On the Ready to Install page, review the installation summary and then click Next. The summary will include aReporting Services SharePoint Mode child node that will show a value of SharePointFilesOnlyMode. ClickInstall.

4.     The installation will take several minutes. You will see the Complete page with the features listed and the status of each feature. You may see an information dialog indicating the computer needs to be restarted.

Step 2: Register and Start the Reporting Services SharePoint Service

Note

If you are installing into an existing SharePoint farm, you do not need to complete the steps in this section. The Reporting Services SharePoint service is installed and started when you ran the SQL Server installation wizard as part of the previous section of this document.

The following are the common reasons why you need to manually register the Reporting Services service.

·         You installed Reporting Services SharePoint mode before SharePoint was installed.

·         The account used to install Reporting Services SharePoint mode, was not a member of the SharePoint farm administrators group. For more information, see the section Setup accounts.

The necessary files were installed as part of the SQL Server installation wizard, but the services need to be registered into the SharePoint farm. The SQL Server 2014 release introduces PowerShell support for Reporting Services in SharePoint mode.

The following steps guide you through opening the SharePoint Management Shell and running cmdlets:

1.     Click the Start button

2.     Click the Microsoft SharePoint 2013 Products group.

3.     Right-click SharePoint 2013 Management Shell click Run as administrator. NOTE: the SharePoint commands are not recognized in the standard Windows PowerShell window. Use the SharePoint 2013 Management Shell.

4.     Run the following PowerShell command to install the SharePoint service. A successful completion of the command displays a new line in the management shell. No message is returned to the management shell when the command completes successfully:

5.  Install-SPRSService

Important

If you see an error message similar to the following: Install-SPRSService : The term 'Install-SPRSService' 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.

6.     Run the following PowerShell command to install the service proxy. A successful completion of the command displays a new line in the management shell. No message is returned to the management shell when the command completes successfully:

7.  Install-SPRSServiceProxy

8.     Run the following PowerShell command to start the service or see the following notes for instructions on how to start the service from SharePoint Central administration:

9.  get-spserviceinstance -all |where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance

Either you are in the Windows Powershell instead of the SharePoint Management Shell or Reporting Services SharePoint mode is not installed. For more information on Reporting Services and PowerShell, see PowerShell cmdlets for Reporting Services SharePoint Mode.

You can also start the service from SharePoint central Administration rather than running the third PowerShell command. The following steps are also useful to verify that the service is running.

1.     In SharePoint Central Administration, click Manage Services on Server in the System Settings group.

2.     Find SQL Server Reporting Services Service and click Start in the Action column.

3.     The status of the Reporting Services service will change from Stopped to Started. If the Reporting Services service is not in the list, use PowerShell to install the service.

Note

If the Reporting Services service stays in the Starting status and does not change to Started, verify the ‘SharePoint 2013 Administration’ service is started in Windows Server Manager.

Step 3: Create a Reporting Services Service Application

This section provides the steps to create a service application and a description of the properties, if you are reviewing an existing service application.

1.     In SharePoint Central Administration, in the Application Management group, click Manage Service Applications.

2.     In the SharePoint ribbon, click the New button.

3.     In the New menu, click SQL Server Reporting Services Service Application..

Important

If the Reporting Services option does not appear in the list, it is an indication that the Reporting Services shared service is not installed. Review the previous section on how to use PowerShell cmdlts to install the Reporting Services service.

4.     In the Create SQL Server Reporting Services Service Application page, enter a name for the application. If you are creating multiple Reporting Services service applications, a descriptive name or naming convention will help you organize your administration and management operations.

5.     In Application Pool section, create a new application pool for the application (recommended). If you use the same name for both the application pool and the services application, it can make ongoing administration easier. This can also be affected by how many service applications you will create and if you need to use several in a single application pool. See the SharePoint Server documentation on recommendations and best practices for application pool management.

Select or create a security account for the application pool. Be sure to specify a domain user account. A domain user account enables the use of the SharePoint managed account feature, which lets you update passwords and account information in one place. Domain accounts are also required if you plan to scale out the deployment to include additional service instances that run under the same identity.

6.     In the Database Server, you can use the current server or choose a different SQL Server.

7.     In Database Name the default value is ReportingService_<guid>, which is a unique database name. If you type a new value, type a unique value. This is the new database to be created specifically for the services application.

8.     In Database Authentication, the default is Windows Authentication. If you choose SQL Authentication, refer to SharePoint documentation for best practices on how to use this authentication type in a SharePoint deployment.

9.     In the Web Application Association section, select the Web Application to be provisioned for access by the current Reporting Services Service Application. You can associate one Reporting Services service application to one web application. If all of the current web applications are already associated with a Reporting Services service application, you see a warning message.

10.   Click OK.

11.   The process to create a service application could take several minutes to complete. When it is complete, you will see a confirmation message and a link to a Provision Subscriptions and Alerts page. Complete the provision step if you want to use the Reporting Services subscriptions feature or the data alerts feature. For more information, see Provision Subscriptions and Alerts for SSRS Service Applications.

 For information on using PowerShell to create a Reporting Services service application, see:

·         See the following section Windows PowerShell script for Steps 1–4.

·         Topic To create a Reporting Services Service Application using PowerShell.

Step 4: Activate the Power View Site Collection Feature.

Power View, a feature of SQL Server 2014Reporting Services Add-in for Microsoft SharePoint Products, is a site collection feature. The feature is activated automatically for root site collections and site collections created after the Reporting Services add-in is installed. If you plan to use Power View, verify that the feature is activated.

If you install the Reporting Services add-in for SharePoint Products after the installation of the SharePoint Server, then the Report Server integration feature and the Power View integration feature will only be activated for root site collections. For other site collections, manually activate the features.

To Activate or Verify the Power View Site Collection Feature

1.     The following steps assume your SharePoint site is configured for the 2013 experience version.

Open your browser to the desired SharePoint site. For example http://<servername>/sites/bi

2.     Click Settings.

3.     Click Site settings.

4.     In the Site Collection Administration group Click Site collection features.

5.     Find Power View Integration Feature in the list.

6.     Click Activate. The feature status will change to Active.

This procedure is completed per site collection. For more information, see Activate the Report Server and Power View Integration Features in SharePoint.

That's all...Cheers