sharepointinstaller Work Item Rss Feed

Created Issue: WSPBuilder's Setup.exe not populating the webpart in the gallery, and also grouping not getting set [14215]

Bijuva — Tue, 22 Sep 2009 06:07:40 GMT

Hi,
I have developed an event handler,called TaskListEventHandler, for the Task list ((ItemAdding, ItemDeleting, ItemUpdating) as feasture using the WSP Builder project template, and I have also added a web part, called RegisterEventHandler, which will be used to bind(register) the events to a list. The webpart is WSP Builder template "Webpart without feature".

Defaultly, when i added the new webpart into the project, the .webpart file was created under the folder 80/wpcatalog. But as i wanted the whole project as a singel feature I moved the .webpart file to the Feature/TaskListEventHandler folder. Now the Feature/TaskListEventHandler contains 3 files elements.xml, feature.xml and the RegisterEventHandler.webpart.

I edited the elememts.xml as follows

<?xml version="1.0" encoding="utf-8" ?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<Module Name="WebPartPopulation" Url="_catalogs/wp" RootWebOnly="TRUE">
<File Url="RegisterEventHandler.webpart" Type="GhostableInLibrary">
<Property Name="Group" Value="TestGroup Webparts"></Property>
<Property Name="QuickAddGroups" Value="TestGroup Webparts"/>
</File>
</Module>
</Elements>

the feature.xml as follows,

<?xml version="1.0" encoding="utf-8"?>
<Feature Id="d0975573-b000-4d0f-bae1-1e9d15761cd0"
Title="TaskListEventHandler"
Description="TaskListEventHandler overrides Item Adding,Deleting and Updating event for any task list. To start using the event handler the feature must be registered to the task list. -By Biju(18 Sep 2009)"
Version="12.0.0.0"
Hidden="FALSE"
Scope="Web"
DefaultResourceFile="core"
ReceiverAssembly="TaskListEventHandler, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9cfae6f598922b94"
ReceiverClass="Test.EventHandler.TaskListFeatureHandler"
xmlns="http://schemas.microsoft.com/sharepoint/">
<ElementManifests>
<ElementManifest Location="elements.xml"/>
<ElementFile Location="RegisterEventHandler.webpart" />
</ElementManifests>
</Feature>

the RegisterEventHandler.webpart as follows,

<webParts>
<webPart xmlns="http://schemas.microsoft.com/WebPart/v3">
<metaData>
<type name="Test.EventHandler.RegisterEventHandler, TaskListEventHandler, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9cfae6f598922b94" />
<importErrorMessage>Cannot import RegisterEventHandler Web Part.</importErrorMessage>
</metaData>
<data>
<properties>
<property name="Title" type="string">RegisterEventHandler</property>
<property name="Description" type="string">This webpart is used to register or unregister the event handler to the list of type 'Task' list, and also adds the custom fields(which are mandatory for the eventhandler to operate sucessfully) on registering to the list - By Biju (16 Sep 2009)</property>
</properties>
</data>
</webPart>
</webParts>

Next, i build the poject using the WSP builder, and later create the deployment folder. When i try to install the feature using the WSPBuilder setup.exe file, the feature is getting deployed sucessfully.The feature and the webpart is getting deployed sucessfully. The web part is available in the web part gallery (SiteSetting-> EditPage-> Add a WebPart).

But the webpart's is not under the specific group which i had set in the elements.xml (currently it is shown under the "Miscellaneous" group) , and also the webpart is not shown(visible/available ) under the root site's web parts Galleries (Site Action->Site Settings->WebParts(Galleries) ).

I tried the installing+deploying + activating the feature using the STSADM command(through batch file), it works sucessfully, even the grouping is getting set as per my requirement.

Could you please suggest me a solution, how can i get it working using the WSPBuilder's Setup.exe

With Regards

Biju

Created Issue: Removing footer from setup.exe [14207]

raghuramanv — Mon, 21 Sep 2009 08:21:26 GMT

Hi all,
I am using wspbuilder for building my web parts and deploying it into my sharepoint sites...I have added the solution installer in my project before building it. I don't want the footer(i.e. www.codeplex.com/sharepointinstaller) in my setup.exe......... How to achieve that? Could it be removed by modifying my setup.exe.config? Any help would be of great use.

Commented Issue: Repair doen´t activate site collection feature

Robin_CodePlex — Mon, 24 Aug 2009 10:32:40 GMT

When repairing the installed solution, the feature is deactivated, the solution is retracted, then redeploys solution to all site collections, but then the feature is not reactivated.
Comments: ** Comment from web user: Robin_CodePlex **

If you update the solution version in the setup config, the installer doesn't give you the option to repair but instead you can upgrade the solution. This way the features remain intact, right?

It helped us dealing with inactive features scoped at WebApplication.

Commented Issue: The Windows Sharepoint Services Admin Service is Not Started!

MikeKnowles — Fri, 21 Aug 2009 11:14:42 GMT

Getting this error when running the setup.exe to install the test project DemoSolution.wsp

The Windows Sharepoint Services Admin Service is Not Started!

Any help with this would be great.
Bret
Comments: ** Comment from web user: MikeKnowles **

First of all, thanks for the great product. The Solution installer is a huge timesaver and easy to use. I think the product would be even better if it were fixed so that the WSS Admin Service is not required. The WSS Admin Service is not installed by default on many SharePoint farms. Solutions will deploy using command-line scripts and Central Admin without WSS Admin running. Perhaps this service is required for WSS only farms and not MOSS farms? I have found this error occurs when building any solution even if the solution install is built with the MOSS only option. It's not clear why WSS Admin is required, and it's a recurring support issue for admins to have to start it to install just one solution from one vendor.

Commented Issue: Repair doen´t activate site collection feature

Ivan_Padabed — Wed, 19 Aug 2009 13:44:48 GMT

We need the fix asap. :)

