November 19, 2016 at 9:45 am
Hello everyone.
I just performed an in-place upgrade for a client from SQL Server 2008 R2 to 2016 (Enterprise Ed). Everything seems fine except that I am getting two errors in the error log upon startup that I have never seen before:
1) InitializeExternalUserGroupSid failed. Implied authentication will be disabled
followed directly by:
2) Implied authentication manager initialization failed. Implied authentication will be disabled.
As mentioned, I have never seen these errors before, and also we are not currently experiencing any problems (that we know of). I checked the error logs from the previous reboot before the upgrade, and this error did not occur on the 2008 R2 version.
Does anyone know what this could be or if we should be concerned?
Thanks!
March 16, 2017 at 4:25 pm
Hi! Were you able to get rid of this message? I experience exactly the same issue and this is the only place on Internet where this issue was raised. What is "Implied authentication manager" anyway? This is the first instance of SQL Server 2016 EE SP1 I've configured. Can't find it anywhere else on SQL2008R2, SQL2012 and SQL2014.
April 11, 2017 at 11:28 am
April 11, 2017 at 11:32 am
April 11, 2017 at 12:18 pm
I figured out that this is related to R runtime and SQL Server Trusted Launchpad which I haven't installed, so I just ignored it. Here is some information on implied authentication.
https://docs.microsoft.com/en-us/sql/advanced-analytics/r-services/security-considerations-for-the-r-runtime-in-sql-server
November 7, 2017 at 7:36 am
I have the same issue on an inherited 2016 installation, and as of Nov. 7, 2017, there are still no other relevant Google hits for this. I don't know if this is normal and expected for a SQL Server 2016 installation that does not use or have R or Machine Learning configured, or if it indicates a problem.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply