Hi,

I am trying to run the following warmup script on my sharepoint 2013 server. I am logged on with my farm administrator account, I have tested that I can connect to the sites by browsing to them and authenticating manually.

Can anyone help me workout why I still get this 401 error when I run the script?

Thanks

I am trying to create multiple URLs for single host named site collection and single zone (Default) using Set-SPSiteURL but I keep getting following error:

"Set-SPSiteURL : Could not set URL http://site2.domain.local/ for zone Default because a URL is already set for the zone. To set a URL for this zone, first remove the existing URLhttp://site1.domain.local/"

Command that I run is: "Set-SPSiteURL -Identity http://site1.domain.local -Url http://site2.domain.local -Zone 0"

If I understood correctly, in SharePoint 2013 you can have multiple URLs configured for single host named site collection and in single zone (in this case zone is Default) but it seems that Set-SPSiteURL cannot do this.

In our environment web application has "standard" root site collection (not host named) using URLhttp://servername and additional host named site collection and with Set-SPSiteURL I cannot create additional URLs per zone in any. Creating additional URLs in different zone (e.q. in Intranet zone) is working ok:

"Set-SPSiteURL -Identity http://site1.domain.local -Urlhttp://site2.domain.local -Zone 1"

but then again creating additional URLs in Intranet zone (Zone 1) returns error mentioned above.

Was anybody successful using Set-SPSiteUrl for multiple URLs per zone, does this maybe work only in multi-tenancy mode (our environment is not multi-tenancy).

Thanks in advance,
Bojan

Hello,

We're having an issue with people who have Office 2013 installed and are trying to open shared office documents from SharePoint. This problem does not come up for people with Office 2010 installed.

The error they get is: "To open this workbook, your computer must have a version of Microsoft Excel installed and your Web browser must support opening files directly from Excel in the browser."

This has only happened to people running Office 2013 on their computer. They can open the file in the browser, but as soon as they try to "Open in Excel" or Word, etc they receive that error. Also these files are opened using Internet Explorer, so that shouldn't be a problem. 

I am working on upgrading SharePoint 2010 to SP3, but am not convinced that this is all I need to do for this to work properly. Any ideas/suggestions are greatly appreciated!

We current have Dynamics ax 2012 and use Sharepoint 2010 for the enterprise portal.

Can we upgrade our Sharepoint installation to 2013 and still host the enterprise portal on ths instance of sharepoint?

Hi

i´m trying to add FBA users to a sites using power shell, and i´m using:

$web = Get-SPWweb http://url

$user = New-SPUser -UserAlias (New-SpClaimsPrincipal -Identity name@example.com -IdentityType $ip ).ToEncodedString() -Web $web

where as found in get-help New-SPClaimsPrincipal

$ip = New-SPIdentityProvider -ASPNetMembershipProvider "myMembershipProvider" -ASPNetRoleProvider "myRoleProvider"

but i could not found New-SpidentityProvider on my powershell

Thanks

hellow all ,

i need hindi language pack for sharepoint server 2013 . i searched on internet but can not find

please any one suggest the url to download. 

Thanks in Advance.

while creating Classic web applicatiuon using powershell commands following error occure

Hello

I would like to update information about Host named Site Collection (HNSC) and also have a place where all the doubts can be answered. So i will check Q&A to keep this discussion up-to-date.

First of all the process to create a HNSC. After some try and fail times i found the most appropriate method to create HNSC sites is the one explained from Critical Path Training, LLC:

1st ensure you delete the standard web application created by the configuration wizard the one created on port 80. delete all web app, content database.

2nd DNS modifications:

if your web server is on test.local, please add a Host entry on this domain with name * and ip the same as your webserver. This way any request to a http://*.test.local is going to be redirected to the webserver/sharepoint.

3rd run the following script (some modifications from original please modify your values at the beginning):

