SharePointTopology Issue Tracker Rss Feed

Commented Issue: Error activating the feature on a foundation site. [709]

bobchauvin — Tue, 29 Nov 2011 19:00:33 GMT

Logs

11/17/2011 08:23:06.24 w3wp.exe (0x0E10) 0x0CA8 SharePoint Foundation General 88jb Medium Feature Activation: Activating Feature 'SharePointFarmInfoTimerJob_Feature' (ID: 'f5bdb83d-a43e-435a-8e3b-73083421b6e5') at URL http://dmd2010. d036972d-0682-4b7d-9fbf-900aa60d8fcc
11/17/2011 08:23:06.25 w3wp.exe (0x0E10) 0x0CA8 SharePoint Foundation General 75fb Medium Calling 'FeatureActivated' method of SPFeatureReceiver for Feature 'SharePointFarmInfoTimerJob_Feature' (ID: 'f5bdb83d-a43e-435a-8e3b-73083421b6e5'). d036972d-0682-4b7d-9fbf-900aa60d8fcc
11/17/2011 08:23:06.33 w3wp.exe (0x0E10) 0x0CA8 SharePoint Foundation Topology 8xqz Medium Updating SPPersistedObject SharePointFarmInfoTimerJob Name=SPFarmInfoTimerJob. Version: -1 Ensure: False, HashCode: 3675257, Id: 65b8720b-5df2-416f-80eb-225cf3f35024, Stack: at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate() at Microsoft.SharePoint.Administration.SPJobDefinition.Update() at SharePointFarmInfoTimerJob.Features.SharePointFarmInfoTimerJob_Feature.SharePointFarmInfoTimerJob_FeatureEventReceiver.FeatureActivated(SPFeatureReceiverProperties properties) at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce) at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce) at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefini... d036972d-0682-4b7d-9fbf-900aa60d8fcc
11/17/2011 08:23:06.33* w3wp.exe (0x0E10) 0x0CA8 SharePoint Foundation Topology 8xqz Medium ...tion featdef, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly) at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, String featureName, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope) at Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId, Boolean force, SPFeatureDefinitionScope featdefScope) at Microsoft.SharePoint.WebControls.FeatureActivator.ActivateFeature(Guid featid, SPFeatureDefinitionScope featdefScope) at Microsoft.SharePoint.WebControls.FeatureActivatorItem.BtnActivateFeature_Click(Object objSender, EventArgs evtargs) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebContro... d036972d-0682-4b7d-9fbf-900aa60d8fcc
11/17/2011 08:23:06.33* w3wp.exe (0x0E10) 0x0CA8 SharePoint Foundation Topology 8xqz Medium ...ls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP._layouts_managefeatures_aspx.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) at System... d036972d-0682-4b7d-9fbf-900aa60d8fcc
11/17/2011 08:23:06.33* w3wp.exe (0x0E10) 0x0CA8 SharePoint Foundation Topology 8xqz Medium ....Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error) at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb) at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineR... d036972d-0682-4b7d-9fbf-900aa60d8fcc
11/17/2011 08:23:06.33* w3wp.exe (0x0E10) 0x0CA8 SharePoint Foundation Topology 8xqz Medium ...untime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) d036972d-0682-4b7d-9fbf-900aa60d8fcc
11/17/2011 08:23:06.35 w3wp.exe (0x0E10) 0x0CA8 SharePoint Foundation Topology 8dyu High The SPPersistedObject, SharePointFarmInfoTimerJob Name=SPFarmInfoTimerJob, could not be updated because the current user is not a Farm Administrator. d036972d-0682-4b7d-9fbf-900aa60d8fcc
11/17/2011 08:23:06.39 w3wp.exe (0x0E10) 0x0CA8 SharePoint Foundation Feature Infrastructure 88jm High Feature receiver assembly 'SharePointFarmInfoTimerJob, Version=1.0.0.0, Culture=neutral, PublicKeyToken=24899278d4c23296', class 'SharePointFarmInfoTimerJob.Features.SharePointFarmInfoTimerJob_Feature.SharePointFarmInfoTimerJob_FeatureEventReceiver', method 'FeatureActivated' for feature 'f5bdb83d-a43e-435a-8e3b-73083421b6e5' threw an exception: System.Security.SecurityException: Access denied. at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate() at Microsoft.SharePoint.Administration.SPJobDefinition.Update() at SharePointFarmInfoTimerJob.Features.SharePointFarmInfoTimerJob_Feature.SharePointFarmInfoTimerJob_FeatureEventReceiver.FeatureActivated(SPFeatureReceiverProperties properties) at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, ... d036972d-0682-4b7d-9fbf-900aa60d8fcc
11/17/2011 08:23:06.39* w3wp.exe (0x0E10) 0x0CA8 SharePoint Foundation Feature Infrastructure 88jm High ...Boolean fForce) The Zone of the assembly that failed was: MyComputer d036972d-0682-4b7d-9fbf-900aa60d8fcc
11/17/2011 08:23:06.39 w3wp.exe (0x0E10) 0x0CA8 SharePoint Foundation General 72by High Feature Activation: Threw an exception, attempting to roll back. Feature 'SharePointFarmInfoTimerJob_Feature' (ID: 'f5bdb83d-a43e-435a-8e3b-73083421b6e5'). Exception: System.Security.SecurityException: Access denied. at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate() at Microsoft.SharePoint.Administration.SPJobDefinition.Update() at SharePointFarmInfoTimerJob.Features.SharePointFarmInfoTimerJob_Feature.SharePointFarmInfoTimerJob_FeatureEventReceiver.FeatureActivated(SPFeatureReceiverProperties properties) at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce) at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce) The Zone of the assembly tha... d036972d-0682-4b7d-9fbf-900aa60d8fcc
11/17/2011 08:23:06.39* w3wp.exe (0x0E10) 0x0CA8 SharePoint Foundation General 72by High ...t failed was: MyComputer d036972d-0682-4b7d-9fbf-900aa60d8fcc
11/17/2011 08:23:06.41 w3wp.exe (0x0E10) 0x0CA8 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (Feature Activation: Activating Feature 'SharePointFarmInfoTimerJob_Feature' (ID: 'f5bdb83d-a43e-435a-8e3b-73083421b6e5') at URL http://dmd2010.). Execution Time=178.126828968486 d036972d-0682-4b7d-9fbf-900aa60d8fcc
11/17/2011 08:23:06.42 w3wp.exe (0x0E10) 0x0CA8 SharePoint Foundation Runtime 6615 Critical Access denied. d036972d-0682-4b7d-9fbf-900aa60d8fcc
Comments: ** Comment from web user: bobchauvin **

Trying the suggested fix from Pientka
http://unclepaul84.blogspot.com/2010/06/sppersistedobject-xxxxxxxxxxx-could-not.html

Commented Issue: Timer Job "The Execute method of job definition .... Invalid number value" [648]

Pientka — Tue, 29 Nov 2011 11:31:52 GMT

It appears that the table updates as the modified time entries show a later time but I get this error in the Logs from the OWSTIMER
entry 1
Invalid number value. A number field contains invalid data. Please check the value and try again.<nativehr>0x8102001a</nativehr><nativestack></nativestack>
entry 2
The Execute method of job definition SharePointFarmInfoTimerJob.SharePointFarmInfoTimerJob (ID 7f96d2c9-6917-44f0-adf2-877120f835f2) threw an exception. More information is included below. Invalid number value. A number field contains invalid data. Please check the value and try again.

entry 3

Exception stack trace:
at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
at Microsoft.SharePoint.Library.SPRequest.AddOrUpdateItem(String bstrUrl, String bstrListName, Boolean bAdd, Boolean bSystemUpdate, Boolean bPreserveItemVersion, Boolean bUpdateNoVersion, Int32& plID, String& pbstrGuid, Guid pbstrNewDocId, Boolean bHasNewDocId, String bstrVersion, Object& pvarAttachmentNames, Object& pvarAttachmentContents, Object& pvarProperties, Boolean bCheckOut, Boolean bCheckin, Boolean bMigration, Boolean bPublish, String bstrFileName, ISP2DSafeArrayWriter pListDataValidationCallback, ISP2DSafeArrayWriter pRestrictInsertCallback, ISP2DSafeArrayWriter pUniqueFieldCallback)
at Microsoft.SharePoint.SPListItem.AddOrUpdateItem(Boolean bAdd, Boolean bSystem, Boolean bPreserveItemVersion, Boolean bNoVersion, Boolean bMigration, Boolean bPublish, Boolean bCheckOut, Boolean bCheckin, Guid newGuidOnAdd, Int32& ulID, Object& objAttachmentNames, Object& objAttachmentContents, Boolean suppressAfterEvents, String filename)
at Microsoft.SharePoint.SPListItem.UpdateInternal(Boolean bSystem, Boolean bPreserveItemVersion, Guid newGuidOnAdd, Boolean bMigration, Boolean bPublish, Boolean bNoVersion, Boolean bCheckOut, Boolean bCheckin, Boolean suppressAfterEvents, String filename)
at Microsoft.SharePoint.SPListItem.Update()
at SharePointFarmInfoTimerJob.SPFarmTopology.AddServerDetails(SPList spFarmTopologyList, String& serverName, Int32& index, SPServer server)
at SharePointFarmInfoTimerJob.SPFarmTopology.FetchSPFarmInfo(SPList spFarmTopologyList)
at SharePointFarmInfoTimerJob.SPFarmTopology..ctor(String siteWebUrl, String spListName)
at SharePointFarmInfoTimerJob.SharePointFarmInfoTimerJob.Execute(Guid targetInstanceId)
at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)

