2011 in review
The WordPress.com stats helper monkeys prepared a 2011 annual report for this blog.
Here’s an excerpt:
The concert hall at the Syndey Opera House holds 2,700 people. This blog was viewed about 22,000 times in 2011. If it were a concert at Sydney Opera House, it would take about 8 sold-out performances for that many people to see it.
A day in SharePoint Admin
I had recently created MySite in SharePoint 2010. The database is used from a MOSS 2007 farm, which have been upgraded to SharePoint 2010. I was trying to create a wiki library with some pages inside it to enable Rating system for pages and libraries. By going to library setting, i was not able to find this option.
I then did the best thing i do, googled it and found that the site should have the these two features enabled in order to get this setting:
site collection feature – SharePoint Server Publishing Infrastructure
Manage Site features – SharePoint Server Publishing
When i tried to enable the “SharePoint Server Publishing” it was asking to enable the “site collection features” first.
I went to enable the “SharePoint Server Publishing Infrastructure” but each time i was getting the below error message:
One or more field types are not installed properly. Go to the list settings page to delete these fields.
I then deleted the wiki library completely which i created to do some test and tried to enable the feature again but still i got the same error.
I then did some research again and found following links:
http://www.experts-exchange.com/Networking/Telecommunications/IP_Telephony/VoIP/Q_26362068.html
This links talk about finding a hidden list i.e. http://(yoursiteurl)/Relationships%20List/allitems.aspx and recreate the list.
I opened the MySite in SharePoint Designer 2010 but i pulled my hair out to no avail as the list was not showing anywhere.
Finally i notices that i use a RSS viewer web part to pull some comic site
(http://feeds2.feedburner.com/DilbertDailyStrip )
I removed that RSS viewer webpart from the top page of Mysite.
Again tried to activate the “SharePoint Server Publishing Infrastructure” and WALLAAH!! The feature is activated successfully.
Just another day of sharepoint Admin. Cheers!!
2010 in review
The stats helper monkeys at WordPress.com mulled over how this blog did in 2010, and here’s a high level summary of its overall blog health:
The Blog-Health-o-Meter™ reads This blog is on fire!.
Crunchy numbers
A helper monkey made this abstract painting, inspired by your stats.
The average container ship can carry about 4,500 containers. This blog was viewed about 21,000 times in 2010. If each view were a shipping container, your blog would have filled about 5 fully loaded ships.
In 2010, there was 1 new post, growing the total archive of this blog to 25 posts.
The busiest day of the year was September 14th with 123 views. The most popular post that day was Event ID 8214: “Object reference not set to an instance of an object”.
Where did they come from?
The top referring sites in 2010 were eventid.net, google.com, experts-exchange.com, google.co.in, and social.technet.microsoft.com.
Some visitors came searching, mostly for object reference not set to an instance of an object sharepoint check out, event id 8214, and sharepoint object model interview questions.
Attractions in 2010
These are the posts and pages that got the most views in 2010.
Event ID 8214: “Object reference not set to an instance of an object” May 2009
17 comments
WSS 3.0: When trying to search on sharepoint site, Getting message “No results matching your search were found.” June 2009
11 comments
After installing the updates or service pack, getting error message accessing the site “Server error: http://go.microsoft.com/fwlink?LinkID=96177″ May 2009
3 comments
Search Administration Error: An error occurred during the processing of . The resource object with key ‘S2SearchAdminDashboard_Title’ was not found. June 2009
1 comment
SharePoint 2010| How to configure Claim or forms authentication for (SUN One Ldap) in sharepoint
ISSUE:
*****
–>You have a SharePoint site http://sharepoint and you are trying to configure the site with Forms based or claims based authentication for SUN One LDAP.
Resolution:
*********
- Open central administration
- Go to Application management—manage web applications
- Choose new on the ribbon and create a new web application
- While creating the web application, choose Claims Authentication
- Open IIS Manager and make backup of web.config files for central administration, sharepoint site and STS(security token services)
Web.config configuration for central admin:
- Open web.config file and look for </PeoplePickerWildcards>
- Paste the below code just above </PeoplePickerWildcards>
<add key=”membershipname” value=”*” />
- Open the central admin web.config file and look for <system.web>
- Paste the below code just below <system.web>
<membership defaultProvider=”membershipname“>
<providers>
<add name=“membershipname“
type=”Microsoft.Office.Server.Security.LDAPMembershipProvider,
Microsoft.Office.Server,
Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71E9BCE111E9429C”
server=”SunOne Ldap FQDN Domain name“
port=”389” useSSL=”false” useDNAttribute=”false”
userDNAttribute=”uid” userNameAttribute=”uid”
userContainer=”ou=People,o=Domain name“
userObjectClass=”person”
userFilter=”(|(ObjectCategory=group)(ObjectClass=person))” scope=”Subtree” otherRequiredUserAttributes=”sn,
givenname, cn” />
</providers>
</membership>
<roleManager defaultProvider=”AspNetWindowsTokenRoleProvider”
enabled=”true”
cacheRolesInCookie=”true”
cookieName=”.PeopleDCRole”>
<providers>
<add name=”rolename“
type=”Microsoft.Office.Server.Security.LDAPRoleProvider,
Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71E9BCE111E9429C”
server=”SunOne Ldap FQDN Domain name“
port=”389” useSSL=”false”
groupContainer=”o=Domain name“
groupNameAttribute=”cn”
groupMemberAttribute=”member”
userNameAttribute=”uid” dnAttribute=”cn”
groupFilter=”(ObjectClass=group)”
scope=”Subtree” />
</providers>
</roleManager>
- After the above changes please do IISRESET and browse the central admin, make sure its opening fine
Web.config configuration for security Token Service(STS)
- Open the Security Token Service(STS) web.config file and look for </configuration>
- Just above this file create two entries like as follows:
<system.web>
</system.web>
- Between the above two entries paste the below code:
<membership defaultProvider=”membershipname“>
<providers>
<add name=”membershipname“
type=”Microsoft.Office.Server.Security.LDAPMembershipProvider,
Microsoft.Office.Server,
Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71E9BCE111E9429C”
server=”SunOne Ldap FQDN Domain name“
port=”389” useSSL=”false” useDNAttribute=”false”
userDNAttribute=”uid” userNameAttribute=”uid”
userContainer=”ou=People,o=Domain name“
userObjectClass=”person”
userFilter=”(|(ObjectCategory=group)(ObjectClass=person))” scope=”Subtree” otherRequiredUserAttributes=”sn,
givenname, cn” />
</providers>
</membership>
<roleManager enabled=”true” >
<providers>
<add name=”rolename“
type=”Microsoft.Office.Server.Security.LDAPRoleProvider,
Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71E9BCE111E9429C”
server=”SunOne Ldap FQDN Domain name“
port=”389” useSSL=”false”
groupContainer=”o=Domain name“
groupNameAttribute=”cn”
groupMemberAttribute=”member”
userNameAttribute=”uid” dnAttribute=”cn”
groupFilter=”(ObjectClass=group)”
scope=”Subtree” />
</providers>
</roleManager>
- After the above changes please do IISRESET and browse the central admin, make sure its opening fine
Web.config configuration for SharePoint Site
- Open web.config file and look for </PeoplePickerWildcards>
- Paste the below code just above </PeoplePickerWildcards>
<add key=”membershipname” value=”*” />
- Now look for <membership defaultProvider=”i”>
- Paste code just below <providers>
<add name=”membershipname“
type=”Microsoft.Office.Server.Security.LDAPMembershipProvider,
Microsoft.Office.Server,
Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71E9BCE111E9429C”
server=”SunOne Ldap FQDN Domain name“
port=”389” useSSL=”false” useDNAttribute=”false”
userDNAttribute=”uid” userNameAttribute=”uid”
userContainer=”ou=People,o=Domain name“
userObjectClass=”person”
userFilter=”(|(ObjectCategory=group)(ObjectClass=person))” scope=”Subtree” otherRequiredUserAttributes=”sn,
givenname, cn” />
- Now look for <roleManager defaultProvider=”c”
- Paste code just below <providers>
<roleManager defaultProvider=”AspNetWindowsTokenRoleProvider”
enabled=”true”
cacheRolesInCookie=”true”
cookieName=”.PeopleDCRole”>
<providers>
<add name=”rolename“
type=”Microsoft.Office.Server.Security.LDAPRoleProvider,
Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71E9BCE111E9429C”
server=”SunOne Ldap FQDN Domain name“
port=”389” useSSL=”false”
groupContainer=”o=Domain name“
groupNameAttribute=”cn”
groupMemberAttribute=”member”
userNameAttribute=”uid” dnAttribute=”cn”
groupFilter=”(ObjectClass=group)”
scope=”Subtree” />
- After the above changes please do IISRESET and browse the central admin and SharePoint site, make sure its opening fine
Final Steps:
- Browse the central admin
- Go to application management—manage web applications
- Highlight the web application on which we are working
- From the ribbon choose “Authentication Providers”
- Choose the zone and modify the Membership Provider & Role Provider
- Save the changes
- Again from the ribbon, choose “User Policy” and add a user from Sun One Ldap with Full control
- Browse the site and verify if the user is able to login into the site
Failed to instantiate file “default.aspx” from module “mobile”: Source path “default.aspx” not found.
1. Symptom –
–>You have a SharePoint site called https://yagyashree.contoso.com in your SharePoint server “SHAREPOINT1″
–>You have deployed a custom template called “Blog” in your SharePoint site and you are using it to create new subsites
–>Whenever you try to create new subsites you get following error on this url https://yagyashree.contoso.com/_layouts/newsbweb.aspx
Failed to instantiate file “default.aspx” from module “mobile”: Source path “default.aspx” not found.
–>But the site gets created but it shows following error
Page not found. We’re sorry, the web page you requested could not be located on our server. Please see the possible causes for this error and your available options below.
–>You are able to use all the other out of the box or custom template without any error successfully
2. Cause –
–>Under the location “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\MobilityRedirect\” the file name “Default.aspx” was renamed to “1default.aspx”
3. Resolution –
–>You should collect the ULS logs from your server while reproducing the issue
–>You should study the log file and find error message related to “MobilityRedirect”
–>Go to the folder “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\MobilityRedirect\”
–>You should see that the “default.aspx” has been renamed to anything different like “1default.aspx” or not even present
–>Take the backup of the file
–>Renamed it back to “default.aspx”
–>Now try again to create new blog site using “Blog” template and you should be able to create it successfully
4. More Information –
Error Found in the ULS log
———————————–
08/24/2009 10:18:22.20 w3wp.exe (0x077C) 0×0334 Windows SharePoint Services General 72j1 High Failed to instantiate file “default.aspx” from module “mobile”: Source path “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\MobilityRedirect\default.aspx” not found.
08/24/2009 10:18:22.20 w3wp.exe (0x077C) 0×0334 Windows SharePoint Services General 8kh7 High Failed to instantiate file “default.aspx” from module “mobile”: Source path “default.aspx” not found.
08/24/2009 10:18:22.20 w3wp.exe (0x077C) 0×0334 Windows SharePoint Services Feature Infrastructure 889y High The element of type ‘Module’ for feature ‘MobilityRedirect’ (id: f41cc668-37e5-4743-b4a8-74d1db3fd8a4) threw an exception during activation: Failed to instantiate file “default.aspx” from module “mobile”: Source path “default.aspx” not found.
08/24/2009 10:18:22.20 w3wp.exe (0x077C) 0×0334 Windows SharePoint Services General 72by High Feature Activation: Threw an exception, attempting to roll back. Feature ‘MobilityRedirect’ (ID: ‘f41cc668-37e5-4743-b4a8-74d1db3fd8a4′). Exception: Microsoft.SharePoint.SPException: Failed to instantiate file “default.aspx” from module “mobile”: Source path “default.aspx” not found. —> System.Runtime.InteropServices.COMException (0×81070587): Failed to instantiate file “default.aspx” from module “mobile”: Source path “default.aspx” not found. at Microsoft.SharePoint.Library.SPRequestInternalClass.EnableModuleFromXml(String bstrFeatureDirectory, String bstrUrl, String bstrXML) at Microsoft.SharePoint.Library.SPRequest.EnableModuleFromXml(String bstrFeatureDirectory, String bstrUrl, String bstrXML) — End of inner exception stack trace — at Microsoft.SharePoint.Librar…
5. For your Reference:
Mobile browsers and devices that are supported in Windows SharePoint Services 3.0 and in SharePoint Server 2007
leave a comment