2
Vote

Timer Job "The Execute method of job definition .... Invalid number value"

description

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

slyuso wrote Oct 28, 2011 at 11:13 PM

Absolutely the same situation.

wrote Nov 2, 2011 at 6:47 PM

slyuso wrote Nov 2, 2011 at 6:58 PM

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"

themind wrote Nov 3, 2011 at 8:18 PM

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

slyuso wrote Nov 3, 2011 at 11:23 PM

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.

Pientka wrote Nov 29, 2011 at 8:19 AM

Is there any support for this problem?

Pientka wrote Nov 29, 2011 at 9:59 AM

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.

Pientka wrote Nov 29, 2011 at 10:31 AM

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.

wrote Feb 14, 2013 at 12:49 AM