Quantcast
Channel: SharePoint for Dummies
Viewing all 60 articles
Browse latest View live
↧

SharePoint 2013 Upgrade Check List

December 11, 2014, 1:50 am
$
0
0
Hi all,

Today, I’ve put all together my SharePoint 2013 upgrade experience.

As I have lot of Farms to admin, in different environments (Prod, pre-Prod, Test), I was faced to several issues.
So, in the ease for everyone, I’ve tried to figure out all the issues I had to solve.

This post is divided in 2 Sections:
1.       Pre-Upgrade CheckList: this is mandatory prior every upgrade
2.       Installation Process: binaries, and how I proceed the upgrade
3.       Trouble shooting: if something is wrong, the solution should/must be in this section


1.       SharePoint 2013 pre-Upgrade CheckList:
- Farm & Install accounts must be DB Owner on all system & content DBs
- Farm & Install accounts must have Security Admin  on all system & content DBs
- If there is mirroring, it must be stopped
- If there is Availability Groups, all DBs must be removed from the A.G
     *Update: the USAGE database must not be part of an A.G nor mirroring
        This DB name is found in the "Manage servers in this farm" section in Central Admin
        The usage database name is like: <db_name>-USAGE
- Copy all needed binaries that must be applied (CU, PU, SP)


2.       Installation Process:
- Logon each server with your Install account
- Launch the binaries installation (exe file). This step can take up to 2,5 hours.
- Reboot all servers
- Check in Central Administration GUI that all servers status are: Upgrade required
- Launch, on each servers the Configuration Wizard, but one step at a time.
   --> launch Configuration Wizard, click "yes"
   --> do the same for each servers of the Farm
- Click "Next" on your Central Admin Server (always start by the Central Admin server).
- When upgrade is finish, DO NOT click to exit.
  Select the next server, and click "Next" in the Configuration Wizard.
  Do the same process to all your server until the last one.
- When all servers are upgraded, close the Configuration Wizard (Next or Finish) and check the server status in the Central Administration GUI:
  "No Action Required"


3.       Trouble Shooting:

What to do if the upgrade fails?
1- Check event viewer for any Farm or Install account access denied in SQL
2- Check ULS
3- Execute the installation via the PSCONFIG cmdlet.
               PSConfig.exe -cmd upgrade -inplace b2b -wait -force

What to do if the Configuration Wizard is showing "Missing on <servername>"?
In the configuration Wizard, if there is some installed patches shown as "Missing on <servername>" (and they are already installed), you can use this PowerShell command :
Get-SPProduct -local
Then, press "Refresh" in the Configuration Wizard".
When the servers are no more in the list, you continue the patching process.

What to do if in the error logs (i.e : Upgrade-20141027-143441-40-error) you have this type of message?
Upgrade SPUpgradeSiteSession           ajxnj        ERROR
                at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
                at System.Net.HttpWebRequest.GetRequestStream()
                at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()

                ==> check that all Application Pools are up and running in IIS on all servers

What to do if you have Site Collection upgrade issue?
If you have this type of line in the error log:
ERROR   Pre-Upgrade [SPSite Url=<Your Site Collection URL/...] failed. Microsoft.SharePoint.Upgrade.SPSiteWssSequence has the ContinueOnFailiure bit set.
                ==> upgrade manually yours sites:
                Get-SPSite -Limit all | Where-Object {$_.NeedsUpgrade} | Upgrade-SPSite -VersionUpgrade -Unthrottled



Thant’s all folks
↧
Search

How to retrieve lost WSP package to prepare the SharePoint migration

March 5, 2015, 1:09 am
$
0
0
Hi All,

In order to prepare the migration of our SharePoint 2010 Farm to SharePoint 2013 Farm, I discover that old wsp packages were still present on the content databases.

Some of them are “relics” from SharePoint 2007 …


Of course, it is not possible to find where those wsp files are stored, and the old SharePoint 2007 servers are removed from the network since several years…


First, I started to enumerate the deployed solutions via PowerShell:

Cmdlet used:
Get-SPSolution | ? { $_.Deployed } | % { $_.DisplayName}

As output, I had this list:

mycompany.customertemplate.wsp
mycompany.mysite.branding.wsp
mycompany.po.projectsitedefinition.v1.2.0.wsp
ev_sharepointwebpartscab.cab
extendeddiagnosticproviders.wsp
sharepointsocialnetworking.wsp


