Sharepoint 2013 installation modules

Hi All,
Question - we are planning to install SP 2013 Ent. Our sysadmin is very experienced but he did not take any SP classes.
He is planning to install SP 2013 Ent in regular/full configuration and then install reporting services integration module.
Are there any other modules/features SP 2013 Ent that not included into regular install and would need to be installed separately ( like SSRS in integrated mode)...?

Sure:
SSRS
PowerPivot (includes PowerView if SSRS is installed)
Project Server
Office Web Apps is now separate server software and requires a dedicated server
Workflow Manager (can be on a separate server)
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.

Similar Messages

SharePoint 2013 Installation and Configuration

Which way is best to install and configure sharepoint 2013 multitier farm?
1. SharePoint Configure Wizard or 2. AutoSPInstaller
Let me know.
Thanks,,,

AutoSPInstaller is the quick way of installing the share point by using the powershell scripts.If we set the correct settings in the script,then it should be good.
SharePoint Configure Wizard is the manuall way of installing the sharepoint.we can choose the options which we requirred.please check the below link that provides more information of sharepoint installations with pre-requisites.
http://expertsharepoint.blogspot.de/2013/11/detailed-sharepoint2013-installation-i.html
Anil Avula[Partner,MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

Sharepoint 2013 installation in windows 2012 R2 server

Hi,
I am unable to install Sharepoint 2013 server on Windows 2012 R2 Server.
I am getting below error
The tool was unable to install Application Server Role, Web Server (IIS) Role.
I checked my IIS it is working fine.
Please help me out.
Regards,
Siva.

Make sure you have the SharePoint 2013 with Service Pack 1 ISO. Pre-SP1 will not install to SP 2013, and you cannot slipstream it yourself.
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.

SharePoint 2013 Installation on Windows Server 2012 R2

https://technet.microsoft.com/en-in/evalcenter/hh973397.aspx the version mentioned in blog ,does it included SP1 ? please confirm.
and also I have downloaded the above and trying to install on Windows Server 202 R2 . I m getting application server web server configuration error while running pre requisites. whether it is application feature issue or SP1 ISSUE, not sure..
http://support.microsoft.com/en-us/kb/2891274 if it is SP1 issue where do I get trial version of SP1.
to be upfront, Microsoft is not clear in documenting all these..very poor.
Please help me with the same.
Thanks, Ram Ch

Hi Ram,
Yes, it is a Slipstream version of SharePoint 2013 including SP1.You can download SharePoint Server 2013 SP1 from the Microsoft Developer Network (MSDN), the Volume Licensing Service Center (VLSC), and the Microsoft Partner Network (MPN).
https://msdn.microsoft.com/en-us/subscriptions/downloads/?FileId=57191#searchTerm=&Languages=en&PageSize=10&PageIndex=0&FileId=57191
For more information, you can have a look at the SharePoint 2013 SP1 FAQ:
http://blogs.technet.com/b/stefan_gossner/archive/2014/02/27/sp2013-sp1-faq.aspx
Best Regards,
Eric
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

SharePoint 2013 installation

Dears,
I am going to install SharePoint 2013 server in my corporation, I am going to use two tiers:
Web server and application server on the same physical server.
Database server on another physical server.
The users in SharePoint server will be get from active directory domain server.
The users will sign in to SharePoint server just from the corporation intranet network.
During this progress I have some questions about:
What is the cost of SharePoint 2013 enterprise server license and how can I get it?
What is the business CAL for users and do I need it?
Can I upgrade the SharePoint version to updated versions like SharePoint 2015..?
Thanks.

Hi
The license structures were changed recently. The best would be to contact a partner/reseller in your area and let them advise you.
You will need a SQL license as well and CALs for users accessing the server. Like with Sharepoint 2010 there was not direct upgrade path and you will need to install the new version i assume the same process will follow with newer versions of sharepoint.
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Sharepoint 2013 installation problem

The program or feature
"\??\C:\Users\username\AppData\Local\Temp\Net41B3.tmp.exe" cannot start or run due to incompatibility with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available.
System Details:
Windows Server 2008 R2 SP1 64 bit.
SQL Server 2008 R2 (installed)
RAM: 6GB
Bipul Raman

could you please give us more details about the issue.
what you trying to install which cause this error?
is it fresh windows installation? do you have the AntiVirus software on the server?
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Windows authentication failure on SharePoint 2013 zone

I am attempting to set up a Windows authentication zone in a SharePoint 2013 installation for use by the search crawler. The zone has been configured to use NTLM in order to eliminate Kerberos from the equation. The result of my
attempts to access the Windows authentication zone is a 403 error. Central Administration is working on the same server, and of course is using Windows authentication.
I know about the issue of using Windows authentication to localhost, and have configured the backconnectionhostnames entry in the registry. To prove that I can use Windows authentication using the intended host name for the SharePoint zone, I have
set up a test IIS site that binds to the host name used by the zone, and successfully authenticated using Windows authentication.
From monitoring the ULS logs it's obvious that I'm actually successfully completing Windows authentication, and getting a SharePoint claim, but from that point I'm being denied by SharePoint. I do know that my Windows credentials has site collection
administrator privileges. The most interesting failure in the ULS log appears to be:
SPApplicationAuthenticationModule: Authorization header doesn't contain Bearer, can't try to perform application authentication.
Another odd thing is that after the ULS indicates I have failed authentication, I'm redirected to /_layouts/AccessDenied.aspx instead of the login page defined in web.config. I have tried many things, including enabling Kernel-mode authentication.
Below is an excerpt from my ULS logs:
SPApplicationAuthenticationModule: There is no Authorization header, can't try to perform application authentication.
Non-OAuth request. IsAuthenticated=False, UserIdentityName=, ClaimsCount=0
[Forced due to logging gap, cached @ 12/01/2014 15:48:32.53, Original Level: Verbose] Value for isAnonymousAllowed is : {0}
[Forced due to logging gap, Original Level: Verbose] Value for checkAuthenticationCookie is : {0}
Claims Windows Sign-In: Sending 401 for request 'https://crawler.my.host/' because the user is not authenticated and resource requires authentication.
[Forced due to logging gap, cached @ 12/01/2014 15:48:32.56, Original Level: VerboseEx] Sending HTTP response {0} - {1}:{2}.
[Forced due to logging gap, Original Level: Verbose] SPRequestModule.PreSendRequestHeaders
Leaving Monitored Scope (Request (GET:https://crawler.my.host:443/)). Execution Time=5320.19544383434
Name=Timer Job SchedulingApproval
Leaving Monitored Scope (Timer Job SchedulingApproval). Execution Time=16.4101862108173
Name=Timer Job SchedulingApproval
Leaving Monitored Scope (Timer Job SchedulingApproval). Execution Time=14.9021733209109
Name=Timer Job SchedulingApproval
[Forced due to logging gap, cached @ 12/01/2014 15:48:32.95, Original Level: Verbose] Completed deserializing the type named {0} and with id {1}.
[Forced due to logging gap, Original Level: VerboseEx] SPFederationAuthenticationModule.OnEndRequest: Start
SPFederationAuthenticationModule.OnEndRequest: User was being redirected to authenticate.
Leaving Monitored Scope (Timer Job SchedulingApproval). Execution Time=17.2175513927049
Claims Windows Sign-In: Sending 401 for request 'https://crawler.my.host/' because the user is not authenticated and resource requires authentication.
Name=Request (GET:https://crawler.my.host:443/)
Micro Trace Tags: 0 nasq
Leaving Monitored Scope (Request (GET:https://crawler.my.host:443/)). Execution Time=9.54646470431298
Name=Request (GET:https://crawler.my.host:443/)
SPTokenCache.ReadTokenXml: Successfully read token XML 'mydomain\myuser'.
Token Cache: Failed to get token from distributed cache for '0).w|s-0-0-0-0-0-0-1234'.(This is expected during the process warm up or if data cache Initialization is getting done by some other thread).
Token Cache: Reverting to local cache to get the token for '0).w|s-0-0-0-0-0-0-1234'.
Token Cache: Entry missing for user 'mydomain\myuser'.
Token Cache: Failed to get token from distributed cache for '0).w|s-0-0-0-0-0-0-1234'.(This is expected during the process warm up or if data cache Initialization is getting done by some other thread).
Token Cache: Reverting to local cache to get the token for '0).w|s-0-0-0-0-0-0-1234'.
Claims Windows Sign-In: User 'mydomain\myuser' for request url 'https://crawler.my.host/' does not have a cached SessionSecurityToken.
[Forced due to logging gap, cached @ 12/01/2014 15:48:33.24, Original Level: VerboseEx] We are in claims windows only mode for for request url '{0}'.
[Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity
[Forced due to logging gap, cached @ 12/01/2014 15:48:33.71, Original Level: Verbose] Completed deserializing the type named {0} and with id {1}.
SPSecurityContext: Added JsonWebSecurityTokenHandler to trust channel factory
SPSecurityContext: Replaced WSTrustRequestSerializer with SPTrust13RequestSerializer
SPSecurityContext: The SecurityTokenServiceBehavior is attached to the TrustChannel.
SecurityTokenServiceSendRequest: RemoteAddress: 'http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc' Channel: 'Microsoft.IdentityModel.Protocols.WSTrust.IWSTrustChannelContract' Action: 'http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue'
MessageId: 'urn:uuid:f175f6ef-a93d-4efe-9173-1fba74b1eed2'
SecurityTokenServiceReceiveRequest: LocalAddress: 'http://servername:32843/SecurityTokenServiceApplication/securitytoken.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue' MessageId:
'urn:uuid:f175f6ef-a93d-4efe-9173-1fba74b1eed2'
Entering monitored scope (ExecuteSecurityTokenServiceOperationServer). Parent No
STS Call: Issuing new security token.
SPSecurityTokenServiceManager!EnsureSharePointLogonRequestClaims: Found primary sid claim. Value: 's-0-0-0-0-0-0-1234'.
Using claim provider 'System' for operation because it is default and it is visible.
Excluding claim provider 'AD' for operation because it is not default and .
Using claim provider 'AllUsers' for operation because it is default and it is visible.
Excluding claim provider 'Forms' for operation because it is not default and .
Using claim provider 'User Profile Claim Provider' for operation because it is default and it is visible.
STS Call Claims Windows: Setting cookie lifetime to: Microsoft.IdentityModel.Protocols.WSTrust.Lifetime
STS Call Claims Windows: Successfully requested sign-in claim identity for user 'mydomain\myuser'.
STS Call: Successfully issued new security token.
Leaving Monitored Scope (ExecuteSecurityTokenServiceOperationServer). Execution Time=13.187150880908
[Forced due to logging gap, cached @ 12/01/2014 15:48:34.87, Original Level: Verbose] The SecurityTokenServiceHeaderInfo including the correlation ID was added.
Leaving Monitored Scope (ExecuteSecurityTokenServiceOperationCaller:http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue). Execution Time=719.713539011243
[Forced due to logging gap, cached @ 12/01/2014 15:48:35.60, Original Level: Verbose] ____{0}={1}
Claims Windows Sign-In: Siginging in the the user 'mydomain\myuser' for request url 'https://crawler.my.host/'.
Updating X.509 certificate validation policy
[Forced due to logging gap, cached @ 12/01/2014 15:48:36.26, Original Level: Verbose] Completed deserializing the type named {0} and with id {1}.
Adding X.509 certificate thumbprint '493E6806F4178EDD685BE5EA0AAF79ED30FB4A90' to root authority trust
SPLocalLoginProvider: Initializing and creating S2S Claim Mappings
SPLocalLoginProvider: Initialized S2S Claim Mappings.
[Forced due to logging gap, cached @ 12/01/2014 15:48:36.37, Original Level: Verbose] Completed deserializing the type named {0} and with id {1}.
[Forced due to logging gap, Original Level: Verbose] Deserializing the type named {0} and with id {1}.
[Forced due to logging gap, cached @ 12/01/2014 15:48:37.17, Original Level: Verbose] Completed deserializing the type named {0} and with id {1}.
[Forced due to logging gap, Original Level: Verbose] Deserializing the type named {0} and with id {1}.
[Forced due to logging gap, cached @ 12/01/2014 15:48:37.96, Original Level: Verbose] Completed deserializing the type named {0} and with id {1}.
[Forced due to logging gap, Original Level: VerboseEx] SPFederationAuthenticationModule.OnSessionSecurityTokenCreated: Start
[Forced due to logging gap, cached @ 12/01/2014 15:48:38.10, Original Level: VerboseEx] SPSam.SetPrincipalFromSessionToken: End
[Forced due to logging gap, Original Level: Verbose] Looking up {0} site {1} in the farm {2}
Token Cache: Failed to add token from distributed cache for '0).w|s-0-0-0-0-0-0-1234'.(This is expected during the process warm up or if data cache Initialization is getting done by some other thread).
Token Cache: Reverting to local cache to Add the token for '0).w|s-0-0-0-0-0-0-1234'.
Token Cache: Successfully added token to cache for '0).w|s-0-0-0-0-0-0-1234'.
SPTokenCache.ReadTokenXml: Successfully read token XML '0).w|s-0-0-0-0-0-0-1234,0#.w|mydomain\myuser,123456789012345,True,dpoRtB/hPcjVrEaJtqVWxhY8Pbfm++oHwWQ5TCB9jBlLx5n2Ky5OqGXM7ntfLB0kqIJNDUkeQrl4wL7xW2m4r0rV1TiOUf+e2mpHq8WOgN67puRViZbCxCkwmmxUpE/1OVNcDFXRCh26tvVFieK99LKZn8BJUtmP8RqxtwtwqBolNjCyZ3rfSSmtFyM3pdWjphdj312R9Lcp9/EhTpvvV1J2lFCig901ZGaPo7zOw3pFyXl1eDs+gF2Bcbc7/mMZw67/gEccsFaekBVH1TK0d9qqr6P/ISeEgzhlK4DChV94ntsw8m8Pb255yTL8WrbTykMFV3jC7R2MvqCmiKGK+g==,https://crawler.my.host/'.
Claims Windows Sign-In: Not writing a cookie for request 'https://crawler.my.host/'.
Claims Windows Sign-In: Successfully signed-in the the user 'mydomain\myuser' for request url 'https://crawler.my.host/'.
Updating header 'LOGON_USER' with value '0#.w|mydomain\myuser' for the request url 'https://crawler.my.host/'.
Leaving Monitored Scope (SPClaimsCounterScope). Execution Time=4957.74267399907
SPApplicationAuthenticationModule: Authorization header doesn't contain Bearer, can't try to perform application authentication.
Non-OAuth request. IsAuthenticated=True, UserIdentityName=0#.w|mydomain\myuser, ClaimsCount=27
Leaving Monitored Scope (PostAuthenticateRequestHandler). Execution Time=31.2877754016223
Micro Trace Tags: 0 nasq,69 air4a,1 air4b,22 air4a,0 air4b,1641 aeayb,732 b4ly,654 erv2,58 erv3,1814 air36,0 air37,42 b4ly,5 agb9s,39 b4ly
Leaving Monitored Scope (Request (GET:https://crawler.my.host:443/)). Execution Time=5101.04328902137
SPFederationAuthenticationModule.OnEndRequest: User was being redirected to authenticate.
[Forced due to logging gap, cached @ 12/01/2014 15:48:38.24, Original Level: Verbose] {0}
[Forced due to logging gap, Original Level: VerboseEx] SPRequestParameters: AppPrincipal={0}, UserName={1}, UserKye={2}, RoleCount={3}, Roles={4}
Site=/
[Forced due to logging gap, cached @ 12/01/2014 15:48:38.37, Original Level: Verbose] {0}
[Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity
[Forced due to logging gap, cached @ 12/01/2014 15:48:38.40, Original Level: VerboseEx] No SPAggregateResourceTally associated with thread.
[Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity
[Forced due to logging gap, cached @ 12/01/2014 15:48:38.48, Original Level: VerboseEx] No SPAggregateResourceTally associated with thread.
[Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity
Access Denied for /. StackTrace:    at Microsoft.SharePoint.Utilities.SPUtility.HandleAccessDenied(HttpContext context)     at Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModule.OnEndRequest(Object sender,
EventArgs eventArgs)     at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)     at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)     at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest
wr, HttpContext context)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr
rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)     at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr
nativeRequestContext, IntPtr moduleData, Int32 flags)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
Leaving Monitored Scope (SPFederationAuthenticationModule.OnEndRequest). Execution Time=351.625416079418
Entering monitored scope (Request (GET:https://crawler.my.host:443/_layouts/AccessDenied.aspx?Source=https%3A%2F%2Fcrawler%2Emy%2Ehost)). Parent No

I'm extending an existing claims based web application. The way I'm testing authentication is by attempting to log in to the Windows authentication zone using the browser and an account with site collection administrator privileges. I've also
tried using the intended crawler service account, but that also fails authentication.
With regard to the default zone issue, I've already experimented with using both the default zone and another zone, but neither works.
BTW, I already have this working in a SharePoint 2013 development environment, and a similar configuration has been in a SharePoint 2010 production environment for over a year, which makes this a particularly maddening problem.
I have enabled Failed Request Tracing, and get a 401.1, 401.2, then a 403 (which says it was caused by the 401.2). I'm not sure of the significance, but the 403 trace shows the module for the 401.2 to be UrlAuthorizationModule, while the module for
the 403 error is FederatedAuthentication.
Per my ULS trace included in my original post, it appears that I'm actually getting a SharePoint claim.

Sharepoint 2013 onedrive for business Ipad App

Hi
We have an on-premise sharepoint 2013 installation and we would like to achieve access to the private library/onedrive using some of our ipads. We have installed One drive for business connected to a VPN. We have put in the url of the
site, which is our intranet page, enter my domain credentials click sign in and get the message. There is a problem with your account. Please try again later
While connected to the VPN if I use the browser to the page it works and I can navigate to other parts of the intranet.
Am I missing something simple?
What should the internal address be like when trying to access onedrive?
Regards
Chris

The ODfB app for iOS will only work while on the WLAN. It doesn't work across any other connection, at least per https://support.office.com/en-US/Article/Use-the-OneDrive-for-Business-app-on-an-iPhone-or-iPad-a1dbdcda-19df-4c06-b908-29c10865d20d?ui=en-US&rs=en-US&ad=US#BKMK_SupportedAuthentication.
If you’re an Office 365 multitenant user, you can
connect from the OneDrive for Business app in any network environment, including Wi-Fi and cellular data. If you’re not using multitenant Office 365, you can connect only when you use your organization’s on-site Wi-Fi network.
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.

Installing SharePoint 2013 in a Windows 2012 R2 Server I was getting the following error

when I install prerequisiteinstaller.exe in sharepoint 2013, got the below error:
Error: The tool was unable to install Application Server Role, Web Server (IIS) Role.
Any expert please help?

Hi,
From your description, I know you get error when you install SharePoint 2013 in Windows Server 2012 R2.
If you have tried all method above. In your case, you have installed the Web Server(IIS), but the
Web Server (IIS) role installation may fail. You could try run commande: aspnet_regii -enable –i.
Here are similar issues:
https://social.technet.microsoft.com/Forums/office/en-US/37cc20db-6cc7-45e0-928c-9a1ddbdab2ae/the-tool-was-unable-to-install-application-server-role-web-server-iis-role?forum=sharepointadmin.
http://itrob.be/sharepoint-2013-installation-issue-the-tool-was-unable-to-install-application-server-role-web-server-iis-role/
As SharePoint 2013 does not support Windows 2012 R2 Server very well what you can find from this blog:
http://blogs.technet.com/b/wbaer/archive/2013/09/22/sharepoint-2013-support-for-windows-server-2012-r2.aspx.
Please try to refer to this article:https://iouchkov.wordpress.com/2013/10/19/how-to-install-sharepoint-2013-on-windows-server-2012-r2/.
Best Regards
Vincent Han
TechNet Community Support

On-premise SharePoint 2013 and SkyDrive Pro Sync Issue

Hi all,
I'm not sure if this is the correct forum between SharePoint and SkyDrive as the issue is related to an update on SkyDrive Pro.
premise SharePoint 2013 installation (migrated from 2010) and Office 2013 installed. SharePoint is patched up to the latest CU. Syncing documents from SharePoint worked fine until KB2817495 was installed. The syncing still seems to work but we cannot add
any new libraries, either directly from the browser using the "sync" button or adding the URL to "Sync a new library". I've tested it with an Office 365 account and the libraries add fine so I'm not sure whether it's a SkyDrive or SharePoint
issue. If I uninstall the update then I can successfully sync new libraries from our on-premise installation.
At this point the only solution I can see is to prevent that update from installing via WSUS.
Kind regards,
Rick

Hi
anuxps ,
Yammer already have Single Sign On with Office 365, but SharePoint Server for on-premise does not follow a 90-day release cycle and it won’t yet. Also we are looking for Yammer integration with on-premise
soon. There are improvements coming.
Reference:
http://social.technet.microsoft.com/Forums/en-US/a6ecdee4-ac28-4989-929b-0e6c9968732e/yammer-sharepoint-onprem-integration?forum=sharepointgeneral
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

SharePoint 2013 and Native Mode SSRS Web Parts

SharePoint 2013 and SQL Server 2012 installation. Trying to get the SSRS native mode web parts installed as per these instructions:
http://msdn.microsoft.com/en-us/library/ms159772.aspx
Have tried both via PowerShell and stsadm. In both cases, get an error regarding "Failed to extract the cab file in the solution". Have done this a bunch of times in SharePoint 2007 and 2010, is this solution no longer supported in
2013 and if so, is there a supported way of integrating with SSRS in Native Mode for SharePoint 2013?

OK, let me amend my statement a bit.
Found this article: http:// social.msdn.microsoft.com /Forums/sqlserver/en-US/5b9de028-5b6a-47c7-8da8-793d1a78df55/error-with-sql-server-2012-rswebpartscab-for-sharepoint-2010
Mind you, I was able to get the SQL Server 2012 version of RSWebParts.cab to install successfully on the SharePoint 2010 dev box in the environment, but figured that trying the SQL Server 2008 R2 version of RSWebParts.cab was worth a shot. It worked
(or at least it installed and I am able to add the web parts to pages). Will post an update once I am able to test full web part functionality with an SSRS Native Mode server.
So, what I can say from my testing:
SQL Server 2012 version of RSWebParts.cab works (installs) for a SharePoint 2010 installation but not for a SharePoint 2013 installation.
SQL Server 2008 R2 version of RSWebParts.cab works (installs) for a SharePoint 2010 installation and for a SharePoint 2013 installation.
There is no update to RSWebParts.cab in SQL Server 2012 SP1 (at all, not in any part of it including the Reporting Services Add-In), the file is always 10/20/2012.
So, as long as you are trying to integrate a SQL Server 2008 R2 SSRS Native Mode instance or lower on your SharePoint 2013 farm, there is a solution. However, it will likely not work against a SQL Server 2012 SSRS Native Mode installation.
So, the amended statement is that:
"The bottom line is that it *appears* that there currently is no supported version of the Native Mode (2.0) version web parts for SQL Server Reporting Services2012
(RSWebParts.cab) for SharePoint 2013. Therefore, there is currently no way to integrate SharePoint 2013 with a SQL Server Reporting Services
2012 instance running in native mode."
And, no, none of this really makes any sense in the least but that is what my testing shows.

SharePoint 2013 SQL Server Edition for BI Features - must be on SharePoint SQL Server?

I need to install SQL Server 2012 for a new SharePoint 2013 installation.
Let's say I want to use the BI features of SharePoint 2013 like PowerView.
I already have a separate SQL Server running SQL Server 2012 BI Edition that is used as the database server for our data warehouse and some apps. But this SQL Server will not be used to house the SharePoint 2013 databases.
Do I need to install SQL Server 2013 BI Edition on the SharePoint 2013 SQL Server (where the SharePoint 2013 databases will be housed) or can I used SQL Server 2013 Standard Edition on that server and utilize the BI Edition on the data warehouse server to
use the BI features of SharePoint?

Yes, BI or Enterprise must be installed on the SharePoint server in order to integrate SSRS. PowerPivot can be on a separate server with just a download (http://www.microsoft.com/en-us/download/details.aspx?id=35577) for certain components residing on
the SharePoint server. This will give you PowerView, as well.
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.

SharePoint 2013 dev environment as standalone with DC - PowerShell in Azure?

Hi,
I am looking for a PowerShell script that create based on a Visual Studio 2013 Azure image a dev environment in azure. I need a Standalone server with DC / SQL / SharePoint 2013 on one server.
Provide Microsoft a script for this requirement?
Regards,

First off, Microsoft does not support SharePoint 2013 on a Domain Controller. Here are some scripting resources, however:
http://msdn.microsoft.com/en-us/library/windowsazure/dn385843.aspx
https://github.com/WindowsAzure/azure-sdk-tools-samples/wiki/Automated-Deployment-of-SharePoint-2013-with-Windows-Azure-PowerShell
http://blogs.msdn.com/b/windowsazure/archive/2013/05/24/automating-sharepoint-deployments-in-windows-azure-using-powershell.aspx
http://blog.appliedis.com/2013/04/29/automating-sharepoint-2013-installation-on-windows-azure-iaas/
http://absolute-sharepoint.com/2013/10/create-a-scripted-sharepoint-2013-development-environment-tutorial-part-1.html
Trevor Seward, MCC
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.

Server 2012 R2 support in SHarePoint 2013

When 2012 R2 is released will SharePoint 2013 be able to run on it? i've seen there are issues with Preview currently....my server admins would rather build machines in r2 for long term but asked my preference.

I would say the Windows Server 2012 R2 does support SharePoint 2013 installation. It's simply because the R2 is still built on the foundation platform of Windows Server 2012. Microsoft hasn't officially published the compatibility of Windows Server 2012
R2 for SharePoint 2013 though.
Thuan Soldier
A 23-year-old man loving Microsoft technologies and making crazy ideas on business journey.
SharePoint Vietnam |
Blog | Twitter

Setting up Sharepoint 2013 for apps

I may have screwed up the appropriate permissions for the service accounts/application pools necessary to get store apps to work. At this point I think I need to start over, but the rest of our Sharepoint install is working. Can I safely remove the App Management
Service Application and Proxy plus the Subscription Settings Service Application and Proxy?
Our Sharepoint 2013 installation is pretty basic - just the Sharepoint application server and a 2012 database server.

Hi,
Any Service Application can be deleted and recreated again. Just make sure that your farm is not depended of the service application while you delete it. One way is to remove the association and see if your Web application work correctly! Make also sure
if you need to keep the service application database or not! If you choose to delete the related data, SQL databases will be deleted too.
Note that Subscription Settings Service Application can't be created using the UI. You need Powershell, see below:
New-SPSubscriptionSettingsServiceApplication -ApplicationPool "SharePoint Web Services Default" -Name "Subscription Settings Service Application" -DatabaseName "SubscriptionSettingsDB"
| New-SPSubscriptionSettingsServiceApplicationProxy
Regards
Henrik A. Halmstrand
sharepointrevealed.com
getspconfig.codeplex.com
Please click Mark As Answer; if a post solves your problem or Vote As Helpful; if a post has been useful to you.

Sharepoint 2013 installation modules

Similar Messages

Maybe you are looking for