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

Link to the Updates for SharePoint 2010 Products

September 5, 2012, 5:34 am
↧
Search

Issue to open some folders in Documents Library

October 10, 2012, 1:29 am
$
0
0
Hi all,

Today I was facing to a strange issue : users were no more able to open Document Library via the “Open with Explorer” Library Tool option.

But, other libraries were able to be opened via this option, and subfolders of the faulty Library.

The error message was :  ... is not accessible. no permission. You might not have permissions to use this network resource.


I made a search on internet, and found the Sean Wallbridge Site http://www.brainlitter.com/2011/12/05/sharepoint-open-with-explorer-errors-the-parameter-is-incorrect/ with the same issue and a nice solution.

Issue is created (in my case) when the end-user created the folder with 2 space characters next each other.
Doing this make SharePoint replacing the first space by “%20”, but not the second space character.

So, the URL is not correctly rendered, and give the mentioned issue.

I had more than 1000 documents in the faulty library.
And about more than 400 folders to review, one by one.

Result was that only 5 folders were wrongly written with 2 time the space character in their name.

Simply edit the item, and removing the extra space, then save solved all the issues.


So, remember that not only the files can have this issue, but also the folder’s name.



That's all folks.
↧
↧

Issues with migrated site containing SharePoint 2007 Branding

October 10, 2012, 1:41 am
$
0
0

Hi all,

Today I’ve solved a Branding issue.

With SharePoint 2007, we have decided to develop a Company Branding, that was used by default on all pages : a new "company custom" master page.

Then this summer, we prepared the migration of all our Site Collection from SharePoint 2007 Farm to brand new SharePoint 2010 Farm.
Faced to the cost reduction, and to be as close as “from the box” as possible, it was decided not to develop a new Branding for SharePoint 2010.

One part of the biggest job was to find and point out all the Sites that could give issue during the migration.

Nearly all sites were migrated without any issue, and we knew that with the use, we, uh… I will be face to  those special cases.


How did the issue was found ?
-          The end-user started to save his site as template (Site Actions à Site Settings è Site Actions à Save Site as Template)
-          Then, he decided to create a subsite with this template.
o   Site Actions à Site Settings èGalleries à Solutions à Upload Solution
o   Select the .wsp, and activate the Solution
o   Site Actions à Create New Site è Select the Active .wsp, Title and URL Name

Of course, the user got this first error (error that is not in relation with this issue) :

So, I wanted to point out this feature with the Get-SPFeature command :
Get-SPFeature -Site http://<my WebApplication URL>/Sites/SiteCollectionName

This command gave me the Feature’s name.

Then, I discovered that this “OpenInClient” was the SharePoint 2010 “Open Documents in Client Applications by Default” Site Collection Feature.

So, for testing, I’ve activated the feature on my test site, and this issue was solved…. But then, I got a new error message in place of the first one :



This is the remaining trace of the old SharePoint 2007 branding that was applied on each sites.

So, what is the situation :
-          I know that this error is the result of a wrong-cleaned branding Site.
-          When creating the new site/subsite, the solution is searching for this specific <branded>.master page, at the Hive 14\Template\FEATURES\xxxxx.Core.SharePoint.Branding.Web folder
-          This folder is not in the features, so, the system gives us this error.

How did I manage to solve this ?
-          Open the site in SPD (SharePoint 2010 Designer)
-          Check the Master Pages content : the <branding>.master is present, but cannot be found on the server

-          Editing the master page give this error message :

-          I’ve made a backup of the site via the Central Administration Backup and Restore GUI.
-          Then, I’ve deleted the faulty master page via SPD.

-           Save site as template, upload the new cleaned .wsp as a solution, then I’ve created a new subsite : No Error


That's all folks.
↧

Microsoft Certification : MCITP SharePoint Administratior 2010

October 26, 2012, 5:01 am
$
0
0
Voilà,

Last month (September 28th 2012), I pass the MS 70-668 exam.
Last Wednesday (October 24th 2012), I pass the MS 70-667 exam.

And this morning, I got my Microsoft Certified IT Professional certification written in my Transcript.


I'm very glad to pass those 2 exams.




That's all folks.
↧

How to solve CU Update issues : the return

November 9, 2012, 2:58 am
$
0
0
Hi all,

Today, I applied the August 2012 CU on your UAT Collaboration Farm.
This farm is populated by 4 servers.

Installing binaries was done without any issue.
Execution of the “SharePoint 2010 Product Configuration Wizard” was done with several issues.
I used my previous post “How to Apply Cumulative Updates and Avoid Issues” to have the process and most solutions in my hands.
But each upgrade is different of the other.

The main issue came from one server, that gave the impression that it’s registry lost the fact that SharePoint 2010 was already installed.
To solve this issue, I had to execute the following command :
                Get-SPProduct –local

Then, a click on the Refresh button of the “Product Configuration Wizard” let me to start the upgrade.


Then, I had all four servers status in “Upgrade Available” mode in Central Administration.