Then, I’ve executed the next code to iterate the solutions collection and to retrieve all missing .wsp, using my previous list:

Add-PSSnapin Microsoft.SharePoint.PowerShell

$farm = Get-SPFarm
$file = $farm.Solutions.Item("<YourSolutionFile>.wsp").SolutionFile
$file.SaveAs("D:\temp\<YourSolutionFile>.wsp")


i.e:
$farm = Get-SPFarm
$file = $farm.Solutions.Item("mycompany.customertemplate.wsp").SolutionFile
$file.SaveAs("D:\temp\mycompany.customertemplate.wsp")


Now, I can yuse those .wsp, in my SharePoint 2010 test-farm.
I'll then prepare the databases by cleaning them from the old useless solutions.




That’s all Folks,



Marc


***** Disclaimer *****
http://www.belgacom.be/maildisclaimer
↧
↧

How to : Add new file type in SharePoint 2010

March 5, 2015, 1:23 am
$
0
0
Hi all,

Today’s task is to add a new managed file type.
The file type is .dmmx from Dropmind.

To achieve this request, I’m following the blog page of Romain K.


Step 1 : Assign an icon to the document in SharePoint

  1. Find a png image of the icon of 16 x 16 pixel with transparency : 
  2. Copy this .png file to your Hive14 folder : ..\14\Template\Images\dropmind.png
  3. Register the picture in the ..14\Template\xml\DOCICON.XML file
        In the section <ByExtension>, add:
                <MappingKey="dmmx"Value="dropmind.png" />

  4. Save the file and test the upload of a .dmmx file:



Step 2 : Declare document mime type as “downloadable” in IIS

  1. Open IIS Console, and browse to your Web Application


  2. Double click on the “Mime Types” menu of the selected Web Application (because I only allow this type of files on a specific Web App)



  3. In the “Action Pane”, top right of the IIS Console, click on the “Add…” button
  4. Declare the custome Mime Type:



  5. Via PowerShell, let’s declare the Mime Type as “Downloadable”:

          $web = Get-SpWebApplication -Identity <WebApplication>
          $web.AllowedInlineDownloadedMimeTypes.Add("application/vnd.dropmind")
          $web.Update()


  6. Now, I’m able to download the file from my SharePoint Site:




Thank's all folks


↧

User credential issue in SharePoint Site

March 5, 2015, 1:36 am
$
0
0
Hi all,

Today, I'll talk about an strange SharePoint issue, but it's not an issue from SharePoint.

It's a client side issue.


