AnsweredAssumed Answered

version update takes forever

Question asked by andrewvr on Feb 6, 2016
Latest reply on Apr 8, 2017 by obaidaaqel86

Hi

 

I have done 2 updates to the latest Jan 2016 version of Forms and Workflow.  One went through without incident - probably 20 minutes overalll - on our local dev server.

 

The other, at a client, took forever.  In fact the GUI installer never finished - I killed the task after 14 hours.

 

I then ran the installation again with the PowerShell scripts and it did eventually finish, but still took an enormously long time.  I could not time the finish, but it was more than 4.5 hours.

 

Unfortunately, I could not find anything that showed me what it was doing whilst it was 'busy', but from the script output, I can see some indications of which stages took so long.

 

Note that the start time here was around 11:45 am.

 

Detected SharePoint 2013 is installed

Stopping Live Relay on server XXXXXX-SPAP.

Stopping Live Relay on server XXXXXX-SPFE.

Resetting Server(s):

        XXXXXX-SPAP

        XXXXXX-SPFE

Stopping Timer service on server XXXXXX-SPAP.

Starting Timer service on server XXXXXX-SPAP.

Stopping Timer service on server XXXXXX-SPFE.

Starting Timer service on server XXXXXX-SPFE.

Updating Solution Core Components

Upgrade job for solution Core Components (NintexWorkflow2013Core.wsp) is not created yet (time waiting=3 seconds)

Upgrade job for solution Core Components (NintexWorkflow2013Core.wsp) in server XXXXXX-SPAP is not finished yet

Upgrade job for solution Core Components (NintexWorkflow2013Core.wsp) in server XXXXXX-SPFE is not finished yet

Upgrade timer job for solution: Core Components (NintexWorkflow2013Core.wsp) in server XXXXXX-SPAP finished successfu

lly at: 02/06/2016 13:12:54

Upgrade timer job for solution: Core Components (NintexWorkflow2013Core.wsp) in server XXXXXX-SPFE finished successfu

lly at: 02/06/2016 13:12:09

Updating Solution Web Front End Components

Upgrade job for solution Web Front End Components (NintexWorkflow2013.wsp) is not created yet (time waiting=3 seconds)

Upgrade job for solution Web Front End Components (NintexWorkflow2013.wsp) in server XXXXXX-SPFE is not finished yet

Upgrade timer job for solution: Web Front End Components (NintexWorkflow2013.wsp) in server XXXXXX-SPFE finished succ

essfully at: 02/06/2016 14:43:26

Updating Solution Enterprise Features

Installing Solution Backwards Compatibility UI

Installing Solution Backwards Compatibility Enterprise Features

Restarting SharePoint Timer Services.

Stopping Timer service on server XXXXXX-SPAP.

Starting Timer service on server XXXXXX-SPAP.

Stopping Timer service on server XXXXXX-SPFE.

Starting Timer service on server XXXXXX-SPFE.

Already installed Certificate: Baltimore CyberTrust Root.crt

Already installed Certificate: GTE CyberTrust Global Root.cer

Already installed Certificate: Microsoft Internet Authority.cer

Already installed Certificate: Microsoft Secure Server Authority.cer

Already installed Certificate: Thawte Primary Root CA.cer

Already installed Certificate: Thawte SSL CA.cer

Already installed Certificate: Thawte SSL CA_SHA2.cer

Updating Solution Nintex Live

      ReInstalling version 3.0.3.2

Resetting Server(s):

        XXXXXX-SPAP

        XXXXXX-SPFE

Upgrade job for solution Nintex Live (NintexLiveCore.wsp) is not created yet (time waiting=3 seconds)

Upgrade job for solution Nintex Live (NintexLiveCore.wsp) in server XXXXXX-SPAP is not finished yet

Upgrade job for solution Nintex Live (NintexLiveCore.wsp) in server XXXXXX-SPFE is not finished yet

Upgrade timer job for solution: Nintex Live (NintexLiveCore.wsp) in server XXXXXX-SPAP finished successfully at: 02/0

6/2016 16:20:49

Upgrade timer job for solution: Nintex Live (NintexLiveCore.wsp) in server XXXXXX-SPFE finished successfully at: 02/0

6/2016 16:20:48

WARNING: Existing version of Nintex Live detected, an Upgrade was performed

Stopping Timer service on server XXXXXX-SPAP.

Starting Timer service on server XXXXXX-SPAP.

Stopping Timer service on server XXXXXX-SPFE.

Starting Timer service on server XXXXXX-SPFE.

 

 

DisplayName                    Id                                       CompatibilityLevel   Scope

-----------                    --                                       ------------------   -----

NintexLiveAdminLinks           29e9a673-31a4-46a3-b0d2-d8e1db1dbd92     14                   Web

Installing Nintex Workflow Start Service on: XXXXXX-SPAP

Installing Nintex Workflow Start Service on: XXXXXX-SPFE

Installing Nintex Live Workflow Queue Service on: XXXXXX-SPAP

Installing Nintex Live Workflow Queue Service on: XXXXXX-SPFE

Resetting Server(s):

        XXXXXX-SPAP

        XXXXXX-SPFE

 

The customer has three Nintex Content databases, with sizes of 5GB, 2GB and 200MB.

 

My questions are:

  • is this an expected duration for an update on a live site?
  • is there a way to arrange things so that it can go through quicker?
  • is there a safe point, before the completion, at which the customer may start using the product?

Outcomes