Plumsail Workflow Action Pack activation issue

by gizmo3k » Fri Feb 24, 2017 4:26 pm

Hi,

I recently got the following error trying to activate the Plumsail Workflow Action Pack on a newly built site:

The Site scoped feature being activated has a dependency on hidden Site Collection scoped feature 'FeatureDefinition/15/9a5d1295-65c0-4c8e-a926-968da90d2ef9' (ID: '9a5d1295-65c0-4c8e-a926-968da90d2ef9'). Hidden features cannot be auto-activated across scopes. There may be one or more visible Site Collection scoped features that auto-activate the dependent hidden feature.


Publishing features are not enabled on the site.

Activating Plumsail used to work fine, I looked at one of our old sites and deactivated the feature, upon
attempting to reactivate it I got this error again.

Has anyone seen this before?

Thanks
gizmo3k
 
Posts: 9
Joined: Fri Aug 12, 2016 2:00 pm

by Roman Rylov » Mon Feb 27, 2017 9:05 am

Hello,

Please pay attention that you need to activate web application feature "Plumsail Auth Service".

https://plumsail.com/docs/workflow-actions-pack/help-pages/Installation%20for%20SharePoint%202013.html#install
User avatar
Roman Rylov
 
Posts: 328
Joined: Tue Nov 11, 2014 6:25 pm

by gizmo3k » Mon Feb 27, 2017 10:51 am

Thanks Roman,

How can I activate this in SharePoint Online? Do I need to deactivate and reactivate the solution?

Any idea why this has now failed? It worked ok previously.

Thanks

Alan
gizmo3k
 
Posts: 9
Joined: Fri Aug 12, 2016 2:00 pm

by Roman Rylov » Mon Feb 27, 2017 2:07 pm

Alan,

Sorry, I didn't notice this is SharePoint Online issue.

This is the hidden feature that should be activated on the site automatically.
Looks like in your case it wasn't activated.
To fix it you can try to reactivate solution or activate the feature manually, as an example you can use the following javascript snippet via browser developer console (press F12 and navigate to console tab to open it):

Code: Select all
(function(featureId, enable) {
    var clientContext = new SP.ClientContext.get_current();
    var featureGuid   = new SP.Guid('{' + featureId + '}');
    var webFeatures   = clientContext.get_site().get_features();

    if (enable) {
        webFeatures.add(featureGuid, true, SP.FeatureDefinitionScope.site);
    } else {
        webFeatures.remove(featureGuid, false);
    }

    clientContext.executeQueryAsync(
        function() { alert('Success!'); }
      , function(sender, args) {
          alert('Fail: ' + args.get_message() + '\n' + args.get_stackTrace());
    });
})('(function(featureId, enable) {
    var clientContext = new SP.ClientContext.get_current();
    var featureGuid   = new SP.Guid('{' + featureId + '}');
    var webFeatures   = clientContext.get_web().get_features();

    if (enable) {
        webFeatures.add(featureGuid, true, SP.FeatureDefinitionScope.site);
    } else {
        webFeatures.remove(featureGuid, false);
    }

    clientContext.executeQueryAsync(
        function() { alert('Success!'); }
      , function(sender, args) {
          alert('Fail: ' + args.get_message() + '\n' + args.get_stackTrace());
    });
})('d7891031-e7f5-4734-8077-9189dd35551c', true);', true);


Please let me know if you need any help.
User avatar
Roman Rylov
 
Posts: 328
Joined: Tue Nov 11, 2014 6:25 pm

by gizmo3k » Mon Feb 27, 2017 2:48 pm

Thanks Roman,

I tried running that, however I got an Invalid or unexpected token error on line 17.

I can't see what's wrong (I don't know the language at all), can you have a look for me please?

Thanks

Alan
gizmo3k
 
Posts: 9
Joined: Fri Aug 12, 2016 2:00 pm

by Roman Rylov » Mon Feb 27, 2017 3:55 pm

Alan,

Could you please leave a request for screen sharing session at support@plumsail.com.
User avatar
Roman Rylov
 
Posts: 328
Joined: Tue Nov 11, 2014 6:25 pm

by gizmo3k » Tue Feb 28, 2017 8:50 am

Hi Roman,

Thanks for all your help.

I deactivated the solution and reactivated it, then used the following (also using PnP-Powershell) to reactivate the feature on each site:

Code: Select all
$root = "https://domain.sharepoint.com/sites/rootsite"

Connect-PnPOnline -Url $root -Credentials $creds

$sites = Get-PnPSubWebs
Write-Host "Started at $(Get-date)" -ForegroundColor Green
foreach ($site in $sites){
    $relativeurl = $site.ServerRelativeUrl.ToString()
    $url = "https://domain.sharepoint.com$relativeurl"
    Connect-PnPOnline -Url $url -Credentials $creds

    Enable-PnPFeature -Identity d7891031-e7f5-4734-8077-9189dd35551c -Web $site -Sandboxed
    Write-Host "Enabled on $url" -ForegroundColor Cyan
}

Write-Host "Ended at $(Get-Date)" -ForegroundColor Green


This appears to work fine, although I am confused why the solution stopped working - it was working fine a couple of weeks ago, with no changes made to the environment.

Thanks

Alan
gizmo3k
 
Posts: 9
Joined: Fri Aug 12, 2016 2:00 pm


Return to Workflow Actions Pack for Office 365

cron