none
UpgradeStatus.aspx doesn't display latest upgrade sessions RRS feed

  • Question

  • I ran a December CU upgrade on 1/8.

    Developers reported some issues on 1/9 and 1/11, on both dates I reran the upgrade via the wizard the  on my 1 SPFE and 1 SPAPP servers. They upgraded successfully, but UpgradeStatus.aspx doesn't reflect the post-1/8 running of the upgrades.

    I ran 

    $sn = get-spserver SPFE
    $sn.needsupgrade

    Returned "True"

    Same for SPAPP returned "False"

    100% sure I ran configuration successfully on both servers, iisresetted, and rebooted.

    Rechecked with Get-SPServer | Where{ $_.NeedsUpgrade -eq $TRUE}, which returned the SPFE and SPSQL servers.

    (FWIW, the issues Developers reported were seemingly unrelated to the upgrade, one was a bad Managed Path, the other was something similar, but the proximity timewise to the CU made me jump to suspect it first.)

    In SPFE ULS I'm looking at most recent PSCDiagnostics. Searching "error", all that comes up is:

    01/11/2019 16:31:16  1  INF      Entering function TaskDriver.Stop
    01/11/2019 16:31:16  1  INF        Entering function TaskDriver.OnTaskDriverStop
    01/11/2019 16:31:16  1  INF          Sending a task driver stop event: TaskDriverEventArgs.EventCriticalityType error, TaskDriverEventArgs.EventType.stop, 
    01/11/2019 16:31:16  1  INF          Entering function TaskDriverStateChange.Enter
    01/11/2019 16:31:16  1  INF            Acquiring the writer lock to change the state
    01/11/2019 16:31:16  1  INF            Current state of the task driver is neverrun.  You want to change it to stoppedrunning
    01/11/2019 16:31:16  1  INF            Changed state of the task driver to neverrun
    01/11/2019 16:31:16  1  INF            Released the writer lock to change the state
    01/11/2019 16:31:16  1  INF          Leaving function TaskDriverStateChange.Enter
    01/11/2019 16:31:16  1  INF          Entering function TaskDriver.FireOnTaskDriverEvent
    01/11/2019 16:31:16  1  INF            Entering function UserInterface.TaskDriverEventHandler
    01/11/2019 16:31:16  1  INF              Received a TaskDriverEventHandler: TaskDriverEventArgs.EventCriticalityType error, TaskDriverEventArgs.EventType stop, message 
    01/11/2019 16:31:16  1  INF              There isn't a current visible user form or the current form is not handling events, so we will handle this task driver event
    01/11/2019 16:31:16  1  INF            Leaving function UserInterface.TaskDriverEventHandler
    01/11/2019 16:31:16  1  INF          Leaving function TaskDriver.FireOnTaskDriverEvent

    Searching for "Success":

    01/11/2019 16:31:16  1  INF    Entering function PsconfigApplicationContext.ClosePsconfigApplication
    01/11/2019 16:31:16  1  INF      The psconfig ui application is closing
    01/11/2019 16:31:16  1  INF      We have do not have a main form, thus the application has been told to close prior to showing the ui at all
    01/11/2019 16:31:16  1  INF    Leaving function PsconfigApplicationContext.ClosePsconfigApplication
    01/11/2019 16:31:16  1  INF    Return code indicates a success
    01/11/2019 16:31:16  1  INF    Entering function Common.StartAllServices
    01/11/2019 16:31:16  1  INF      Starting Service SPWindowsTokenServiceInstance
    01/11/2019 16:31:16  1  INF      Calling ServiceInstance.Start() start the SPWindowsTokenServiceInstance service
    01/11/2019 16:31:16  1  INF      Starting Service SPTracingServiceInstance
    01/11/2019 16:31:16  1  INF      Calling ServiceInstance.Start() start the SPTracingServiceInstance service
    01/11/2019 16:31:16  1  INF      Starting Service SPAdministrationServiceInstance
    01/11/2019 16:31:16  1  INF      Calling ServiceInstance.Start() start the SPAdministrationServiceInstance service
    01/11/2019 16:31:16  1  INF      Starting Service SPTimerServiceInstance
    01/11/2019 16:31:16  1  INF      Calling ServiceInstance.Start() start the SPTimerServiceInstance service
    01/11/2019 16:31:16  1  INF      Starting Service SPDistributedCacheServiceInstance
    01/11/2019 16:31:16  1  INF      Calling ServiceInstance.Start() start the SPDistributedCacheServiceInstance service
    01/11/2019 16:31:16  1  INF    Leaving function Common.StartAllServices
    01/11/2019 16:31:16  1  INF  Leaving function PsconfigUserInterfaceMain.Main

    Where else to look? 

    Thanks





    • Edited by scogordo Monday, January 14, 2019 6:08 PM
    Monday, January 14, 2019 5:34 PM

Answers

  • Resolved. Orphaned site,  https://blog.bugrapostaci.com/2015/11/09/cleaning-orphan-database-from-sharepoint-farm/, identified a <fld type="null" /> and deleted it through ps.

    Thanks y'all. As usual, the answer always seems so simple once you know what it is.

    Thursday, January 17, 2019 8:52 PM