# =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
#       Script: SetupSharePointForHNSC.ps1
#
#       Author: Critical Path Training, LLC
#               http://www.CriticalPathTraining.com
#
#  Description: Configures a SharePoint 2013 install for hosting Host-Named Site Collections (HNSC).
#               This involves creating a Web Application in SharePoint that has no host header bindings.
#               Using DNS, all requests are mapped to this Web Application. You then create the site collections
#                   via PowerShell as you can't create HNSC's via the browser (Central Administration).
#
# Optional Parameters:
#               $WebApplicationName - Name of the Web application to create to host HNSC's.
#                 DEFAULT - "SharePoint HNSC Host - 80"
#               $AppPoolName - Name of the app pool to create to host the HNSC Web Application.
#                 DEFAULT - "SharePoint Default HNSC AppPool"
#               $ManagedAccountUsername - Username of the managed account to create for the app pool's identity.
#                 DEFAULT - WINGTIP\SP_Content
#               $AdminAccountUsername - Administrator of the domain.
#                 DEFAULT - WINGTIP\Administrator
#               $WfeName - SharePoint WFE name.
#                 DEFAULT - WINGTIPALLUP
#               $DeleteCACreatedWebApp - Flag indicating if the default Web Application ceated by CA 
#                 should be deleted.
#                 DEFAULT - TRUE
#               $CreateDefaultSiteCollections - Flag indicating if two default site collections should be created.
#                 These are intranet.wingtip.com (team site) & dev.wingtip.com (developer site).
#                 DEFAULT - TRUE
# =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=

param(
	[string]$WebApplicationName = "SharePoint HNSC Host - 80",
	[string]$AppPoolName = "SharePoint Default HNSC AppPool",
	[string]$ManagedAccountUsername = "MACHINE1\SP_Content",
	[string]$AdminAccountUsername = "MACHINE1\Administrador",
	[string]$WfeName = "MACHINE1",
	[switch]$DeleteCACreatedWebApp = $true,
	[switch]$CreateDefaultSiteCollections = $true
)
$ErrorActionPreference = 'Stop'
#not used now
$appHostDomain = "apps.test.local"

Write-Host
Write-Host "Configuring SharePoint Server 2013 Hosting Named Site Collection" -ForegroundColor White
Write-Host " Script Steps:" -ForegroundColor White
Write-Host " (0) Validating parameters..." -ForegroundColor White
Write-Host " (1) Verify SharePoint PowerShell Snapin Loaded" -ForegroundColor White
Write-Host " (2) Deleting default Central Administration Created Web Application" -ForegroundColor White
Write-Host " (3) Verifing / Creating New App Pool Managed Account" -ForegroundColor White
Write-Host " (4) Creating New Web Application to Service HNSC's" -ForegroundColor White
Write-Host " (5) Creating Default Site Collections" -ForegroundColor White
Write-Host

#
# verify parameters passed in
#
Write-Host "(0) Validating parameters..." -ForegroundColor White
if ($WebApplicationName -eq $null -xor $WebApplicationName -eq ""){
	Write-Error '$WebApplicationName is required'
	Exit
}
if ($AppPoolName -eq $null -xor $AppPoolName -eq ""){
	Write-Error '$AppPoolName is required'
	Exit
}
if ($ManagedAccountUsername -eq $null -xor $ManagedAccountUsername -eq ""){
	Write-Error '$ManagedAccountUsername is required'
	Exit
}
if ($WfeName -eq $null -xor $WfeName -eq ""){
	Write-Error '$WfeName is required'
	Exit
}



# Load SharePoint PowerShell snapin
Write-Host
Write-Host "(1) Verify SharePoint PowerShell Snapin Loaded..." -ForegroundColor White
$snapin = Get-PSSnapin | Where-Object {$_.Name -eq 'Microsoft.SharePoint.PowerShell'}
if ($snapin -eq $null) {
	Write-Host "    ..  Loading SharePoint PowerShell Snapin" -ForegroundColor Gray
    Add-PSSnapin "Microsoft.SharePoint.PowerShell"
}
Write-Host "    Microsoft SharePoint PowerShell snapin loaded" -ForegroundColor Gray 



