We met an issue on Office Web App with SharePoint 2013.

Error message on the page:

Sorry, there was a problem and we can't open this document. If this happens again, try opening the Microsoft Word.

There is no related log in Windows Event viewer.

In SharePoint ULS log, related message as below:

08/12/2014 06:42:45.49 w3wp.exe (0x2C90)                        0x2FE0  SharePoint Foundation                 Claims Authentication                         ahds8    Unexpected       SPJsonWebSecurityBaseTokenHandler: Issuer name in token '00000003-0000-0ff1-ce00-000000000000@testrealm' doesn't match any of the registered issuer names for trusted sts 'collaboration metadata'.                7ba9aedb-4658-4a32-aaaa-20bcd0d52be6
08/12/2014 06:42:45.49 w3wp.exe (0x2C90)                       0x2FE0  SharePoint Foundation                 Monitoring                         b4ly                Medium               Leaving Monitored Scope (Application Authentication Pipeline). Execution Time=7,5254676222816                7ba9aedb-4658-4a32-aaaa-20bcd0d52be6
08/12/2014 06:42:45.49 w3wp.exe (0x2C90)                       0x2FE0  SharePoint Foundation                 Application Authentication                    ajezu     Unexpected       SPApplicationAuthenticationModule: Failed to authenticate request, unknown error. Exception details: System.IdentityModel.Tokens.SecurityTokenException: Issuer name is not registered     at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityBaseTokenHandler.ValidateTokenIssuer(X509SecurityToken signingKey, String tokenIssuer)     at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityBaseTokenHandler.ValidateToken(SecurityToken token)     at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityTokenHandler.ValidateToken(SecurityToken token)     at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.TryExtractAndValidateToken(HttpContext httpContext, SPIncomingTokenContext& tokenContext)     at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.ConstructIC...              7ba9aedb-4658-4a32-aaaa-20bcd0d52be6
08/12/2014 06:42:45.49*               w3wp.exe (0x2C90)                       0x2FE0  SharePoint Foundation                 Application Authentication                  ajezu     Unexpected       ...laimsPrincipalAndSetThreadIdentity(HttpApplication httpApplication, HttpContext httpContext, SPFederationAuthenticationModule fam)     at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.AuthenticateRequest(Object sender, EventArgs e)            7ba9aedb-4658-4a32-aaaa-20bcd0d52be6
08/12/2014 06:42:45.49 w3wp.exe (0x2C90)                       0x2FE0  SharePoint Foundation                 General                                8nca                Medium               Application error when access /sites/111/_vti_bin/wopi.ashx, Error=Issuer name is not registered   at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityBaseTokenHandler.ValidateTokenIssuer(X509SecurityToken signingKey, String tokenIssuer)     at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityBaseTokenHandler.ValidateToken(SecurityToken token)     at Microsoft.SharePoint.IdentityModel.SPJsonWebSecurityTokenHandler.ValidateToken(SecurityToken token)     at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.TryExtractAndValidateToken(HttpContext httpContext, SPIncomingTokenContext& tokenContext)     at Microsoft.SharePoint.IdentityModel.SPApplicationAuthenticationModule.ConstructIClaimsPrincipalAndSetThreadIdentity(HttpApplication httpApplication, HttpContext httpCont...              7ba9aedb-4658-4a32-aaaa-20bcd0d52be6

The farm is having 2 WFE. There is NLB setting up for them.

AAM has been set to Default.

OWA binding set to -AllowHttp, zone set to internal-http. AllowOAuthOverHttp set to true.

The strange thing is when days ago we finish the installation, we try the link http://{server_name}/somefolder/document.docx to do the test, it works fine.

But today we try the link http://{NLB_link}/somefolder/documnet.docx, above error occur.

We are not sure whether AAM setting cause this issue or some other reaone. But even we remove the AAM to use the Server Name in link, still above issue.

Any idea/comments would be appriciated.

Hi

I have just uppgraded our news site from SP2010 to SP2013 without major incidents.
Though one small issue is that all our news post dates are blank. The user that posted the news and the news itself is ok. The site uses the publishing template.

anyone have any tips for fixing this?

brgs

Bjørn

Hi,

We have a customer that wanted to implement SharePoint 2013 Foundation Edition.

I would like to know whether the following functionalities are possible in SharePoint Foundation

1. Total Internal users 6000 (portal has to be accessed via internet and intranet) ? For SharePoint Foundation any additional license required other than Windows CAL ?

2. The SharePoint Foundation Servers should be able to Scaled out (multiple WFE and Load balanced) Are there any limitations for Foundation edition ?

3. Customer wanted to use Form Based Windows Authentication in the internet and Windows authentication in intranet ? Is this possible in Foundation edition ?

Please advise

Ready for Action

Hi

I try to hide the Site Contents from the Quick Launch 

I've tried it with "Edit Links" but can not be removed (it's located under the "Edit Links")

