SharePoint 2010 , Version :14.0.6117.5002 ,SQL 2008 R2

We were unable to export the SharePoint My Site profile picture to Active directory.

We were seeing "Completed export error" in the MIISclient.

This usually happens when we use the different path to upload picture like: https://mysite/my/customPicLIb not the default SharePoint location https://mysite/my/USER%PHOTOS.

Hence we were not seeing any picture in the https://mysite/my/USER%PHOTOS location.

We were seeing below error when we have executed the following command.

Update-SPProfilePhotoStore -MySiteHostLocation https://mysite/my

____________________________________________________

Update-SPProfilePhotoStore : Error processing the photo URL https://mysite/my/customPicLIb/userAlias.jpg for user Domain\user

6493: The file https://mysite/my/customPicLIb/userAlias.jpg does not exist.

At line:1 char:27

+ Update-SPProfilePhotoStore <<<< -MySiteHostLocation "https://mysite/my

+ CategoryInfo : WriteError: (:) [Update-SPProfilePhotoStore], Fi

leNotFoundException

+ FullyQualifiedErrorId : Microsoft.Office.Server.UserProfiles.PowerShell.

SPCmdletUserProfilePhotoStore

__________________________________________________

We have to remove the pictures from the user profiles for the users who have "X" mark in the MySite.

And After that we have to execute the "Update-SPProfilePhotoStore" command.

Update-SPProfilePhotoStore -MySiteHostLocation https://mysite/my/

all the users profile pictures should get imported in the https://mysite/my/USER%PHOTOS location.

We will see the user photo pictures in 3 different size.

Run the full profile import after that and pictures got export successfully in the AD.

Disclaimer

All posts are provided "AS IS" with no warranties, and confers no rights.

Recently I came across one interesting issue, When we tried to view the site usage report for the site collection "https://testsite/_layouts/SpUsageSite.aspx" and the "queries over past 30 days" are not displaying any data.

but it was showing the site usage report correctly for each day.

We have checked and found in the verbose ULS logs that “Office SharePoint Usage Analytics Log Processing” job was not running even though it was scheduled to run every 15 min daily on all the servers.

If job will be successfully executed then it should show this logs entry in the ULS logs. in our case it was not showing it.

Example:

5/18/2012 11:45:11.60 OWSTIMER.EXE (0x1CB4) 0x0978 Windows SharePoint Services Timer 5utp Verbose Scheduled timer job Office SharePoint Usage Analytics Processing, id {} at 18 May 2012 12:00:11 +0530 (now is 18 May 2012 11:45:11 +0530)

05/18/2012 11:45:11.60 OWSTIMER.EXE (0x1CB4) 0x1E18 Windows SharePoint Services Timer 8e45 Verbose Begin invoke timer job Office SharePoint Usage Analytics Processing, id {}, DB n/a

05/18/2012 11:45:11.63 OWSTIMER.EXE (0x1CB4) 0x1E18 Windows SharePoint Services Timer 8e46 Verbose End invoke timer job Office SharePoint Usage Analytics Processing, id {}, DB n/a

I have fixed the issue by following the below steps:

- Stop the timer service on all the SharePoint server.

- Disable and enable the following usage timer jobs from the central admin site.

· Usage Analysis (for the web applications)

· Office SharePoint Usage Analytics Log Import

· Office SharePoint Usage Analytics Log Processing

- After that start the timer service.

More Info about site usage report

If job will be successfully executed then it should show this logs entry in the ULS logs.

Example:

5/18/2012 11:45:11.60  OWSTIMER.EXE (0x1CB4)                    0x0978 Windows SharePoint Services    Timer                          5utp Verbose  Scheduled timer job Office SharePoint Usage Analytics Processing, id {CBAAE9CA-CD78-4476-8A46-0186D9728880} at 18 May 2012 12:00:11 +0530 (now is 18 May 2012 11:45:11 +0530) 

05/18/2012 11:45:11.60  OWSTIMER.EXE (0x1CB4)                    0x1E18 Windows SharePoint Services    Timer                          8e45 Verbose  Begin invoke timer job Office SharePoint Usage Analytics Processing, id {CBAAE9CA-CD78-4476-8A46-0186D9728880}, DB n/a 

05/18/2012 11:45:11.63  OWSTIMER.EXE (0x1CB4)                    0x1E18 Windows SharePoint Services    Timer                          8e46 Verbose  End invoke timer job Office SharePoint Usage Analytics Processing, id {CBAAE9CA-CD78-4476-8A46-0186D9728880}, DB n/a 