So, I execute the psconfig cmdlet :
                Psconfig –cmd upgrade –inplace b2b –wait

Directly, I had errors and the upgrade failed.

So, opening the created log files like “Upgrade-20121109-xxxxxx-xxx.log” point me out serveral sites to correct.
As I’m working on our test environment, I decided to simply delete the faulty sites.
Some were backed-up, as I need to restore one of them.

Then, the psconfig worked fine for 3 out of 4 servers… Ugh!

What’s wrong with this last server?
It was like the upgrade process was already running on this server…
Check in the server process list, and I didn’t found any running process.



So, I googled on the Microsoft.SharePoint.Administration.SPUpgradeConcurrencyException, and found SharePointGeoff site.
Nearly same type of error, and a 4-steps solution:

1.       Stsadm –o setproperty –pn command-line-upgrade-running –pv No
2.       IISReset
3.       Restart the "SharePoint 2010 Timer" Service
4.       Psconfig –cmd upgrade –inplace b2b –wait –force


Then, now, all my servers of this farm have the status : “No Action Required”.


Job’s done.



↧
↧

Issue with SharePoint 2010 Farm Update

January 15, 2013, 5:31 am
$
0
0
Hi all,

Today, I’m taking the time to solve my “Upgrade Available” issue in my production farm.

Last time, I’ve noticed that, after successfully upgraded my production farm, the status went back to “Upgrade Available” after being successful.
So, the binaries are 14.0.6117.5002


The status is now as on this screen below :

I know that I have 2 sites that gave me errors when upgrading my farm, but I used a workaround to be able to apply the Feb 2012 CU :
Backup/Delete/Restore of both faulty sites.

Step 1: let’s list the DB where are located those 2 sites

Central Administration => Upgrade and Patch Management => Review database status:



I google about this status “Database is up to date, but some sites are not completely upgraded”, and fount this link when I found 2 powershell lines to execute:

$DB = Get-SPContentDatabase -Identity DB_NAME
Upgrade-SPContentDatabase -id $DB

This must be done for each DB after having fixed the error.

To be honest, I used this Upgrade-SPContentDatabase command to check the resulting error log, and find the site, and the error type.

Step 2 : let’s check the error log and find the direction to look



Opening the “Upgrade-20130115-094410-390.log, then finding the first [ERROR] entry show this :


[powershell] [V2VRecordCenterUpgradeSiteAction (13.0.2.0)] [ERROR] [15/01/2013 09:44:14]: Failed to run V2VRecordCenterUpgradeSiteAction.Upgrade for SPWeb (http://shpteam.xxxxxxxx/sites/TTeamSite/backoffice), the following error occured:The specified name is already in use.

Please try again with a new name. at:   at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
   at Microsoft.SharePoint.Library.SPRequest.AddGroup(String bstrUrl, String bstrName, String bstrDescription, Int32 lOwnerID, Boolean bOwnerIsUser, UInt64 iPermMask, Int32 lUserId, Boolean bUseExisting, Boolean bSelfOwner)
   at Microsoft.SharePoint.SPGroupCollection.AddInternal(String name, SPMember owner, SPUser defaultUser, String description)
   at Microsoft.SharePoint.SPGroupCollection.Add(String name, SPMember owner, SPUser defaultUser, String description)
   at Microsoft.SharePoint.Utilities.SPUtilityInternal.CreateDefaultSharePointGroups(SPWeb web, String strUserLogin, String strUserLogin2, String strGroupNameSeed)
   at Microsoft.Office.RecordsManagement.Internal.DocumentRoutingFeatureReceiver.<>c__DisplayClass2.<FeatureActivated>b__0()
   at Microsoft.Office.Server.Utilities.CultureUtility.RunWithCultureScope(CodeToRunWithCultureScope code)
   at Microsoft.Office.RecordsManagement.Internal.DocumentRoutingFeatureReceiver.FeatureActivated(SPFeatureReceiverProperties properties)
   at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)
   at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce)
   at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
   at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, String featureName, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope)
   at Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId)
   at Microsoft.Office.Server.Upgrade.SiteAction.ActivateFeature(SPFeatureCollection features, Guid featureGuid, String featureScope, Boolean force)
   at Microsoft.Office.Server.Upgrade.SiteAction.ActivateFeatures(SPFeatureCollection features, Guid[] featureGuids, String featureScope)
   at Microsoft.Office.Server.DLC.Upgrade.V2VRecordCenterUpgradeSiteAction.UpgradeWeb(SPWeb web)


So, I had to go to the site, and I was not able to find the name that was already in use….

I google again , and find a post of Gayan Peiris with this little explanation :


In my case, the duplicate name was “Back Office”.

But, I was able to find only 1 “Back Office” site, the site mentioned into the error log.

Then, I decide to go to the root URL of this site “http://shpTeam.xxxxxxx/sites/TTeamSite”
I found then, that the mentioned “Back Office” name was a sub site of TTeamSite.

And, another “Back Office” site was already created, but with the “bo” name instead of “Back Office”.

Both sub sites had the same name, and this was the root cause of the issue.

I deleted the “Back Office” sub site, and got this situation:
  "Back Office" name is now used once.

Then, I’ve executed again the Upgrade-SPContentDatabase command, I my DB was successfully upgraded.

Not, here is the situation :

Step 3 : do the same steps as beginning, and solve the issue following the given error message in the log.

This is the error lines found on the log :
[powershell] [SPSiteWssSequence2] [ERROR] [15/01/2013 10:46:03]: Feature upgrade incomplete for Feature 'PublishingWeb' (Id: '94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb') in Web 'http://shpworkgroup.xxxxxx/sites/WWorkgroup'. Exception: Provisioning did not succeed. Details: Failed to provision role definitions. OriginalException: Value does not fall within the expected range.  (Inner Exception: Value does not fall within the expected range.)
[powershell] [SPSiteWssSequence2] [ERROR] [15/01/2013 10:46:03]: Feature upgrade incomplete for Feature 'PublishingWeb' (Id: '94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb') in Web 'http://shpworkgroup.xxxxxx/sites/WWorkgroup'. Exception: Dependency feature 'PublishingSite' (id: f6924d36-2fa8-4f0b-b16d-06b7250180fa) for feature 'PublishingWeb' (id: 94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb) is not activated at this scope.

So, I activate the features for this site :

stsadm -o activatefeature -filename publishingSite\feature.xml -url http://shpworkgroup.xxxxxx/sites/WWorkgroup -force
stsadm -o activatefeature -filename publishingWeb\feature.xml -url http://shpworkgroup.xxxxxx/sites/WWorkgroup -force



Then, let’s upgrade again the DB :

$DB = Get-SPContentDatabase -Identity DB_NAME
Upgrade-SPContentDatabase -id $DB

Looks nicer :





But, unfortunately, the status is still the same :



Checking the upgrade status via the stsadm command :
stsadm.exe -o localupgradestatus


So, all seems ok, except the CADM page.

Let’s recycle IIS :

Check the CADM page :

Voilà !

I can now plan the next step : run the SharePoint Products Configuration Wizard.


Job’s done.


↧

How to Delete a corrupt file entry in SQL DB

May 6, 2013, 1:35 am
$
0
0
Hi All,

Today, I’ll explain the way I found to clear a file issue in one of the SharePoint 2010 site.
File is visible in the AllDocs list, but not available even when opening the Library with the “Open with Explorer”  ribbon option.

The faulty file the file name mentioned in the red box hereunder, and it’s extension is .xmind (event if the icon is a pdf).

So, all the site is working like a charm, without any error.



When trying to open the file, or making any change to it via the drop-down menu of the file, I got the http 500 error :




First, I made a –databaserepair to find the corruption, and try to fix it with the –deletecorruption parameter : didn’t help.

PS C:\Users\sharepoint_install> stsadm.exe -o databaserepair -url http://<siteURL>/Sites/SiteName -databasename Sharepoint_Content_shpDBName_RestoreFromProductionForTest

<OrphanedObjects Count="2">
  <Orphan Type="SecurityScope" SiteId="{69446A31-82A4-481E-9889-4661A810AD16}" Name="Sites/SiteName/Lists/ProjectDocuments /P131070_SmartMonitoring_WBS.xmind" InRecycleBin="No" />
  <Orphan Type="SecurityScope" SiteId="{96A99C51-C636-4593-BF9C-ED610ACA4743}" Name="Sites/SiteName/Lists/ProjectDocuments /P131063_Project_Definition_One Number_draft v0.1.docm" InRecycleBin="No" />
</OrphanedObjects>

PS C:\Users\ sharepoint_install> stsadm.exe -o databaserepair -url http://<siteURL>/Sites/ SiteName -databasename Sharepoint_Content_shpDBName_RestoreFromProductionForTest

Violation of PRIMARY KEY constraint 'Perms_PK'. Cannot insert duplicate key in object 'dbo.Perms'. The duplicate key value is (96a99c51-c636
-4593-bf9c-ed610aca4743, 0x, Sites/SiteName/Lists/ProjectDocuments/P131063_Project_Definition_One Number_draft v0.1.docm).
The statement has been terminated.



Then, I decide to open SQL, and start finding the document entries.
Of course, there is no clear post/site/info showing all the tables to check.

I found 2 tables :
-          AllDocs
-          AllDocStreams


First things first :

1.       Find the file in the AllDocs table and grab the Id entry

/****** Script for SelectTopNRows command from SSMS  ******/
SELECT*
  FROM [Sharepoint_Content_shpDBName_RestoreFromProductionForTest].[dbo].[AllDocs]
  WHERE [DirName] like'Sites/SiteName/Lists/ProjectDocuments'
/**********************************************************/


The result is :


So, I have the unique Id, and looking at the column named “DocLib RowId” let me do a double-check that the file is the correct item to delete (check the ID row in the List from the first screen).


2.       Find the same Id entry in the AllDocStreams table

/****** Script for SelectTopNRows command from SSMS  ******/
SELECT [Id]
      ,[SiteId]
      ,[Content]
      ,[RbsId]
      ,[InternalVersion]
FROM [Sharepoint_Content_shpDBName_RestoreFromProductionForTest].[dbo].[AllDocStreams]
WHERE [Id]='DEF629C6-3A40-473A-BDD5-BB295E9E1AB1'
/**********************************************************/




3.       Delete both entries in the SQL DB :

/****** Script for SelectTopNRows command from SSMS  ******/
DELETE
  FROM [Sharepoint_Content_shpDBName_RestoreFromProductionForTest].[dbo].[AllDocStreams]
  WHERE [Id]='DEF629C6-3A40-473A-BDD5-BB295E9E1AB1'
/**********************************************************/

Result : (1 row(s) affected)



/****** Script for SelectTopNRows command from SSMS  ******/
DELETE
FROM [Sharepoint_Content_shpDBName_RestoreFromProductionForTest].[dbo].[AllDocs]
where [Id]='DEF629C6-3A40-473A-BDD5-BB295E9E1AB1'
/**********************************************************/

Result : (1 row(s) affected)


4.       Test that the file is no more listed in the Site:

Voilà, my test in the UAT farm is successful, I’ll do the changes into the Production environment.


That’s all Folks.


nb: change done with success in production.
↧

How to Restore a Deleted Site Collection in SharePoint 2010

May 15, 2013, 1:26 am
$
0
0
Hi all,

Today, I was asked to restore deleted files from a deleted Site Collection in our production farm.

As usual, when I receive this kind of request (recover deleted files) , the procedure is:

-          - Ask SQL Team to restore the DB from the day before deletion
-          - Mount the DB in a  specific Web Application
-          - Set the restored DB as “Offline” in Central Administration
-          - Go to the site and export the deleted files to the client’s SharePoint Site
-          - Remove the restored DB from the Web Application
-          - Delete the DB from SQL


The SQL Corporate rules concerning the backup retention time is 14 days.

But this time, the site was deleted for 16 days, so out of the backup retention time…
No restore available.


Then, I remember that the production DB are keeping the deleted Site Collections for 30 days !!!
Thus I will be able to restore the deleted Site Collection, and my client will be happy to recover all missing files.

Steps to follow are:

-          Get-SPDeletedSite : this will give the list of all deleted Sites Collection in the Farm


In the red box, I can find the Path and the Deletion Time, that match with the info given by the client.

-          I will then restore the Site Collection with the following cmd :
Restore-SPDeletedSite –Identity “/Sites/CD10000059”
               
                /!\ A Site Collection must not already exist at the URL location to perform a restore /!\


Voilà, the site is now restored from the DB’s recycle bin.


That’s all folks
↧
Search

How to restore the "default.aspx" in SharePoint Designer 2010

May 16, 2013, 5:24 am
$
0
0
Hi all,

Today, I got a ticket concerning the fact that the “default.aspx” was deleted in a Site Collection.


My first question was “How did they achieve this?”, because they cannot delete system files, as SharePoint Designer 2010 access is limited at the Web Application level:



So, I had to open the Site Collection in SharePoint Designer 2010 with full access to be able to view all files.

To do this, I’ve allowed the Web Application option : “Allow Site Collection Administrators to see the URL Structure of their Web Site”
Then, I’ve opened the Site Collection in SharePoint Designer 2010, and set back the options in “SharePoint Designer Settings” as our default settings. (this, to avoid other clients to open their site in SharePoint Designer 2010 and letting them braking their site)

In SPD2010 (SharePoint Designer 2010), the “default.aspx” was missing.
But, I saw the file “Organogram.pptx” with the blue icon.
Checking it’s properties gave me the satisfaction that the “default.aspx” was overwritten by the .pptx, but was still known by SharePoint as the “default.aspx” file.





So, I decided to do a “Reset to Site Definition” of this file :



The .pptx file was “cleaned” (check it’s size), and the original faulty .pptx is now set as a copy, and not simply deleted:



Thus, I’ve renamed the “clean” .pptx into “default.aspx



A page refresh, and the client site is now up’n running again:



Job's done.

↧
↧

Event ID: 7362: The super user account utilized by the cache is not configured

June 18, 2013, 2:38 am
$
0
0
Event ID: 7362: The super user account utilized by the cache is not configured


Hi all,

Today, I’ll explain how I solve the Event ID 7362 concerning the Publishing Cache.
I made a copy/paste of the used explanation from Stephan Albert Bren blogspot.
On his page, there is the stsadm version that I didn’t used, because I prefer to use PowerShell version.
Also, check the references at the bottom of his post, referring to Microsoft TechNet and other blogs.

