Skip to content

SharePoint: Error: Failed to activate feature 'PublishingPrerequisites'

SharePoint V3: Error: Failed to activate feature ‘PublishingPrerequisites’

 
Description:
Receiving error when attempting to activate the Office SharePoint Server Publishing Infrastructure, site collection feature:

Error: Failed to activate feature ‘PublishingPrerequisites’


Solution:

- Run IISReset on the front end web servers — Start > Run > CMD > iisreset /noforce

- Activate the feature
Site Actions > Site Settings > Site Collection Features > Office SharePoint Server Publishing Infrastructure > Activate

SharePoint MySite Portal Home Link

The problem is when you view a MySite, you don’t get a link back to your Portal site.  Easy enough to add a link in SharedServices1 > Personalization site links.  Except that when you click and return to your Portal, the menu has retained the MySite navigation because the URL contains “?MySiteView=1″.

The solution (as per link) is to add a # on the end of the URL you enter in Personalization Link like this http://server/sites/home/#, this makes the rest of the link an anchor so SP will ignore it and display your normal menu.


Picture Library SlideShow Webpart for SharePoint 2007

Picture Library SlideShow Webpart shows all the pictures from the picture library in a slide show format. The image transformations can be selected list of available transformations. Fill in the picture library name in the Custom Property.

Download from codeplex : Download Picture Library SlideShow Webpart

Employee Directory Webpart for SharePoint 2007 user profiles

The Employee Directory webpart displays a complete list of all Active Directory profiles imported by the SSP into SharePoint 2007.

Features:

1. Displays a complete list of all Active Directory profiles imported by the SSP into SharePoint 2007.
2. Displays the following fields on the list: Photograph, Name, Department, Job Title, Email Address, Work Phone, Cell Phone.
3. Allows the user to sort the list by Name, Department, Title, Cell Phone, Work Phone, Email
4. Allow searching of the list by Name or Department
5. Allow grouping of the list by Department
6. Allows Filter on Name, Department, Title columns
7. Provide link to each employee’s person.aspx (mySite) page display other details about the employee.

Download the webpart (wsp) file from codeplex : Download Employee Directory WSP

SharePoint 2007 Design Tip: Import your CSS for SharePoint Themes

SharePoint 2007 Design Tip: Import your CSS for SharePoint Themes
 
One of the major drawbacks of SharePoint themes is you have to reapply the theme to any site that uses your custom theme in order to see any new changes that you have made.  This happens because when you apply a theme to a SharePoint site, a copy of the theme is added for the site in the content database. 
Try it out, open a test site in SharePoint Designer and look at the folder structure in the Folder List task pane.  If you have already applied a theme to this site, you will see a _themeF5_theme folder will appear if you didn’t have a theme applied the first time, and the sub folder under this directory will change to reflect the theme you just applied. folder. If you have not applied a theme to this site, then this folder will not appear.  Expand the folder and you will see a single sub folder named the same as your theme.  Now go and change the theme the site uses through a browser.  Return to SharePoint Designer and hit to refresh the Folder List.   The
When you make a change to the theme files on the web server, it does not update any copies of the theme that live in the content database.  When you apply a new theme in the browser, it replaces the copy in the content database with a new theme.  That is why you have to physically reapply a theme when you make changes, you have to replace the theme copy in the content database.
From a development perspective, the theme copy in the content database is rather handy.  If you update any of the files in the content database (by changing the CSS files in SharePoint Designer and importing in new images), the changes automatically appear in the browser. Woo-hoo! This just made life easier when it comes to developing themes.
But after you finish up development, you are stuck back with the problem of how to update your theme in the future, especially if it is applied to several sites.  This is where this trick comes in.

Import CSS to Create Editable Themes

Create a copy of the final theme.css file and store it in another location on the web server, such as:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033\STYLES\YOURCUSTOMFOLDERHERE
You can even rename the file, it no longer needs to be named theme.css.

Open the original theme.css file in the custom theme folder, delete out all of the contents, and add an import rule for your new CSS file:
@import “/_layouts/1033/styles/YOURCUSTOMFOLDERHERE/theme.css”;

Save the file and deploy your theme (add text to SPTHEMES.xml and reset IIS).   Apply your new theme to the site.  Now go to the new CSS file in the Styles folder and make a change.   Refresh your browser.  Your change will appear.  That is cool.
By moving around your files and using the import rule  you can create a theme that you can update without reapplying the theme to every site that uses it.  Be sure to update your image paths in your CSS styles to a location where you can edit the images as well, such as:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\IMAGES\YOURCUSTOMFOLDERHERE 

Below are a couple of screen shots for the end result of this method.
View of the file structure on the web server
Image showing file structure on the web server
View of the theme folder and the theme.css file that is still in the theme folder
Image showing custom theme folder and custom theme.css file

ड्रीम्स

कभी-कभी बहुत सारे ड्रीम्स में से एक पूरा हो जाता है, उसके लिए बहुत मेहनत करनी पड़ती है और अपने आप पर भरोसा करना पड़ता है, जिंदगी एक चांस सभी को देती है!

Enabling and Disabling mySite in SharePoint 2007

Enabling mySites in SharePoint 2007:

  1. Go to the Shared Service Provider that is hosting the MySites
  2. Go to Personalization Services Permissions
  3. Add or Edit the user account you want to enable the MySites functionality for.
    1. If you want to give all authenticated users permissions then edit the NT Authority\Authenticated Users account
    2. If you previously deleted the Authenticated Users Account then you might have to add it back in if the first part of step 3a remains true.

  4. When you get to the permissions screen check these 2 permissions
    1. Create Personal Site
    2. Use Personal Features.

