sharepointinstaller Work Item Rss Feed

Commented Issue: Fix scalability issue with web applications containing 1000s of site collections [17468]

deverly — Tue, 18 Jun 2013 23:15:02 GMT

If you have a site collection-scoped features and want the user to pick one or more site collections, this can fail if there are a large number of site collections in the web application you are browsing. This tends to happen with my sites, but that may not be the only cause. See also: Allow re-running the installer to change activation settings (http://sharepointinstaller.codeplex.com/WorkItem/View.aspx?WorkItemId=17469).
Comments: ** Comment from web user: deverly **

I am seeing this error as well.

05/02/2013 12:47:08.38 OWSTIMER.EXE (IP-0AA0BAE0:0x1314) 0x0FA0 SharePoint Foundation Topology umal Medium Solution Deployment : Missing one or more of the following attributes from the root node in solution _scrubbed_.wsp: assembly '', type ''. d276416c-eb21-459d-a849-34801636905e

05/02/2013 12:47:08.52 OWSTIMER.EXE (IP-0AA0BAE0:0x1314) 0x0FA0 SharePoint Foundation Topology 5mfi Medium Solution Deployment : No deployment call out defined for solution '_scrubbed_.wsp'. d276416c-eb21-459d-a849-34801636905e

05/02/2013 12:47:10.65 OWSTIMER.EXE (IP-0AA0BAE0:0x1314) 0x0FA0 SharePoint Foundation Topology b9h6 Medium The configuration database was queried for a non-existent object with the id 6764ecfe-556b-4db3-bf7f-213e7c2c5b18. Most commonly, this is caused by removing an SPFeatureDefinition without writing upgrade code to remove references to the feature from each site. d276416c-eb21-459d-a849-34801636905e

Commented Issue: Fix scalability issue with web applications containing 1000s of site collections [17468]

wastrilith2k — Wed, 12 Jun 2013 14:49:46 GMT

Hi! I am getting a similar error. Is the message you are having regarding "Collection was modified; enumeration operation may not execute"?

Thanks!

James

Closed Issue: AutoStatusPlus [17802]

PerrySharePoint — Wed, 10 Apr 2013 16:59:02 GMT

Installation fault with following details:

***** SOLUTION DEPLOYMENT *****
PROJECTSERVER : The channel 'ipc client' is already registered.

***** ERROR *****
PROJECTSERVER : The channel 'ipc client' is already registered.

CodePlex.SharePointInstaller.InstallException: PROJECTSERVER : The channel 'ipc client' is already registered.
---> CodePlex.SharePointInstaller.InstallException: PROJECTSERVER : The channel 'ipc client' is already registered.

at CodePlex.SharePointInstaller.InstallProcessControl.WaitForJobCompletionCommand.Execute()
--- End of inner exception stack trace ---
at CodePlex.SharePointInstaller.InstallProcessControl.WaitForJobCompletionCommand.Execute()
at CodePlex.SharePointInstaller.InstallProcessControl.TimerEventInstall(Object myObject, EventArgs myEventArgs)

I'm new to this and are struggling. Any assistance would be appreciated.
Comments: Unrelated to SharePoint Solution Installer

Commented Issue: AutoStatusPlus [17802]

PerrySharePoint — Wed, 10 Apr 2013 16:58:50 GMT

This error is not arising from SharePoint solution installer, because it does not use "ipc client".

Commented Issue: spadmin error [18124]

PerrySharePoint — Wed, 10 Apr 2013 16:57:53 GMT

When I use the installer, it results in an error shown below:

<Server Name> : http://server:3931/ : This operation uses the SharePoint Administration service (spadmin), which could not be contacted. If the service is stopped or disabled, start it and try the operation again.
test_site_1 : Error: The removal of this file failed: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\MyFeature\elements.xml.

However, the administration service is running fine, and the user is also a local administrator.

This appears to be sporadic and usually disappears when I run the installer again.

Any suggestions would be highly appreciated as this is critical, and one of our client is facing this issue quite often.

Thanks,
Karthik
Comments: ** Comment from web user: PerrySharePoint **

http://noverse.com/blog/2012/06/how-to-write-a-good-bug-report/

Highlights: At least include what version of platform (SharePoint here), what version of product, what you expected to see, and what you did see, and how to reproduce.

Commented Issue: Locked sitecollection causes an uninstall error [19236]

PerrySharePoint — Wed, 10 Apr 2013 16:57:29 GMT

Hello,

I've got a sharepointfarm with 2 webapplications and some sitecollections.
I'm installing a solution on, lets call it, webapplication 1.
Then I lock a sitecollection in webapplication 2.
Now, when I try to uninstall the solution the installer throw an "Failed to deativate features. Access to this Web site has been blocked." exception and performs a rollback.

How can i prevent this error?

Thanks for any advices!

With best regards
ChrisHarp

2010-12-06 14:18:33,426 User [6] ERROR CodePlex.SharePointInstaller.Installer [(null)] <(null)> - Access to this Web site has been blocked.

Please contact the administrator to resolve this problem.
Microsoft.SharePoint.SPException: Access to this Web site has been blocked.

Please contact the administrator to resolve this problem. ---> System.Runtime.InteropServices.COMException (0x81020071): Access to this Web site has been blocked.

Please contact the administrator to resolve this problem.
at Microsoft.SharePoint.Library.SPRequestInternalClass.OpenWebInternal(String bstrUrl, Guid& pguidID, String& pbstrRequestAccessEmail, UInt32& pwebVersion, String& pbstrServerRelativeUrl, UInt32& pnLanguage, UInt32& pnLocale, String& pbstrDefaultTheme, String& pbstrDefaultThemeCSSUrl, String& pbstrAlternateCSSUrl, String& pbstrCustomizedCssFileList, String& pbstrCustomJSUrl, String& pbstrAlternateHeaderUrl, String& pbstrMasterUrl, String& pbstrCustomMasterUrl, String& pbstrSiteLogoUrl, String& pbstrSiteLogoDescription, Object& pvarUser, Boolean& pvarIsAuditor, Int32& plSiteFlags)
at Microsoft.SharePoint.Library.SPRequest.OpenWebInternal(String bstrUrl, Guid& pguidID, String& pbstrRequestAccessEmail, UInt32& pwebVersion, String& pbstrServerRelativeUrl, UInt32& pnLanguage, UInt32& pnLocale, String& pbstrDefaultTheme, String& pbstrDefaultThemeCSSUrl, String& pbstrAlternateCSSUrl, String& pbstrCustomizedCssFileList, String& pbstrCustomJSUrl, String& pbstrAlternateHeaderUrl, String& pbstrMasterUrl, String& pbstrCustomMasterUrl, String& pbstrSiteLogoUrl, String& pbstrSiteLogoDescription, Object& pvarUser, Boolean& pvarIsAuditor, Int32& plSiteFlags)
--- End of inner exception stack trace ---
at Microsoft.SharePoint.Library.SPRequest.OpenWebInternal(String bstrUrl, Guid& pguidID, String& pbstrRequestAccessEmail, UInt32& pwebVersion, String& pbstrServerRelativeUrl, UInt32& pnLanguage, UInt32& pnLocale, String& pbstrDefaultTheme, String& pbstrDefaultThemeCSSUrl, String& pbstrAlternateCSSUrl, String& pbstrCustomizedCssFileList, String& pbstrCustomJSUrl, String& pbstrAlternateHeaderUrl, String& pbstrMasterUrl, String& pbstrCustomMasterUrl, String& pbstrSiteLogoUrl, String& pbstrSiteLogoDescription, Object& pvarUser, Boolean& pvarIsAuditor, Int32& plSiteFlags)
at Microsoft.SharePoint.SPWeb.InitWebPublic()
at Microsoft.SharePoint.SPWeb.get_ServerRelativeUrl()
at Microsoft.SharePoint.SPWeb.get_Url()
at CodePlex.SharePointInstaller.Wrappers.SiteInfo.IsAccessible(SPWeb web)
at CodePlex.SharePointInstaller.Commands.Feature.DeactivateFeaturesCmd.Execute()
at CodePlex.SharePointInstaller.Controls.InstallProcessControl.Execute(Object sender, DoWorkEventArgs e)
2010-12-06 14:18:34,441 User [1] INFO CodePlex.SharePointInstaller.Installer [(null)] <(null)> -
***** Uninstall Failed 12/6/2010 2:18:34 PM *****
Comments: ** Comment from web user: PerrySharePoint **

I think "Development V2" may be dead?

Closed Issue: DeactivatedSiteCollections is not assigned values [18695]

PerrySharePoint — Wed, 20 Mar 2013 06:41:06 GMT

Hi

1. Line 1168 of InstallProcessControl.cs has

// KML - not sure why JPI didn't just do this above and avoided using the local dictionary
// LFN - Agree, local dictionary removed making the following code obsolete.
/*
foreach (SPSite _spSite in _dicDeactivatedSiteCollections.Values)
{
deactivatedSiteCollections.Add(_spSite);
}
DeactivateFeature(deactivatedSiteCollections, featureIds);
*/

The deactivatedSiteCollections is used by Upgrade and Repair command to reactivate features.

2. Actually I don't think "Upgrade" and "Repair" should deactivate features and reactivate features at all.

Usually the deactivating features will do clean-up work to remove settings from system. If "Upgrade" and "Repair" do deactivating, it will do cleanup which is not desirable during "Upgrade" and "Repair". During "Upgrade" and "Repair", the process should leave the feature as it is, no deactivating or activating. If users do want to do deactivating or activating, they could do uninstallation and re-installation.
Comments: Outdated. Last question to submitter was three years ago and received no answer, so appears abandoned by submitter.

Closed Issue: Facing problem while upgrade process [21463]

PerrySharePoint — Wed, 20 Mar 2013 06:38:40 GMT

When i am trying to upgrade installed product using CodePlex SharePoint Installer it gives me following error:
Solution "xxxxxxxxxxx.wsp" is not deployed. It is upgraded in the configuration database. To deploy to the front end machines, use the Deploy method.

When i tried debugging the code, i found that code gives such error on following line:
solution.Upgrade(FileUtil.GetRootedPath(SolutionInfo.File), JobCmd.GetImmediateJobTime());
Comments: Submitter never responded and never gave basic version info.

Reopened Issue: Facing problem while upgrade process [21463]

PerrySharePoint — Wed, 20 Mar 2013 06:38:06 GMT

Closed Issue: Facing problem while upgrade process [21463]

PerrySharePoint — Wed, 20 Mar 2013 06:37:50 GMT

Commented Issue: Facing problem while upgrade process [21463]

PerrySharePoint — Fri, 22 Feb 2013 00:42:22 GMT

Note: I've just composed the above template to post for bug reports that lack such info; I'm surprised how many people don't even bother to include basic version info for the software and the SharePoint version.

But, this bug report is a nice one in that the submitter went the extra mile and used the debugger and reported the source code. That was nicely done.

My advice would be to try uninstalling the solution, then reinstalling it.

Commented Issue: Facing problem while upgrade process [21463]

PerrySharePoint — Fri, 22 Feb 2013 00:40:30 GMT

I think several good principles for all bug reports are:

1) Remember to describe your environment and what version of software you are using; in cases involving SharePoint software, remember to also specify what version of SharePoint you are using.