Big thanks to Stephan for his clear explanation of the root cause of this event ID.




Problem

The following error appears in the Windows Application event log:

 

















Solution

On new installations, the SharePoint super user account is configured to run under the machine's local System account.  However, this causes complications and thus the warning.  This should be addressed during setup, but isn't included in the setup wizard. 



Step 1: Create Super User and Super Reader Domain Accounts

Create super user and super reader domain accounts



Step 2: SQL Database access rights

Make sure these accounts have similar access to all SharePoint databases.

Script to use for each Content Database:

SQL Script 1 for adding the Super User account as db_owner:


 










SQL Script 2 for adding the Super Reader account as db_reader:




 Step3: Configure Accounts in SharePoint Central Administration

Go to your SharePoint CA GUI:
Central Admin -> Manage Web Application -> User Policy

Add DOMAIN\super_user           – Full Control
Add DOMAIN\super_reader        – Full Read



Step 3: Using SharePoint Management Shell

Open a SharePoint PowerShell

Execute the following commands:

$w = Get-SPWebApplication -Identity http://[webappurl/]
$w.Properties["portalsuperuseraccount"] = “DOMAIN\super_user”
$w.Properties["portalsuperreaderaccount"] = “DOMAIN\super_reader”
$w.Update()

Close the shell

 





Step 4: Reset IIS

Step 5: Verification

Open a SharePoint PowerShell

Execute the following:

 


 Output should read:
 




Important Note :
Please do the mentioned steps when adding a new Web Application in Application and/or Collaboration Farm.


Source: http://alstechtips.blogspot.be/2012/04/event-id-7362-super-user-account.html


Job’s done.

↧

Unable to enter the Enterprise Licence on SharePoint Server 2010

July 31, 2013, 5:24 am
$
0
0
Hi all,

This time, I was asked to install the Enterprise Licence into our Standard SharePoint 2010 Server test Farms.

We have 3 Farms in Test environment:
-          Collaboration Farm (4 VM)
-          Application Farm (1VM)
-          Service Farm (2 VM)

So, I tried to add the Licence Key via the Central Admin GUI, and I always got an error : “An error occurred”.

After close work with Microsoft, I set the logs into Verbose mode and reproduce the issue, and then finished by running the Microsoft Diagnostic tool for SharePoint.
Then, I got an explanation of my problem.
This issue happens when the Farm does not have enough resources or the load is too high or a combination of both (VM servers, in a test environment – less CPU and less RAM than in production), the upgrade process wants to upgrade all services (new ones for instance) and so on, on all servers.
It’ll try this 3 times, afterwards it gives a time-out as being impossible because the Farm was too busy.

Then, I’ve executed with success the proposed action, explained hereunder:

Action plan:
========

Please take all necessary measures before executing the action plan in order to be able to restore your Farm from backups.


1. Create a simple console application (code) that does nothing, just returns a success code, call it psconfig.exe (see details below)
2. Backup the original psconfig.exe and replace it with the previously created app.
3. Perform the operation (Enable Enterprise features)
4. Restore the original psconfig.exe
5. Run psconfigui.exe on all servers in the farm

Details:

If you don’t have visual studio installed you can use the compiler to create the exe file. 
Steps:  

1. Create new text file and write this piece of code:
Code sample: 

namespace customapp 
{ 
  class Program 
    { 
      static void Main(string[] args) 
        { 
          System.Environment.ExitCode = 0; 
        } 
    } 
}
2. Save the file as psconfig.cs
3. Open a command prompt by choosing “Run as administrator” 
4. Put the created file in c:\<location>
5. Navigate to C:\Windows\Microsoft.NET\Framework64\v2.0.50727 folder 
6. Run the csc command giving as parameter the source file (c:\psconfig.cs) 
• e.g. C:\Windows\Microsoft.NET\Framework64\v2.0.50727>csc c:\psconfig.cs
7. The file psconfig.exe will be created on path C:\Windows\Microsoft.NET\Framework64\v2.0.50727>csc c:\psconfig.cs

==========================================


And that’s it!

Now, I have to plan a technical activity to add the Enterprise Licence into my production Farm.
According to Microsoft specialist, I’ll not facing the same issue as my production Farm has enough CPU/RAM.

But in case of, I have this procedure, tested and approved.


Job’s done.
↧

Error 404 with Calendar Overlay across 2 Web Applications (part 1)

July 31, 2013, 5:50 am
$
0
0
Hi all,

Last week, I received a mail asking me if there was an issue with SharePoint.
The reported problem was that the client got an “Error 404” page when opening an item in her Overlay Calendar.

So, first thing first, is to reproduce the issue;

The client is using a calendar in her SharePoint Site (let’s call it TT2013MMA from the shpTeamCalendar Web Application).
Then she added the calendar of another site (let’s call it WW2013MMA from the shpWorkCalendar Web Application).

All is working like a charm, as the items of both calendars are correctly added, named in the TT2013MMA Calendar.