Disabling mySites in SharePoint 2007:

In order to turn off or disable the MySite or MyLinks functionality you need to be an Sharepoint administrator.
Go to the Central Administration Web Page
Click on the link for Shared Services Administration
     –If you have more than one SSP, select the one that is running the MySites functionality
Under “User Profiles and My Sites” click Personalization Services Permissions
Select the group you want to limit the functionality for.  More than likely you will just have NTAuthority\Authenticated Users.
In the next screen you will see a list of checkboxes,
     –To disable MySites uncheck “Create Personal Site”
     –To disable MyLinks uncheck “Use Personal Features”

Geeta Saar

  • क्यों व्यर्थ की चिंता करते हो? किससे व्यर्थ डरते हो? कौन तुम्हें मार सक्ता है? आत्मा ना पैदा होती है, न मरती है।
  • जो हुआ, वह अच्छा हुआ, जो हो रहा है, वह अच्छा हो रहा है, जो होगा, वह भी अच्छा ही होगा। तुम भूत का पश्चाताप न करो। भविष्य की चिन्ता न करो। वर्तमान चल रहा है।
  • तुम्हारा क्या गया, जो तुम रोते हो? तुम क्या लाए थे, जो तुमने खो दिया? तुमने क्या पैदा किया था, जो नाश हो गया? न तुम कुछ लेकर आए, जो लिया यहीं से लिया। जो दिया, यहीं पर दिया। जो लिया, इसी (भगवान) से लिया। जो दिया, इसी को दिया।
  • खाली हाथ आए और खाली हाथ चले। जो आज तुम्हारा है, कल और किसी का था, परसों किसी और का होगा। तुम इसे अपना समझ कर मग्न हो रहे हो। बस यही प्रसन्नता तुम्हारे दु:खों का कारण है।
  • परिवर्तन संसार का नियम है। जिसे तुम मृत्यु समझते हो, वही तो जीवन है। एक क्षण में तुम करोड़ों के स्वामी बन जाते हो, दूसरे ही क्षण में तुम दरिद्र हो जाते हो। मेरा-तेरा, छोटा-बड़ा, अपना-पराया, मन से मिटा दो, फिर सब तुम्हारा है, तुम सबके हो।
  • न यह शरीर तुम्हारा है, न तुम शरीर के हो। यह अग्नि, जल, वायु, पृथ्वी, आकाश से बना है और इसी में मिल जायेगा। परन्तु आत्मा स्थिर है – फिर तुम क्या हो?
  • तुम अपने आपको भगवान के अर्पित करो। यही सबसे उत्तम सहारा है। जो इसके सहारे को जानता है वह भय, चिन्ता, शोक से सर्वदा मुक्त है।
  • जो कुछ भी तू करता है, उसे भगवान के अर्पण करता चल। ऐसा करने से सदा जीवन-मुक्त का आन्दन अनुभव करेगा।

ASp.NET Dynamic Menu (Sitemap) does not work in IE 8.0

ASP.NET sitemap dynamic menu renders nice in FF2, FF3. But it never worked right in IE7 and IE8. I was never able to justify the (probably many) hours it would take to troubleshoot the css. Just getting my site working as well as it does was enough to turn my antipathy toward web UI work into tangible dislike. I also tried using Superfish menus, the sample downloaded worked fine with did not work with my website in IE8.

(I know some people enjoy web UI work. I’ve only found it to be one of the most frustrating experiences in all the years I’ve been programming Seriously – could we have invented anything more arcane??)

Until I try to navigate using one of the drop-down menus. All that appears is a while box! How can IE8 not render an ASP.NET Menu control?!?!?!?!?!

Well, it turns out that this is a known issue that the IE8 and ASP.NET teams are working on. It also turns out that it is apparently a z-order issue with the Menu control and the way it renders, so it can be argued that IE8 is actually doing the “right thing” (even though other browsers, including FF3 render the way I’d expect).

In my case, I’m using themes and skins, and so I am using a css style to fix the z-order.

To do this, I added the workaround to my site-wide css style sheet:

.IE8Fix
{
z-index: 1000;

}

And then I edited my skin file to apply this style to all my Menu controls:

<asp:Menu runat="server" BackColor="#83B8E4"



This was easy for me, because I already had the skin set up to apply numerous other properties and styles to the elements of the Menu control. I simply added the CssClass property to the existing DynamicMenuStyle element.

I published the project to my web server and just like that my Menu control is displaying correctly in IE8.

Great!

Synchronize Outlook contacts with MS SQL Database

Project Description
In this application we have two features. One is to IMPORT all the contacts, second is export from Outlook to MS SQL database.
This is useful for the first time. And the second time is for synchronizing between Outlook and Database.

Features:
1. Import Contacts to Outlook from Database.
2. Export Contacts from Outlook to Database.
3. Synchronizing Contacts between Outlook and Database. If any information changes in the backend or in the outlook contacts it will updates that info.
If a new contact is found, then it will add that contact to outlook contacts or database while synchronizing.

Additional information and download is available here: information and download.

next release will contain sending bulk emails to stored address in the database.

keywords:
bulk email, sync, synch, outlook, import contacts, export contacts, outlook contacts, mass mail, bulk mail, mass email, synchronization