All replies

  • One other thing, FarmStatus.aspx shows No Action Required for all farm servers.

    ???

    Gonna rerun PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures, see if the magic happens.
    • Edited by scogordo Monday, January 14, 2019 8:44 PM
    Monday, January 14, 2019 6:32 PM
  • The farm is being upgraded in the timer service process. The task is 100.00% completed.
    Finalizing the upgrade...

    Failed to upgrade SharePoint Products.

    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfig
    urationTaskException was thrown.  Additional exception information: The upgrade
    command is invalid or a failure has been encountered.

    Attempt to register null pointer at:

    Attempt to register null pointer at:.   (EventID:ajyw5)

    Upgrade completed with errors.  Review the upgrade log file located in ...Upgrade-20190114-204944-786-b2d9278ea8bc47858e414e155e48ee11.log.  The number of errors and warnings is listed

    ---

    Looks like I'm tracking down an orphanded db, I'll update...

    • Edited by scogordo Tuesday, January 15, 2019 2:00 AM
    Tuesday, January 15, 2019 1:57 AM
  • Tried 

    $dbs = Get-SPDatabase 
    $dbs | %{Write-Host "Database"$_.Name;if($_.Exists){Write-Host "DB Exists." -f Green}else{Write-Host "DB does not exist." -f red}}

    All dbs return "DB Exists"

    Logs:

    Timestamp              Process                                  TID    Area                          Category                      EventID Level      Message Correlation
    01/14/2019 20:51:27.21 PSCONFIG (0x1A80) 0x60F4 SharePoint Foundation Upgrade SPFarmSequence2 ajy6a INFO SPFarm Name=SharePoint_Config 00000000-0000-0000-0000-000000000000
    01/14/2019 20:51:27.21 PSCONFIG (0x1A80) 0x60F4 SharePoint Foundation Upgrade SPFarmSequence2 ajy6a WARNING Feature could not be upgraded. Exception: Feature definition id -83d9-4a61-b1dd-3c7c1c8901f7' could not be found. 00000000-0000-0000-0000-000000000000
    01/14/2019 20:51:27.26 PSCONFIG (0x1A80) 0x60F4 SharePoint Foundation Upgrade SPFarmSequence2 ajy6a INFO SPFarm Name=SharePoint_Config 00000000-0000-0000-0000-000000000000
    01/14/2019 20:51:27.26 PSCONFIG (0x1A80) 0x60F4 SharePoint Foundation Upgrade SPFarmSequence2 ajy6a WARNING Feature could not be upgraded. Exception: Feature definition id 'fdfeeaf7-db7e-4073-9578-18ce8eda5c72' could not be found. 00000000-0000-0000-0000-000000000000
    Timestamp              Process                                  TID    Area                          Category                      EventID Level      Message Correlation
    01/14/2019 20:51:41.65 OWSTIMER (0x034C) 0x024C SharePoint Foundation Upgrade SPFarmSequence2 ajy6a INFO SPFarm Name=SharePoint_Config 11111111-2222-3333-4444-555555555555
    01/14/2019 20:51:41.65 OWSTIMER (0x034C) 0x024C SharePoint Foundation Upgrade SPFarmSequence2 ajy6a WARNING Feature could not be upgraded. Exception: Feature definition id '55555555-6666-7777-8888-999999999999' could not be found. 11111111-2222-3333-4444-555555555555
    01/14/2019 20:51:41.67 OWSTIMER (0x034C) 0x024C SharePoint Foundation Upgrade SPFarmSequence2 ajy6a INFO SPFarm Name=SharePoint_Config 11111111-2222-3333-4444-555555555555
    01/14/2019 20:51:41.67 OWSTIMER (0x034C) 0x024C SharePoint Foundation Upgrade SPFarmSequence2 ajy6a WARNING Feature could not be upgraded. Exception: Feature definition id 'fdfeeaf7-db7e-4073-9578-18ce8eda5c72' could not be found. 11111111-2222-3333-4444-555555555555
    01/14/2019 20:51:54.68 OWSTIMER (0x034C) 0x024C SharePoint Foundation Upgrade SPHierarchyManager ajyw5 INFO SPWebApplication Name=Company Portal 11111111-2222-3333-4444-555555555555
    01/14/2019 20:51:54.68 OWSTIMER (0x034C) 0x024C SharePoint Foundation Upgrade SPHierarchyManager ajyw5 ERROR Attempt to register null pointer at:    at Microsoft.SharePoint.Upgrade.SPHierarchyManager.AddNextLevelObjects(Object current, IEnumerable nextObjects)     at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, Boolean bRecursing, SPDelegateManager delegateManager)     at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, SPDelegateManager delegateManager)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.RunRecursiveUpgrade(Object o, Boolean bNeedsUpgrade, SPTree`1 root, Double rootRatioOrg, SPChronoMeter chronoMeter)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.RunRecursiveUpgrade(Object o, Boolean bNeedsUpgrade, SPTree`1 root, Double rootRatioOrg, SPChronoMeter chronoMeter)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.RunRecursiveUpgrade(Object o, Boolean bNeedsUpgrade, SPTree`1 root, Double rootRatioOrg, SPChronoMeter chronoMeter)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.RunRecursiveUpgrade(Object o, Boolean bNeedsUpgrade, SPTree`1 root, Double rootRatioOrg, SPChronoMeter chronoMeter)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.RunRecursiveUpgrade(Object o, Boolean bNeedsUpgrade, SPTree`1 root, Double rootRatioOrg, SPChronoMeter chronoMeter)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Administration.SPUpgradeJobDefinition.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPAdministrationServiceJobDefinition.ExecuteAdminJob(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)  . 11111111-2222-3333-4444-555555555555
    01/14/2019 20:52:18.87 OWSTIMER (0x034C) 0x024C SharePoint Foundation Upgrade SPHierarchyManager ajyw5 INFO No context object 11111111-2222-3333-4444-555555555555
    01/14/2019 20:52:18.87 OWSTIMER (0x034C) 0x024C SharePoint Foundation Upgrade SPHierarchyManager ajyw5 ERROR Attempt to register null pointer at:    at Microsoft.SharePoint.Upgrade.SPHierarchyManager.AddNextLevelObjects(Object current, IEnumerable nextObjects)     at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, Boolean bRecursing, SPDelegateManager delegateManager)     at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, SPDelegateManager delegateManager)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse)     at Microsoft.SharePoint.Administration.SPServerProductInfo.DetectLocalUpgradeStatus()     at Microsoft.SharePoint.Administration.SPServerProductInfo.DetectLocalProductVersions(SPProductVersions prodVer)     at Microsoft.SharePoint.Administration.SPServerProductInfo.UpdateProductInfoInDatabase(Guid serverGuid)     at Microsoft.SharePoint.Administration.SPUpgradeJobDefinition.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPAdministrationServiceJobDefinition.ExecuteAdminJob(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)  . 11111111-2222-3333-4444-555555555555
    01/14/2019 20:52:25.27 OWSTIMER (0x034C) 0x024C SharePoint Foundation Upgrade SPUpgradeSession aj0ur INFO No context object 11111111-2222-3333-4444-555555555555
    01/14/2019 20:52:25.27 OWSTIMER (0x034C) 0x024C SharePoint Foundation Upgrade SPUpgradeSession aj0ur ERROR Upgrade completed with errors.  Review the upgrade log file located in F:\LOGS\Upgrade-20190114-.log.  The number of errors and warnings is listed at the end of the upgrade log file. 11111111-2222-3333-4444-555555555555

    Tuesday, January 15, 2019 2:33 AM
  • Hi,

    What is the result after you run "PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures"?

    You would check below article about "Failed to upgrade SharePoint Products", there are many solutions in this article:

    https://social.technet.microsoft.com/Forums/en-US/94a8bb64-e0ea-493f-8e29-01347b1fc6c7/psconfig-fails-quotfailed-to-upgrade-sharepoint-productsquot?forum=smallbusinessserver

    Best regards,

    Allen Bai


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Tuesday, January 15, 2019 8:20 AM
  • Thanks Allen. Results are above (i know there's a lot to read ;))

    Bringing them down:

    The farm is being upgraded in the timer service process. The task is 100.00% completed.
    Finalizing the upgrade...

    Failed to upgrade SharePoint Products.

    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfig
    urationTaskException was thrown.  Additional exception information: The upgrade
    command is invalid or a failure has been encountered.

    Attempt to register null pointer at:

    Attempt to register null pointer at:.   (EventID:ajyw5)

    Upgrade completed with errors.  Review the upgrade log file located in ...Upgrade-20190114-204944-786-b2d9278ea8bc47858e414e155e48ee11.log.  The number of errors and warnings is listed

    Tuesday, January 15, 2019 3:54 PM
  • Hi,

    From the results, the issue is about "Failed to upgrade SharePoint Products". So have you checked the article provided in my first reply?(do not directly see the answer, see others' replies)

    Also check the upgrade log for more information.

    Best regards,

    Allen Bai


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Wednesday, January 16, 2019 6:16 AM
  • Thanks for the link, Allen, unfortunately didn't find anything that seemed useful.

    Poring over the non-ERROR upgrade log now....

    Wednesday, January 16, 2019 5:56 PM
  • Resolved. Orphaned site,  https://blog.bugrapostaci.com/2015/11/09/cleaning-orphan-database-from-sharepoint-farm/, identified a <fld type="null" /> and deleted it through ps.

    Thanks y'all. As usual, the answer always seems so simple once you know what it is.

    Thursday, January 17, 2019 8:52 PM
  • Hi,

    I am glad that you have fixed your issue.

    Do not forget to mark your reply as an answer, this will close this thread. And other people who have similar issue will directly see your answer.

    Best reagrds,

    Allen Bai


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Friday, January 18, 2019 1:48 AM