The problem start when you click on one of the items.
If the item is from the same calendar (the TT2013MMA), the details of this item is opened and can be reviewed/modified.
If the item is from the calendar located on the other Web Application (WW2013MMA), we got a nice looking 404-Error page not found.

I made some research, and I notice that doing calendar overlay across multiple Web Application gave the same problem.


http://sharepoint.stackexchange.com/questions/58218/sharepoint-2010-calendar-overlays-acoss-2-web-appllications               
http://www.dotnetspark.com/links/56569-cant-overlay-calendar-from-differnet-web.aspx      
http://social.technet.microsoft.com/Forums/sharepoint/en-US/7ad58dab-a707-4bf6-ac1d-3fbe20fcfe44/calendar-overlay-across-multiple-site-collections


So, at the request of Microsoft, I’ve reproduce with success the issue in my Test Farm with 2 brand new Web Applications.


Server name : test.domain\TestServerName

Tests were done with in both sites: test.domain\MyLogin (Mathot Marc)

Calendar working with Overlay : http://shpWorkCalendar-test.domain/sites/WW2013MMA
Calendar of the second Web App : http://shpTeamCalendar-test.domain/sites/TT2013MMA


The Overlay Calendar is on http://shpWorkCalendar-test.domain/sites/WW2013MMA
And the item added from this calendar are in green.

The overlayed calendar (from the second Web Application), is on this site :http://shpTeamCalendar-test.domain/sites/TT2013MMA
The items from the TT2013MMA calendar are in yellow.


Calendar using the Overlay in the shpWorkCalendar Web Application:



 Calendar from the second Web Application : shpTeamCalendar






Now, let’s check the URL pointing to the different items in the shpWorkCalendar:
                The URL is correct :
-          Web Application of the Calendar : shpWorkCalendar
-          Site (WW2013MMA) is created on the shpWorkCalendar Web Application



The URL of the item is incorrect:
-          Web Application of the calendar is shpWorkCalendar
-          Site (TT2013MMA) is created on shpTeamCalendar and NOT on shpWorkCalendar.
SharePoint is pointing to the source Web Application (shpWorkCalendar) instead of the correct URL where the item was created.
The correct URL must be : http://shpTeamCalendar-test.domain/sites/TT2013MMA/Lists/Calendar/DispForm.aspx?ID=3





Same fort his second item :
                The correct URL must be : http://shpTeamCalendar-test.domain/sites/TT2013MMA/Lists/Calendar/DispForm.aspx?ID=2








And also for the last one:
               The correct URL must be : http://shpTeamCalendar-test.domain/sites/TT2013MMA/Lists/Calendar/DispForm.aspx?ID=1



  
Result on clicking on the NOK item, is a Error-404 page.


My vendor already made testing, and had the same results as mine.
Now, waiting for the Microsoft specialist to make the same tests, and give his feedback.



So, as far as from now, I have no solution, nor workaround.


... to be continued...

↧

Error 404 with Calendar Overlay across 2 Web Applications (part 2)

August 1, 2013, 12:40 am
$
0
0
Hi all,

This is the reply that I’ve received this morning from our Vendor concerning the Calendar Overlay issues between multiple Web Applications: “it’s by design”.
So, no fix can be expected for this at the moment.

Therefore, I recommend educating the end user to open the item in the correct Web Application when needed.


You can find hereunder the complete explanation:


--------------------------------------------------------------- 
Hello Marc

As I also could repro the issue, MSFT did further research and found that this behavior is ‘by design’.
The issue has been addressed by the product group earlier and this was their answer :


It turns out it is by design:
=====================

We have conducted a thorough investigation into this matter and have determined the issue is Design Change Request in a feature area of substantial complexity. This complexity precludes making changes in this area outside of a major release.

The SharePoint calendar aggregation feature was designed to aggregate calendars within a single web application.
The calendar can aggregate across alternate access mappings, but not across apps. The alternate access mapping support did, however, make it appear that calendars could be aggregated across multiple web apps, but that is not a supported scenario.Adding support for cross web application calendaraggregation would involve significant feature work and as such, is not possible in a QFE.

Microsoft carefully reviews all Hotfix requests, as each code change must maintain or improve both quality and stability of the product.
In this instance, the risks to product quality and potential for destabilization are too high to permit changes in this area outside of a major release.

We thank you for bringing this issue to our attention and continuing to work with us on improving our products for customers worldwide.


The response is actually coming from the product group and they have no ETA on this nor if it will be fixed or not in future releases.
--------------------------------------------------------------- 



Voilà.


↧
↧

PowerShell cmdlets for SharePoint ::: Check DB that must be upgraded

November 28, 2013, 5:24 am
$
0
0
Hi all,

Today, I’ll write down the PowerShell cmdlets used to diagnostic and solve the error “Database is in compatibility range and upgrade is recommended”.

The reason of this error is simple: I ran the SharePoint Feb 2013 Cumulative Update on my production Farm, and I got errors.
Thus, some DB’s are upgraded, other are not.