“Office SharePoint Usage Analytics Log Processing”  job responsible for processing the search queries usage data like: "queries over past 30 days"  and this Job run every 15min.

Means, we should see the new search queries usage data every 15 min in the site usage reports. How to verify: we can see that search keyword in the “SpUsageSiteSearchQueries.aspx" page. Screenshot attached for reference.

In backend, “SpUsageSiteSearchQueries.aspx" page pull up the data from the Sharepoint DB.

Description of the Project Server 2010 cumulative update package (Project server-package): April 24, 2012
Note: By installing this package, you will apply the whole cumulative update for Project Server, SharePoint Server, and SharePoint Foundation. It includes all applicable updates from the list of individual server updates in the following table.     Project Server 2010

SharePoint server-package     2598151 https://support.microsoft.com/kb/2598151 

Description of the SharePoint Server 2010 cumulative update package (SharePoint server-package): April 24, 2012
Note: By installing this package, you will apply the whole cumulative update for SharePoint Server and SharePoint Foundation. It includes all applicable updates from the list of individual server updates in the following table.     SharePoint Server 2010

SharePoint Foundation server-package     2598321 https://support.microsoft.com/kb/2598321 

Description of the SharePoint Foundation 2010 cumulative update package (SharePoint Foundation server-package): April 24, 2012    SharePoint Foundation 2010

Recently came across with one Membership issue, we were unable to see the Membership Tab in my profile Users memberships and Also we were not able see in the MIISclient even though the User Profile Full Synchronization Job was completed successfully.

In the ULS logs also we were not seeing any error.

I have managed to resolve the issue by following below steps.

Attribute hideDLMembership was set to "True" for the AD Groups hence it was not getting Exported in the MIIScleint.

• You can use your LDAP/Active Directory tool of choice, including ADSIEdit, to modify it.

• AD security group Attribute hideDLMembership we need to set as FALSE.

• Re-run the Profile import again. Now we will see that AD groups in the MIISclient and MySite Membership page.

More Details:

You can run the following command against the problematic AD groups in the AD and get to know about the properties.

ldifde -m -f c:\output.txt -d "CN=test,cn=USERS,dc=dctest,dc=com"

In the output.txt we can find the "hideDLMembership" details.

OR

We can take the netmon trace from the Sharepoint server while running the import in the UPA.

Open the Netmon logs and type below filter string in the "Filter Option".

ContainsBin(FrameData, ASCII, "hideDLMembership")

you will find the below:

""""""""""

2075481 8:24:56 PM 4/23/2012 1381.1918453 miiserver.exe Uñ..äó.Òh.ÿ!.ÑK.×Â.Øc.Õ©.üÛ.±’Ò..פ.ûÞ.úŠ.;top.group...V.€œ.€Ô.û...û+..û:...Ñ....displayName.testgrp....Ñ....groupType.0xffffffff80000002.."Ñ.

...hideDLMembership..true...„..member

"""""""""""

When we put “=Today+5” in the Calculated Value box in the site column(Example:’startdate’), only the users who have Site Collection Administrator permissions can add new items to the list; all other get “Access Denied” even if they have “full control” permissions on the list.

Product

SharePoint 2007, WSS 3.0

Resolution

We need to add the same ‘user’ or ‘AD group’ in the "Restricted readers" group in the root site collection, after that we should be able to create a ‘new item’ using the ‘date calculated column’ in the custom list.

Note:

If we are using a 'unique permission'  for the “subsite” where the custom columns is added, then we need to add the same ‘user’ or ‘AD group’ in the "Restricted readers" group in the “subsite” only.

Search keyword
-------------------
MOSS 2007,  Calculated Value ,  “=Today+5”, custom site column

Disclaimer

All posts are provided "AS IS" with no warranties, and confers no rights.

Unable to create a site collection using the custom template in the central administration site. But able to create the site collection using the OOB template.

Following error gets in the event viewer.

Event ID: 4965

Task Category: Publishing Provisioning

Source: Office SharePoint Server

Event log message was: 'Failed to initialize some site properties for Web at Url: '<https://sharepoint/en-us'>'. Exception was: 'System.UnauthorizedAccessException: Attempted to perform an unauthorized operation.

at Microsoft.SharePoint.SPGlobal.HandleUnauthorizedAccessException(UnauthorizedAccessException ex)

at Microsoft.SharePoint.SPWeb.EnsureUser(String loginName)

at Microsoft.SharePoint.Publishing.CacheManager.<.ctor>b__0()

at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state)

at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2()

at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)

at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)

at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)

at Microsoft.SharePoint.Publishing.CacheManager..ctor(SPSite site)

at Microsoft.SharePoint.Publishing.CacheManager.GetManager(SPSite site, Boolean useContextSite)

at Microsoft.SharePoint.Publishing.CacheManager.GetManager(SPSite site)

at Microsoft.SharePoint.Publishing.PublishingWeb.get_PagesListId()

at Microsoft.SharePoint.Publishing.Internal.AreaProvisioner.InitializePublishingWebDefaults()'

RESOLUTION:

I managed to resolve the issue by entering the correct SharePoint farm account in the central admin application pool.

We can also resolve this issue by re - syncing the SharePoint farm account using this KB '934838' article also. If you are not sure where we have changed the farm account manually in SharePoint services.

Search Keyword

MOSS 2007, 'System.UnauthorizedAccessException:'

Then to fix the issue, You need to install MOSS 2007 with SP2 in the server.

Related KB : You cannot upgrade from Windows Server 2008 to Windows Server 2008 R2 after you install Office SharePoint Server 2007 on a computer that is running Windows Server 2008

https://support.microsoft.com/kb/962935 

Below are the steps to create a “slipstream” for the MOSS 2007, which will include the MOSS SP2 binary. 

1. Download a WSS 3.0 and MOSS SP2.

Link:

Windows SharePoint Services 3.0 Service Pack 2 (SP2) - English

https://www.microsoft.com/downloads/details.aspx?FamilyId=79BADA82-C13F-44C1-BDC1-D0447337051B&displaylang=en

The 2007 Microsoft Office Servers Service Pack 2 (SP2)

https://www.microsoft.com/downloads/details.aspx?FamilyId=B7816D90-5FC6-4347-89B0-A80DEB27A082&displaylang=en

2. Go to Start -> “Run” and extract both the SharePoint SP2 pack with this command and save in the “Updates” folder inside the MOSS binary location, like “c:\MOSS_setup\updates and after that run “setup.exe” for the MOSS 2007 installation.

Note:  Delete Wsssetup.dll from the "Updates" folder, this is important. Otherwise only WSS SP2 will be installed.

Installation should complete without an error.

Command:

c:\WSS-SP2\wssv3sp2-kb953338-x64-fullfile-en-us.exe /extract

c:\MOSS-SP2\officeserver2007sp2-kb953334-x64-fullfile-en-us.exe /extract

Screenshot for reference.

Search Keyword

MOSS 2007 installation issue with Windows 2008 R2

Disclaimer:

All posts are provided "AS IS" with no warranties, and confers no rights.

Recently, I have faced one issue related to the Sharepoint alerts. SharePoint server was unable to send the email alerts to the users.

Reason, Exchange 2007 server was blocking “Anonymous users” emails. We have enabled the “Anonymous users” settings in the “Hub transport” server, after that Sharepoint alerts started working.

Info : In exchange 2007 server by default “Anonymous users” is disabled. But in the Exchange 2003 “Anonymous users” is enabled by default.

Below are steps to enable the “Anonymous users” in the Exchange 2007 server.

We have two method to enable the “Anonymous users” emails from the exchange server.

First method

Example:

Exchange Hub transport IP Address : 10.0.0.1

SharePoint Server IP Address : 10.0.0.10

1.  Open a “Exchange Management Console” in Exchange 2007 server.

2. Select “Default” receive connectors and Right click –> “Properties”

3. Check on the “Anonymous users” from the list and click on “OK” to apply the settings.

Note: Above settings will enable the “Anonymous users” for all the incoming email traffic from all the external domains.

If we want to configure the “Anonymous users” for specific to SharePoint server. We can achieve that also by following below steps. 

Second Method :

We need to create a new separate connector to enable the “Anonymous users” for all the SharePoint email alerts.

1. Open a “Exchange Management Console” in Exchange 2007 server.

2. Right click on the “Receive connector area” and select the “New Receive Connector”.

3. In the wizard, type “Name” of the connector.

Example:

Exchange Hub transport IP Address : 10.0.0.1