Thanks!

Hi

How much disk Space do SharePoint enterprise need ?

My SharePoint intranet site could not open more and I could not
open the administration site more

I could see that I have 5 G back on the C

So how much do SharePoint need

Hi,

I have a sharepoint 2013 setup which was pointing to a database server(call it DBOLD). DBOLD was shut down due to some issue and we got a new DB server (call it DBNEW). As per the info i have the DBOLD was shut down and config wizard was run to connect to the DBNEW The SP2013 setup is currently pointing to DBNEW and sharepoint is working fine.(The new content databases are getting created in the DBNEW instance).

The issue is when i login to central admin and go to manage servers in farm, the database it is pointing to still shows it as DBOLD(screenshot attached).

I need to update this to show it as DBNEW.

Installed Service Pack 1 on a SharePoint 2013 environment.  However when executing the Products Configuration Wizard or psconfig via powershell I keep getting the same error below.

08/11/2014 04:02:38  18  ERR                  Task upgrade has failed with an unknown exception

08/11/2014 04:02:38  18  ERR                  Exception: Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade-20140811-040150-359 was updated by Domain\SpAdmin, in the psconfigui (4724) process, on machine Server1.  View the tracing log for more information about the conflict.

   at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure)

   at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()

   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Update()

   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ProgressUpdateEventHandlerMethod(Object sender, SPProgressUpdateEventArgs args)

   at Microsoft.SharePoint.Upgrade.SPUpgradeSiteSession.set_Percentage(Double value)

   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.SetOverallProgressPercentage(Double percentage)

   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.PercentageFinished()

   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.FinishOnLocalThread()

   at Microsoft.SharePoint.Upgrade.SPManager.RunUpgradeSiteSessionCore(Object lockObject, SPSite site, SPUpgradeOperationFlags upgradeOperationFlags, Boolean checkConcurrentSiteUpgradeSession)

   at Microsoft.SharePoint.Upgrade.SPManager.<>c__DisplayClass2.<RunUpgradeSiteSession>b__0()

   at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param)

   at Microsoft.SharePoint.Upgrade.SPManager.RunUpgradeSiteSession(SPSite site, SPUpgradeOperationFlags upgradeOperationFlags, Boolean sendEmail, Boolean checkConcurrentSiteUpgradeSession)

   at Microsoft.SharePoint.SPSite.StartUpgradeBypassAllowUpgradeCheck(SPSiteUpgradeType upgradeType, Boolean queueOnly, Boolean consoleOutput, Boolean throwIfUpgradeNotNeeded, Boolean sendEmail, Boolean checkConcurrentSiteUpgradeSession)

   at Microsoft.SharePoint.SPSite.Upgrade(Boolean recursively)

   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)

   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)

   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)

   at Microsoft.SharePoint.Administration.SPDatabase.Upgrade(Boolean recursively)

   at Microsoft.SharePoint.Administration.SPContentDatabase.<>c__DisplayClass2.<Upgrade>b__0()

   at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param)

   at Microsoft.SharePoint.Administration.SPContentDatabase.Upgrade(Boolean recursively)

   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)

   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)

   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)

   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)

   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)

   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)

   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)

   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)

   at Microsoft.SharePoint.Upgrade.SPManager.InplaceUpgradeAdministrationWebApplication()

   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()

   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Below are steps I have already tried all with the same results.  I am looking for anything not already listed that may have worked for you.

1. 1st Solution Attempt
   1. Reboot all servers in farm
   2. Clear Config Cache on all servers
   3. IISReset
   4. Psconfig.exe –cmd –upgrade –inplace b2b –force –cmd applicationcontent –install –cmd installfeatures
2. 2nd Solution Attempt
   1. Stsadm –o setproperty –pn command-line-upgrade-running –pv No (on all servers)
   2. IIS Reset
   3. Restart the Windows SharePoint Timer
   4. Psconfig –cmd upgrade –inplace b2b –wait –force
   5. Then also psconfig –cmd upgrade –inplace b2b –force –cmd applicationcontent –install –cmd installfeatures –cmd installcheck -noinstallcheck
3. 3rd Solution Attempt
   1. Stsadm –o setproperty –pn command-line-upgrade-running –pv Yes (on all servers)
   2. Stsadm –o setproperty –pn command-line-upgrade-running –pv No (on all servers)
   3. IIS Reset
   4. Restart the Windows SharePoint Timer
   5. Psconfig –cmd upgrade –inplace b2b –wait –force
   6. also psconfig –cmd upgrade –inplace b2b –force –cmd applicationcontent –install –cmd installfeatures  –cmd installcheck –noinstallcheck
