Friday, May 14, 2010
Versions of SharePoint 2010
http://technet.microsoft.com/en-us/evalcenter/ee388573.aspx
SharePoint Server 2010 Enterprise Client Access License features
For organizations looking to expand their business collaboration platform to enable advanced scenarios. Use the Enterprise capabilities of SharePoint to fully interoperate with external line-of-business applications, Web services, and Microsoft Office client applications; make better decisions with rich data visualization, dashboards, and advanced analytics; and build robust forms and workflow-based solutions.
SharePoint Server 2010 for Internet Sites, Enterprise
For organizations looking to create customer-facing public internet sites and private extranets using the full enterprise capabilities of SharePoint. This provides full SharePoint Enterprise functionality and no other technical limits.
SharePoint Server 2010 Standard Client Access License features
For organizations looking to deploy a business collaboration platform across all types of content. Use the core capabilities of SharePoint to manage content and business processes, find and share information and expertise, and simplify how people work together across organizational boundaries.
SharePoint Server 2010 for Internet Sites, Standard
For small and mid-sized organizations looking to create public Internet sites or basic extranets using the Standard features of SharePoint Server 2010.
SharePoint 2010 Product key
SharePoint Server 2010 Enterprise Client Access License Features: GGDG8-JCMXH-8KG8C-RJYYX-3Y33H
SharePoint Server 2010 for Internet Sites, Enterprise: 9FPGB-W6QTT-G68T4-TBX7M-R624H
SharePoint Server 2010 Standard Client Access License Features: KB443-F7CJV-J2RP4-QYQJ7-6PBB3
SharePoint Server 2010 for Internet Sites, Standard: H4P2T-CYKM7-9FKKD-DTQ7X-W69GG
http://technet.microsoft.com/en-us/evalcenter/ee391660.aspx
HAPPY SHAREPOINTING!!!!
Tuesday, May 04, 2010
Retrieve Solution file from SharePoint Farm
Developer created .wsp file and installed in SharePoint farm . We need install these solution files to new farm and we have no clue where developer has saved these files.It's not in Visual Source safe too.
Disaster Recovery :
Pull the .wsp from the existing farm using code below :
SPSolutionCollection solutions = SPFarm.Local.Solutions;
foreach (SPSolution solution in solutions)
{
SPPersistedFile wspFile = solution.SolutionFile;
wspFile.SaveAs("c:\\Temp\\Solutions\\" + solution.Name);
}
Make sure directory exists .
Enjoy!
Tuesday, April 27, 2010
System.Data.SqlClient.SqlError: Exclusive access could not be obtained because the database is in use. (Microsoft.SqlServer.Express.Smo)
I did following steps to get it working( Make sure you can afford SQL DB outage during the restore )
1) Run the following SQL Query on SSP DB
USE master
GO
ALTER DATABASE YOUR_SSP_DB_NAME
SET OFFLINE WITH ROLLBACK IMMEDIATE
2) Perform SQL Restore from Backup
3)
ALTER DATABASE YOUR_SSP_DB_NAME
SET ONLINE
Thats It .
This process is much simpler than the Central Administration Restore process. For some weird reasons i kept on getting errors while trying with Central Administration console .
Monday, April 19, 2010
Friday, April 16, 2010
Working with List Items MOSS 2007
http://splistitemeditor.codeplex.com/
Wednesday, April 07, 2010
Content Query Web Part : Master of all OOB webpart
Customization Sample :
http://msdn.microsoft.com/en-us/library/bb447557.aspx
This is one of the most powerful webpart but still SharePointers avoid it's usage due to its complex looking .xsl language . Fact is that once you understand XSL then this webpart will become common in your websites.
The site collection could not be restored. Please make sure the content databases are available and have sufficient free space
Follow this article in case you bump on to above error :
http://support.microsoft.com/kb/926061
Thursday, March 11, 2010
Exception Error 0x80020009 when trying to Activate "Office Sharepoint Server Publishing Infrastructure"
Following are the steps :
stsadm -o activatefeature -filename publishing\feature.xml -url http://URL -force
stsadm -o activatefeature -filename publishingresources\feature.xml -url http://URL -force
stsadm -o activatefeature -filename publishingSite\feature.xml -url http://URL -force
stsadm -o activatefeature -filename publishingweb\feature.xml -url http://URL -force
stsadm -o activatefeature -filename publishinglayouts\feature.xml -url http://URL -force
stsadm -o activatefeature -filename navigation\feature.xml -url http://URL -force
Worked for me ...
Monday, February 15, 2010
Thursday, February 11, 2010
Thursday, January 21, 2010
Error in PortalCrawl Web Service.
To get it working i had to create a dummy root site collection at http://servername
Wednesday, January 06, 2010
Request for the permission of type 'System.Security.Permissions.FileIOPermission failed
In case you receive security issue when executing the managed code infopath form , solution is to make the infopath form Full Trust.
To make form full trust , in Office Infopath design mode, go to Tools -> Form Options -> Security and Trust -> Full Trust (Change Security level to full trust ).
Publish theform .
Auditing SharePoint 2007 List/ Library
Auditing documents/ list items in SharePoint 2007 is a 3 step process :
1) Create Site Collection Policy
- Go to Site Actions ->Modify all Site Settings - >Site Collection Policies
- Create new policy -> Provide Name and Enable Auditing
- Select Events you would like to audit -> Click OK
2) Set up the Document Library / List which requires auditing
- Go to List Settings of Document Library you would like to audit
- Click on Information Management Policy Settings
- Under use site collection policy , select the policy you had defined in first step
- Click Ok
At this point you library / list is set for auditing and any action will be logged .
3) Viewing the results
- Go to Site Actions ->Modify all Site Settings - >Audit log Reports
- Under Custom Reports click on "Run a custom report "
- Select checkbox "Restrict this Report to " and select corresponding web application and list name
- You can select various filters (start date , end date , users ), though these are optional but its better to use them as they improve the report performance
- Select the events you would like to see the report for and click ok
- Voila ! you have the details reports with worksheet displaying the activity and usernames ,you have to use the filter to zero down to required data. UserNames can be accessed worksheet named"Report Data". Event column will display the action performed on a particular item
Enjoy !
Tuesday, January 05, 2010
HAPPY NEW YEAR !!!!
Bring it on !!!!
Thursday, December 31, 2009
Another user has changed the structure of this list .
Another user has changed the structure of this list . All your pending changes to this list will be discarded . To retrieve the latest copy of the list , click refresh
Suggested Resolution : Removing comma in hyperlinks
Reference URL : http://bmerri19.wordpress.com/
Wednesday, December 30, 2009
Implementing ASP.NET Impersonation
Impersonation can be implemented using one of four methods:
- Impersonate the IIS authenticated account or user
- Impersonate a specific user for all the requests of an ASP.NET application
- Impersonate the authenticating user in code
- Impersonate a specific user in code
More details give in following article :
http://support.microsoft.com/kb/306158#4
Tuesday, December 22, 2009
Feature '7a8b11f4-38b2-402b-ad94-1213e25150ca' for list template '1102' is not installed in this farm. The operation could not be completed.
It was happening because ShaerPoint Site was searching for the following feature "PWAProposals" which was present in my dev machine and not in my production . I was able to move it successsfully before as i used stsadm-backup but it started failing with stsadm -export.
Resolution :
Just copy the feature from your source server ---> destination server and install the feature. This will resolve the issue . Well this is not ideal solution . I am still in process of figuring out the reference to the feature in order to remove it from list template.
Tuesday, December 08, 2009
Sharepoint Config DB Size Grown too large
Did some search and the below steps solved the issue. The steps given below is not recommended to be implemeted in production , only in development / QA machine in order to save some resource .
1) Right click on you DB -> Properties
2)Select Options
3) Change the Recovery Model to SIMPLE and Click Ok
Once that is done ,
-Right click on DB -> Tasks - > Shrink -> Files
- In File type select log and click OK
My Config DB Log files were reduced from 35 GB - > 504 KB
Note : Simple recovery model is not suggested for Production Systems
Wednesday, December 02, 2009
Allow Access Request SharePoint 2007
1) Go To Site Settings ->Modify All Site Settings
2) Click on Advanced Permissions under User and Permission
3)List Settings -> Access Requests
4) Set the email ID and activate the Allow Request for access
Reference Architecture: Building a Cost Optimized, High-Throughput HL7, EDI, and FHIR Processing Pipeline on OCI ( Published in Oracle Blog)
OCI (Oracle Cloud Infrastructure) provides more than 200 services to build your next enterprise application. Explore the blog to learn how ...
-
Ever wanted to have a people picker kind of control in Infopath form and that too in browser mode. Did i heard yes :) , well there is a Acti...
-
Am sure lot's of people would be wondering how to hide menu items of a list eg document libraries "Send to " menu item . In o...
-
I got this error for quite some time and i had no clue what was wrong in my page . Page consisted of only 2 panel controls . That's all ...