2) Describe clearly how to reproduce the problem.

3) Check relevant logs and quote (via copy & paste, not manually retyping) any errors or warnings. For SharePoint, check the ULS logs in the SharePoint 12/14/15 hive.

Closed Issue: Incorrect config key [17996]

PerrySharePoint — Thu, 21 Feb 2013 17:23:35 GMT

Hi

Love this tool, it's greay. Just downloaded v1.2.2 and noticed small error. In the demo config file, there's a key called "FarmFeatureId". The key should actually be "FeatureId" - if you use FarmFeatureId then the feature isn't activated at the end of the process.

The readme is correct, but if like me, you just edited the demo file, you might be left wondering why the feature didn't activate.

Cheers.
Comments: Taken care of, per comments

Closed Issue: Hard Coded Solution Title in SharePointSolutionInstaller_V1_2_2.zip [19104]

PerrySharePoint — Thu, 21 Feb 2013 17:22:41 GMT

It looks like there is a hard coded solution title in the binary available for download. During an upgrade we noticed that the solution title wasn't what we had set within our config. I checked through the source code
and everything looks fine.

So I loaded Setup.exe using reflector I can see the following:

Program::CreateProcessControl() : InstallProcessControl
---

internal static InstallProcessControl CreateProcessControl()
{
InstallProcessControl control = new InstallProcessControl();
control.Title = "Installing";
control.SubTitle = "Please wait while Ontolica is installed";
return control;
}
Comments: Fixed in release 1.2.4

Commented Issue: Hard Coded Solution Title in SharePointSolutionInstaller_V1_2_2.zip [19104]

PerrySharePoint — Thu, 21 Feb 2013 17:21:31 GMT

Fixed in release 1.2.4..

Commented Feature: Support for selecting and installing multiple solutions [7933]

Israa17 — Tue, 21 Feb 2012 13:36:51 GMT

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

Yes please I need this so much

Created Issue: Facing problem while upgrade process [21463]

psnagarkar — Thu, 08 Sep 2011 06:20:00 GMT

Commented Issue: Locked sitecollection causes an uninstall error [19236]

z5903743 — Mon, 30 May 2011 07:04:35 GMT

Support win7 it?

Commented Issue: Locked sitecollection causes an uninstall error [19236]

z5903743 — Mon, 30 May 2011 07:03:41 GMT

Support win7 it?

Commented Issue: Locked sitecollection causes an uninstall error [19236]

PerrySharePoint — Thu, 05 May 2011 05:49:28 GMT

Oh, ok. I'm not familiar with the V2 code, so I don't edit it.