Error in Activating the WebApp feature

Topics: Enhanced Blog Edition
Jun 29, 2007 at 3:54 AM
I am having trouble activating the webapp in the web application level. I have successfully installed and deployed the solution in the farm using the following commands:

stsadm -o addsolution -filename c:\cks.ebe.wsp
stsadm -o deploysolution -name CKS.EBE.wsp -immediate -allowgacdeployment

But when I activate it using this command:

stsadm -o activatefeature -name "CKS EBE WebApp" -url https://mysite/

it posts this error:

"Failed to find the XML file at the location '12\Template\Features\CKS EBE WebApp\feature.xml'

I checked the Central Administration page but I didn't see any "CKS:EBE Web Application Feature" there. What am I missing? Did I skip something? Or is there something ele I need to do?
Developer
Jun 29, 2007 at 12:41 PM
Arthur,

Can you check "Solution Management" in the Operations section of Central Administration. There you should see the CKS:EBE solution. Can you ensure that it has been deployed and that there are no errors.

You could try retracting the solution & deploying again.

Vince
Jul 2, 2007 at 12:35 AM
Hi Vince,

Thanks for the reply. I checked the location you specified and I didn't find there any CKS or EBE as well. I've been trying to retract and redeploy the solution for quite a few times but still it posts the same error message when I get in that step. Yes, there were no other errors I encountered other than the web application level error.

Arthur
Developer
Jul 2, 2007 at 9:35 PM
Arthur,

Can you check the the LOGS in the 12 folder to see if there any other errors being generated when you deploy the solution?

If you can't see the Solution under Solution Management it would imply the inital addsolution failed. Can you try the stsadm -o addsolution and then go to solution management to see if the solution is actually there?

It may also be worth trying to run "stsadm -o execadmsvcjobs" after the -o deploysolution incase the deployment job is not running.

Vince
Jul 3, 2007 at 1:10 AM
Hi Vince,

I tried it again and still i got the same results. I'm certain it is successfully added because when i tried to run it again, it posted an error:

'A solution with the same name "cks.ebe.wsp" or id "cabb604e-bd2d-4404-8996-196aff90bebe" already exists in the solution store.
c:\cks.ebe.wsp: The Solution installation failed.'

Also, I tried running "stsadm -o execadmsvcjobs" after the -o deploysolution and it displayed:

'Executing.
Operation completed successfully.'

Here is the log about stsadm.exec from the \12\LOGS folder:

07/03/2007 08:04:47.86 STSADM.EXE (0x373C) 0x2140 ULS Logging Unified Logging Service 8wsv High ULS Init Completed (STSADM.EXE, onetnative.dll)
07/03/2007 08:04:47.88 STSADM.EXE (0x373C) 0x2140 Windows SharePoint Services Topology 0 Medium Diagnostics settings: 32768
07/03/2007 08:04:48.27 STSADM.EXE (0x373C) 0x2140 Windows SharePoint Services General 0 Medium Windows SharePoint Services log file
07/03/2007 08:04:48.27 STSADM.EXE (0x373C) 0x2140 Windows SharePoint Services General 72ju Medium stsadm: Running activatefeature
07/03/2007 08:04:48.93 STSADM.EXE (0x373C) 0x2140 Windows SharePoint Services General 8e1f High Failed to find the XML file at location '12\Template\Features\CKS EBE WebApp\feature.xml'
07/03/2007 08:04:48.93 STSADM.EXE (0x373C) 0x2140 Windows SharePoint Services General 72ju High stsadm: Failed to find the XML file at location '12\Template\Features\CKS EBE WebApp\feature.xml' Callstack: at Microsoft.SharePoint.SPXmlDocCache.GetGlobalXmlDocumentCore(String pathXml, Boolean bFeature) at Microsoft.SharePoint.SPXmlDocCache.GetGlobalXmlDocument(String pathAllFeaturesRelativeXml) at Microsoft.SharePoint.Administration.SPFeatureDefinition.GetFeatureIdAndScope(String featureDefinition, Guid& featureId, SPFeatureScope& scope) at Microsoft.SharePoint.StsAdmin.SPOperation.GetFeatureIdFromParams() at Microsoft.SharePoint.StsAdmin.SPActivateFeature.Run(StringDictionary keyValues) at Microsoft.SharePoint.StsAdmin.SPStsAdmin.RunOperation(SPGlobalAdmin globalAdmin, String strOperation, StringDictionary keyValues, SPParamCollection pars)
07/03/2007 08:04:50.58 STSADM.EXE (0x373C) 0x2140 ULS Logging Unified Logging Service 8wsw High Now terminating ULS (STSADM.EXE, onetnative.dll)
07/03/2007 08:06:36.71 STSADM.EXE (0x3480) 0x2A74 ULS Logging Unified Logging Service 8wsv High ULS Init Completed (STSADM.EXE, onetnative.dll)
07/03/2007 08:06:36.73 STSADM.EXE (0x3480) 0x2A74 Windows SharePoint Services Topology 0 Medium Diagnostics settings: 32768
07/03/2007 08:06:37.12 STSADM.EXE (0x3480) 0x2A74 Windows SharePoint Services General 0 Medium Windows SharePoint Services log file 07/03/2007 08:06:37.12 STSADM.EXE (0x3480) 0x2A74 Windows SharePoint Services General 72ju Medium stsadm: Running activatefeature
07/03/2007 08:06:37.82 STSADM.EXE (0x3480) 0x2A74 Windows SharePoint Services General 8e1f High Failed to find the XML file at location '12\Template\Features\CKS EBE WebApp\feature.xml'
07/03/2007 08:06:37.82 STSADM.EXE (0x3480) 0x2A74 Windows SharePoint Services General 72ju High stsadm: Failed to find the XML file at location '12\Template\Features\CKS EBE WebApp\feature.xml' Callstack: at Microsoft.SharePoint.SPXmlDocCache.GetGlobalXmlDocumentCore(String pathXml, Boolean bFeature) at Microsoft.SharePoint.SPXmlDocCache.GetGlobalXmlDocument(String pathAllFeaturesRelativeXml) at Microsoft.SharePoint.Administration.SPFeatureDefinition.GetFeatureIdAndScope(String featureDefinition, Guid& featureId, SPFeatureScope& scope) at Microsoft.SharePoint.StsAdmin.SPOperation.GetFeatureIdFromParams() at Microsoft.SharePoint.StsAdmin.SPActivateFeature.Run(StringDictionary keyValues) at Microsoft.SharePoint.StsAdmin.SPStsAdmin.RunOperation(SPGlobalAdmin globalAdmin, String strOperation, StringDictionary keyValues, SPParamCollection pars)
07/03/2007 08:06:40.30 STSADM.EXE (0x3480) 0x2A74 ULS Logging Unified Logging Service 8wsw High Now terminating ULS (STSADM.EXE, onetnative.dll)
Jul 4, 2007 at 3:30 AM
Hi,

I was able to solve my problem. I used -local instead of -immediate in deploying the solution. A colleague of mine told me to use that because I am implementing the solution in a single server and not a farm. It works fine now. Thank you very much!
Mar 25, 2009 at 3:19 PM
I was having the same error when using the install command for a feature on a virtual machine.  ArthurP's fix worked.  Thanks!