SharePoint server IP Address : 10.0.0.10

4. “Add” the IP address of the “Hub transport” server.

5. “Add” the IP address of the “SharePoint Server” server.

6. Click on “New” to create the new “receive connector”.

7. Click on “finish” the wizard.

8. Now right click on the “Sharepoint” connector and Go to “Properties” section.

9. Select the “Anonyms users” and click on “Apply” button.

After that click on “OK” button to save the settings.

10. Subscribe for the email alerts in the SharePoint site.

Now you will get the SharePoint “Alerts” for that users.

Keyword for search: “The e-mail message cannot be sent. Make sure the outgoing e-mail settings for the server are configured correctly.”

                     MOSS 2007, WSS 3.0, Outgoing Email is not working in SharePoint site.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Disclaimer:

All posts are provided "AS IS" with no warranties, and confers no rights.

SYMPTOMS:

When you tried to delete the SSP from the search admin page, if you are getting

this error.

"Unprovisioning Failed:"cannot open database "<search database >""

OR

If you tried to delete the SSP using the Command line you will get this error

message "cannot open database "<search database >" ".

Resolution:

• Create a new dummy database with the same name(we can see the database name in the error) in the SQL server using the SharePoint admin account.
• Run this command in the command prompt.

"stsadm -o deletessp -title ShareServiceName -force"

• We should be able to delete the SSP in the MOSS server.

 If you are unable to see the properties of document library items in the SharePoint site and getting "unexpected error has occurred" and after enabling the callstack ="true" and customerrors = "OFF", getting below error

Error Message

 Server Error in '/' Application.

------------------------------------------?

Cannot find ContentPlaceHolder 'PlaceHolderLeftNavBar' in the master page '~masterurl/default.master', verify content control's ContentPlaceHolderID attribute in the content page.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

?

Exception Details: System.Web.HttpException: Cannot find ContentPlaceHolder 'PlaceHolderLeftNavBar' in the master page '~masterurl/default.master', verify content control's ContentPlaceHolderID attribute in the content page.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.?

?

Stack Trace:

[HttpException (0x80004005): Cannot find ContentPlaceHolder 'PlaceHolderLeftNavBar' in the master page '~masterurl/default.master', verify content control's ContentPlaceHolderID attribute in the content page.]

?? System.Web.UI.MasterPage.CreateMaster(TemplateControl owner, HttpContext context, VirtualPath masterPageFile, IDictionary contentTemplateCollection) +1190

?? System.Web.UI.Page.get_Master() +65

?? System.Web.UI.Page.ApplyMasterPage() +18

? ?System.Web.UI.Page.PerformPreInit() +61

?? System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1272

Specific error message

-----------------------------

Cannot find ContentPlaceHolder 'PlaceHolderLeftNavBar' in the master page '~masterurl/default.master', verify content control's ContentPlaceHolderID attribute in the content page.

Note:

Modify the "default.Master" page in SharePoint is not recommended. Always create a copy of master page and then modify the copied master page as per the requirement.

Some good TechNet article which talk about this.

Building Simple Master Pages for Windows SharePoint Services 3.0

 <https://msdn.microsoft.com/en-us/library/bb684920.aspx>

How to customize application pages in the Layouts folder in SharePoint Server 2007 and in Windows SharePoint Services 3.0

https://support.microsoft.com/kb/944105

Reason for this error.

ContentPlaceHolder 'PlaceHolderLeftNavBar' missing in the  in the custom Master page.

 I got this error on the custom master page not in the "Default OOB " SharePoint Master page. 

I have done following steps to resolve the error in the Custom Master page

o     Open a SharePoint Designer.

o     Open the site by clicking File | Open Site options.

o     Expand the _catalogs folder.

o     Expand the MasterPage Gallery Folder.

o     Right click on the custom masterpage you want to work with and select Check Out.

o     Now open the custom Master page again.

o     In the Find and Replace dialog, enter this : "<asp:contentplaceholder" (without quotes) and Clicked on Find All.

o     Add below code in the custom master page.

 <asp:ContentPlaceHolder id="PlaceHolderLeftNavBar" runat="server"/>

o     Saved the Custom Master page and "check in" the Custom Master page.

o     After this we should be able to view the properties of the documents in the document library.

------------------------------------------------------------------------------------------------------------------------------------------

Disclaimer:

All posts are provided "AS IS" with no warranties, and confers no rights.