Strausy's O365/SharePoint KB

I have been pulling my limited hair out for a week trying to figure out why a Site Owner will Full Control on the site would always get denied when they tried to respond to Access Requests. When they received the email and clicked on " Accept or decline this request " which goes to https://[siteurl]/ Access Requests/pendingreq.aspx they would get " Sorry, this site hasn't been shared with you. " Preliminary Troubleshooting Steps I went through each and every permission group on the site to make sure the Site Owner group was the owner of the group. I went through each list or library that had broken site permissions and made sure the Site Owners group had Full Control of those as well. They all did. Then I looked at the Permission Level of the Site Owner's group. It said Full Control, but it also had that awful "Limited Access" permission. This site had many owners and many times they all tried their best to limit access to certain things and...

SharePoint_Server_Name = Trouble_Ahead I recently had a friend of mine ask for some SharePoint 2013 troubleshooting help. It seemed that the server was running fine (Single Server Farm) but trying to configure a Secure Store Target Application for Excel Services that was causing grief. The error message was  "Your session has expired. Restart this wizard to continue." The Correlation ID has a few errors, but one in particular stated  "_admin/sssvc/ managetargetapplicationinstanc e.aspx' doesn't match the Page '_admin/sssvc/ managetargetapplicationfields. aspx"  which in itself is not very useful.  But looking more into that error and noticing the server name is  sharepoint_dev  a light went on and a feeling of dread for said friend.  SharePoint doesn't like underscores in server names, especially service apps on a single server farm where Central Admin is using the server name as the URL.  You have two options really.  You c...

This post is something I encountered for the first time I can remember. Honestly, this may have happened before, but not in the last 3+ years of patching SharePoint 2010/2013 have I encountered the following error; "The installation of this package has failed." I've had my fair share of Config Wizard failing, but never the initial binaries failing. Did a bit of digging and the root cause was me, having had to only use one executable for patching SharePoint, not paying attention to the CU hotfix package. This particular package extracted an extra cab file, specifically ubersrv_1.cab. I mistakenly deleted that file and just tried to use the .exe. Thanks to http://blogs.msdn.com/b/kaevans/archive/2013/06/11/sharepoint-2013-kb2726992-the-installation-of-this-package-failed.aspx for steering me in the right direction. If it were not for Google/Bing/Yahoo (insert search engine of choice) I would still be perplexed.

Recently a SharePoint farm I am working with was only showing a specific Help item. It was the most recent third-party tool and nothing else. Within each Site Collection is a Help Settings link. This determines what Help Collections you can show to a user and typically contain at least the SharePoint 2010 help, but this was missing. Stumbling through little or nothing, I found that the actual help items are stored in "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\HCCab\[language id], which in the English language pack is 1033. There were plenty of files here, but not seemed to be installed. Using SharePoint Management Shell you can find out what Help Collections are installed. Get-SPHelpCollection is detailed on this TechNet article . To fix this, the Help Collections simply needed to be installed using Install-SPHelpCollection, detailed in this TechNet article . So I simply ran Install-SPHelpCollection -LiteralPath ‘C:\Program Files\Common File...

The issue at hand is when you go to Site Actions > Site Settings >  People and Groups. Under the Quick Launch the Groups are displayed. If you select "More..." you go to the /_layouts/groups.aspx page to hopefully sell all the SharePoint groups listed in that Site Collection. For some unknown reason I can only see the first 30 groups. This happens in 2 of the 5 SharePoint 2010 environments I have tried this on. Some have many site collections, some have 1, some are pre-SP1 and some are post SP1.  As usual, when I write a post it is because I had a hard time finding the exact fix for my problem. There are a few other blog posts out there with the same issue, but they did not fix the issue for me. I will list those below if it may help someone else. The fix for me was actually a comment on another post on SharePoint 2007 with the same issue by "Carlos J Sosa M" which was quite easy to do, unlike finding GUIDs and the like. I have modified for clarity. 1...

I recently had a user state they could not publish an InfoPath form to a SharePoint Form library that was not setup for InfoPath Forms Services. Since that required an Enterprise CAL it was not enabled until a license was purchased. During the troubleshooting I walked through their form and verified it was set to the correct Compatibility level. I went into the Form Library that was created and verified "Open in Client Application" was also selected, but each time the error was that InfoPath couldn't find the server. Having reproduced this on several sites and even different web applications and several farms, I knew it had to be either proxy or network related. I've seen numerous post about that exact error, but could not pinpoint a fix. I progressed down the path of it being a proxy issue, a LAN setting, etc., but I was wrong! A big clue came when I notice the "New Document" was active even though I had not published a Form yet. When I clicked on i...

I recently had an issue where Spell Check was not working for any site, any site collection or any web app in SharePoint 2010. It also occurred in two different SharePoint farms. The error message was "The spelling check cannot be completed because there is no dictionary installed for the current language." and occurred in any list item or page where spell check was an option. Although you can enable/disable the Spell Checker feature in Central Admin in Manage Farm Features, it was already Activated. Deactivating and re-Activating did not resolve it. A few other posts I read indicated it may be a permissions issue relating to the SharePoint permission levels, but those turned out to be a dead end as well The ultimate fix was actually file permissions on the server. I did not have the local "Users" group granted Read access on the Program Files folder where SharePoint was installed. I granted that group this right, did and IISRESET an SharePoint Spell Chec...