Write-Host
Write-Host "(2) Deleting default Central Administration Created Web Application..." -ForegroundColor White
if ($DeleteCACreatedWebApp -eq $true){
  Write-Host "    .. searching for default Web App, created by Central Administration..." -ForegroundColor Gray 
  $defaultWebApp = Get-SPWebApplication | Where-Object {$_.DisplayName -eq $WebApplicationName}
  if ($defaultWebApp -eq $null) {
    Write-Host "    .. failed to find default Web App" -ForegroundColor Yellow
    Write-Host "    Skipping this step" -ForegroundColor Yellow
    Write-Host "    ACTION: you should check Central Administration to see if a default Web App is present; having two default Web Apps is going to cause problems" -ForegroundColor Yellow
  } else {  
    Write-Host "    Found default web app, name = " $defaultWebApp.DisplayName -ForegroundColor Gray 
    Write-Host "    .. deleting default Web App..." -ForegroundColor Gray 
    Remove-SPWebApplication -Identity $defaultWebApp -DeleteIISSite -RemoveContentDatabases -Confirm:$false
    Write-Host "    Default Web App deleted" -ForegroundColor Gray 
  }
} else {
  Write-Host "    Skipping this step per parameter passed in" -ForegroundColor Gray 
}



Write-Host
Write-Host "(3) Verifing / Creating New App Pool Managed Account..." -ForegroundColor White
Write-Host "    .. Checking for existing managed account for user $ManagedAccountUsername..." -ForegroundColor Gray 
$managedAccount = Get-SPManagedAccount -Identity $ManagedAccountUsername -ErrorAction SilentlyContinue
if ($managedAccount -ne $null) {
  Write-Host "    Found existing managed account for $ManagedAccountUsername, skipping this step" -ForegroundColor Gray 
} else {
  Write-Host "    .. creating new managed account for $ManagedAccountUsername..." -ForegroundColor Gray 
  Write-Host "    .. obtaining reference to $ManagedAccountUsername account that will be a managed account for apps and Web Applications..." -ForegroundColor Gray 
  $securePassword = ConvertTo-SecureString "Password1" -AsPlainText -Force
  $contentAccountCredentials = New-Object System.Management.Automation.PSCredential($ManagedAccountUsername, $securePassword)
  Write-Host "    .. creating managed account for $ManagedAccountUsername..." -ForegroundColor Gray 
  $managedAccount = New-SPManagedAccount $managedAccountCredentials
  Write-Host "    $ManagedAccountUsername is now a managed account in SharePoint" -ForegroundColor Gray 
}



Write-Host
Write-Host "(4) Creating New Web Application to Service HNSC's..." -ForegroundColor White
Write-Host "    .. obtaining Active Directory claims authentication provider..." -ForegroundColor Gray 
$authProvider = New-SPAuthenticationProvider
Write-Host "    .. creating a new web application..." -ForegroundColor Gray 
$hnscWebApp = New-SPWebApplication -Name $WebApplicationName -AuthenticationProvider $authProvider -ApplicationPool $AppPoolName -ApplicationPoolAccount $managedAccount -DatabaseName "WSS_Content_HNSCDefaultHost"
Write-Host "    New HNSC Web Application created" -ForegroundColor Gray 
Write-Host "    .. creating default site collection at root without a template..." -ForegroundColor Gray 
$rootSite = New-SPSite -Name "Root HNSC Site Collection" -Url "http://machine01" -HostHeaderWebApplication $hnscWebApp -OwnerAlias $AdminAccountUsername
Write-Host "    Root site created" -ForegroundColor Gray 




Write-Host
Write-Host "(5) Creating Default Site Collections..." -ForegroundColor White
if ($CreateDefaultSiteCollections -eq $false) {
  Write-Host "    .. per parameter passed in, skipping this step" -ForegroundColor Gray 
} else {
  # create default team site
  Write-Host "    .. creating default team site..." -ForegroundColor Gray 
  $teamSite = New-SPSite -Name "Wingtip Intranet" -Url "http://intranet.network.com" -HostHeaderWebApplication $hnscWebApp -Template "STS#0" -OwnerAlias $AdminAccountUsername
  Write-Host "    Default team site created" -ForegroundColor Gray 
  # create default developer site
  Write-Host "    .. creating developer site..." -ForegroundColor Gray 
  $developerSite = New-SPSite -Name "Wingtip Developer Site" -Url "http://dev.network.com" -HostHeaderWebApplication $hnscWebApp -Template "DEV#0" -OwnerAlias $AdminAccountUsername
  Write-Host "    Developer site created" -ForegroundColor Gray 
}

Write-Host 
Write-Host "Finished configuring SharePoint Server 2013 for HNSC! Script details are as follows:" -ForegroundColor Green
Write-Host

