none
"Could not find the schedule for this work item" powerpivot scheduled refresh on sharepoint upon uploading new version

    Question

  • We are in the process of migrating to sharepoint 2013, and while testing the powerpivot functionalities we encountered the following strange behaviour:

    For a workbook with a set scheduled refresh, upon uploading a new version of this document, the old schedule has disappeared and we are asked to set a (new) schedule.

    When a new schedule is set, the data refresh history page does display the previous refresh jobs...

    When I upload a new version of a workbook, and not set a new schedule, the next day nothing seems to have happened, but when I set a schedule for this workbook and view the corresponding history page, it does show that sharepoint tried to refresh the workbook at the scheduled time (set for the old version of the workbook), but failed with the message "Could not find the schedule for this work item"

    Since we regularly update our workbooks, I do not want to manually set a refresh job every time I upload a new version of a document, so I hope there is some kind of fix. Does someone have any ideas?

    Wednesday, July 31, 2013 6:52 AM

Answers

  • Hi Ed,

    Yes, it still is. We're in contact with Microsoft, and it is a known issue that should have been solved with a hotfix (see below). 

    Unfortunately the fix only works in some cases:

    - upload document -> set refresh schedule -> upload the exact same document without alterations (fail)
    - upload document -> set refresh schedule -> upload the same document, but with changes made locally (fail)
    - upload document -> set refresh schedule -> download the document from sharepoint -> make some changes locally -> upload to sharepoint (succeeds)

    Knowledge base 2874879, and perform the following steps:

    1.       Download the hotfix from the KB above (if you don’t already have it.)
    2.       Run the EXE file to extract the SQLServer2012-KB2874879-x64.exe file to a file location (e.g. C:\Temp)
    3.       Open a command prompt and browse the location where the EXE file was extracted
    4.       Run the following command: SQLServer2012-KB2874879-x64.exe /extract: C:\Temp\SQLUpdate
    5.       Once the files are extracted, browse to the SQLUpdate folder (or whatever directory you specified) and browse to C:\temp\SQLUpdate\1033_enu_lp\x64\setup
    6.       You should find a sppowerpivot.msi file in that folder.
    7.       Move that file to your SharePoint server(s) and install that update.  
    8.       Once the sppowerpivot.msi file has been installed on all of your SharePoint servers, run the PowerPivot configuration tool.   The tool should report that an upgrade is necessary. 
    9.       Once the upgrade is done, test your file and you should have the refresh schedules after editing a file with the client.


    Monday, October 28, 2013 7:42 AM

All replies

  • Have you made any progress with this?

    Thanks!


    Ed Price, SQL Server Customer Program Manager (Blog, Small Basic, Wiki Ninjas, Wiki)

    Answer an interesting question? Create a wiki article about it!

    Thursday, August 22, 2013 6:25 PM
  • I'm afraid not.

    I'm in the process of checking the entries in the DB, corresponding to the schedules, to see if everthing is set correctly. It appears the database does not change values when uploading a new version of a file. When next setting a schedule again, the entry in the Database is updated: this is as expected.

    So, the DB entries are not the reason Sharepoint/PowerPivot cannot find a schedule... very strange...

    I'm at a loss what to do next



    • Edited by Jasper Kock Friday, August 23, 2013 1:25 PM
    Friday, August 23, 2013 7:01 AM
  • Any ideas for Jasper?

    Thanks!


    Ed Price, SQL Server Customer Program Manager (Blog, Small Basic, Wiki Ninjas, Wiki)

    Answer an interesting question? Create a wiki article about it!

    Friday, September 13, 2013 6:50 PM
  • Jasper, is this still an issue?

    Thanks!


    Ed Price, SQL Server Customer Program Manager (Blog, Small Basic, Wiki Ninjas, Wiki)

    Answer an interesting question? Create a wiki article about it!

    Friday, October 25, 2013 8:08 PM
  • Hi Ed,

    Yes, it still is. We're in contact with Microsoft, and it is a known issue that should have been solved with a hotfix (see below). 

    Unfortunately the fix only works in some cases:

    - upload document -> set refresh schedule -> upload the exact same document without alterations (fail)
    - upload document -> set refresh schedule -> upload the same document, but with changes made locally (fail)
    - upload document -> set refresh schedule -> download the document from sharepoint -> make some changes locally -> upload to sharepoint (succeeds)

    Knowledge base 2874879, and perform the following steps:

    1.       Download the hotfix from the KB above (if you don’t already have it.)
    2.       Run the EXE file to extract the SQLServer2012-KB2874879-x64.exe file to a file location (e.g. C:\Temp)
    3.       Open a command prompt and browse the location where the EXE file was extracted
    4.       Run the following command: SQLServer2012-KB2874879-x64.exe /extract: C:\Temp\SQLUpdate
    5.       Once the files are extracted, browse to the SQLUpdate folder (or whatever directory you specified) and browse to C:\temp\SQLUpdate\1033_enu_lp\x64\setup
    6.       You should find a sppowerpivot.msi file in that folder.
    7.       Move that file to your SharePoint server(s) and install that update.  
    8.       Once the sppowerpivot.msi file has been installed on all of your SharePoint servers, run the PowerPivot configuration tool.   The tool should report that an upgrade is necessary. 
    9.       Once the upgrade is done, test your file and you should have the refresh schedules after editing a file with the client.


    Monday, October 28, 2013 7:42 AM
  • Hi Ed,

    Yes, it still is. We're in contact with Microsoft, and it is a known issue that should have been solved with a hotfix (see below). 

    Unfortunately the fix only works in some cases:

    - upload document -> set refresh schedule -> upload the exact same document without alterations (fail)
    - upload document -> set refresh schedule -> upload the same document, but with changes made locally (fail)
    - upload document -> set refresh schedule -> download the document from sharepoint -> make some changes locally -> upload to sharepoint (succeeds)

    Knowledge base 2874879, and perform the following steps:

    1.       Download the hotfix from the KB above (if you don’t already have it.)
    2.       Run the EXE file to extract the SQLServer2012-KB2874879-x64.exe file to a file location (e.g. C:\Temp)
    3.       Open a command prompt and browse the location where the EXE file was extracted
    4.       Run the following command: SQLServer2012-KB2874879-x64.exe /extract: C:\Temp\SQLUpdate
    5.       Once the files are extracted, browse to the SQLUpdate folder (or whatever directory you specified) and browse to C:\temp\SQLUpdate\1033_enu_lp\x64\setup
    6.       You should find a sppowerpivot.msi file in that folder.
    7.       Move that file to your SharePoint server(s) and install that update.  
    8.       Once the sppowerpivot.msi file has been installed on all of your SharePoint servers, run the PowerPivot configuration tool.   The tool should report that an upgrade is necessary. 
    9.       Once the upgrade is done, test your file and you should have the refresh schedules after editing a file with the client.


    Great! Did you file a bug on Connect, or did the Microsoft team file a bug on this?

    Thanks!


    Ed Price, SQL Server Customer Program Manager (Blog, Small Basic, Wiki Ninjas, Wiki)

    Answer an interesting question? Create a wiki article about it!

    Wednesday, October 30, 2013 1:50 PM
  • Is there any more information on this?

    This KB is supposed to also fix the email issue when a PowerPivot refresh fails. I am not getting any emails even after installing the KB.

    Thank you

    Monday, January 13, 2014 8:17 PM
  • Is there any more information on this?

    This KB is supposed to also fix the email issue when a PowerPivot refresh fails. I am not getting any emails even after installing the KB.

    Thank you


    This KB? http://support.microsoft.com/kb/2874879/en-us

    Ed Price, Power BI & SQL Server Customer Program Manager (Blog, Small Basic, Wiki Ninjas, Wiki)

    Answer an interesting question? Create a wiki article about it!

    Friday, January 17, 2014 7:05 PM
  • Neither CU 6 nor CU 7 below fix the issue for me.

    http://support.microsoft.com/kb/2894115

    Thank you

    Friday, January 17, 2014 7:07 PM
  • Hi,

    Since my post in October we tried a few small things, but actually just disregarded the whole issue since this takes to much time to fix and is clearly not working properly. 

    We now created a job that refreshed the powerpivots locally and push them to sharepoint each day: it seems to be even faster

    Monday, January 20, 2014 9:29 AM
  • Would you mind sharing how you went about it? johnjack11 at Hotmail.com

    Thanks

    Monday, January 20, 2014 1:39 PM
  • It is very dirty: I created an Excel VBA script that loops through a folder, refreshes the powerpivots, sets some slicers and saves the files. Then it creates a connection to Sharepoint (via mapping of a network drive) and copy/pastes the files to it.

    it is very basic, and not really neat, but it does the trick

    Monday, January 20, 2014 1:46 PM
  • hi,

    i've the same issue ... i try to install the Hotfix and i get an error in the PowerPivot Config tool.

    ==================== Lösungsdateien und Assemblyinformationen aktualisieren ====================
    ==================== PowerPivot-Farmlösung aktualisieren ====================
    11/02/14 10:18:28:4757 Verbose: UpgradePowerPivotFarmSolution.NeedsExecute
    11/02/14 10:18:28:4757 Verbose: Running function IsFarmConfigured to check whether SharePoint is configured regardless of availability
    11/02/14 10:18:28:4757 Verbose: Farm is configured
    11/02/14 10:18:28:4767 Verbose: Running function IsFarmAvailable to check whether SharePoint farm is available
    11/02/14 10:18:28:4767 Verbose: Farm is configured and not null
    11/02/14 10:18:28:4767 Verbose: Farm is available and has 54 services
    11/02/14 10:18:28:4767 Verbose: Disk assembly version: 11.0.3381.0
    11/02/14 10:18:28:4767 Verbose: Entering function GetService(Guid)
    11/02/14 10:18:28:4787 Verbose: Service is installed.
    11/02/14 10:18:28:4787 Verbose: Extracting version from farm assembly
    11/02/14 10:18:28:4796 Verbose: Comparing two versions: ver1 is 11.0.3000.0. Ver2 is 11.0.3381.0
    11/02/14 10:18:28:4796 Verbose: Result of comparison: -1
    11/02/14 10:18:28:4796 Verbose: UpgradePowerPivotFarmSolution.NeedsExecute(True)
    11/02/14 10:18:28:4816 Verbose: UpgradePowerPivotFarmSolution.CanExecute
    11/02/14 10:18:28:4826 Verbose: solution file name is powerpivotfarmsolution.wsp
    11/02/14 10:18:28:4826 Verbose: Found solution location in regsitry setting
    11/02/14 10:18:28:4826 Verbose: The location is C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Resources\powerpivotfarmsolution.wsp
    11/02/14 10:18:28:4826 Verbose: The path for solution is C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Resources\powerpivotfarmsolution.wsp.
    11/02/14 10:18:28:4835 Verbose: UpgradePowerPivotFarmSolution.CanExecute(True)
    11/02/14 10:18:35:6957 Verbose: UpgradePowerPivotFarmSolution.Execute
    11/02/14 10:18:35:6977 Verbose: Update PowerPivot farm solution
    11/02/14 10:18:35:6977 Verbose: solution file name is powerpivotfarmsolution.wsp
    11/02/14 10:18:35:6977 Verbose: Found solution location in regsitry setting
    11/02/14 10:18:35:6977 Verbose: The location is C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Resources\powerpivotfarmsolution.wsp
    11/02/14 10:18:35:6977 Verbose: Upgrading SharePoint solution from C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Resources\powerpivotfarmsolution.wsp
    11/02/14 10:18:35:6977 Verbose: UpgradePowerPivotSolution 'C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Resources\powerpivotfarmsolution.wsp' 'powerpivotfarmsolution.wsp' $true
    11/02/14 10:18:35:7075 Verbose: Running PowerShell Script:
    11/02/14 10:20:58:8243 Verbose: Upgrading solution powerpivotfarmsolution.wsp in Farm
    11/02/14 10:20:58:8243 Verbose: Upgrade job for solution powerpivotfarmsolution.wsp is not created yet (time waiting=3 seconds)
    11/02/14 10:20:58:8243 Verbose: Upgrade job for solution powerpivotfarmsolution.wsp is not created yet (time waiting=6 seconds)
    11/02/14 10:20:58:8253 Verbose: Upgrade job for solution powerpivotfarmsolution.wsp is not created yet (time waiting=9 seconds)
    11/02/14 10:20:58:8253 Verbose: Upgrade job for solution powerpivotfarmsolution.wsp is not created yet (time waiting=12 seconds)
    11/02/14 10:20:58:8253 Verbose: Upgrade job for solution powerpivotfarmsolution.wsp is not created yet (time waiting=15 seconds)
    11/02/14 10:20:58:8253 Verbose: Upgrade job for solution powerpivotfarmsolution.wsp is not created yet (time waiting=18 seconds)
    11/02/14 10:20:58:8253 Verbose: Upgrade job for solution powerpivotfarmsolution.wsp in server COMPSP1 is not finished yet
    11/02/14 10:20:58:8253 Verbose: Upgrade timer job for solution: powerpivotfarmsolution.wsp in server COMPSP1 finished successfully at: 02/11/2014 09:19:33
    11/02/14 10:20:58:8253 Verbose: Unregistering old health rules
    11/02/14 10:20:58:8253 Verbose: Retrieving solution from the farm.
    11/02/14 10:20:58:8253 Verbose: SPFarm.Local is not null
    11/02/14 10:20:58:8321 Verbose: 3 solutions in the solution store
    11/02/14 10:20:58:8321 Verbose: Solution powerpivotfarm14solution.wsp is installed in the farm
    11/02/14 10:20:58:8321 Verbose: Solution powerpivotfarmsolution.wsp is installed in the farm
    11/02/14 10:20:58:8321 Verbose: Solution powerpivotwebapplicationsolution.wsp is installed in the farm
    11/02/14 10:20:58:8321 Verbose: PowerPivot Solution is installed in the farm.
    11/02/14 10:20:58:8321 Verbose: UpgradePowerPivotFarmSolution.Execute(Succeeded)
    ==================== Farmlösung für PowerPivot 14-Modus aktualisieren ====================
    11/02/14 10:18:28:4914 Verbose: UpgradePowerPivot14FarmSolutionName.NeedsExecute
    11/02/14 10:18:28:4914 Verbose: Running function IsFarmConfigured to check whether SharePoint is configured regardless of availability
    11/02/14 10:18:28:4914 Verbose: Farm is configured
    11/02/14 10:18:28:4914 Verbose: Running function IsFarmAvailable to check whether SharePoint farm is available
    11/02/14 10:18:28:4914 Verbose: Farm is configured and not null
    11/02/14 10:18:28:4943 Verbose: Farm is available and has 54 services
    11/02/14 10:18:28:4943 Verbose: Disk assembly version: 11.0.3381.0
    11/02/14 10:18:28:4943 Verbose: Entering function GetService(Guid)
    11/02/14 10:18:28:4982 Verbose: Service is installed.
    11/02/14 10:18:28:4982 Verbose: Extracting version from farm assembly
    11/02/14 10:18:28:4982 Verbose: Comparing two versions: ver1 is 11.0.3000.0. Ver2 is 11.0.3381.0
    11/02/14 10:18:28:4982 Verbose: Result of comparison: -1
    11/02/14 10:18:28:4992 Verbose: UpgradePowerPivot14FarmSolutionName.NeedsExecute(True)
    11/02/14 10:18:28:4992 Verbose: UpgradePowerPivot14FarmSolutionName.CanExecute
    11/02/14 10:18:28:4992 Verbose: solution file name is PowerPivotFarm14Solution.wsp
    11/02/14 10:18:28:4992 Verbose: Found solution location in regsitry setting
    11/02/14 10:18:28:4992 Verbose: The location is C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Resources\PowerPivotFarm14Solution.wsp
    11/02/14 10:18:28:4992 Verbose: The path for solution is C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Resources\PowerPivotFarm14Solution.wsp.
    11/02/14 10:18:28:4992 Verbose: UpgradePowerPivot14FarmSolutionName.CanExecute(True)
    11/02/14 10:20:58:8331 Verbose: UpgradePowerPivot14FarmSolutionName.Execute
    11/02/14 10:20:58:8350 Verbose: Update PowerPivot 14 farm solution
    11/02/14 10:20:58:8360 Verbose: solution file name is PowerPivotFarm14Solution.wsp
    11/02/14 10:20:58:8360 Verbose: Found solution location in regsitry setting
    11/02/14 10:20:58:8360 Verbose: The location is C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Resources\PowerPivotFarm14Solution.wsp
    11/02/14 10:20:58:8360 Verbose: Upgrading SharePoint solution from C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Resources\PowerPivotFarm14Solution.wsp
    11/02/14 10:20:58:8360 Verbose: UpgradePowerPivotSolution 'C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Resources\PowerPivotFarm14Solution.wsp' 'PowerPivotFarm14Solution.wsp' $false
    11/02/14 10:20:58:8360 Verbose: Running PowerShell Script:
    11/02/14 10:22:41:1768 Verbose: Upgrading solution PowerPivotFarm14Solution.wsp in Farm
    11/02/14 10:22:41:1768 Verbose: Upgrade job for solution PowerPivotFarm14Solution.wsp is not created yet (time waiting=3 seconds)
    11/02/14 10:22:41:1768 Verbose: Upgrade job for solution PowerPivotFarm14Solution.wsp is not created yet (time waiting=6 seconds)
    11/02/14 10:22:41:1768 Verbose: Upgrade job for solution PowerPivotFarm14Solution.wsp is not created yet (time waiting=9 seconds)
    11/02/14 10:22:41:1768 Verbose: Upgrade job for solution PowerPivotFarm14Solution.wsp in server COMPSP1 is not finished yet
    11/02/14 10:22:41:1768 Verbose: Upgrade timer job for solution: PowerPivotFarm14Solution.wsp in server COMPSP1 finished successfully at: 02/11/2014 09:21:19
    11/02/14 10:22:41:1778 Verbose: Retrieving solution from the farm.
    11/02/14 10:22:41:1778 Verbose: SPFarm.Local is not null
    11/02/14 10:22:41:1788 Verbose: 3 solutions in the solution store
    11/02/14 10:22:41:1788 Verbose: Solution powerpivotfarm14solution.wsp is installed in the farm
    11/02/14 10:22:41:1788 Verbose: Solution powerpivotfarmsolution.wsp is installed in the farm
    11/02/14 10:22:41:1788 Verbose: Solution powerpivotwebapplicationsolution.wsp is installed in the farm
    11/02/14 10:22:41:1798 Verbose: PowerPivot Solution is installed in the farm.
    11/02/14 10:22:41:1798 Verbose: UpgradePowerPivot14FarmSolutionName.Execute(Succeeded)
    ==================== PowerPivot-Webanwendungslösung aktualisieren ====================
    11/02/14 10:18:28:5001 Verbose: UpgradePowerPivotWebAppSolution.NeedsExecute
    11/02/14 10:18:28:5001 Verbose: Running function IsFarmConfigured to check whether SharePoint is configured regardless of availability
    11/02/14 10:18:28:5001 Verbose: Farm is configured
    11/02/14 10:18:28:5001 Verbose: Running function IsFarmAvailable to check whether SharePoint farm is available
    11/02/14 10:18:28:5001 Verbose: Farm is configured and not null
    11/02/14 10:18:28:5041 Verbose: Farm is available and has 54 services
    11/02/14 10:18:28:5041 Verbose: Disk assembly version: 11.0.3381.0
    11/02/14 10:18:28:5041 Verbose: Entering function GetService(Guid)
    11/02/14 10:18:28:5080 Verbose: Service is installed.
    11/02/14 10:18:28:5080 Verbose: Extracting version from farm assembly
    11/02/14 10:18:28:5080 Verbose: Comparing two versions: ver1 is 11.0.3000.0. Ver2 is 11.0.3381.0
    11/02/14 10:18:28:5080 Verbose: Result of comparison: -1
    11/02/14 10:18:28:5080 Verbose: UpgradePowerPivotWebAppSolution.NeedsExecute(True)
    11/02/14 10:18:28:5080 Verbose: UpgradePowerPivotWebAppSolution.CanExecute
    11/02/14 10:18:28:5080 Verbose: solution file name is powerpivotwebapplicationsolution.wsp
    11/02/14 10:18:28:5080 Verbose: Found solution location in regsitry setting
    11/02/14 10:18:28:5080 Verbose: The location is C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Resources\powerpivotwebapplicationsolution.wsp
    11/02/14 10:18:28:5080 Verbose: The path for solution is C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Resources\powerpivotwebapplicationsolution.wsp.
    11/02/14 10:18:28:5080 Verbose: UpgradePowerPivotWebAppSolution.CanExecute(True)
    11/02/14 10:22:41:1798 Verbose: UpgradePowerPivotWebAppSolution.Execute
    11/02/14 10:22:41:1827 Verbose: Update PowerPivot web app solution
    11/02/14 10:22:41:1827 Verbose: solution file name is powerpivotwebapplicationsolution.wsp
    11/02/14 10:22:41:1827 Verbose: Found solution location in regsitry setting
    11/02/14 10:22:41:1847 Verbose: The location is C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Resources\powerpivotwebapplicationsolution.wsp
    11/02/14 10:22:41:1847 Verbose: Upgrading SharePoint solution from C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Resources\powerpivotwebapplicationsolution.wsp
    11/02/14 10:22:41:1847 Verbose: UpgradePowerPivotSolution 'C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Resources\powerpivotwebapplicationsolution.wsp' 'powerpivotwebapplicationsolution.wsp' $false
    11/02/14 10:22:41:1847 Verbose: Running PowerShell Script:
    11/02/14 10:24:22:6886 Verbose: Upgrading solution powerpivotwebapplicationsolution.wsp in Farm
    11/02/14 10:24:22:6895 Verbose: Upgrade job for solution powerpivotwebapplicationsolution.wsp is not created yet (time waiting=3 seconds)
    11/02/14 10:24:22:6895 Verbose: Upgrade job for solution powerpivotwebapplicationsolution.wsp is not created yet (time waiting=6 seconds)
    11/02/14 10:24:22:6895 Verbose: Upgrade job for solution powerpivotwebapplicationsolution.wsp is not created yet (time waiting=9 seconds)
    11/02/14 10:24:22:6895 Verbose: Upgrade job for solution powerpivotwebapplicationsolution.wsp in server COMPSP1 is not finished yet
    11/02/14 10:24:22:6895 Verbose: Upgrade timer job for solution: powerpivotwebapplicationsolution.wsp in server COMPSP1 finished successfully at: 02/11/2014 09:23:02
    11/02/14 10:24:22:6895 Verbose: Retrieving solution from the farm.
    11/02/14 10:24:22:6895 Verbose: SPFarm.Local is not null
    11/02/14 10:24:22:6905 Verbose: 3 solutions in the solution store
    11/02/14 10:24:22:6905 Verbose: Solution powerpivotfarm14solution.wsp is installed in the farm
    11/02/14 10:24:22:6905 Verbose: Solution powerpivotfarmsolution.wsp is installed in the farm
    11/02/14 10:24:22:6905 Verbose: Solution powerpivotwebapplicationsolution.wsp is installed in the farm
    11/02/14 10:24:22:6905 Verbose: PowerPivot Solution is installed in the farm.
    11/02/14 10:24:22:6905 Verbose: UpgradePowerPivotWebAppSolution.Execute(Succeeded)
    ==================== PowerPivot-Assemblyinformationen aktualisieren ====================
    11/02/14 10:18:28:5089 Verbose: UpdatePowerPivotAssemblyInformation.NeedsExecute
    11/02/14 10:18:28:5109 Verbose: Running function IsFarmConfigured to check whether SharePoint is configured regardless of availability
    11/02/14 10:18:28:5109 Verbose: Farm is configured
    11/02/14 10:18:28:5109 Verbose: Running function IsFarmAvailable to check whether SharePoint farm is available
    11/02/14 10:18:28:5109 Verbose: Farm is configured and not null
    11/02/14 10:18:28:5138 Verbose: Farm is available and has 54 services
    11/02/14 10:18:28:5148 Verbose: Disk assembly version: 11.0.3381.0
    11/02/14 10:18:28:5148 Verbose: Entering function GetService(Guid)
    11/02/14 10:18:28:5187 Verbose: Service is installed.
    11/02/14 10:18:28:5187 Verbose: Extracting version from farm assembly
    11/02/14 10:18:28:5187 Verbose: Comparing two versions: ver1 is 11.0.3000.0. Ver2 is 11.0.3381.0
    11/02/14 10:18:28:5187 Verbose: Result of comparison: -1
    11/02/14 10:18:28:5187 Verbose: UpdatePowerPivotAssemblyInformation.NeedsExecute(True)
    11/02/14 10:18:28:5187 Verbose: UpdatePowerPivotAssemblyInformation.CanExecute
    11/02/14 10:18:28:5187 Verbose: UpdatePowerPivotAssemblyInformation.CanExecute(True)
    11/02/14 10:24:22:6915 Verbose: UpdatePowerPivotAssemblyInformation.Execute
    11/02/14 10:24:22:6925 Verbose: Update PowerPivot assembly information
    11/02/14 10:24:22:6925 Verbose: UpdatePowerPivotAssemblyInformation
    11/02/14 10:24:22:6934 Verbose: Running PowerShell Script:
    11/02/14 10:25:25:0865 Verbose: SharePoint Timer Service wird beendet.
    11/02/14 10:25:25:0865 Verbose: SharePoint Timer Service wurde erfolgreich beendet.
    11/02/14 10:25:25:0865 Verbose: 
    11/02/14 10:25:25:0865 Verbose: PowerPivot system service instance was successfully updated
    11/02/14 10:25:25:0865 Verbose: Stopping services...
    11/02/14 10:25:25:0865 Verbose: 
    11/02/14 10:25:25:0865 Verbose: Es wird versucht, den Dienst zu beenden...
    11/02/14 10:25:25:0865 Verbose: 
    11/02/14 10:25:25:0865 Verbose: Internetdienste wurden erfolgreich beendet.
    11/02/14 10:25:25:0865 Verbose: 
    11/02/14 10:25:25:0865 Verbose: SharePoint Administration wird beendet.
    11/02/14 10:25:25:0865 Verbose: SharePoint Administration wurde erfolgreich beendet.
    11/02/14 10:25:25:0865 Verbose: 
    11/02/14 10:25:25:0865 Verbose: SharePoint Tracing Service wird beendet.
    11/02/14 10:25:25:0865 Verbose: SharePoint Tracing Service wurde erfolgreich beendet.
    11/02/14 10:25:25:0865 Verbose: 
    11/02/14 10:25:25:0865 Verbose: Starting services...
    11/02/14 10:25:25:0865 Verbose: SharePoint Tracing Service wird gestartet.
    11/02/14 10:25:25:0865 Verbose: SharePoint Tracing Service wurde erfolgreich gestartet.
    11/02/14 10:25:25:0865 Verbose: 
    11/02/14 10:25:25:0865 Verbose: SharePoint Administration wird gestartet.
    11/02/14 10:25:25:0865 Verbose: SharePoint Administration wurde erfolgreich gestartet.
    11/02/14 10:25:25:0865 Verbose: 
    11/02/14 10:25:25:0865 Verbose: 
    11/02/14 10:25:25:0865 Verbose: Es wird versucht, den Dienst zu starten...
    11/02/14 10:25:25:0865 Verbose: 
    11/02/14 10:25:25:0865 Verbose: Internetdienste wurden erfolgreich gestartet.
    11/02/14 10:25:25:0865 Verbose: 
    11/02/14 10:25:25:0865 Verbose: 
    11/02/14 10:25:25:0865 Verbose: SharePoint Timer Service wurde erfolgreich gestartet.
    11/02/14 10:25:25:0865 Verbose: 
    11/02/14 10:25:25:0865 Verbose: UpdatePowerPivotAssemblyInformation.Execute(Succeeded)
    ==================== PowerPivot-Funktionen und -Objekte aktualisieren ====================
    ==================== Bereitstellung von Instanzen des PowerPivot-Systemdiensts aufheben ====================
    11/02/14 10:18:28:5197 Verbose: UnprovisionPowerPivotSystemServiceInstances.NeedsExecute
    11/02/14 10:18:28:5197 Verbose: Running function IsFarmConfigured to check whether SharePoint is configured regardless of availability
    11/02/14 10:18:28:5207 Verbose: Farm is configured
    11/02/14 10:18:28:5207 Verbose: Running function IsFarmAvailable to check whether SharePoint farm is available
    11/02/14 10:18:28:5207 Verbose: Farm is configured and not null
    11/02/14 10:18:28:5236 Verbose: Farm is available and has 54 services
    11/02/14 10:18:28:5236 Verbose: Disk assembly version: 11.0.3381.0
    11/02/14 10:18:28:5236 Verbose: Entering function GetService(Guid)
    11/02/14 10:18:28:5275 Verbose: Service is installed.
    11/02/14 10:18:28:5275 Verbose: Extracting version from farm assembly
    11/02/14 10:18:28:5275 Verbose: Comparing two versions: ver1 is 11.0.3000.0. Ver2 is 11.0.3381.0
    11/02/14 10:18:28:5275 Verbose: Result of comparison: -1
    11/02/14 10:18:28:5275 Verbose: Entering function GetService(Guid)
    11/02/14 10:18:28:5314 Verbose: Service is installed.
    11/02/14 10:18:28:5314 Verbose: Service is installed. Verify if there is a local instance.
    11/02/14 10:18:28:5343 Verbose: Service instance found in local server.
    11/02/14 10:18:28:5343 Verbose: UnprovisionPowerPivotSystemServiceInstances.NeedsExecute(True)
    11/02/14 10:18:28:5343 Verbose: UnprovisionPowerPivotSystemServiceInstances.CanExecute
    11/02/14 10:18:28:5343 Verbose: UnprovisionPowerPivotSystemServiceInstances.CanExecute(True)
    11/02/14 10:25:25:0874 Verbose: UnprovisionPowerPivotSystemServiceInstances.Execute
    11/02/14 10:25:25:0894 Verbose: Uprovision PowerPivot local System Service instance
    11/02/14 10:25:25:0894 Verbose: UnprovisionLocalPowerPivotServiceInstances "35F084BE-5ED5-4735-ADAA-6DB08C03EF26"
    11/02/14 10:25:25:0894 Verbose: Application base: C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Bin\
    11/02/14 10:25:25:0904 Verbose: Execution Assembly for new AppDomain: Microsoft.AnalysisServices.SPAddin.Configuration.Proxy, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91:
    11/02/14 10:25:43:0725 Verbose: Return value: False
    11/02/14 10:25:43:0735 Verbose: Success
    11/02/14 10:25:43:0764 Verbose: Running PowerShell Script from app domain:ConfigurationProxy
    11/02/14 10:25:43:0764 Verbose: 
    11/02/14 10:25:43:0764 Verbose: GAC    Version        Location                                                  
    11/02/14 10:25:43:0764 Verbose: ---    -------        --------                                                  
    11/02/14 10:25:43:0764 Verbose: True   v4.0.30319     C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Sh...
    11/02/14 10:25:43:0764 Verbose: Unprovisioning PowerPivot service instance 
    11/02/14 10:25:43:0764 Verbose: 
    11/02/14 10:25:43:0764 Verbose: 
    11/02/14 10:25:43:0764 Verbose: Last entry : 
    11/02/14 10:25:43:2248 Verbose: UnprovisionPowerPivotSystemServiceInstances.Execute(Succeeded)
    ==================== PowerPivot-Funktionen auf Farmebene aktualisieren ====================
    11/02/14 10:18:28:5353 Verbose: UpgradePowerPivotFarmFeatureInstances.NeedsExecute
    11/02/14 10:18:28:5363 Verbose: Running function IsFarmConfigured to check whether SharePoint is configured regardless of availability
    11/02/14 10:18:28:5363 Verbose: Farm is configured
    11/02/14 10:18:28:5363 Verbose: Running function IsFarmAvailable to check whether SharePoint farm is available
    11/02/14 10:18:28:5363 Verbose: Farm is configured and not null
    11/02/14 10:18:28:5363 Verbose: Farm is available and has 54 services
    11/02/14 10:18:28:5363 Verbose: Disk assembly version: 11.0.3381.0
    11/02/14 10:18:28:5363 Verbose: Entering function GetService(Guid)
    11/02/14 10:18:28:5392 Verbose: Service is installed.
    11/02/14 10:18:28:5402 Verbose: Extracting version from farm assembly
    11/02/14 10:18:28:5402 Verbose: Comparing two versions: ver1 is 11.0.3000.0. Ver2 is 11.0.3381.0
    11/02/14 10:18:28:5402 Verbose: Result of comparison: -1
    11/02/14 10:18:28:5402 Verbose: UpgradePowerPivotFarmFeatureInstances.NeedsExecute(True)
    11/02/14 10:18:28:5402 Verbose: UpgradePowerPivotFarmFeatureInstances.CanExecute
    11/02/14 10:18:28:5402 Verbose: UpgradePowerPivotFarmFeatureInstances.CanExecute(True)
    11/02/14 10:25:43:2248 Verbose: UpgradePowerPivotFarmFeatureInstances.Execute
    11/02/14 10:25:43:2268 Verbose: Upgrade PowerPivot Farm feature instances
    11/02/14 10:25:43:2268 Verbose: UpgradePowerPivotFarmFeatureInstances
    11/02/14 10:25:43:2268 Verbose: Application base: C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Bin\
    11/02/14 10:25:43:2288 Verbose: Execution Assembly for new AppDomain: Microsoft.AnalysisServices.SPAddin.Configuration.Proxy, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91:
    11/02/14 10:25:58:6083 Verbose: Return value: False
    11/02/14 10:25:58:6083 Verbose: Upgrade PowerPivot Farm feature instances
    11/02/14 10:25:58:6112 Verbose: Running PowerShell Script from app domain:ConfigurationProxy
    11/02/14 10:25:58:6112 Verbose: Calling upgrade on PowerPivot feature
    11/02/14 10:25:58:6112 Verbose: Calling upgrade on PowerPivot feature
    11/02/14 10:25:58:6112 Verbose: Last entry : Calling upgrade on PowerPivot feature
    11/02/14 10:25:58:6776 Verbose: UpgradePowerPivotFarmFeatureInstances.Execute(Succeeded)
    ==================== PowerPivot-Funktionen in der Zentraladministration aktualisieren ====================
    11/02/14 10:18:28:5412 Verbose: UpgradePowerPivotAdminFeatureInstances.NeedsExecute
    11/02/14 10:18:28:5421 Verbose: Current action state: None
    11/02/14 10:18:28:5421 Verbose: Running function IsFarmConfigured to check whether SharePoint is configured regardless of availability
    11/02/14 10:18:28:5421 Verbose: Farm is configured
    11/02/14 10:18:28:5421 Verbose: Running function IsFarmAvailable to check whether SharePoint farm is available
    11/02/14 10:18:28:5431 Verbose: Farm is configured and not null
    11/02/14 10:18:28:5451 Verbose: Farm is available and has 54 services
    11/02/14 10:18:28:5451 Verbose: Disk assembly version: 11.0.3381.0
    11/02/14 10:18:28:5451 Verbose: Entering function GetService(Guid)
    11/02/14 10:18:28:5480 Verbose: Service is installed.
    11/02/14 10:18:28:5490 Verbose: Extracting version from farm assembly
    11/02/14 10:18:28:5490 Verbose: Comparing two versions: ver1 is 11.0.3000.0. Ver2 is 11.0.3381.0
    11/02/14 10:18:28:5490 Verbose: Result of comparison: -1
    11/02/14 10:18:28:5490 Verbose: UpgradePowerPivotAdminFeatureInstances.NeedsExecute(True)
    11/02/14 10:18:28:5490 Verbose: UpgradePowerPivotAdminFeatureInstances.CanExecute
    11/02/14 10:18:28:5490 Verbose: UpgradePowerPivotAdminFeatureInstances.CanExecute(True)
    11/02/14 10:25:58:6776 Verbose: UpgradePowerPivotAdminFeatureInstances.Execute
    11/02/14 10:25:58:6795 Verbose: Upgrade PowerPivot Admin feature instances
    11/02/14 10:25:58:6795 Verbose: UpgradePowerPivotAdminFeatureInstances
    11/02/14 10:25:58:6795 Verbose: Application base: C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Bin\
    11/02/14 10:25:58:6815 Verbose: Execution Assembly for new AppDomain: Microsoft.AnalysisServices.SPAddin.Configuration.Proxy, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91:
    11/02/14 10:26:39:8188 Verbose: Return value: False
    11/02/14 10:26:39:8198 Verbose: Upgrade PowerPivot Admin feature instances
    11/02/14 10:26:39:8227 Verbose: Running PowerShell Script from app domain:ConfigurationProxy
    11/02/14 10:26:39:8227 Verbose: Calling upgrade on PowerPivotAdmin feature
    11/02/14 10:26:39:8227 Verbose: Last entry : Calling upgrade on PowerPivotAdmin feature
    11/02/14 10:26:39:8872 Verbose: UpgradePowerPivotAdminFeatureInstances.Execute(Succeeded)
    ==================== PowerPivot-Funktionen auf Websiteebene aktualisieren ====================
    11/02/14 10:18:28:5500 Verbose: UpgradePowerPivotSiteFeatureInstances.NeedsExecute
    11/02/14 10:18:28:5509 Verbose: Running function IsFarmConfigured to check whether SharePoint is configured regardless of availability
    11/02/14 10:18:28:5509 Verbose: Farm is configured
    11/02/14 10:18:28:5509 Verbose: Running function IsFarmAvailable to check whether SharePoint farm is available
    11/02/14 10:18:28:5509 Verbose: Farm is configured and not null
    11/02/14 10:18:28:5529 Verbose: Farm is available and has 54 services
    11/02/14 10:18:28:5529 Verbose: Disk assembly version: 11.0.3381.0
    11/02/14 10:18:28:5529 Verbose: Entering function GetService(Guid)
    11/02/14 10:18:28:5568 Verbose: Service is installed.
    11/02/14 10:18:28:5568 Verbose: Extracting version from farm assembly
    11/02/14 10:18:28:5568 Verbose: Farm assembly version: 11.0.3000.0
    11/02/14 10:18:28:5568 Verbose: Comparing two versions: ver1 is 11.0.3000.0. Ver2 is 11.0.3381.0
    11/02/14 10:18:28:5568 Verbose: Result of comparison: -1
    11/02/14 10:18:28:5568 Verbose: UpgradePowerPivotSiteFeatureInstances.NeedsExecute(True)
    11/02/14 10:18:28:5568 Verbose: UpgradePowerPivotSiteFeatureInstances.CanExecute
    11/02/14 10:18:28:5568 Verbose: UpgradePowerPivotSiteFeatureInstances.CanExecute(True)
    11/02/14 10:26:39:8872 Verbose: UpgradePowerPivotSiteFeatureInstances.Execute
    11/02/14 10:26:39:8921 Verbose: Upgrade PowerPivot Site feature instances
    11/02/14 10:26:39:8989 Verbose: UpgradePowerPivotSiteFeatureInstances
    11/02/14 10:26:39:8999 Verbose: Application base: C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Bin\
    11/02/14 10:26:39:9009 Verbose: Execution Assembly for new AppDomain: Microsoft.AnalysisServices.SPAddin.Configuration.Proxy, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91:
    11/02/14 10:27:05:6958 Verbose: Return value: False
    11/02/14 10:27:05:6958 Verbose: Upgrade PowerPivot site feature instances
    11/02/14 10:27:05:6987 Verbose: Running PowerShell Script from app domain:ConfigurationProxy
    11/02/14 10:27:05:6987 Verbose: Calling upgrade on PowerPivotSite feature
    11/02/14 10:27:05:6987 Verbose: Calling upgrade on PowerPivotSite feature
    11/02/14 10:27:05:6987 Verbose: Last entry : Calling upgrade on PowerPivotSite feature
    11/02/14 10:27:05:7583 Verbose: UpgradePowerPivotSiteFeatureInstances.Execute(Succeeded)
    ==================== PowerPivot-Systemdienst aktualisieren ====================
    11/02/14 10:18:28:5578 Verbose: UpgradePowerPivotSystemService.NeedsExecute
    11/02/14 10:18:28:5578 Verbose: Running function IsFarmConfigured to check whether SharePoint is configured regardless of availability
    11/02/14 10:18:28:5578 Verbose: Farm is configured
    11/02/14 10:18:28:5578 Verbose: Running function IsFarmAvailable to check whether SharePoint farm is available
    11/02/14 10:18:28:5578 Verbose: Farm is configured and not null
    11/02/14 10:18:28:5617 Verbose: Farm is available and has 54 services
    11/02/14 10:18:28:5617 Verbose: Disk assembly version: 11.0.3381.0
    11/02/14 10:18:28:5617 Verbose: Entering function GetService(Guid)
    11/02/14 10:18:28:5656 Verbose: Service is installed.
    11/02/14 10:18:28:5656 Verbose: Extracting version from farm assembly
    11/02/14 10:18:28:5656 Verbose: Farm assembly version: 11.0.3000.0
    11/02/14 10:18:28:5656 Verbose: Comparing two versions: ver1 is 11.0.3000.0. Ver2 is 11.0.3381.0
    11/02/14 10:18:28:5656 Verbose: Result of comparison: -1
    11/02/14 10:18:28:5656 Verbose: UpgradePowerPivotSystemService.NeedsExecute(True)
    11/02/14 10:18:28:5656 Verbose: UpgradePowerPivotSystemService.CanExecute
    11/02/14 10:18:28:5656 Verbose: UpgradePowerPivotSystemService.CanExecute(True)
    11/02/14 10:27:05:7583 Verbose: UpgradePowerPivotSystemService.Execute
    11/02/14 10:27:05:7593 Verbose: Upgrade PowerPivot System Service and local instance
    11/02/14 10:27:05:7602 Verbose: Running function IsFarmConfigured to check whether SharePoint is configured regardless of availability
    11/02/14 10:27:05:7602 Verbose: Farm is configured
    11/02/14 10:27:05:7602 Verbose: Running function IsFarmAvailable to check whether SharePoint farm is available
    11/02/14 10:27:05:7602 Verbose: Farm is configured and not null
    11/02/14 10:27:05:7622 Verbose: Farm is available and has 54 services
    11/02/14 10:27:05:7632 Verbose: Disk assembly version: 11.0.3381.0
    11/02/14 10:27:05:7632 Verbose: Entering function GetService(Guid)
    11/02/14 10:27:05:7661 Verbose: Service is installed.
    11/02/14 10:27:05:7661 Verbose: Extracting version from farm assembly
    11/02/14 10:27:05:7661 Verbose: Farm assembly version: 11.0.3000.0
    11/02/14 10:27:05:7661 Verbose: Comparing two versions: ver1 is 11.0.3000.0. Ver2 is 11.0.3381.0
    11/02/14 10:27:05:7661 Verbose: Result of comparison: -1
    11/02/14 10:27:05:7661 Verbose: UpgradeSystemServiceInstance $False
    11/02/14 10:27:05:7661 Verbose: Application base: C:\Program Files\Microsoft SQL Server\110\Tools\PowerPivotTools\SPAddinConfiguration\Bin\
    11/02/14 10:27:05:7681 Verbose: Execution Assembly for new AppDomain: Microsoft.AnalysisServices.SPAddin.Configuration.Proxy, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91:
    11/02/14 10:28:26:8132 Verbose: UpgradePowerPivotSystemService.Execute(Failed)
    Fehler beim Ausführen der Aktion: PowerPivot-Systemdienst aktualisieren
    11/02/14 10:28:26:7380 High: Upgrade PowerPivot System Service and service instances failed
    11/02/14 10:28:26:7380 High: Fehler während der Ausführung des PowerShell-Skripts.
    11/02/14 10:28:26:7419 High: Pipeline Error when running PowerShell script
    11/02/14 10:28:26:7419 High: Update-PowerPivotSystemService : Das Upgrade wurde mit Fehlern abgeschlossen. 
    
    11/02/14 10:28:26:7419 High: Pipeline Error when running PowerShell script
    11/02/14 10:28:26:7419 High: Überprüfen Sie die Upgradeprotokolldatei unter 'C:\Program Files\Common 
    
    11/02/14 10:28:26:7419 High: Pipeline Error when running PowerShell script
    11/02/14 10:28:26:7419 High: Files\Microsoft Shared\Web Server 
    
    11/02/14 10:28:26:7419 High: Pipeline Error when running PowerShell script
    11/02/14 10:28:26:7419 High: Extensions\15\LOGS\Upgrade-20140211-102720-838.log'. Die Anzahl der Fehler und 
    
    11/02/14 10:28:26:7419 High: Pipeline Error when running PowerShell script
    11/02/14 10:28:26:7419 High: Warnungen ist am Ende der Updateprotokolldatei aufgeführt.
    
    11/02/14 10:28:26:7419 High: Pipeline Error when running PowerShell script
    11/02/14 10:28:26:7419 High: In Zeile:1 Zeichen:77
    
    11/02/14 10:28:26:7419 High: Pipeline Error when running PowerShell script
    11/02/14 10:28:26:7419 High: + Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction:SilentlyContinue; 
    
    11/02/14 10:28:26:7419 High: Pipeline Error when running PowerShell script
    11/02/14 10:28:26:7419 High: Upda ...
    
    11/02/14 10:28:26:7419 High: Pipeline Error when running PowerShell script
    11/02/14 10:28:26:7419 High: +                                                                             
    
    11/02/14 10:28:26:7419 High: Pipeline Error when running PowerShell script
    11/02/14 10:28:26:7419 High: ~~~~
    
    11/02/14 10:28:26:7419 High: Pipeline Error when running PowerShell script
    11/02/14 10:28:26:7419 High:     + CategoryInfo          : InvalidResult: (:) [Update-PowerPivotSystemServi 
    
    11/02/14 10:28:26:7428 High: Pipeline Error when running PowerShell script
    11/02/14 10:28:26:7428 High:    ce], PSInvalidOperationException
    
    11/02/14 10:28:26:7428 High: Pipeline Error when running PowerShell script
    11/02/14 10:28:26:7428 High:     + FullyQualifiedErrorId : Microsoft.AnalysisServices.SPAddin.PowerShell.Up 
    
    11/02/14 10:28:26:7428 High: Pipeline Error when running PowerShell script
    11/02/14 10:28:26:7428 High:    gradePowerPivotMidTierService
    
    11/02/14 10:28:26:7428 High: Pipeline Error when running PowerShell script
    11/02/14 10:28:26:7428 High:  
    
    11/02/14 10:28:26:7428 High: Running PS Script failed. Reason:Fehler während der Ausführung des PowerShell-Skripts.
    11/02/14 10:28:26:8132 High: Ausnahme beim Ausführen der Aktion 'UpgradePowerPivotSystemService': Fehler beim Ausführen des Skripts aus einer anderen Anwendungsdomäne.
    

    Log:

    Timestamp              	Process                                 	TID   	Area                          	Category                      	EventID	Level     	Message 	Correlation
    02/11/2014 10:27:20.83	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxlm	INFO	======================================================================================	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.83	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxln	INFO	Upgrade session starts	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.83	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxlo	INFO	Command line: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -noninteractive -inputFormat text -outputFormat text -encodedCommand QQBkAGQALQBQAFMAUwBuAGEAcABpAG4AIABNAGkAYwByAG8AcwBvAGYAdAAuAFMAaABhAHIAZQBQAG8AaQBuAHQALgBQAG8AdwBlAHIAUwBoAGUAbABsACAALQBFAHIAcgBvAHIAQQBjAHQAaQBvAG4AOgBTAGkAbABlAG4AdABsAHkAQwBvAG4AdABpAG4AdQBlADsAIABVAHAAZABhAHQAZQAtAFAAbwB3AGUAcgBQAGkAdgBvAHQAUwB5AHMAdABlAG0AUwBlAHIAdgBpAGMAZQAgAC0AQwBvAG4AZgBpAHIAbQA6ACQAZgBhAGwAcwBlACAALQBWAGUAcgBiAG8AcwBlADoAJAB0AHIAdQBlAA== 	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.84	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxlp	DEBUG	User: COMPRI\SP_farm	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.84	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxlq	DEBUG	Current Machine: COMPSP1	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.84	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxlr	INFO	Mode: InPlace	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.84	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxls	INFO	Current SharePoint Build: 15.0.4551.1001	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.84	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxlx	INFO	Upgrade Object: MidTierServiceInstance	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.84	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxly	INFO	Upgrade Operation Flags: Recursive	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.84	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxl0	INFO	======================================================================================	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.91	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPManager	ajyi1	INFO	Preparing to upgrade PersistedUpgradableObject: MidTierServiceInstance.  This object's current status is Disabled. Setting it to Upgrading	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.92	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	aloop	DEBUG	Entering upgrade for [MidTierServiceInstance]	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.92	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxnf	ERROR	Cannot upgrade [MidTierServiceInstance].	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.93	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxng	DEBUG	Skip upgrading [MidTierServiceInstance].	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.93	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	alooy	DEBUG	Exiting upgrade for [MidTierServiceInstance].  Elapsed Time=[00:00:00]	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.93	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPManager	ajyi3	INFO	Resetting the status of PersistedUpgradableObject: MidTierServiceInstance to Disabled.	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.95	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPHierarchyManager	ajyw6	DEBUG	[SPTree Value=MidTierServiceInstance] added to dependency cache by lookup	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.96	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPManager	ajyi6	INFO	Finished upgrading MidTierServiceInstance.	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.96	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxl4	INFO	======================================================================================	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.96	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxl5	INFO	Upgrade session failed. 1 errors and 0 warnings encountered.	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.96	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxl6	INFO	Suchen Sie nach möglichen Ursachen für Upgradeprobleme, indem Sie die Zeichenfolgen [ERROR] und [WARNING] in der Upgradeprotokolldatei durchsuchen. Weitere Informationen zur Wiederherstellung nach Upgradefehlern finden Sie unter "http://go.microsoft.com/fwlink/?LinkId=259653".	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.96	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxl7	INFO	======================================================================================	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.96	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxl8	DEBUG	Setting upgrade session object to offline	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.96	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxn2	DEBUG	UPGRADE PERCENTAGE: 100.00000000% done, Total Elapsed Time 00:00:00.1230516.	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.99	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxl9	DEBUG	Releasing upgrade lock	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.99	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxma	DEBUG	Stop the session maintenance thread.	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    

    Error Log:

    Timestamp              	Process                                 	TID   	Area                          	Category                      	EventID	Level     	Message 	Correlation
    02/11/2014 10:27:20.92	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxnf	INFO	No context object	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    02/11/2014 10:27:20.92	powershell (0x2E44)	0x092C	SharePoint Foundation Upgrade	SPUpgradeSession	ajxnf	ERROR	Cannot upgrade [MidTierServiceInstance].	17f8a300-95e1-44a7-aad5-ecedfc2eef9f
    

    What is worng ? Can anybody help me ?

    Tuesday, February 11, 2014 9:37 AM