Action: when user trying to create new site using sharepoint Application templateError: Feature '75a0fea7-c54f-46b9-86b1-2e103a8fedba' is not installed in thisfarm, and can not be added to this scope. Solution:Did you install the Application Template Core prior to installing the ProjectTracking Workspace?If not, you would have to do that first, and then re-install the ProjectTracking Workspace.step1: First install ApplicationTemplateCore- stsadm -o addsolution -filename "C:\ApplicationTemplateCore.wsp"
- stsadm -o deploysolution -name "ApplicationTemplateCore.wsp" -allowgacdeployment -immediate -force
- stsadm -o copyappbincontent
step2:Install your selected Application template- stsadm -o addsolution -filename "C:\Inetpub\wwwroot\wss\VirtualDirectories\WSP\ProjectTrackingWorkspace.wsp"
- stsadm -o deploysolution -name "ProjectTrackingWorkspace.wsp" -allowgacdeployment -immediate -force
- stsadm -o copyappbincontent
You cannot create a new document, Open document, or check out an existing document in a Windows SharePoint Services 3.0 document library when you have multiple versions of Office installedThe problem happens when you have, or had, two versions of office installed. You have to go into your program files directory and delete the version of owssupp.dll you're not using (for example if you upgraded to office 2007 and then downgraded back to office 2003 you delete owssupp.dll in the office12 directory). IE 7's manage addons you can see two versions of the owssupp dll registered so IE gets confused and you have to forcefully remove the version you're not using anymore.To resolve this problem, install hotfix 938888. For more information about hotfix 938888, click the following article number to view the article in the Microsoft Knowledge Base:
938888 (http://support.microsoft.com/kb/938888/ )
Today's best practices recommendation, why you should require check out in your document libraries, and how to go about doing so.
The reason that it's recommended that you require check out on the documents in your library is that, unless you do so, multiple users will be able to check out and edit a single document at the same time*, and without any indication that another user is already editing the same document. What do you think happens if two people are making changes to the same document at the same time? If you said, "whoever saves first wins," give yourself a gold star.
Such headaches can be avoided by requiring that users check out a document from a library before making changes. Don't worry, if someone has checked out a given document and is in the process of making changes, a read-only version can still be accessed by other users.
Is it a complicated or laborious process to set up a document library to require check out? Not at all. In fact, setting up a document library to require check out is as simple as selecting a single radio button in the library settings:
To navigate to the above setting, from within the library itself,- first select Document Library Settings from the Settings dropdown,
- then select the Versioning Settings hyperlink under the General Settings header.
- From there, you'll be presented with the setting options page for the library, and you'll notice that the last option is Require Check Out. Once you're here, all you need to do is switch the defaulted Require Check Out radio button selection from No to Yes (as pictured above),
- click OK at the bottom of the page, and you're all set.
Use content Editor Webpart and copy following code into source editor, and add this web part to your Calendar's New Item Page [NewForm.aspx]
< type="text/javascript">
var TDs = document.getElementsByTagName("TD");
var i=0;
var tagContent = "";
while (i <>
{
try{tagContent = TDs[i].innerText TDs[i].textContent;
if (tagContent.indexOf("Workspace") == 0 tagContent.indexOf("Workspace") == 3)
{
TDs[i+1].parentNode.removeChild(TDs[i+1]);
TDs[i].parentNode.removeChild(TDs[i]);
}
}
catch(err){}i=i+1;
}
< /script >
