Tuesday, August 25, 2009

Microsoft SharePoint Workspace 2010 download

Microsoft SharePoint Workspace 2010 download is locked due to over response. So, we are expecting the beta release at any time. 

However, As per their blogs, I am listing some of the key points of SharePoint Workspace 2010:

1.  Groove will be known as SharePoint Workspace Manager.
2.  SharePoint Server 2010 will be 64 bit only.
3.  IE 6.0 will not be supported.
4.  SharePoint Workspace Manager and OneNote will be a part of the Office 2010 ProPlus SKU.
5.  Migration should be smoother from 2007 to 2010 than 2003 to 2007.
6.  2010 will support silverlight controls effectively.
7.  Now, you can Insert/Delete data through BDC.
8.  Faceted search has been introduced.


I will update this post, If there is any latest news about Microsoft SharePoint Workspace 2010.


Monday, August 24, 2009

Error: HTTP 404: File Not Found in MOSS 2007 (SharePoint)

Error:  

HTTP 404: File Not Found. 

(Or)

SharePoint site can not be opened in SharePoint Designer.

Reason:

Usually this error will occur due to the below reasons:
1. If the portal is not attached with "Central Administration" portal.  i.e. The portal will be running        in IIS. But the Portal site may not be created in "Central Admin". 
2. The Port may not be associated with SSP.
3. Identity of the IIS application pool may be different. or the Application Pool Identity password may be changed. 

Solution:
1. Create a new "Web application" in the same port with the previous credentials & with the same database name through the "Application Management".  And don't create "Site Collection". (This is applicable, if the problem is due to Reason 1")

2. Associate the Port (Web application) with SSP, if the reason is 2.

3. Go to IIS and open the properties of the Application pool for this specific port and update the username,password in the "Identity" tab.

Important: 
Don't forget to restart the IIS. Else, your master pages will not take effect in the "Application pages".

Thursday, August 20, 2009

Hiding Menu in DispForm.aspx (MOSS 2007)

Sometimes, you may struggle to hide the "Menu Toolbar" which is displaying in the top of the Display Form page.



You may tried to hide by editing the page in SP Designer & writing Java Scripts. But they will not reflect in page. Because, you may forgot to add the "Push" method.

OK. So, here is an sample script, that will hide the "Menu Toolbar" from the DispForm.aspx.

<script language="javascript" type="text/javascript">
function check()
{
var elements=document.body.getElementsByTagName("a");
for (var index=0; index <>
{
if(elements[index].title.toLowerCase()=="edit item")
elements[index].parentNode.parentNode.parentNode.parentNode.parentNode.parentNode.style.display="none";
}
}  
var elements=document.body.getElementsByTagName("td");
for (var index=0; index <>
{
if(elements[index].innerText.toLowerCase()=="itemworkspaceurl")
elements[index].parentNode.style.display="none";
}
}  
}
_spBodyOnLoadFunctionNames.push("check()");
</script>


Once you have applied this script, final screen will be like,




That's It...

Wednesday, August 19, 2009

System.Security.Policy.PolicyException: Required permissions cannot be acquired.

ErrorSystem.Security.Policy.PolicyException: Required permissions cannot be acquired.

Reason:
The Trust level may be Mimimal.

Solution:
1.  Go  to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\config
2.  Open "Web.Config"
3.  Find <trust level="WSS_Mimimal" originurl=""></trust>
4.  Replace by <trust level="Full" originurl=".*"></trust>
5.  Save and Exit
6.  Open your Sharepoint Website web.Config.
7.  Do the steps 3 & 4.
8.  Save and Exit

That's It...

'truncate_only' is not a recognized BACKUP option.

Error:

'truncate_only' is not a recognized BACKUP option.

Reason:
This error will occur, if you run the 'Backup Log' query in 'SQL Server 2008'. Because, SQL Server 2008 will not support this command. 

Your Query: backup log WSS_Content_5001 with truncate_only

Solution:

So, you have to run query in the below format.

Use DBName
GO
Alter Database DBName Set Recovery Simple
GO
Alter Database DBName Set Recovery Full
GO
DBCC SHRINKFILE ('Log Name', 1) 

That's it...

Friday, August 7, 2009

Error: Unable to extract manifest.xml from:

Reason:
Sometime you will get the "Unable to extract manifest.xml from:" error, when you are trying to deploy WSP files using WSPBuilder. Mostly this error will occur, if you are using 64bit Windows 2003 server. 

Solution:
1. Go to http://wspbuilder.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=30858 and download 64bit WSPbuilder with IIS7 support. (Version 1.0.6)
2. Also, download the "cablib.dll" from the same url. (Important)
3. Install the downloaded WSPBuilder in that server.
4. Goto command prompt & type "Assembly" (Without quotes). This will open Asseembly folder. Or go to "C:\windows\Assembly\" (Both actions are same)
5. Drag and drop the "cablib.dll" into the "Assembly" folder. (Important)

Thats it. 

Thursday, August 6, 2009

Error: The list is too large to save as a template. The size of a template cannot exceed 10485760 bytes.

Reason:

By default, Microsoft has restricted the download size of the list template as 10MB (10485760 bytes). If you are trying to save site/list template which are having more than 10MB size, you will get "The list is too large to save as a template. The size of a template cannot exceed 10485760 bytes." error. 

To resolve this issue, you have to run the below command in the command prompt:
stsadm -o setproperty -propertyname max-template-document-size -propertyvalue 524288000


In my above command, I have set template limit as 500MB. 


Error: The template you have chosen is invalid or cannot be found

Reason: 
Day by day, your MOSS server's number of features (under C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES) will increase gradually. During the deployment, the target server may not have all the source machine features. 

So, you will get the "The template you have chosen is invalid or cannot be found" error. If you are removed the unnecessary dependant features, your "Workspace template" will work fine. 

Solution:
However, the solution is somewhat hectic. Just follow my instructions carefully. (Don't miss any step and don't ignore the naming convension.)

1. Download the STPInspector from Codeplex (http://stpinspector.codeplex.com/Release/ProjectReleases.aspx)
2. Downloaded CabArc from Microsoft (http://support.microsoft.com/kb/310618)
3. Copy STSInspector tool into MOSS Server (Important)
4. Extract Cabarc files into C:\cabarc (Follow the same name as specified here)
5. Download STP from the portal through browser. (http://Portal:80/_catalogs/wt/Forms/Common.aspx)
6. Browse & Inspect the downloaded stp using STPInspector
7. Note the Missing features GUID (which are not ticked in the result list)
8. Rename the STP file as .CAB 
9. use the CabArc to extract the contents into the folder (ex: Cabarc X Project.cab)
10.Open the Manifest.xml in notepad from the extracted files
11.Search the missing guid (which are found using STPInspector) and delete the Feature XML tag in the Manifest.XML.
12. Save the Manifest.xml
13. Make the new CAB using CabArc (Ex: CabArc N ModifiedProject.cab C:\Folder\*.*)
14. Rename the .CAB file as .STP
15. Upload this file using stsadm -o addtemplate -filename "C:\ModifiedProject.STP" -Title "STPTitle" -Description ""


Thats it.