Now, I want to list them, and check in my test environment if I can upgrade each DB one by one without having my entire Farm down.
If my farm is down during the process, I must prepare a technical activity and work on it during the night.

I found a post from academicjargongiving the cmdlets to use. 

List DB that need to be upgraded:
Get-SPDatabase | ?{$_.NeedsUpgrade –eq $true} | Select Name

List DB that need to be upgraded and upgrade them:
Get-SPContentDatabase | ?{$_.NeedsUpgrade –eq $true} | Upgrade-SPContentDatabase

And this cmdlet if you want to upgrade one specific content DB:
                Get-SPContentDatabase –Identity SP2010_MySiteContentDB | Upgrade-SPContentDatabase



In bonus, another post from academicjargon on How to Install and Configure SharePoint using Windows Powershell.


Job’s done.
↧

How to replace an existing URL located in the Top Navigation Bar

January 27, 2014, 5:42 am
$
0
0
Hi All,

Today's request is to replace the Hyperlink in the navigator bar, as the referenced site URL has changed.




And last but not least, the request is to change this hyperlink to all sites inside the Web App: more than 1800 Site Collection.


This is the used Code:

#----------------------------------------------------------------------
#Below the code to update the topnavigationbar
#  for all Site Collection of the mentioned Web Application .
# Author : Marc Mathot
# Date: November 2013
#----------------------------------------------------------------------
$Webs= Get-SPSite -WebApplication "http://SharePoint.Contoso.com"  -limit ALL | Get-SPWeb -limit all

Foreach($Web in $Webs)
{
$TN = $Web.Navigation.TopNavigationBar | Where-Object {$_.Title -eq "Landing Page & Wiki"}
if ($TN.url -like "http://SharePoint.Contoso.com*")
{
   write-host "Updating $($Web.url)"
  “Updating $($Web.url), $($TN.Url)” | out-file D:\temp\LandingPageUpdate.csv   -append
    $TN.Url = "http://NewSharePoint.Contoso.com/Pages/LandingPageWikiDefault.aspx"
    $TN.update()
}
}
#----------------------------------------------------------------------

Also, in parallel, I had to modify the template used to create the new sites into this Web App.
Doing this will avoid having to run this script periodically to correct the changes.




That's all folks
↧
Search

MissingWebPart Error in SharePoint 2010

January 27, 2014, 5:57 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 proceed:

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

Step 2:
-          Select the WebPart Class GUID

Step 3:
           -     Create the SQL Function and execute it into PowerShell:

function Run-SQLQuery ($SqlServer, $SqlDatabase, $SqlQuery)
{
    $SqlConnection = New-Object System.Data.SqlClient.SqlConnection
    $SqlConnection.ConnectionString = "Server =" + $SqlServer + "; Database =" + $SqlDatabase + "; Integrated Security = True"
    $SqlCmd = New-Object System.Data.SqlClient.SqlCommand
    $SqlCmd.CommandText = $SqlQuery
    $SqlCmd.Connection = $SqlConnection
    $SqlAdapter = New-Object System.Data.SqlClient.SqlDataAdapter
    $SqlAdapter.SelectCommand = $SqlCmd
    $DataSet = New-Object System.Data.DataSet
    $SqlAdapter.Fill($DataSet)
    $SqlConnection.Close()
    $DataSet.Tables[0]
}

-          Run this command with the related WebPart Class GUID:

Run-SQLQuery -SqlServer "SRV_DATABASE" -SqlDatabase "SharePoint_Content_sharepointWorkgroup17" -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, with the URL where the Missing Web Part is located:

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


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

                  Adding at the end of the URL "?contents=1" will let SharePoint to show the "Web Part Page"


-          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.




That's all folks




↧

How to Limit the Self-Service Site Creation in SharePoint 2013 to only users added into a specific AD Group

January 27, 2014, 6:20 am
$
0
0
Hi all,

Today, I was asked to allow the self-service site creation for the mySite in my SharePoint 2013 Farm.
As the audience will be only for the test users, I've decided to do in the same way as I've done for my SharePoint 2010 Farm.

1-      Creation of a new AD Group.
          


2-      Set the Self-Service Site Creation to "ON":
          In Central Administration, highlight the mySite Web App
          


          Select the MYSITE Web App, then review all 5 sections:
-          Self-Service Site Creation
-          User Permissions
-          User Policy
-          Anonymous Policy
-          Permission Policy


               

o   Self-Service Site Creation:
              

o   User Permissions: check this in the "Site Permissions" section
         

o   User Policy: use the default values

o   Anonymous Policy: use the default values

o   Permission Policy: use the default values




3-      Configuration of the User Profile Service Application:

In Central Administration, select the "Manage Service Applications" link:

In the "Service Applications" page, select the "User Profile Service Application":



            Now, select "Manage User Permissions" from the "People" section:
              
           From this Window, I've added my AD Group (in blue):

                


