Tangible Thoughts

We were using Beta 2 of v2 in production, and there wasn't much that changed in RTM. Why do you think Beta 2 of v3 will be that much different?

yeah but RTM was a much more stable product than Beta 2 was. Ofcourse the UI changed.

I think we all know that Beta 2 is good and that you can deploy it in production. But the emphasis should be, its still not finished, and yes we are working on it.

Afterall this is Microsoft and with SharePoint I hope that RTM ships without things hanging out of the product in a bad way.

hehe, beta != release

pretty scary when a consultant is giving you that kind of information!

I have got a work around if you just enable the feature from the command line.

stsadm -o activatefeature -id AEBC918D-B20F-4a11-A1DB-9ED84D79C87E -url http://mysharepoint.com

That does fix it. You can then go in an enable the Office SharePoint Server Publishing features on other sites as well then to.

Hope that helps.. otherwise email me and I will see what I can do.

nice find morgan. funny that this is broken :)

Nice fix... works welll

I executed the script above to enable the feature, but here is the error I get when the search results are displayed:

System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {B8C4B6BA-6A45-4CB3-A80F-D66C40A9F22E} failed due to the following error: 80040154. at Microsoft.Office.Server.Search.Query.QueryInfo.InitializeCanaryChecker() at Microsoft.Office.Server.Search.Query.QueryInfo.GenerateDigest() at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.ClickLogPostdata() at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnPreRender(EventArgs e)

Can you please help?

As far as I understand, this is probably because one of the dll's is not registered. Just trying to figure out, which one it is...

Hi, I am also getting the error with CLSID {B8C4B6BA-6A45-4CB3-A80F-D66C40A9F22E}

Did you get any further with working out which Dll needs registered

hi, when activating the feature with the script, i get the same error as when creating a report center site: Feature '00bfea71-dbd7-4f72-b8cb-da7ac0440130' is not installed in this farm, and can not be added to this scope.

ok, i've found the solution myself :-) i searched in the 12\template\features directory to the xml with the feature i was missing ( i know, a huuuge job) installed & activated it, and everything seems up and running. hope it helps you too!

I am still receiving the same error message even after using the "stsadm" command line fixed mentioned earlier. Which XML in the 12\template\features directory did you install and activate?

After combing through the net, this was the only site that had anything resembling what I was running into. To save some hair pulling I will post here first.

To elaborate on the searching through the template folder...

Here is what I had when trying to create a new "My Sites" site:

Dependency feature with id d992aeca-3802-483a-ab40-6c9376300b61 for feature 'BaseWebApplication' (id: 4f56f9fa-51a0-420c-b707-63ecbb494db1) is not installed. OR from the log file:

Exception was thrown while ensuring dependencies met for feature 'BaseWebApplication' (id: 4f56f9fa-51a0-420c-b707-63ecbb494db1): System.ArgumentException: Dependency feature with id d992aeca-3802-483a-ab40-6c9376300b61 for feature 'BaseWebApplication' (id: 4f56f9fa-51a0-420c-b707-63ecbb494db1) is not installed. at Microsoft.SharePoint.SPFeatureCollection.CheckFeatureDependency(SPFeatureDefinition featdefDependant, SPFeatureDependency featdep, Boolean fActivateHidden, Boolean fForce) at Microsoft.SharePoint.SPFeatureCollection.CheckFeatureDependencies(Guid featidDependee, Boolean fActivateHidden, Boolean fForce)

searching the features folder, I found 3 documents that contained the GUID d992aeca-3802-483a-ab40-6c9376300b61.
They were BaseWebApplication, PremiumWebApplication, and BulkWorkflowTimerJob.

I scratched my head for a couple of minutes, and reread the error message. Something was not installed, I tried something I had found above that activated a feature, but mine was not installed.

so...

STSADM -o installfeature -name BulkWorkflowTimerJob

Then I was able to activate my BaseWebApplication.

STSADM -o activatefeature -id d992aeca-3802-483a-ab40-6c9376300b61 -url http://mysite

This was not enough though, I had other features that magically were no longer installed. So when creating a web collection I got another GUID. Not installed, so repeat.
Search the features folder for a feature xml file with the GUID as its id, and then get the parent folder name to add to this command.

STSADM -o installfeature -name MySiteLayouts

and then

STSADM -o installfeature -name MySiteQuickLaunch

After this last iteration, (I would suggest that you try and create a site, and add what you need, don't just blindly run all of these commands) I was able to create a "My Sites" Collection Page

Activating a custom document library feature gives command line error....actually im new to sharepoint and learning to activate a feature...
stsadm –o activatefeature –filename “CustomDocumentLibrary\feature.xml” –url "http://SPSTest/SiteDirectory/CustomSite"
gives me command line error...

I had a problem very similar to this one while trying to deploy Application Templates to a WSS3 site. The exact error message was:

Feature '75a0fea7-2791-45a2-896f-e538f91032d8' is not installed in this farm, and can not be added to this scope.

I had neglected to install and deploy the ApplicationTemplateCore.wsp. Once installed all was well again.

I have tried installing the ApplicationTemplateCore and then other Application Templates and did see the same problems. I have removed and deleted all the templates and then again redepolyed them back again. Once all done did a iisreset (or u can do net stop w3svc / net start w3svc). Everything worked nicely. I think the readme.txt file which is coming with the templates never mentions to restart the IIS and thats why everyone is facing this issue. Hope this helps everyone.

Thanks

You need to retract the ApplicationTemplateCore and then DELETE it. Restart IIS, and then go in install ApplicationTemplateCore.wsp exactly as described in the README file.

I had the same "blah blah is not installed in the farm" problem and this process resolved the it.

I had same problem..but i fix it...

At first you have to download ApplicationTemplateCore.wsp and add in to sharepoint according readme file...
Via command line, run "stsadm –o addsolution –filename
ApplicationTemplateCore.wsp"
Next, run "stsadm –o deploysolution –name
ApplicationTemplateCore.wsp -allowgacdeployment
Finally, run stsadm -o copyappbincontent

after that you can add other tempates (templates.wsp) in sharepoint according same instruction above :-) i hope that helps you..