4. 4th Attempt
   1. Install next Stable CU after SP1 per link
   2. Stsadm –o setproperty –pn command-line-upgrade-running –pv No (on all servers)
   3. IIS Reset
   4. Restart the Windows SharePoint Timer
   5. Psconfig –cmd upgrade –inplace b2b –wait –force
   6. also psconfig –cmd upgrade –inplace b2b –force –cmd applicationcontent –install –cmd installfeatures  –cmd installcheck –noinstallcheck

1. Stsadm –o setproperty –pn command-line-upgrade-running –pv Yes(on all servers)
2. IIS Reset
3. Restart the Windows SharePoint Timer
4. Psconfig –cmd upgrade –inplace b2b –wait –force

Hello,

I installed a new 3-Tier environment and a developer's environment (SharePoint 2013 Enterprise / Windows Server 2012), everything went fine and all the services are working correctly, but I cannot see any forms (ex : default workflow association form) with Internet Explorer(tried with 10 and 11).

Those forms work perfectly fine in Chrome or Firefox, but in Internet Explorer, I get the error :

SEC7113: css was ignored due to mime type mismatch

on the item FormResource.aspx

I have never had this error on other environments, before.. I tried looking into the IIS mime types, tried looking into it with Fiddler, but couldn't find anything helpful.

I tried accessing another SP Farm outside of the Intranet and could access those forms with IE, so I'm guessing it is not a problem with IE's configuration but more a server-side problem.

Has anyone ever have this problem, or does anyone have an idea to how I could solve it ?

Thanx,

Antonin

Hi, I have Sharepoint 2013 Foundation, I extended web app in order to provide external access. When I use basic authentication I can log in from LAN and use sharepoint, but when I change to integrated (NTLM) log in screen pops up repeatedly.

Any ideas?

Hello,

We are having 5 servers in the farm and I'm applying april 2014 CU in SP2013 envirment. Now PSconfig completed successfully on 4 servers but It's failing only on one server. I see that When I kick off the PSConfig, It stops the sharepoint timer job and sharepoint administator service and then It never restarts. So when PSconfig reaches to "Upgrading SharePoint Products", It takes a long time and then gives exceptions/errors and finally It gets failed.

In the error log, I see below errors for multiple features,

An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.
  Additional exception information: Upgrade completed with errors.  

ERROR	Feature upgrade incomplete for Feature 'Feature Name' (Id: 15/'7e29c5c3-cca5-4a94-898c-abeccf77e947') in Farm 'Farm'. Exception: Failed to add web config modification for SPResourcesExpressionBuilder.  (Inner Exception: The Windows SharePoint Services Web.Config Update timer job has taken longer than 5 minutes to complete.)	00000000-0000-0000-0000-000000000000

I think It's beacuse of the sharepoint timer job nevers gets started. I can mananully started the sharepoint timer job after the PSconfig failed.

Can someone please help?

Thanks

I'm working out all the bugs in the SharePoint 2013 environment. Right now I'm trying to get a SP 2013 Workflow to actually work.

I'm trying the simplest thing I can.  Just go to the end of the workflow.

I've got one stage.  In transition I have GOTO "End of Workflow". 

When I start the workflow it creates the page as if it is running but stays stuck under "Running Workflows".  It does not log anything if I attempt to write a log.

I've tried this on both a new and updated (from 2010) site.  Neither work.  SP10 workflows work fine.

David Jenkins

I plan to use sharepoint hybrid

I want to know how does the user profile service work

is it going to use two services ? one is in online ,one is on local ?

actually i want to use one user profile service both online and onpremises can use

Hi all,

I have a question about connecting multiple Active Directories to SharePoint 2013.

We are building a SharePoint 2013 environment with several Web Applications. Each Web Application hosts the SharePoint environment of a different company.

Each company has their own UPS which has to connect to the company AD located in the company network. The different companies may not see users of the other companies in the people picker.  The users has to sign in with SSO.

What is the best way to accomplish this? 

Mark

Hi,

I've managed to configure my farm so that  Microsoft Online Directory Services (Office 365 etc.) can be used for STS authentication, but what I'm actually trying to do is allow user authentication - that is, I'm hoping to be able to use the user's O365 credentials to authenticate them in my own farm so they can view certain parts of it. If I need to write my own login form or authentication provider or whatever that's fine, as long as the user doesn't need to enter anything when they access my farm (provided they already have cached O365 credentials in their browser session).

FWIW I actually need to be able to support the possibility that users are coming from multiple O365 tenancies, whereby each site collection will be configured to allow users from a different O365 tenancy (more or less).

If it's not possible to do with my own development farm on a PC, it is possible if the farm is hosted in Azure?