Write-Host "=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=" -ForegroundColor White
Write-Host "Root Site Collection Details" -ForegroundColor White
Write-Host "Site URL:        " $rootSite.Url -ForegroundColor White
if ($CreateDefaultSiteCollections -eq $true) {
  Write-Host
  Write-Host "Default Team Site Collection Details" -ForegroundColor White
  Write-Host "Site Title:    " $teamSite.RootWeb.Title -ForegroundColor White
  Write-Host "Site URL:      " $teamSite.Url -ForegroundColor White
  Write-Host
  Write-Host "Developer Site Collection Details" -ForegroundColor White
  Write-Host "Site Title:    " $developerSite.RootWeb.Title -ForegroundColor White
  Write-Host "Site URL:      " $developerSite.Url -ForegroundColor White
}
Write-Host "=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=" -ForegroundColor White
Write-Host 

Now you have one WEB Application where you can host multiple (up to 200.000) site collections, and one database content where all your site collection is stored. The system (as Trevor below says) create a partition in the Web APP database using a Subscription ID field for this purpose.

Well once you have your Web APP and you site collections it's time to add the URL Zones to this Site collections and adjust your DNS zones.

Lets say that our SharePoint Web/App server is on a private network and we have a NAT server that exposes a 90.90.90.90 IP (dev.network.com) to our private machine 10.10.10.10 (machine1) and want to use http://dev to reach the http://dev.network.com site collection created before

We use the following Shell command to create an alternate URl on the intranet zone:

$site = Get-SPSite "http://dev.network.com" (this url is on the default zone because was the one we use to create the collection

Set-SPSiteURL -Identity $site -Url http://dev -Zone 1 (0 for default, 1- for intranet, 2- etc)

And now lets introduce the ip resoluction for dev. We have two options in the hosts file or in the internal DNS of our site.

Now the questions and things to consider (please help)

why if i open a chrome/IE/Safari/firefox in the same machine with http://dev the applications as again and again for credentials? where is the mistake?

Thanks

I have just installed SharePoint 2013 in our domain.  I have two web servers sat on windows 2012 and a backend SQL 2008 r2 database.  We have a 2 way domain trust set up and I want people in both domains to be able to access sharepoint but I can't seem to configure it so.

However if for example I go to the C drive on my web server and view the properties of a folder and under security I try and add a user in for domain B I can so it does lead me to beleive that this is a sharepoint issue but how do I configure it so I can see that second domain?

We also have in place a sharepoint 2010 pilot environment and that can see users from domain b so maybe i'm missing something in my 2013 environment or Microsfot have changed something.

any advice would be much appreicated.

When I create a PerformancePoint report using PP Dashboard Designer and click preview, I get an error.  The error says my rdl cannot be found.

In Designer the report URL is: http://webapp.mysite.com/mysite/report.rdl

In the error I have http://webapp.mysite.com/mysite/mysite/report.rdl

for some reason it is duplicating the site name in the rdl path.  Does anyone know what is causing this or how to prevent it?

Thanks,

Vincent

Vincent

Hi,

After installing SharePoint 2013 successfully , we created User Profile Service Application i.e. User profile Service & User profile Synchronization Service are running. Also , FIM service is running. The issue is : "While creating a new connection by clicking in User Profile synchronization Connections ,able to populate the AD connections (Populate containers) but after clicking on OK , getting anerror - Thread is Aborted". No error is logged in SharePoint ULS and in Event Viewer.

Any help would be highly appreciated !!!

Regards,

Vipul Jain

Hello All!

Recently I migrated our exchange server from 2003 to 2010, it works well. But when I use OWA to log in, in the control panel, when I clicked the "Options"button, it showed "change password","Create rule"..., when I choose each one of the above actions, the OWA logged off itself, and in the loggin page, whatever user name or PWD I inputted, it did not allow me to login the OWA again.

any suggestions? Thank you very much.

Seems Forefront is only going to continue for Cloud hosted farms.  Does anybody have details of third partys who have a SharePoint 2013 on-prem compatible product now or in the pipeline.

Many thanks.

Brian T

I am getting an odd error after I install OWA - the test page works fine, but when I hit the default page to view the pages in browser I am getting the following error -

[KeyNotFoundException: The given key was not present in the dictionary.]
   Microsoft.Office.Web.Apps.Environment.WacServer.AFarmTopology.GetMachine(String machineName) +111
   Microsoft.Office.Web.Apps.Environment.WacServer.WSServiceInstanceFinderAdapter..ctor() +364

[TargetInvocationException: Exception has been thrown by the target of an invocation.]
   System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) +0
   System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) +159
   System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) +256
   System.Activator.CreateInstance(Type type, Boolean nonPublic) +127
   Microsoft.Office.Web.Common.EnvironmentAdapters.HostEnvironment.LoadAdapterInstance(AdapterLoadInformation adapterInfo, Boolean readAppConfigOnly) +154
   Microsoft.Office.Web.Common.EnvironmentAdapters.<>c__DisplayClass16.<BuildInstance>b__15() +168
   System.Lazy`1.CreateValue() +14389240
   System.Lazy`1.LazyInitValue() +91
   Microsoft.Office.Web.Common.ServiceInstanceFinder.RefreshList(Object state) +279