Facts:
 - User is Site Collection Administrator
 - User gets popup to enter his login/password (credentials) when accessing to his SharePoint Site
 - Login & Password are correct
 - Login to his SharePoint site from another computer is working (this is the first test I've asked the user to do and provide me his feedback)


Solution: Check the user credentials on your computer:

 - Click on Start
 - Control Panel
 - User Account
 - Credential Manager
 - Remove from Vault all references to SharePoint sites


Possible reason:
 As company policy, we must change our password several times per year.
 I bet that Windows kept (for this user) his old password in cache, thus replacing automatically his credentials by the one stored in the Credential Manager.



That's all folks
↧

Diagnose and Clean MissingWebPart and MissingAssembly issues

March 5, 2015, 6:45 am
$
0
0
Hi all,

Today I found useful cmdlets to diagnose and clear those errors in the Content DB of my SharePoint 2010 Farm.


How to:

Step 1:
 - Test-SPContentDatabase -name <ContentDB_Name> -webapplication <Web App URL>

Step 2:
 - Select the WebPart Class GUID

Step 3:
 - Run this command with the related WebPart Class GUID:

Run-SQLQuery -SqlServer "SRV_DATABASE" -SqlDatabase "SharePoint_Content_sharepoint_db_name" -SqlQuery "SELECT * from AllDocs inner join AllWebParts on AllDocs.Id = AllWebParts.tp_PageUrlID where AllWebParts.tp_WebPartTypeID = '9812863c-ee62-dab6-57f5-79e9d4d36022'" | select Id, SiteId, DirName, LeafName, WebId, ListId, tp_ZoneID, tp_DisplayName | Format-List

Step 4:
 - The result will give the below info:

Id                            : a5da7b36-083f-4d07-b50b-8f1fc8d7bbe9
SiteId                      : 53061278-8b1d-4d6d-9dce-8568f90c5574
DirName                 : Sites/blahblasite/Sandbox/TestWSServiceLevelDashboard
LeafName               : default.aspx
WebId                     : 2ab691b1-0d74-4bf2-9524-c6b1d969cfac
ListId                      :
tp_ZoneID              : Left
tp_DisplayName     :


 - The URL to use is:                http://shareppoint.contoso.com/Sites/blahblahsite/Sandbox/TestWSServiceLevelDashboard/default.aspx?contents=1

 - So, here are the steps that I follow to remove the “ErrorWebPart”:
     1- select the Error rows
     2- click on “Close” to set them as “No” for the “Open on Page?” column
     3- select the same Error rows then Delete them



Step 5:
 - Execute again the “Test-SPContentDatabase” to check that all entries for the MissingWebPart are gone.


Thanks all folks
↧
↧

How to install AppFabric when having Error 1603?

March 30, 2015, 2:59 am
$
0
0
Hi all,

Today’s story is about an issue to install the AppFabric pre-requisite for a test stand-alone SharePoint 2013 Farm.

After downloading all the .msi given by Microsoft in this blog http://blogs.technet.com/b/praveenh/archive/2013/02/22/sharepoint-2013-prerequisites-fails-with-msi-installer-error-code-1603-while-installing-appfabric-1-1.aspx, I was still getting the error code 1603:

appfabric installation failed because installer msi returned with error code 1603


Checking the Environment path didn’t make me happy, as it was already correct.

Rebooting the server before trying again to manually install the AppFabric was another fail.


Then, I’ve decided to uninstall the AppFabric, reboot the server, then re-install the AppFabric:
   it woks like a charm !!!!


In the same way, I’ve patched the AppFabric up-to V1.1 CU5




Voilà,


Thanks all folks
↧

Search Issue: Internal Server Error Exception

March 30, 2015, 11:34 pm
$
0
0
HI All,

Today I found the solution of our error with the Search in our SharePoint 2010 Farm.


The problem is that each user making a search into his Site collection via the Search Box as bellow, received this error message:





After checking services, IIS, Central Administration, rebooting all servers from this Service Farm, I still had plenty of Error with the Event ID 8313:



The solution is to stop/start (from Central Administration) the “Search Query and Site Settings Service” from each affected servers.
In my case, I had 2 servers having the service activated.
Thus, I’ve stop/start the servcice on both servers.


The main reason of the Round Robin Service Load Balancer Event, is that when the service is activated on several servers, if the first server cannot fint the search URL, it’ll send the request to the second server.
The risk is to have a ping-pong play between those servers.

To figure out this issue, I’ve read lot of blogs, and I found a clear explanation in Henry Ong blog.
He save my day.


Also, according to Microsoft, I was asked to schedule a daily recycling of the Application Pool for the “Search Query and Site Settings Service” service.
By default, the recycling is not set in IIS.

First point: find the correct Application Pool.

In the event log, the Affected Endpoint washttps://<servername>/61c52c151c..../....svc
In the IIS Manager, under “SharePoint Web Services” path, I found it and opened the “Advanced Settings” from the right pane.
Thus, I had the Application Pool to schedule the recycle.


Now, open the Application Pools path, and select the correct Application Pool.
In the right pane, under the “Edit Application Pool” section, select “Recycling”:
                I‘ve decided that this Application Pool will be recycled each day at 4:50 AM.



Don't forget to do this manipulation on all servers that will start the “Search Query and Site Settings Service” service.



Thanks all Folks


↧

Confirm Site use and Deletion

March 31, 2015, 12:58 am
$
0
0
Hi All,

Today, I spend time to check the Retention Time of an unused mySite.
One of my client was complaining that he received a mail reminder that his mySite will be deleted as there is no activity.

Here is the way to check in SharePoint 2013 (same as SharePoint 2010):

 - Step 1:


 - Step 2:



Et Voilà !!!



That’s all folks


↧
Search

Search did not provide new items

May 11, 2015, 5:04 am
$
0
0
Hi All,


Today, I’ll talk about the Search issue I had few weeks ago.

This started on our SharePoint 2010 production Farm, with complain from users that weren’t able to find they newly added documents in the Search box.
At the beginning, I was asking them to wait until next working day, as the Incremental Crawl was running.

Then, days passed, and more and more users were complaining again and again.

Checking the server was showing that the Incremental Crawl were running, but really slowly.
Every days, I was receiving tickets about the usage of the CPU of my crawl server that was stuck at 100%.

When reading over the web, I discovered that the Crawl engine was using all the CPU while crawling.
This was driving me to the wrong path, and letting my server going deeper in the “glue”

I started to pause all the Content Sources, except one, but nothing seems to unstruck the index crawl.

So, I started to think about this problem, and facing Incremental Crawl of more than 300 hours, I decided to call Microsoft for having their support.
First of all, they confirmed that the Crawl process is using 100% of the available CPU, even if you add more and more CPU.
But the advantage, is that the Crawling Time is reduced.

Then, Microsoft asked me to run the Diagnostic Tool on my Service Farm, and they first pointed out that my servers were not fitting to the minimum hardware requirements: 2CPU + 40Gb HDD.

Then, I made a CPU and HDD upgrade: 4CPU + 270Gb HDD.

I started a Full Crawl of each Content Sources, then gradually, I’ve implemented the “Crawl Schedules” for each Content Sources.


Since last week, all the Content Sources are correctly crawling, and nobody is complaining.


So, this is the point to check when you have a search issue:
 - Number of CPU
 - Size of your log disk
 - Crawl Schedule starting at different time
 - Content DataBases are attached/detached, a Full Crawl must be performed (information given by Microsoft)



Voilà,


Thanks all folks

↧
↧

SharePoint 2013 returns to 'upgrade required' status

August 26, 2015, 4:03 am
$
0
0
Hi all,

This post is related to the fact that after upgrading your SharePoint Farm with success, you are faced again with some servers in the "Upgrade Required" status.

As this issue was still coming and coming after each try to re-upgrade my farm, I decided to open a case at Microsoft support.

So, hereunder, you can find the resolution steps that will bring your smile back.


In summary, if one or several servers (my production farm is composed by 25 servers) are going back to the "Upgrade Required" after being marked as "No Action Required" during few days, check first if you don't have some sites that were not upgraded.
In this case, only 1 Site Collection wasn't correctly upgraded, and after a manual upgrade (via powershell cmdlets), all was solved.



Here is the case summary for your records:
==================
Title: SHP2013 returns to 'upgrade required' status
Severity: B
Status: Resolved and Closed

ACTION/RESULT:
Customer reported that after completing the upgrade to CU December 2014 (more than once) on the SharePoint 2013 farm - some the "Servers in this Farm" were still showing "Upgrade Required"

CAUSE/RESOLUTION:
In a previous upgrade attempt, there was the indication of a Site Collection that was not provisioned correctly:
07-24-2015 13:12:59.59 OWSTIMER (0x1CEC) 0x1F5C SharePoint Foundation Upgrade SPSiteWssSequence alsj5 WARNING SPWeb [https://mysite.sharepoint.me/sites/myname] [MyName, MyFirstName] is in a partially provisioned state. 021f1d9d-33b4-00ca-36cd-9ce05d7b2e40

Running (Get-SPSitehttps://mysite.sharepoint.me/sites/myname).NeedsUpgradeshowed that this needs to be upgraded.
Customer ran the script:
$dir = Get-Location
$file = "$dir\farmSCUpgradeRequired.txt"

#Sites
Get-SPWebApplication -includecentraladministration | ForEach-Object {
               $webappurl = $_.Url
               $_.Sites | ForEach-Object {
                              "{0};{1};{2}" -f $webappurl, $_.URL, $_.NeedsUpgrade
               }
} | Out-File $file
This showed that the site collection mentioned before was in fact the only one needing an upgrade.

Customer ran the powershell command Upgrade-SPSite https://mysite.sharepoint.me/sites/myname -versionupgrade
The Site Collection was upgraded successfully.

After this, customer ran the "Product Version Job" timer job, and only 2 servers were still showing "Upgrade Required".
Running "stsadm -o localupgradestatus" showed only for these 2 servers, the following error message:
  <object>
    <name>Sharepoint_SA_UserProfile_Profile</name>
    <type>Microsoft.Office.Server.Administration.ProfileDatabase</type>
    <level>2</level>
    <status>Cannot Upgrade</status>
  </object>
  <object>
    <name>Sharepoint_SA_UserProfile_Social</name>
    <type>Microsoft.Office.Server.Administration.SocialDatabase</type>
    <level>2</level>
    <status>Cannot Upgrade</status>
  </object>

This means that the servers had something different than the rest of the servers, as the Databases were already up to date.
Running Get-SPDatabase|where {$_.Name -like"*UserProfile*"} |ftName, NeedsUpgrade, NeedsUpgradeIncludeChildren, CanUpgrade also showed the information for these databases on the affected servers.

As this issue could only be on the servers, running the Configuration Wizard on both affected servers, made the message "Upgrade Required" go away.
After some days, the servers are still on a stable state.
=================



That's all folks
↧

Why a Content DataBase is not cleaning the free space after Move-SPSite or Delete-SPSite?

November 9, 2015, 3:37 am
$
0
0
Hi all,

I was faced to a full Database, and the quick-win solution, was to move some sites to another Database.

After making the list of the site collection present in the database, I found that the moved sites were no more present, as expexted.
But on the SQL side, the Database was still full…

I’ve asked our SQL Team to Shrink the Database, but nothing was changed.

Then, I’ve search why the space used by the moved sites was not cleared by the Timer Job.
Timer Job… The Gradual Site Delete timer job.

I’ve found why the Database didn’t change the free space after moving sites.
The timer job in SharePoint wasn’t correctly set.

After checking, the job supposed to be run automatically every day from 10PM to 6AM, but it wasn’t run.


Reason: start time is before end time. Seems that Microsoft logic is … special.

In the drop down list, the time for the timer job (same problem for all timer jobs in all SharePoint versions) start at 12AM and ends at 11PM.

The problem, is that by default, the Gradual Site Delete timer job is set as below: from 10PM to 6AM
This is quite logic for us (human), but I’ve the impression that the timer job doesn’t see the 6AM after 10PM in the drop-down list.
Also, I found that clicking on the “Run Now” button didn’t free the space in the concerned Database.


Thus, this default setting seems not allowing the Timer Job to run:




Solution: instead  of starting at 10PM, I’ve set it to start at 12AM
                                Now, no more red warning message.
                                And clicking on “Run Now” button is directly clearing the free space of all the                                      databases of my Web App.




So, I’ve had to check all my Gradual Site Delete timer job for each Web App I have.
Also, I found this problem to my SharePoint 2010 Farm and my brand new SharePoint 2013 Farms.


Hope this could help.



That’s all Folks
↧

SharePoint 2013 ::: Database is in Compatibility range and upgrade is recommended ::: Database is too old and upgrade is required

April 26, 2016, 3:28 am
$
0
0
Hi all,

After the December 2014 CU, all my farms have their BDC Service Database in compatibility range.


I found the solution from Markus’ Blog and I’ve executed this PowerShell command:

Add-PSSnapinMicrosoft.SharePoint.PowerShell
(Get-SPDatabase|?{$_.type -eq"Microsoft.SharePoint.BusinessData.SharedService.BdcServiceDatabase"}).Provision()

Also, I got an error (as mentionned in his post), and checked the access rights.

This is the error I had:
PS C:\Windows\system32> (Get-SPDatabase | ?{$_.type -eq "Microsoft.SharePoint.BusinessData.SharedService.BdcServiceDatabase"}).Provision()
Exception calling "Provision" with "0" argument(s): "Cannot find the object "dbo.Versions" because it does not exist or you do not have permissions."
At line:1 char:1
+ (Get-SPDatabase | ?{$_.type -eq "Microsoft.SharePoint.BusinessData.SharedService ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : SqlException


So, I’ve asked to the SQL Team to add the SPDataAccess for the service account:

Then, I ran again the PowerShell command, and my BDCS database is now in “No action required” status.



I’ve also 3 system database that are in “Database is too old and upgrade is required” status.

For those 3 DBs, I’ve tried the same way as for the BDCS database:

First, getting the correct Type Name for each DB:
Get-SPDatabase|ft -Auto

Second, preparing the PowerShell commands:
(Get-SPDatabase|?{$_.type -eq"Microsoft SharePoint Foundation Subscription Settings Database"}).Provision()
(Get-SPDatabase|?{$_.type -eq"Microsoft.Office.Server.Administration.ProfileDatabase"}).Provision()
(Get-SPDatabase|?{$_.type -eq"Microsoft.Office.Server.Administration.SocialDatabase"}).Provision()

Third, checking and adapting the SQL settings for SPDataAccess

Finally, executing my PowerShell commands.



Voilà,


That’s all Folks !!!
↧

SharePoint 2013 and Microsoft Security Patch side effects

September 25, 2016, 1:39 am
$
0
0
Hi all,

Last week, I've patch with big success my production Farm (15 servers) and my Disaster recovery Farm (15 sercers).

Little explanation about our configuration:

All the db (system, content, search, etc) are located on a SQL Cluster, set with several availability groups. (this point made me having white hairs during the previous Cuulative Updates).

On that Clustr, there is a primary group, where all the changes made in SharePoint (system, content, search, etc...) are commited (Read/Write).
Then, on the secondary group, all dbs are autoatically sync from primary to secondary group (thus, in case of ay issue, I can easilly have a fresh backup and replace the faulty db).

So, those 2 SQL cluster, are "dedicated" to my Primary Prod SharePoint Farm.

Beside this, I have a backup farm. She is identical to the primary farm, and was designed in case of disaster recovery, to replace the main Farm.

In the procedure, I've changed it to reduce the user impact to it's minimum.
The estimation is 2 time 5 minutes: DNS switch from Primary Farm to Secondary Farm, and Secondary Farm to Primary Farm.


So, to be short, both Farms were patched without issue.

The problem came 3 days later, when the mandatory security patch where applied on half of the servers in the company (Next half is done 2 days later).

I discovered that 1 server was back in "Upgrade required"... Oh, my words!!!!
Then, the day later, I had 5 other servers back in that status.

During that time, we had the support of Microsoft, and they recommend us to execute this powershell command:
     Get-SPProduct -local
     Reboot the server

Then, I did this procedure, and it works!!!!

After that, I've only execute the powershell command without rebooting the server, and my servers went back to "No Upgrade Required".

This powershell command must be executed on each server that have received a microsoft security patch.


So, If your farm was successfully patched, and some server are back in the status "Upgrade Required", thus try this powershell command.
Your Farm and server are still up and running, and in take less than 5 minutes to correct the issue.



Voilà,


That’s all Folks !!!
↧
↧

SharePoint 2013 ::: How to restore the deleted "Suggested sites to follow" Web Part from a user's MySite

December 19, 2016, 11:39 pm
$
0
0
Hi all,

Today’s challenge is to restore the Web Part “Suggested sites to follow” that was deleted by the user himself.

So, do not lose your time in trying to find the Web Part in the Add Web Part page of the mySite, it is not available.


After googleling, I found this link to a Microsoft article to remove the concerned Web Part using PowerShell.

The script, provided by Microsoft, that put me on the track is:

Add-PsSnapin Microsoft.SharePoint.PowerShell
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.WebPartPages")
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Publishing")

$useraccount = "useraccount"
$url = "http://" + [System.Net.Dns]::GetHostName() + "/my/personal/" + $useraccount
$site = get-spsite $url
$web = $site.RootWeb
$pageUrl= "Social/Sites.aspx"
$webPartManager =  $web.GetLimitedWebPartManager($pageUrl, [System.Web.UI.WebControls.WebParts.PersonalizationScope]::Shared);
$webPart = $webPartManager.WebParts | where-object { $_.WebBrowsableObject.GetType().Name -eq "ProjectSearchBrowseWebpart" }

if($webPart -ne $null)
{
    $webPartManager.DeleteWebPart($webPart)
}
$web.Update();


In the script, I found the name of the Web Part "ProjectSearchBrowseWebpart", and the page to find it.
Then, I decided to compare the code of both pages “Social/Sites.aspx” from my mySite and from the user’s mySite, using SharePoint Designer 2013.


I found then the difference at the end of the code:

Hereunder is the code from my mySite, and in yellow, the missing code in the user’s mySite code:

            <div class="ms-contentFollowing-sitesRightZone ms-tableCell ms-verticalAlignTop">
                <div class="ms-contentFollowing-bottomZoneContainer">
                    <WebPartPages:WebPartZone runat="server" FrameType="None" ID="RightZone" Title="<%$Resources:sps,LayoutPageZone_RightZone%>" Orientation="Vertical"><ZoneTemplate>
                                                                           <SPSWC:ProjectSearchBrowseWebpart runat="server" CategoryString="Site" AllowEdit="False" ChromeType="TitleOnly" Description="The recommendations web part suggests content a user may wish to follow within a farm." Title="Suggested sites to follow" ID="projectSearchBrowseWebPart" __MarkupType="vsattributemarkup" __WebPartId="{344EF58F-509A-3DE1-T3DG-ID0T674FOR6Z}" WebPart="true" __designer:IsClosed="false" partorder="2"></SPSWC:ProjectSearchBrowseWebpart>

                                                                           </ZoneTemplate></WebPartPages:WebPartZone>
                </div>
            </div>
        </div>
    </div>
</asp:Content>


So, I simply made a copy/paste of the missing line, save the user’s “Social/Sites.aspx” page, and made a refresh of his mySite in the browser.

 ==>Problem solved.




Voilà,


That’s all Folks !!!

↧

SharePoint 2013 ::: BCS Database is in compatibility range and upgrade is recommended

September 5, 2017, 3:00 am
$
0
0
Hi all,

A few time ago, I went trought this message for the BCS Database on SharePoint 2013:

BCS Database is in compatibility range and upgrade is recommended


To solve this issue, I've executed this PowerShell commands:

This solved my particular issue.
If you have the same type of message for other databases, please proceed by the same way, by replacing the name of the DB by the known name when doing a Get-Member 


Add-PSSnapinMicrosoft.SharePoint.PowerShell
Get-SPDatabase|FT -autoname,type
(Get-SPDatabase|?{$_.type -eq"Microsoft.SharePoint.BusinessData.SharedService.BdcServiceDatabase"}).Provision()



Voilà,



That’s all Folks !!!
↧
Search

SharePoint 2013 ::: .NET Server Error ::: Event ID 1023

October 23, 2018, 3:47 am
$
0
0

Hi all,

Today, I'm checking one of my Farms, in my test environment, and while opening Central Administration site, I was faced to this nice Runtime Error:




Following this discover, I've tested to access to the Farm via PowerShell commands.

- First, let's load the SharePoint snapin:
          add-pssnapin Microsoft.SharePoint.PowerShell
     ==> no errors, ths it means that my farm isn't broken.

- Secondly, let's check the Farm version:
     ==> (Get-SPFarm).buildversion

Major  Minor  Build  Revision
-----  -----  -----  --------
15     0      4957   1000   


Ok, defenitely, it is not a SharePoint Farm issue.

Then, I saw some .NET Runtime (Event ID 1023) errors in the Event Viewer.
After googleling a little bit, I found the solution explained by Bryan Peters in this post.

I've made the exactly same procedure, on my both servers, and the Farm is back to live.

Create a new DWORD, followed by an IIS Reset:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework
New registry DWORD : LoaderOptimization
Value : 1
IIS Reset


==> Problem solved.



Voilà,


That’s all Folks !!

↧

SharePoint 2013 ::: Event ID 6482 ::: An update conflict has occured

November 5, 2018, 6:26 am
$
0
0
Hi all,

Today, I'm facing with Event ID 6482, indicating that the job is failing due to an update conflict.



The resolution for this issue is to delete ALL .xml files where the mentioned file is located.


1. Finding the filename:
The first line give the file name of the .xml file to find. The name is located into the brackets at the end of the line:
service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (a5744ce1-d592-42fc-a081-82188cbee126).

2. Stop the "SharePoint Timer Service"

3. Browse on each servers of your farm to this path:
C:\ProgramData\Microsoft\SharePoint\Config

4. Delete all .xml files present into the folder where .xml files are located (the other folder does contain  ".PERSISTEDFILES" : do not toutch them)

5. Edit the file "Cache.ini", and write down the number "1"

6. Save the "Cache.ini" file

7. Repeat steps 2 to 6 on each servers of your farm

8. Restart the "SharePoint Timer Service" on each servers of your farm.

9. Check that all cache files are automatically recreated.

10. Check that the file "Cache.ini" contains another number then "1"



==> Problem solved.



Voilà,


That’s all Folks !!
↧
↧

SharePoint 2016 On-Prem ::: Error within Word and Excel Online

January 7, 2019, 2:55 am
$
0
0
Hi All,


Today I'm closing this case opened last month at Microsoft.

The issue is that on SharePoint 2016 On-Prem, it is no more possible to open any excel nor word file in the Word/Excel Online, or to have a preview of the document.

This is the error exemple that we were experiencing:


After several hours, passed with Microsoft engineer, lot of test and logs, we came to the fact that Office Web App must be reinstalled with the latest version.

And today, I was executing the latest Action Plan (A.P) proposed by the Microsoft Engineer: cleaning the Config Cache in SharePoint 2016.

Before going further, the A.P must be executed on each servers in your Farm, otherwise, you will be facing with a nice correlation ID with this message: "An update conflict..."



Below is a summary of the issue:
Scope:
You are using SharePoint Server 2016 OnPremise and lately you noticed that the users cannot open the Office files in the browser anymore.
Also the preview does not work as expected.

To be more specific:
1. The user john.doe@contoso.com navigates to https://shp.contoso.com/sites/TeamSite01/_layouts/15/start.aspx#/MyDoc/Forms/Default.aspx and selects the Word file called “Migration Doc-01.docx
2. By opening the file in Word Online, the following message appears:
Server Error in ‘/x’ Application.
Runtime Error
Description: An application error occurred on the server. The current customer error settings for this application prevent the details of the application from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a “web.config” configuration file located in the root directory of the current web application. This <customErrors> tag should then have its “mode” attribute set to “Off”

<!—Web.Config Configuration File -->
  <configuration>
<system.web>
<customErrors mode=”Off”/>
</system.web>
</configuration>”

Notes: The current error page you are seeing can be replaced by a custom error page by modyfing the “defaultRedirect” attribute of the application’s <customErrors> configuration tag to point to a custom error page URL.

<!—Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode=”RemoteOnly” defaultRedirect=”mycustompage.htm”/>
</system.web>
</configuration>”


Action Plan:
1 - Delete the configuration cache, on EACH servers in your Farm,  using the information from this article : https://gallery.technet.microsoft.com/office/SharePoint-2010-2013-21f55320
I've used the PowerShell script after verifying that the cache was in the correct location

2 - Run this command Update-SPWOPIProofKey  in PowerShell, from each server in your Farm
3 - Start the timer job WOPI Discovery Synchronization from Central Administration Console : as I have 2 WFE servers, I've executed both WOPI timer jobs
4 - Test the Preview and opening online your document:




This procedure will also be working with SharePoint 2010 and 2013.
Only check the path where the config folder of SharePoint is located, and adapt into your PowerShell Script.
In 2016, it is located at: C:\ProgramData\Microsoft\SharePoint\Config



Voilà,

That’s all Folks !!!





↧

"An update conflict has occurred, and you must re-try this action" in SharePoint

January 7, 2019, 3:02 am
$
0
0
Hi all,

I was facing this issue when trying to run manually a timer job from the Central Administration GUI.

According to Microsoft, I've clear the cache of SharePoint only from 1 server of my Farm.
I've 4 servers in that Farm, and I had to clear the cache on each servers in my Farm.

This article explain how to clear the cache config, but the path mentioned is specific for SharePoint 2007:
https://support.microsoft.com/en-us/help/939308/error-message-when-you-try-to-modify-or-to-delete-an-alternate-access

Use this article for the path for SharePoint 2010, 2013 and 2016:

https://gallery.technet.microsoft.com/office/SharePoint-2010-2013-21f55320



Voilà,

That’s all Folks !!!
↧

SharePoint 2013 ::: IIS Config file is corrupted

April 9, 2020, 12:29 am
$
0
0
Hi all,

Issue with IIS while opening the Application Pool





Checked the config file, and it was corrupted.

Solution:

1- Check when the file was last modified
2- Find the last correct file in the history folder of  your <drive>:\inetpub\history
3- stop iis : iisreset /stop
4- Copy the last correct backup file
5- start iis : iisreset /start
6- Check that the application pools are started in IIS Manager
7- Check the different Web Applications


Voilà,

That’s all Folks !!!
↧
Viewing all 60 articles
Browse latest View live
Search