Thanks

Dylan

Hi everyone,

We're currently experiencing some issues saving a site as an template.

This is the error we get in the event viewer:

Exception information: 
    Exception type: InvalidOperationException 
    Exception message: Error saving solution to temporary file
   at Microsoft.SharePoint.SPSolutionExporter.ExportWebAsSolution()
   at Microsoft.SharePoint.SPSolutionExporter.ExportWebToGallery(SPWeb web, String solutionFileName, String title, String description, ExportMode exportMode, Boolean includeContent, String workflowTemplateName, String destinationListUrl, Action`1 solutionPostProcessor, Boolean activateSolution)
   at Microsoft.SharePoint.ApplicationPages.SaveAsTemplatePage.BtnSaveAsTemplate_Click(Object sender, EventArgs e)
   at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

I've looked everywhere for this error and all the sites point to a permission issue; I've check that already: it isn't. We've tried creating this template via PowerShell, C# command line application, SharePoint Designer and the savetmpl.aspx page at the site itself: no result; Yes, it is a publishing site, but that didn't stop us. We've created a site template from a different site and the publishing feature was also enabled there.

Later this site really helped me into digging deeper into the logs: http://www.sharepointblogs.be/blogs/vandest/archive/2014/05/23/sharepoint-how-to-troubleshoot-issues-with-save-as-template.aspx

The annoying part is: the folder that is being created by the web application pool user when saving the site as a template is totally empty!

How can this be? Did I miss something? Could someone help me with this issue?

Thanks in advanced!

With kind regards,

M. Hekman

Hello,

Is-it possible to apply a workflow to all documents (site and subsites) ?

I created a reusable workflow who works well in just one site for now but i would like to apply it on each futur subsite created automatically by powershell. 

I'm currently trying wsp package deployment for each subsites but when i try to manually associate the workflow to a list, i do not see it in "Select Workflow Template"

Powershell part for adding wsp + association to list

#Include the additional dll references required
[Void] [System.Reflection.Assembly]:: LoadWithPartialName("System")
[Void] [System.Reflection.Assembly]:: LoadWithPartialName("Microsoft.SharePoint.Workflow")
#open the web
$web = Get-SPWeb "http://site/subsite"
#list to which the workflow is to be associated
$list=$web.Lists["List"];
#create workflow association object
$culture=new-object System.Globalization.CultureInfo("en-US");
$basetemplate = $web.WorkflowTemplates.GetTemplateByName("Workflow test",$culture);
$wftasklist=$web.Lists["Workflow Tasks"];
$wfhistorylist=$web.Lists["Workflow History"];
$wfAssoc=[Microsoft.SharePoint.Workflow.SPWorkflowAssociation]:: CreateListAssociation($basetemplate,"list",$wftasklist,$wfhistorylist);
#associate workflow to list
$list.AddWorkflowAssociation($wfAssoc);
$list.Update();
#cleanup and end
$web.Dispose();	

Error :

Exception calling "CreateListAssociation" with "4" argument(s): "Value cannot
be null."
At line:1 char:1
+ $wfAssoc=[Microsoft.SharePoint.Workflow.SPWorkflowAssociation]::
CreateListAssoc ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : ArgumentNullException

$basetemplate is empty

If anyone can help me.

thank you !!

Hi

I am in the process of doing a SP 2010 to 2013 upgrade for a number of extranet sites that use FBA. Both environments have now been configured to use the same membership services database. I have done a database attached upgrade and all looked okay. We originally created users in the 2010 env. and assigned them to roles which are assigned various permissions read, contribute, update etc. this works fine in 2010. In 2013 the users cannot login. People picker in 2013 sees users and roles also if I add a user to say owners they can login. if i check permissions within 2010 it shows users in roles, in 2013 it misses all role based permissions. I have a number of servers in the farm and have configured the web app, STS on all the servers and CA to use FBA. Like I say it sees the roles but does not seem to recognise a user is in a role which I don't understand.

I have ran out of ideas.

Any assistance would be appreciated and thanks in advance.

Phil 

I am currently using SharePoint Online and loving it, but I have come across one item that is giving me a problem. I am working on creating a corporate intranet site and when I add the "Announcements" web part it only allows me to display one announcement at a time -- I'd like to be able to show two or three rows of two or three announcements per row -- but I am only able to click an arrow to go to the next one so there is ALOT of wasted space on the page. One of the things that I really like about the announcements web part is that it is clean and having the ability to put a picture behind the next and then see more of the information after hovering over it is just awesome in my opinion.

Could someone please assist or suggest another alternative?

Currently I want to move my site collection from staging server to production, using Backup & restore site collections.

But my question is whether backup then restore a site collection will move all the web parts ? or I need to move the web parts separately ?