How would I debug this further to find out what field in the update is causing the issue and if its something I can change in the table or whether its something else?

Thanks
Comments: ** Comment from web user: Pientka **

Resolution of Invalid number problem is to change all Number columns on SharePoint list to Single line text. then it will start to work. Ehh. Great product but this bugs are really annoying.

Commented Issue: Timer Job "The Execute method of job definition .... Invalid number value" [648]

Pientka — Tue, 29 Nov 2011 10:59:19 GMT

Is there any way to turn off chaecking SMTP sever from this solution. In my case SMTP server is Exchange Farm without access for SharePoint account.

Commented Issue: Timer Job "The Execute method of job definition .... Invalid number value" [648]

Pientka — Tue, 29 Nov 2011 09:19:36 GMT

Is there any support for this problem?

Commented Issue: Error activating the feature on a foundation site. [709]

Pientka — Tue, 29 Nov 2011 09:19:05 GMT

https://plus.google.com/109423462029200221494/posts/hxS1LD6Aa3a - Here is the answer.

Commented Issue: Error activating the feature on a foundation site. [709]

bobchauvin — Thu, 17 Nov 2011 16:40:27 GMT

Activates successfully on Central Admin, but not on other sites.

Created Issue: On page to configure the SharePoint List, clicking ok does nothing . No lists created. [710]

bobchauvin — Thu, 17 Nov 2011 16:09:11 GMT

The page seems to refresh, but this is not normal for clicking [Ok] on config pages. Usually you are sent back to the parent page.

Lists are not created. Settings are saved.

Commented Issue: Error activating the feature on a foundation site. [709]

bobchauvin — Thu, 17 Nov 2011 15:38:45 GMT

If I run the ps1 file to install it does acitivate but does NOT create the list, and I get a similar error when I try to deactivate the feature via the site admin page.

Commented Issue: Error activating the feature on a foundation site. [709]

bobchauvin — Thu, 17 Nov 2011 13:28:57 GMT

And My the user I'm activating via IS a Farm Admin.

Created Issue: Error activating the feature on a foundation site. [709]

bobchauvin — Thu, 17 Nov 2011 13:26:55 GMT

Commented Issue: Timer Job "The Execute method of job definition .... Invalid number value" [648]

slyuso — Thu, 03 Nov 2011 23:23:54 GMT

Answering themind

As I pointed out, the issue observed on a Stand-alone server installation.
There is no issue in running the job. The issue is with the exception while running the job.

Did you have issues before adding the farm admin account to the local administrators group on the mail server ?
Is your installation Stand-alone?
There is no code related to e-mail in this job.

Commented Issue: Timer Job "The Execute method of job definition .... Invalid number value" [648]

themind — Thu, 03 Nov 2011 20:18:25 GMT

Adding the farm admin account to the local administrators group on the mail server allowed this job to run on my SharePoint server.

Commented Issue: Timer Job "The Execute method of job definition .... Invalid number value" [648]

slyuso — Wed, 02 Nov 2011 18:58:35 GMT

The above issue is actually a bug.
This can be observed on a Stand-alone server installation.

Repro:
Run:
Set-SPFarm | Format-List *
A part of the info will return
Servers : {MyDomain.loc, MyOwnCorrentServerName}

Unlike in the case of a farm installation, there is an extra entry
MyDomain.loc

While enumerating servers in the farm (
SPFarmTopology.cs,
private void FetchSPFarmInfo(SPList spFarmTopologyList) ,

foreach (SPServer server in sharepointFarm.Servers)),

AddServerDetails(spFarmTopologyList, ref serverName, ref index, server); throws exception

for the server name "MyDomain.loc"

Commented Issue: Timer Job "The Execute method of job definition .... Invalid number value" [648]

slyuso — Fri, 28 Oct 2011 23:13:14 GMT

Absolutely the same situation.

Created Issue: Timer Job "The Execute method of job definition .... Invalid number value" [648]

lucidqdreams — Tue, 25 Oct 2011 23:31:04 GMT

Commented Issue: Timer job fails when farm account does not have permissions on outgoing e-mail server [597]

brianlala — Sat, 15 Oct 2011 16:17:16 GMT

The timer job will always fail when the farm account does not have the (read perf counter) permissions on the box that is used as outgoing e-mail server. Outgoing e-mail server is treated as a server in the farm (as an invalid one) and the farm account does not have permissions by default to read the necessary perf counters which causes an exception in the timer job. The exception is taken care of but sets string values instead of double values in the data that is pushed in to the list, which causes the list update to fail.

A workaround is to change the AddServerDetails() method to have this check:
Double result = 0;
if (Double.TryParse(taskMgrInfo.CPUUsage, out result)) {
spFarmTopologyListItem[Global.cpuUsageColumnName] = taskMgrInfo.CPUUsage;
spFarmTopologyListItem[Global.freeSpaceDetailsColumnName] = taskMgrInfo.SystemDirectorySpaceUsage;
spFarmTopologyListItem[Global.freeDiskSpace] = taskMgrInfo.DiskFreeSpace;
spFarmTopologyListItem[Global.diskSpaceCapacity] = taskMgrInfo.DiskCapacity;
spFarmTopologyListItem[Global.freeSpacePercentColumnName] = taskMgrInfo.SystemDirectoryFreeSpaceInPercentage;
spFarmTopologyListItem[Global.memoryUsageDetailsColumnName] = taskMgrInfo.MemoryUsage;
spFarmTopologyListItem[Global.freeMemorySpace] = taskMgrInfo.FreeMemory;
spFarmTopologyListItem[Global.memoryCapacity] = taskMgrInfo.TotalMemory;
spFarmTopologyListItem[Global.memoryUsagePercentColumnName] = taskMgrInfo.MemoryUsageInPercentage;
}
Comments: ** Comment from web user: brianlala **

I agree with @wictor. Running the timer service as a local admin is generally agreed to be bad practice; suggesting we run it as a domain admin is just... crazy.

On the positive side though, this add-in has huge potential though, looking forward to a proper fix/workaround!

Cheers
Brian

Commented Issue: Timer job fails when farm account does not have permissions on outgoing e-mail server [597]

wictor — Fri, 14 Oct 2011 06:26:08 GMT

Running the timer service as domain administrator is still not recommended (by anyone). Yes it's a "secured" Windows service, but when running this using domain admin creds you give it far to much power and no granularity in control.

My suggestion is that for the SMTP server (which is actually not a part of the farm, even though it's listed as an SPServer) is treated differently than the other servers. It's interesting to see if it exits and is alive (a ping might be sufficient).

Commented Issue: Timer job fails when farm account does not have permissions on outgoing e-mail server [597]

AravindKS — Thu, 13 Oct 2011 19:37:29 GMT

Good to hear about your work around but I'm still not convinced why its evil to run SharePoint timerjob with domain account credentials. Timer Job is a secured windows services which runs in your environment. Timer job executes the operation which you have trusted and have scheduled. So I dont find any security threat or evil in running the SharePoint timerjob with Domain admin credentials.

Moreover to solve all (many) permissions issues only, we came out with timerjob rather than other options.

Commented Issue: Timer job fails when farm account does not have permissions on outgoing e-mail server [597]

wictor — Thu, 13 Oct 2011 17:26:07 GMT

Seriously? That is no solution you could use in any other scenarios than testing. Running the timer service as domain admin is as worst practice as you can get. My code change listed above does the trick just fine, and I'll use that for now. It works great and we have a visual representation of the farm health.

Commented Issue: Timer job fails when farm account does not have permissions on outgoing e-mail server [597]

AravindKS — Thu, 13 Oct 2011 16:49:34 GMT

Can you try configuring the SharePoint timerjob windows service to run in domain administrator credentials? The timerjob will try to execute with the credentials which has been used for it configuration. Probably the domain administrator credentials should have permission to make WMI calls to the SMTP server machine. I will surely make a note of it and will take care of it in my next version.

Thanks for logging the issue.