Created Issue: Repair doen´t activate site collection feature

pjcoliveira — Tue, 07 Jul 2009 13:47:19 GMT

When repairing the installed solution, the feature is deactivated, the solution is retracted, then redeploys solution to all site collections, but then the feature is not reactivated.

Commented Issue: Error: Feature is not installed in this farm, and can not be added to this scope

stuartwhiteford — Mon, 06 Jul 2009 15:21:06 GMT

Hi,
When i am trying to install a solution i am getting the following error during the installation "Feature 'MyFeatureID' is not installed in this farm, and can not be added to this scope.". This error comes after the solution has been installed and it has been deployed, but when the installer is trying to activate the feature it gives the above error. The follwing are the error details
***** SOLUTION DEPLOYMENT *****
myServerName : http://myServerName:4444/ : The solution was successfully deployed.

***** FEATURE ACTIVATION *****
***** ERROR *****
Feature '8425eaf7-6ace-4597-83c7-831ca8614d6d' is not installed in this farm, and can not be added to this scope.
CodePlex.SharePointInstaller.InstallException: Feature '8425eaf7-6ace-4597-83c7-831ca8614d6d' is not installed in this farm, and can not be added to this scope. ---> System.InvalidOperationException: Feature '8425eaf7-6ace-4597-83c7-831ca8614d6d' is not installed in this farm, and can not be added to this scope.
at Microsoft.SharePoint.SPFeatureCollection.AddInternal(Guid featureId, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly)
at Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId, Boolean force)
at CodePlex.SharePointInstaller.InstallProcessControl.ActivateSiteCollectionFeatureCommand.Execute()
--- End of inner exception stack trace ---
at CodePlex.SharePointInstaller.InstallProcessControl.ActivateSiteCollectionFeatureCommand.Execute()
at CodePlex.SharePointInstaller.InstallProcessControl.TimerEventInstall(Object myObject, EventArgs myEventArgs)

Any Help would be appriciated
Thanks
Comments: ** Comment from web user: stuartwhiteford **

I had this error when trying to activate a Workflow feature. As it turns out I didn't have the folder structure set up correctly in my Visual Studio solution and the manifest.xml file wasn't copying the workflow.xml and feature.xml files to the FEATURES folder under the 12 hive. Once I'd corrected this it activated fine.

Closed Feature: MSI Integration

lfastrup — Sun, 21 Jun 2009 16:04:08 GMT

Integration into MSI which could either be done by providing commandline parameters or by implementing an System.Configuration.Installer class.
Comments:

MSI integration has no place in the SharePoint solution world.

Closed Issue: Timer Service is NOT started - Server 2008

lfastrup — Sun, 21 Jun 2009 16:01:54 GMT

I am recieving the "The Windows SharePoint Services Timer service is NOT started!" when running the SharePoint solution installer demo. This is on Server 2008 with MOSS 2007 running fine. I have restarted the timer service and verified that all other SharePoint services are running. Ideas?
Comments:

No fix other than turning off Windows User Account Control. Did, however, add better error message to ease the troubleshooting for the user running the installer on the server.

Commented Issue: Timer Service is NOT started - Server 2008

lfastrup — Sun, 21 Jun 2009 16:00:30 GMT

This is because Windows User Account Control is turned on! Turn it off and the problem is solved.
However, V1.2.2 of the installer now gets around the problem when checking the timer service. It will instead show a detailed error message hinting to turn off User Account Control

Created Issue: Error: Feature is not installed in this farm, and can not be added to this scope

anshul — Mon, 23 Mar 2009 05:53:27 GMT

Commented Issue: Timer Service is NOT started - Server 2008

pault70 — Tue, 03 Mar 2009 15:41:26 GMT

Running as administrator solved this for me.

Created Issue: Running the Windows Installer on Windows 7 crashes the App

JeroenRitmeijer — Wed, 18 Feb 2009 16:27:53 GMT

I know users are not supposed to run it on Windows 7, but I wold have expected a nice message, something like 'SharePoint is not installed on this machine.

Created Issue: Feature scoped for Site (Site collection) not activated during installation if Setup running user is not administrator on the Site collection

exton — Wed, 18 Feb 2009 11:36:59 GMT

I'm developing a Site scoped feature that I'm installing with this great utility. I was troubleshooting why my feature wouldn't get activated after my installation even though I configured it to be so with FeatureId setting in Setup.exe.config.
After a while I figured out that it was because the administrator user I was logged in as wasn't administrator user on that specific site collection.

Why I would like to call this an issue is that the installer happily reported my feature as activated and I couldn't find anything that indicated on that something went wrong.

My proposed solution is to add some kind of permission check for the site collection the feature is about to be activated on, since the code
SPFeature feature = siteCollection.Features.Add(featureId.Value, true);
on line 1092 in InstallProcessControl.cs (of the 1.2 release) doesn't throw any exception even if the user running the setup doesn't have permission to admin that site collection.

Created Issue: Feature scoped for Site (Site collection) not activated during installation if Setup running user is not administrator on the Site collection

exton — Wed, 18 Feb 2009 11:35:50 GMT

Created Issue: The Windows Sharepoint Services Admin Service is Not Started!

bpelkey — Fri, 06 Feb 2009 02:33:35 GMT

Getting this error when running the setup.exe to install the test project DemoSolution.wsp

The Windows Sharepoint Services Admin Service is Not Started!

Any help with this would be great.
Bret

Commented Issue: Timeout error

khabba — Fri, 16 Jan 2009 13:28:04 GMT

Hi

When deploying on a production server, the client gets this error. Can someone shed more light please:

***** ERROR *****
Timeout error
CodePlex.SharePointInstaller.InstallException: Timeout error at CodePlex.SharePointInstaller.InstallProcessControl.WaitForJobCompletionCommand.Rollback()
at CodePlex.SharePointInstaller.InstallProcessControl.TimerEventRollback(Object myObject, EventArgs myEventArgs)

Thanks
Comments: ** Comment from web user: khabba **

Check if the Windows SharePoint Services Timer runs under an account that has the appropriate rights to run.

Commented Feature: MSI Integration

RyanWheeler — Fri, 21 Nov 2008 19:23:54 GMT

Integration into MSI which could either be done by providing commandline parameters or by implementing an System.Configuration.Installer class.
Comments: ** Comment from web user: RyanWheeler **

Eric - a heads up on the can of worms you will run into with MSI's on 2008 with UAC enabled. I been at this for a week now and don't have the answer, just warning you of what to expect and give you some clues.
Admin users run with a standard user token that doesn't have admin permissions and UAC 'upgrades' to privileged token as necessary - http://technet.microsoft.com/en-us/library/cc709628.aspx
You do custom installation in MSI's via CustomActions that can run immediately (as part of config UI) or Deferred (as part of the actual installation)
CustmActions can run as
A) NoImpersonate (which then runs under context of NT Authority\System and has full admin permissions)
B) Impersonated - which runs under the account of whomever kicked off the install.
Problems....
* A) will not work when db is on seperate server as System doesn't have permission (actually at that point it is Computer$ account) and you will get errors such as "The EXECUTE permission was denied on the object 'proc_putObject'..."
* B) will run fine EXCEPT if UAC is on as then impersonated user has standard token, is not member of local admin group and can't run stsadm with admin permissions or access .NET's .InstallState file (System.Configuration.Install.Installer)
You may think that you can use requireAdministrator in a manifest on your custom action or rely on UAC swapping standard token for privileged token, but that won't work.
You could use a bootstrapper to force requireAdministrator in manifest and thereby get privileged token from start - but that defeats some of the point of an MSI
I think I am going to settle for warning users to run from privileged cmd line (same effect as requireAdministrator bootstrapper) if it detects 2008.
More here http://stackoverflow.com/questions/304353/mark-msi-so-it-has-to-be-run-as-elevated-administrator-account
Get in touch if you want more detail - just warning you that its a nasty nasty can of worms ahead! Thanks for the great work!

Commented Feature: Support for selecting and installing multiple solutions

ravensorb — Wed, 22 Oct 2008 13:10:59 GMT

Support for selecting and installing multiple solutions in one go
Comments: ** Comment from web user: ravensorb **

I to would love to see this. I have the need to install 10 or 15 wsp files at a time, it would be great to have on installer that handles them all in one shot.

Created Issue: Solution File not found!

blalwani — Tue, 14 Oct 2008 15:16:47 GMT

Issue with the system check. Sometimes fails to detect the solution file and sometimes it works. However, solution file (wsp) does exist in the same directory but the system check fails sometimes at Solution file not found.