The settings for my AD Group is : thus, only users present in this AD Group will be able to create on demand their mySite when entering their mySite URL : http://mySite-uat.xxx.net
               

Do not forget to uncheck the "Create Personal Site" entry to all other groups, otherwise everybody from the organisation will be able to create his mySite.
               





That's all folks



↧
↧

SharePoint 2010 : The search function does not seem to work in some cases.

January 28, 2014, 5:55 am
$
0
0
Hi all,

Today, I decided to figure out with a recurrent problem with the Search engine.
Search engine, is the standard version of SharePoint 2010 (not the enterprise version).

And, customers are always complaining about it, saying that it’s not always working.
After checking, testing and log-reading, the only visible thing is : search is working O_°

So, today, I made long tests and reproduce the problem, and give a credible explanation to my customer.

The problem is that the customer is trying to search as in Google, with part of the name.
What is wrong?
It should give back some results, but there is only the “no results found” page sent back to him.


So, I discover that the search engine will only search for the exact word in the path of the file, but it’ll give a result only if the keyword is not part of a word in the file name.

In my example, the customer is trying to have results for “VE11”.
There is no word “VE11” in the library.
But there is “VE 11” in the library, and the search is using them as 2 keywords: “VE” & “11”, and search for each of them.



Input from my customer:
Keyword(s) : SharePoint 2010 : Contoso Internal
Site URL : http://shareppoint.contoso.com/sites/YourSite/default.aspx
Make your selection : Probleem
Describe : The search function does not seem to work in some cases.
Een voorbeeld uit de library “CCJ requests invoiced” op batch datum 11/12/2013:
Example: If we search on “VE 11” as part of a file name from the "CCJ requests invoiced" library, we get no result. If we search on another part of that same file name e.g. “345340” we do find a result. Idem for a search on “TU60” without result, whereas “345225” from the same name, does give a result.
Attachment : Ja

My research and conclusion:
Checked search.
Result found with all given examples.
Test with: "VE 11" and "345340"
VE 11 => several results
               

345340 => 1 result
               

VE11 => no results

VE11L3005493 => 1 result : VE11L3005493 13 ccj 345340.msg

Try to search with this word “ve11l3005493”, starting with first letter, then adding eachletter one by one.
You’ll find out how the search engine of SharePoint 2010 is working.
The search is indexing complete part of the names of the file name, not part of the different names making the filemane.
The matching result is always written in bold.
This is the reason why there is no result for "VE11", but you gor result for "345340", and also results for "VE 11" (as "VE" and "11" are indexed by the SharePoint search engine.



Then, I decided to make a last test : writing the keyword between asterisk  è*VE11*
Et voilà.







That’s all Folks


↧

How to sign in as a different user in SharePoint 2013

February 25, 2014, 1:04 am
$
0
0
Hi all,

Today I had to login to a SharePoint 2013 site with the farm account, from my desktop.

I simply add “/_layouts/closeConnection.aspx?loginasanotheruser=true” after the site URL :

http://MyProjectSite.contoso.com/Sites/Shp4DummiesProjects/_layouts/closeConnection.aspx?loginasanotheruser=true



Voilà,

That’s all Folks !!!
↧

Issue with SharePoint 2013 Farm Update

June 22, 2014, 12:29 pm
$
0
0
Hi all,

Last week, I was facing lot of issue applying the SharePoint 2013 SP1 upgrade.

First, was installing the binaries on each SharePoint 2013 server.
It took me an average on 2:30 hours per server.
The only advantage is that the binaries can be installed on each Farm server at the same time.

Then, I've prepared all my SharePoint Servers (15 servers ....) with the SharePoint Configuration Wizard.

At that moment, I was facing an extreme long long long configuration time for the Wizard.

Checking the sharepoint logs, I had only lines about PowerShell doing something... time to time.


After restarting the Wizard several times, and letting the Wizard working at his own way, I discovered that using the Configuration Wizard was not the solution.
Thus, I've decided to do the configuration via the psconfig.exe.
When there is an error, it shows clearly the issue.

Thus, I've discovered that executing the configuration wizard with the Install account gave issue in the database access.
When executing the configuration wizard with the Farm account, it gave insufficent access rights to some DB.

At that point, I've asked to our SQL Team to set the Farm and the Install account as dbo (db owner) to all DB's of the Farm.

Thus, executing the configuration wizard went without any issue, and each server was configured, one by one in less than 30 minutes each.


I've asked our Microsoft consultant about this issue, and he was not aware of the problem.
I've showed him my server, and he told me (before I discover the problem) that powershell was still working, and I have to wait....


So, before installing SP1 (or CU, or PU), do not forget to double check the access rights of your farm and install account.
Doing this will save you lot of time when installing SP, CU or PU in SharePoint 2013 (and in extension for SharePoint 2010)


Voilà, I hope it'll help you saving lot of time.


Job's done.
↧
Viewing all 60 articles
Browse latest View live
Search