[OfficeServiceException: ServiceInstanceFinderAdapter did not return data on first request]
   Microsoft.Office.Web.Common.ServiceInstanceFinder.RefreshList(Object state) +1330
   Microsoft.Office.Web.Common.ServiceInstanceFinder..cctor() +282

[TypeInitializationException: The type initializer for 'Microsoft.Office.Web.Common.ServiceInstanceFinder' threw an exception.]
   Microsoft.Office.Web.Common.HttpHelper.AppendOfficeHeaders(HttpContext context) +37
   Microsoft.Office.Web.OpenFromUrl.OpenFromUrlHttpModule.BeginRequest(Object source, EventArgs e) +698
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +165

I have several Sharepoint 2010 Foundation solutions(wsps).   They activate withou issues in Office/365 sites that have been upgraded to Sharepoint 2013 (although I am told its not exactly Sharepoint 2013 but close).   However on a new Sharepoint 2013 Foundation site I installed on a Windows Server 2012 server I can not activate these solutions (although there are other simpler wsp that I could activate).

The activation error is Sorry Something went wrong. unknown exception in sandbox worker process.  Here is the ULS log trace

-  - An unknown exception occurred while executing a sandboxed code solution request in the worker process.\r\n|0 - userCodeWrapperType.FullName = "Microsoft.SharePoint.UserCode.SPUserCodeFeatureCallOutWrapper", userAssemblyGroup = ".UserCodeAssemblyGroupId = ", GroupId = "5CC4316D56C049059A2B3F8A2DF77937-64H18khiUct086o7UWw5NISbr1upFDAyV9bSukL+QXk="", .RootDirectoryPath = "C:\ProgramData\Microsoft\SharePoint\UCCache\8CF9F53D8AAFD55\5CC4316D56C049059A2B3F8A2DF77937%2D64H18khiUct086o7UWw5NISbr1upFDAyV9bSukL%2BQXk%3D-2"", siteCollectionId = a09390a5-6ab3-42f7-bd76-b927f57c838a - Inner Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.Remoting.RemotingException: An attempt to connect to the remote activator failed with exception 'System.Runtime.Remoting.RemotingException: Cannot resolve 'channel' template reference: 'http client'.   
 at System.Runtime.Remoting.Activation.RemotingXmlConfigFileParser.ReportUnableToResolveTemplateReferenceError(ConfigNode node, String referenceName, RemotingXmlConfigFileData configData)   
 at System.Runtime.Remoting.Activation.RemotingXmlConfigFileParser.ProcessChannelsChannelNode(ConfigNode node, RemotingXmlConfigFileData configData, Boolean isTemplate)   
 at System.Runtime.Remoting.Activation.RemotingXmlConfigFileParser.ProcessChannelsNode(ConfigNode node, RemotingXmlConfigFileData configData)   
 at System.Runtime.Remoting.Activation.RemotingXmlConfigFileParser.ProcessApplicationNode(ConfigNode node, RemotingXmlConfigFileData configData)   
 at System.Runtime.Remoting.Activation.RemotingXmlConfigFileParser.ParseConfigNode(ConfigNode rootNode)   
 at System.Runtime.Remoting.Activation.RemotingXmlConfigFileParser.ParseDefaultConfiguration()   
 at System.Runtime.Remoting.RemotingConfigHandler.LoadMachineConfigIfNecessary()   
 at System.Runtime.Remoting.RemotingConfigHandler.FindDelayLoadChannelForCreateMessageSink(String url, Object data, String& objectURI)   
 at System.Runtime.Remoting.RemotingServices.CreateChannelSink(String url, Object data, IMessageSink& chnlSink)   
 at System.Runtime.Remoting.RemotingServices.Unmarshal(Type classToProxy, String url, Object data)   
 at System.Runtime.Remoting.Activation.LocalActivator.DoRemoteActivation(IConstructionCallMessage ctorMsg)'.   
 at System.Runtime.Remoting.Activation.LocalActivator.DoRemoteActivation(IConstructionCallMessage ctorMsg)   
 at System.Runtime.Remoting.Activation.LocalActivator.Activate(IConstructionCallMessage ctorMsg)   
 at System.Runtime.Remoting.Messaging.ClientContextTerminatorSink.SyncProcessMessage(IMessage reqMsg)   
 at System.Runtime.Remoting.Activation.ActivationServices.Activate(RemotingProxy remProxy, IConstructionCallMessage ctorMsg)   
 at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(IMessage reqMsg)   
 at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)   
 at Microsoft.SharePoint.SPSite_SubsetProxy..ctor()     -
 -- End of inner exception stack trace ---    Server stack trace:    
 at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)   
 at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)   
 at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)   
 at System.Activator.CreateInstance(Type type, Boolean nonPublic)   
 at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)   
 at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)   
 at System.Activator.CreateInstance(Type type, Object[] args, Object[] activationAttributes)   
 at Microsoft.SharePoint.SPSite.__CreateInstance_SPSite(Boolean forStaticMethod, Object[] constructorParameters)   
 at Microsoft.SharePoint.SPSite.RegisterCallContextUserCodeToken__Inner(Byte[] userCodeToken)   
 at Microsoft.SharePoint.SPSite.RegisterCallContextUserCodeToken(Byte[] userCodeToken)   
 at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.SetBinaryTokens(Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext)   
 at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId)   
 at Microsoft.SharePoint.UserCode.SPUserCodeApplicationHostAppDomainRef.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId)   
 at Microsoft.SharePoint.UserCode.SPUserCodeAppDomain.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext, Boolean shouldUsageLog, Int32 currentProcessId)   
 at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcessProxyForShim.ExecuteInternal(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext)   
 at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcessProxy.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, Byte[] binaryUserCodeToken, Byte[] proxyOperationToken, SPUserCodeExecutionContext executionContext)   
 at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)   
 at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)    Exception rethrown
 at [0]:    
 at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)   
 at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)   
 at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.ExecuteDelegate.EndInvoke(IAsyncResult result)   
 at Microsoft.SharePoint.UserCode.SPUserCodeWorkerProcess.Execute(Type userCodeWrapperType, SPUserCodeCachedAssemblyGroup userAssemblyGroup, Guid siteCollectionId, SPUserToken userToken, String currentAffinity, SPUserCodeExecutionContext executionContext)

Earllibby

I am deploying a new Windows Server 2012 box with SharePoint Foundation 2013 and SQL Server 2012 Express.  I would like to get RBS working.  I have succesfully done this in the past with SPS 2010 and SQL 2008 but the 2013 / 2012 mix is giving me a bit of trouble.  Here is what has been done so far, all of these steps have worked.

- Ran SQL queryies to provision the filestream

- Installed the rbs.msi via the command prompt with correct instance name and database name

- Used power shell to enable RBS for my content database

This is a single server, single database setup.  When I execute the PowerShell command $rbss I do not get any errors, output says that rbs is enabled and the provder name is my new filtestream.  I can still upload documents to SharePoint.  However, none of the documents actually go to my d:\blobstore folder location that was provisioned in my sql queries.  I have not adjusted the default file size for rbs.  The instructions I followed were from here:http://technet.microsoft.com/en-us/library/ee748631.aspx

Please let me know where I can start to look to resolve this issue, any input is helpful.  Thank you.