Hello,

I created new project based on the template out-of-the-box proposal, but after that i can't see the following diagram ..

Hello everyone:

I´m getting an error in Approval Center - Project Server 2010

For an especific user I get this error:

I have not found any solution in your threads :

2 approvers have the message in Approval center : An unhandled exception occurred in Microsoft.Office.Project.Server.BusinessLayer.Statusing.StatusingReadStatusApprovalsForProjectForGridJson.

If I try in delegate mode for them I have the same error

But if I change the status manager (me instead of them) I can approve all their pending approvals

The message is still the same for them even if they have nothing to approve

I have no orphan project

Waht can I do ??

I am afraid that the others users could have the same message

Hi,

When I go to PWA -> Approval Center -> History -> Status Updates I get the following error instead of the normal grid:

An unhandled exception occurred in Microsoft.Office.Project.Server.BusinessLayer.Statusing.StatusingReadStatusApprovalHistoryForGridJson.

It appears to be related to just my account though.  Using the same browser, I can use view someone else's status history without any problem through a delegate session.  From a different computer, I used the system account to go into my personal account through delegation and still encounter the same error on the page. 

Any idea how I get this corrected?  Thanks!

-Tyler 

Hi Recently we have applied Load balancing to our production and development server, but we are getting error while trying to save and submit timesheet for resource . The jobs are failing and blocking the Queue 

This is the error message 

This is due to Load balancing , as when we undo the load balancing there are no issue with timesheet updates .
anyone has any idea ????
Regards

Our customer have a Project Server 2013 on-premise solution and they would like their super users to be able to build the OLAP cubes on request.<o:p></o:p>

In 2010 this was done within Server Settings, but in 2013 it is done in Central Administration.<o:p></o:p>

However, if I look in the Global Permissions in the Security Groups there is a permission called "Manage Cube Building Service". In 2010 this permission enabled users to build the cube from Server Settings. But what does it do in 2013?<o:p></o:p>

If I enable the permission, I can manually browse to the 2010 version of Manage OLAP Cubes (http://projectserver/PWA/_layouts/15/pwa/CubeAdmin/CubeAnalysisAdmin.aspx) but everything is grayed out.<o:p></o:p>

Did the project team forget to remove the permission or does it have a function?<o:p></o:p>

Can I somehow get the "http://projectserver/PWA/_layouts/15/pwa/CubeAdmin/CubeAnalysisAdmin.aspx" page to work?<o:p></o:p>

We have many customers who want to build the OLAP cubes on request, is there some other way to do this?<o:p></o:p>

Hi:

I group some custom fields at the Project Center (portfolio/programs/subprograms), but some on this are empty (see the image). I want to eliminate this fields (subprograms; subprogramas in the image), but next level (the projects) must continue to be visible.

Is it possible?

Thanks 

Pablo

We have plenty of projects and sometimes it is impossible to do a copy paste of tasks, I select a task => right clic copy

But when I want to copy the task => paste is disabled in grey in the right clic menu

CTRL V does not work too

It is not linked to a specific project , some users has the problem , me too in new blank projects ie  

What can I do ?

We are looking to  use project server 2013 for resource and project portfolio management.  We are an IT department of approximately 600 growing to 1,000 within the next several years.

We would like to us PS2013 to do the following :

• Manage Portfolio of Projects
• Manage Resources against this Portfolio
• Calculate Project Finances using resource roles and rates

I would be grateful to have both comments on experience , both positive and negative.

Thank You

Hi I am trying to add a new app server to my project server 2013  farm.

All the servers are patched to the same level (oct 2013) but when I run the wizard I get an error saying to install Cu on the server already in the farm.

I can see that the the "Product Version Job"  ("job-admin-product-version") is failing from the ULS logs (below).

Could anyone offer any help or advice?

Thanks

Pratrap

PS2013 ULS Error: "patchca not found. Falling back"

02/10/2014 14:58:31.72 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Logging Correlation Data xmnv Medium Name=Timer Job job-admin-product-version b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:31.72 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology b3ud Medium Updating local spserver.AutoUpdateEnabled = [True], notification level = [aunlNotifyBeforeDownload] b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:31.72 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 8xqz Medium Updating SPPersistedObject SPServer Name=P15SERVER2. Version: 18171 Ensure: False, HashCode: 18911339, Id: 5a5c4298-4e55-4658-9715-f1034b696415, Stack:    at Microsoft.SharePoint.Administration.SPServerProductInfo.UpdateProductInfoInDatabase(Guid serverGuid)     at Microsoft.SharePoint.Administration.SPProductVersionJobDefinition.Execute(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) b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:32.00 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:32.77 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:32.88 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:33.08 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:33.19 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:33.33 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:33.49 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:33.58 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:33.69 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:33.77 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:33.91 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:34.00 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:34.11 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:34.38 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:34.47 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:34.63 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:34.74 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:34.83 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:34.95 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:35.13 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:35.38 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:35.50 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:57.44 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:57.64 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:57.83 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:58.06 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:58:58.56 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:01.00 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:01.17 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:01.72 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:13.03 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:13.50 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:13.72 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:13.86 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:14.02 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:14.25 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.80 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Topology 999p High patchca not found. Falling back b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.92 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyw6 High 02/10/2014 14:59:15.92 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPHierarchyManager ajyw6 DEBUG [SPTree Value=SPFarm Name=SharePoint_Config] added to dependency cache by lookup b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.92 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade aj036 Medium 02/10/2014 14:59:15.92 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade FarmSequence aj036 INFO Adding the SessionStateService to the hierarchy... b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.92 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade aj037 Medium 02/10/2014 14:59:15.92 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade FarmSequence aj037 INFO Adding the StateService to the hierarchy... b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.92 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy5z High 02/10/2014 14:59:15.92 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPFarmSequence ajy5z DEBUG Adding Service Application [SecureStoreServiceApplication Name=Secure Store Service] to the upgrade hierarchy. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.92 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy5z High 02/10/2014 14:59:15.92 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPFarmSequence ajy5z DEBUG Adding Service Application [StateServiceApplication Name=State Service] to the upgrade hierarchy. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.92 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy5z High 02/10/2014 14:59:15.92 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPFarmSequence ajy5z DEBUG Adding Service Application [PsiServiceApplication Name=Project Server Service Application] to the upgrade hierarchy. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.92 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy5z High 02/10/2014 14:59:15.92 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPFarmSequence ajy5z DEBUG Adding Service Application [ExcelServerWebServiceApplication Name=Excel Services Application] to the upgrade hierarchy. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy5z High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPFarmSequence ajy5z DEBUG Adding Service Application [SPSecurityTokenServiceApplication Name=SecurityTokenServiceApplication] to the upgrade hierarchy. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy5z High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPFarmSequence ajy5z DEBUG Adding Service Application [SPTopologyWebServiceApplication Name=Topology] to the upgrade hierarchy. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade fbv7 Medium 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade FarmUpgradeSequence 0000 INFO Adding FormsService Id=87ca8941-c404-40ac-8e94-6acfb670fdd4 to the upgrade hierarchy. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade aj26u High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession aj26u DEBUG Disposing [SecureStoreServiceApplication Name=Secure Store Service]. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmk High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmk DEBUG IsBackwardsCompatible [SPServer Name=P15SERVER2] returned: True. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmk High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmk DEBUG IsBackwardsCompatible [SPFarm Name=SharePoint_Config] returned: True. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPServerSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPServerSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPServerSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPServerSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade aj2jj High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade ServerSequence aj2jj DEBUG Search ServerSequence returns BuildVersion '15.0.4551.1002' b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade aj2jj High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade ServerSequence aj2jj DEBUG Search ServerSequence returns BuildVersion '15.0.4551.1002' b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade ServerSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade ServerSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade aj2jl High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade ServerSequence aj2jl DEBUG Search ServerSequence returns TargetBuildVersion '15.0.4551.1002' b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade aj2jl High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade ServerSequence aj2jl DEBUG Search ServerSequence returns TargetBuildVersion '15.0.4551.1002' b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmf High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmf DEBUG CanUpgrade [SPServer Name=P15SERVER2] returned: True. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade aj2jj High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade ServerSequence aj2jj DEBUG Search ServerSequence returns BuildVersion '15.0.4551.1002' b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade aj2jl High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade ServerSequence aj2jl DEBUG Search ServerSequence returns TargetBuildVersion '15.0.4551.1002' b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmx High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmx DEBUG NeedsUpgrade [SPServer Name=P15SERVER2] returned: False. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade aj2jj High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade ServerSequence aj2jj DEBUG Search ServerSequence returns BuildVersion '15.0.4551.1002' b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade aj2jl High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade ServerSequence aj2jl DEBUG Search ServerSequence returns TargetBuildVersion '15.0.4551.1002' b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmx High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmx DEBUG NeedsUpgrade [SPServer Name=P15SERVER2] returned: False. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy6f High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPServerSequence ajy6f DEBUG Web service Instance SPWebServiceInstance added. Status = Online b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy6f High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPServerSequence ajy6f DEBUG Web service Instance SPWebServiceInstance Name=WSS_Administration added. Status = Online b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmx High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmx DEBUG NeedsUpgrade [SPWebServiceInstance] returned: False. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmx High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmx DEBUG NeedsUpgrade [SPWebService] returned: False. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmx High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmx DEBUG NeedsUpgrade [SPWebApplication Name=PWA - 82] returned: False. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy60 High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPWebApplicationSequence ajy60 DEBUG Web application [SPWebApplication Name=PWA - 82] has 1 IisSettings object b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:15.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy61 High 02/10/2014 14:59:15.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPWebApplicationSequence ajy61 DEBUG Searching for sites with Server Comment = PWA - 82 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.02 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy66 High 02/10/2014 14:59:16.02 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPWebApplicationSequence ajy66 DEBUG Adding a iis web site object with instance Id = [1486512703] b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.03 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:16.03 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPIisWebSiteWssSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.03 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:16.03 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPIisWebSiteWssSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.05 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:16.05 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.05 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:16.05 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.05 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:16.05 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.05 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:16.05 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.06 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:16.06 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade DlcIisWebSiteSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.06 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:16.06 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade DlcIisWebSiteSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.08 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:16.08 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.08 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:16.08 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.08 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmf High 02/10/2014 14:59:16.08 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmf DEBUG CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] returned: True. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.11 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmx High 02/10/2014 14:59:16.11 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmx DEBUG NeedsUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] returned: False. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.17 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmf High 02/10/2014 14:59:16.17 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmf DEBUG CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] returned: True. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.25 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmf High 02/10/2014 14:59:16.25 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmf DEBUG CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] returned: True. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmx High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmx DEBUG NeedsUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] returned: False. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxn3 High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxn3 DEBUG Disposing [Microsoft.SharePoint.Administration.SPIisWebSite]. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxn3 High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxn3 DEBUG Disposing [Microsoft.SharePoint.Administration.SPIisWebSite]. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy5i High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPContentDatabaseSequence ajy5i DEBUG Returning SchemaVersion [15.0.145.0] for Database WSS_Content_82, Status = Online. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy5i High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPContentDatabaseSequence2 ajy5i DEBUG Returning SchemaVersion [15.0.14.0] for Database WSS_Content_82, Status = Online. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmx High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmx DEBUG NeedsUpgrade [SPContentDatabase Name=WSS_Content_82] returned: False. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxpf High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPContentDatabaseSequence ajxpf DEBUG Adding root web/site collection web templates below ContentDatabase WSS_Content_82. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajywv High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPSiteWssSequence ajywv DEBUG Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajywv High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade WebAnalyticsSiteSequence ajywv DEBUG Microsoft.Office.Server.WebAnalytics, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajywv High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade MossSiteSequence ajywv DEBUG Microsoft.SharePoint.Portal.Upgrade, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajywv High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade DlcSiteSequence ajywv DEBUG Microsoft.Office.Policy, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajywv High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SiteSequence ajywv DEBUG Microsoft.Office.Server.Search, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajywv High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade ExcelMobileViewerSiteSequence ajywv DEBUG Microsoft.Office.Excel.WebUI.Mobile, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajywv High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SiteSequence ajywv DEBUG Microsoft.Office.InfoPath.Server, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajywv High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPWebWssSequence ajywv DEBUG Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajywv High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade WorkflowWebSequence ajywv DEBUG Microsoft.SharePoint.WorkflowServicesBase, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.31 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajywv High 02/10/2014 14:59:16.31 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade MossWebSequence ajywv DEBUG Microsoft.SharePoint.Portal.Upgrade, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.36 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Database fa42 Monitorable A large block of literal text was sent to sql (length 44801).  This can result in blocking in sql and excessive memory use on the front end.  Verify that no binary parameters are being passed as literals, and consider breaking up batches into smaller components.  If this request is for a SharePoint list or list item, you may be able to resolve this by reducing the number of fields. Call stack:    at Microsoft.SharePoint.Utilities.SqlSession.OnPostExecuteCommand(SqlCommand command, SqlQueryData monitoringData)     at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior, SqlQueryData monitoringData, Boolean retryForDeadLock)     at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior)     at Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.GetSiteNeedsUpgrade(SPUpgradeSession session, SPContentDatabase database, Dictionary`2& dictSitesNeedUpgrade, Dictionary`2& dictSitesNeedFeatureUpgrade)     at Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.AddNextLevelObjects()     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.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.SPProductVersionJobDefinition.Execute(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) b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.36 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Database fa43 High Slow Query Duration: 31.3339 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.36 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Database fa44 High Slow Query StackTrace-Managed:    at Microsoft.SharePoint.Utilities.SqlSession.OnPostExecuteCommand(SqlCommand command, SqlQueryData monitoringData)     at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior, SqlQueryData monitoringData, Boolean retryForDeadLock)     at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior)     at Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.GetSiteNeedsUpgrade(SPUpgradeSession session, SPContentDatabase database, Dictionary`2& dictSitesNeedUpgrade, Dictionary`2& dictSitesNeedFeatureUpgrade)     at Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.AddNextLevelObjects()     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.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.SPProductVersionJobDefinition.Execute(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) b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.36 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Database tzku High ConnectionString: 'Data Source=hpserver\p15farm;Initial Catalog=WSS_Content_82;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[OWSTIMER][1][WSS_Content_82]'    Partition: 00000000-0000-0000-0000-000000000000<->ffffffff-ffff-ffff-ffff-ffffffffffff ConnectionState: Open ConnectionTimeout: 15 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.36 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Database tzkv High SqlCommand: 'EXEC sp_executesql N'                  DECLARE @SiteSequenceVersions TABLE (Id uniqueidentifier PRIMARY KEY, ApplicableWebTemplate int, TargetVersionNumber bigint, PreviousTargetVersionNumber bigint, SiteSequence bit)                  DECLARE @FeatureVersions TABLE (Id uniqueidentifier PRIMARY KEY, TargetVersionNumber bigint, PreviousTargetVersionNumber bigint)                  DECLARE @TemplateVersions TABLE (Id int, LocaleId int NULL, FromProductVersion int, BeginFromSchemaVersion int, EndFromSchemaVersion int, CompatibilityLevel int)                  INSERT INTO @SiteSequenceVersions VALUES (''43b447bb-40ea-4f88-9356-a0229008afe7'', 0, 15000000350000, 4000000250000, 1);INSERT INTO @SiteSequenceVersions VALUES (''2d4d698e-aabe-4373-a37f-4fc7f2228431'', 0, 15000000010000, 0, 1);INSERT INTO @SiteSequenceVersions VALUES (''a5d5f97f-cf94-4074-9b7c-cb5708f96c27'', 0, VALUES (''00bfea71-4ea5-48d4-a4ad-7ea5c011abe5'', 15000000010000, 14000000000000);INSERT INTO @, 3, 1, 2, 15); INSERT VALUES (21, NULL, 4, 0, 11, 15); INSERT INTO @TemplateVersions VALUES (54, NULL, 3, 0, 6, 15); INSERT INTO @ SV.SiteId                      FROM                         (                           SELECT SiteId, WebId, VersionId, Version, RANK() OVER (PARTITION BY SiteId, WebId, VersionId ORDER BY Id DESC) AS Rank          '     CommandType: Text CommandTimeout: 0 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.36 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Database aek90 High SecurityOnOperationCheck = True b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.36 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxpg High 02/10/2014 14:59:16.36 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPContentDatabaseSequence ajxpg DEBUG All SPSite(s) in [SPContentDatabase Name=WSS_Content_82] have up-to-date Schema versions. No need to add them to the upgrade tree. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.36 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmx High 02/10/2014 14:59:16.36 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmx DEBUG NeedsUpgrade [SPWebApplication Name=psfv4 - 84] returned: False. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.36 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy60 High 02/10/2014 14:59:16.36 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPWebApplicationSequence ajy60 DEBUG Web application [SPWebApplication Name=psfv4 - 84] has 1 IisSettings object b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.36 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy61 High 02/10/2014 14:59:16.36 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPWebApplicationSequence ajy61 DEBUG Searching for sites with Server Comment = psfv4 - 84 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.47 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajy66 High 02/10/2014 14:59:16.47 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPWebApplicationSequence ajy66 DEBUG Adding a iis web site object with instance Id = [1080981000] b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.49 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:16.49 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPIisWebSiteWssSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.49 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:16.49 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPIisWebSiteWssSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.50 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:16.50 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.50 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:16.50 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.52 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:16.52 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.52 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:16.52 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.56 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:16.56 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade DlcIisWebSiteSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.56 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:16.56 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade DlcIisWebSiteSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.67 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:16.67 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.67 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:16.67 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.67 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmf High 02/10/2014 14:59:16.67 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmf DEBUG CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] returned: True. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmx High 02/10/2014 14:59:16.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmx DEBUG NeedsUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] returned: False. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:16.94 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyw6 High 02/10/2014 14:59:16.94 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPHierarchyManager ajyw6 DEBUG [SPTree Value=Microsoft.SharePoint.Administration.SPIisWebSite] added to dependency cache by lookup b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:17.02 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:17.02 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPIisWebSiteWssSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:17.02 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:17.02 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPIisWebSiteWssSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:17.16 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:17.16 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:17.16 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:17.16 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:17.28 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:17.28 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:17.28 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:17.28 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:17.39 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:17.39 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade DlcIisWebSiteSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:17.39 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:17.39 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade DlcIisWebSiteSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:17.50 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxg High 02/10/2014 14:59:17.50 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxg DEBUG UpgradableBuildBypassInternal = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:17.50 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajyxh High 02/10/2014 14:59:17.50 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade IisWebSiteSequence ajyxh DEBUG UpgradableBuildBypass = 0 b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:17.50 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmf High 02/10/2014 14:59:17.50 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmf DEBUG CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] returned: True. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:18.00 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmf High 02/10/2014 14:59:18.00 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmf DEBUG CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] returned: True. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:18.27 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxmx High 02/10/2014 14:59:18.27 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxmx DEBUG NeedsUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] returned: False. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:18.27 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxn3 High 02/10/2014 14:59:18.27 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxn3 DEBUG Disposing [Microsoft.SharePoint.Administration.SPIisWebSite]. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:18.27 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Upgrade ajxn3 High 02/10/2014 14:59:18.27 OWSTIMER (0x0C50) 0x0C3C SharePoint Foundation Upgrade SPUpgradeSession ajxn3 DEBUG Disposing [Microsoft.SharePoint.Administration.SPIisWebSite]. b5e7729c-c3ca-00fb-9641-5456b62f8522 b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:18.27 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Timer 6398 Critical The Execute method of job definition Microsoft.SharePoint.Administration.SPProductVersionJobDefinition (ID 3aff2ecc-be89-41c5-b079-877224484809) threw an exception. More information is included below.  Collection was modified; enumeration operation may not execute. b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:18.27 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Timer 72ae Unexpected Exception stack trace:    at System.Collections.Generic.List`1.Enumerator.MoveNextRare()     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.SPProductVersionJobDefinition.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result) b5e7729c-c3ca-00fb-9641-5456b62f8522
02/10/2014 14:59:18.28 OWSTIMER.EXE (0x0C50) 0x0C3C SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (Timer Job job-admin-product-version). Execution Time=46552.0829 b5e7729c-c3ca-00fb-9641-5456b62f8522

This is a follow on question to this one: Phantom Actuals.

We are on PS 2010.  Work resources enter timesheets in SEM.  Task Tracking Method is set to Hours of Work done per period ... always has been.

A PM has managed to get a bunch of bogus actuals saved/published on one of the tasks on the project.  My theory this was either by:

• using the % complete buttons/features of MS Pro
• jacking with the task such that it was toggled to a summary/non-summary task.  It is currently not a summary task.

... despite my job aids and other communications to not do such things ...

Anyways, I strongly suspect the PM did something to basically indicate the task was complete while it still had remaining work ... so all that remaining work was added as actual work.  The PM did admit to attempting to close the task to updates ... which is something you would only do for a task that is supposedly compelete.

Why MSP Pro allows this to happen given our PS server settings clearly indicate that % complete is not allowed is beyond me.  Also ... why "sync to protected" actuals does not resolve thsi is also beyond me.

The only method I know to resolve is to edit all related timesheets to force a task update.  I estimate that at 28 timesheets -- ain't nobody got time for that!!

Questions:

1. Any other ways to fix this? 
2. I'm tempted to restore the project to Sunday night's backup.  If I do that, will any task updates approved after that backup be applied or will those timesheets need to be recalled/resubmitted in order for those to be applied (or will the updates just be applied after the next timesheet approval cycle since task updates are cumulative).
3. Why doesn't sync to protected actuals fix this?
4. What can I possibly do to make sure no blankety blank blankety blanking PM uses % complete on an Enterprise Project ever again ... or if they try to, MS Project won't let them?  The Enterprise Task Tracking setting does not seem to be respected in MS Project Pro.  If there is another setting -- I would love to hear about it.
5. The fact that MSP Pro ignores the Enterprise Task tracking setting really feels like a bug.  We are on MS Project Pro client version 14.0.6129.5000 (oct 2012) ... I'll ask about getting us current but I don't see anything in the release notes that would indicate this has been fixed.  I can't imagine we are the only ones being impacted by this.

Thanks for any input.

Grady

Hi,

I am doing a test to see if i can create a link by typing the link path (f.i. <>\plan2\1) in the predecessor column without having edit rights to the other plan.

I expect this to be possible as the edit in the other plan (creation of link) is only done after the change is accepted through the LBP (link between projects) window. Besides, when i do it to both my own plans, in this LBP window i get 'create external link' as difference to accept.

When I do it on Project Server 2010 to a plan I do not own or having edit rights on, I got the message 'file not found'.

Is this message related to what I am trying or does it have another cause?

Does someone know if what I want can be done?

Rgds

Sander

Hi,

We have around 1000 projects in our PS2013 environment, and project site is not associated any of them. We have created a new template for project site.

To now create and associate this template with each project (without having to manually publish), we have to use option of managing connected site, but here we can create only one site at a time.

Is there a way for bulk create for multiple projects in one shot? 

Thanks in advance

Atul Sharma

I have added "Hyperlink Address" field in Task Summary view on Project Details page. When I am trying to edit the task in Project Web Application (PWA), the Hyperlink Address kept read only. However when I edit the tasks in Project Professional I am able to insert hyperlinks and those links are available in PWA too.

Please let me know why Hyperlink Address field is read only in PWA?

Many Thanks!!

Hi

we migrated a 2007 environment to 2013 (db upgrade to 2010 SP2, then to 2013 August 2013 CU).

In 2007 the enterprise global works without any issues. Open and save is possible without problems.

In the 2013 environment now: We open the Enterprise Global, change anything (to make Project recognize that there is something to save....) and save the Eglobal. Some seconds later Project closes "unexpectedly" and the Eglobal remains checked out.

We found out that this already happens in the 2010 intermediate environment.

So this morning I  thought I should copy all views etc. to a project file as a backup and recreate the eglobal as I had done ages ago in 2007.

But I found out that the eglobal.sql file in Program Files\Microsoft Office Servers\15\SQL\..... does not exist any more. Microsoft has removed it.

Anyone having a great idea (apart from opening a call or recreating the eglobal in 2007 and start migration again) ?

Thanks

Christoph

Christoph Muelder | Senior Consultant, MCTS, MCSE, MCT | SOLVIN information management GmbH, Germany

Hi to all:

It seems that is not possible to change the lookup table associated to a custom field in Project Server 2010. So the only alternative is to delete the custom field, create the field again and associate the right lookup table. Please I need to confirm if this is correct.

Thank you very much

Regards

Carlos Negroni

I have successfully installed SharePoint 2013 and Project Server 2013. I have created a couple of projects and just finished importing an existing .MPP in Project Server. However when I click on "Projects" in the Project Server Home Page navigation bar, I receive a "Sorry Something Went Wrong Error" with the following details below. Going to the Web Parts Maintenance Page doesn't seem to offer any resolution and I have no idea what went wrong.

If I type in the full URL of the Site created by the .MPP import, it comes up just fine and seems to be working. However, if I go to the PWA Home page and click on "Tasks" I receive the same error as described above.

Any guidance in researching and resolving this would be greatly appreciated. Below is what I received when click on "Projects". If I click on the " Troubleshoot issues with Microsoft SharePoint Foundation" Link I receive an invalid URL message.

Setup:  Project Server 2010, Single Entry Mode, "Require Line Approval Before Timesheet Approval" checked. (We don't actually use Timesheets, resources always use "send status" rather than "submit timesheet".

The issue:  When you pull timesheet data (either using the sample report or when you create something less clunky to query the DB, either way) each "line" has a status of either "Approved", "Pending Approval", "Pending", or "Rejected".  I've seen some other people dance around this topic, but I can't find anywhere that it's directly addressed.  The problem is, the "default" status appears to be whatever the previous week was, rather than "Pending".  The only way I've been able to determine if a line status was *really* sent is by filtering either by the sum of work for the line being greater than 0, or by the "comment" field (FYI it's so annoying that Comment is not included in the TimesheetLine_UserView view) not being blank.

I have been filtering on these items for my own time reporting use (that's one of my fabulous jobs here, bugging people to enter project hours) but now I'm trying to make a report that the Resource Managers can use to monitor their own groups, and it's really tricky, because I want them to be able to see the line items which have actual 0 work, but I don't want to have to explain that the "Approved" or "Pending Approval Status" is a lie.  I may be able to solve this with a "case" statement in the query, but I'm wondering if this is something Microsoft knows about, or if it's an issue that no one has been able to quantify well enough to get it any attention.

Thoughts?