July 21, 2017 at 8:06 am
I am running SQL Server 2014 with two named instances on the same 2012 server
Problem: The SQL Server Agent will not start unless I have the FQDN in the "Alias Local Host Server " of the connection properties of the SQL Server Agent - matter of fact it the same for both instances on that server. Both the service and the agent are using the Virtual Service accounts provided by SQL Server. Encryption of data in transit is enabled and I have the service accounts added to the private key. If i add the FQDN in this Alias Local Host Server - the service starts up just fine.
Errors:
In windows Application Event log i get
SQLServerAgent could not be started (reason: Unable to connect to server 'MyServer\instance'; SQLServerAgent cannot start).
In the AgentOut log i get
2017-07-21 08:54:04 - ! [298] SQLServer Error: 802, SSL Provider: The target principal name is incorrect. [SQLSTATE 08001]
Checking select @@servername is correct.
Any ideas would be appreciated.
Jeff
July 21, 2017 at 10:52 am
Don't really know for sure, but I suspect that the enabling of encryption of data in transit may require that. Not sure exactly why.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
July 21, 2017 at 12:39 pm
Thanks for the response.
All of our server has that encryption and this one is only having the trouble.
Whats crazy is we are trying to run an SSIS package using an Agent Job and we are getting the same error. So we figure if we fix the Alias issue... the SSIS package will work.
Jeff
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply