Error 30063 - SQL Server could not set fdhost.exe process to 65535 because the value is not valid.

Question

Post reply

Error 30063 - SQL Server could not set fdhost.exe process to 65535 because the value is not valid.

Rasmus Remmer Bielidt

SSCommitted

Points: 1767
More actions
October 23, 2015 at 1:57 am

#304442

How do I go about fixing the error/warning in the topic?
Is it a registry entry somewhere? I searched the registry for fdhost.exe without finding a parameter set to 65535.
I should say, it appears in the errorlog on instance startup right after the fdhost process has been started. The FT service is running when looking at the Configuration manager.
[font="Courier New"]2015-10-22 23:25:15.770spid17sA new instance of the full-text filter daemon host process has been successfully started.
2015-10-22 23:25:15.780spid17sWarning: SQL Server could not set fdhost.exe processor affinity to 65535 because the value is not valid.[/font]

Viewing 10 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

ft55 Ten Centuries Points: 1210 More actions · Answer 1

Hi Ramus,

Did you get to the bottom of this error message as we are experiencing the same issue.

Thanks

Frant101

Rasmus Remmer Bielidt SSCommitted Points: 1767 More actions · Answer 2

Hi Frant101,

No, havent found a fix yet. Keep me posted if you do.

ft55 Ten Centuries Points: 1210 More actions · Answer 3

Hi,

Still working on it and trying to establish if its anything to be concerned about.

Configuration of Machine 2 Sockets , 20 Cores , 40 logical processors - although we only have 40 logical processors, Windows Server 2012 R2 has created two processor groups (thought this was only meant to happen when you had over 64 logical processors ?)

SQL Server sees this logical CPU's as NumNode0 - CPU0 to CPU19 and NumNode1 - CPU64 to CPU83

I've established that we only see this message in the error log when we set the processor affinity mask to use any of the logical processors from the second processor group (CPU64 - CPU83).

Currently trying to establish why Windows Server 2012 has created a 2nd processor group as I don't think this is expected behaviour. The below links helped me :

http://blogs.msdn.com/b/psssql/archive/2011/11/11/sql-server-clarifying-the-numa-configuration-information.aspx

http://blogs.msdn.com/b/saponsqlserver/archive/2011/04/20/changes-in-affinity-settings-of-sql-server-2008-r2-to-support-gt-64-logical-processors.aspx

http://blogs.msdn.com/b/saponsqlserver/archive/2010/09/28/windows-2008-r2-groups-processors-sockets-cores-threads-numa-nodes-what-is-all-this.aspx

Thanks

Frant101

johnwalker10 SSCrazy Eights Points: 9124 More actions · Answer 4

Please check if you got any non-default values for the configurations:

'affinity mask' and ‘affinity64 mask’

if so, then set them default

Rasmus Remmer Bielidt SSCommitted Points: 1767 More actions · Answer 5

I am not sure what the default settings are, but ours look like this - I don't think they have been changed.

[font="Courier New"]

name min max config run

affinity I/O mask-2147483648214748364700

affinity mask -2147483648214748364700

affinity64 I/O mask-2147483648214748364700

affinity64 mask -2147483648214748364700[/font]

SQL server also created two NUMA nodes for our setup which, from the errorlog is

[font="Courier New"]SQL Server detected 2 sockets with 4 cores per socket and 8 logical processors per socket, 16 total logical processors; using 16 logical processors based on SQL Server licensing. This is an informational message; no user action is required.[/font]

NumaNode0 is CPU0 through CPU7, NumaNode1 is CPU64 through CPU71.

ft55 Ten Centuries Points: 1210 More actions · Answer 6

I can confirm the following link fixed the issue for us :

http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04650594&sp4ts.oid=5379860

Changing the System ROM BIOS option from Clustered to Flat for the NUMA Group Size Optimization allowed Windows to see all 40 logical processors in one Windows Processor Group and in turn stopped the warning message appearing in the Error Logs.

SQL Server now correctly sees this logical CPU's as NumNode0 - CPU0 to CPU19 and NumNode1 - CPU20 to CPU39

Obviously this only applies to HP ProLiant Gen9 server configured with an Intel Xeon E5 2600v3 processor

Hope the info helps

Frant101

Rasmus Remmer Bielidt SSCommitted Points: 1767 More actions · Answer 7

Well spotted!

As it turns out, we're also using G9 HP with Xeon 26xx processors. I've asked our systems department to upgrade the BIOS and set the NUMA Group Size Optimization to FLAT - will post if this solves the issue at our side as well.

Johan Bijnens SSC Guru Points: 135587 More actions · Answer 8

Great feedback, guys ! :w00t:

Thanks.

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data and code to get the best help

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

Rasmus Remmer Bielidt SSCommitted Points: 1767 More actions · Answer 9

Upgrading our HP Proliant G9 Xeon server to the newest BIOS and setting the NUMA Group to FLAT also resolved our issue.

Thanks for helping out.