Answered by:
Login to Archive Database Fails

Question
-
Installed Skype for Business 2015 Standard on Server 2016. Everything works fine except...Tried to implement archiving to a separate SQL 2008r2 (SP2) server. I receive no errors when publishing the topology but see this error on the SQL server:
Login failed for user "domain\computername$". Reason Token-based server access validation failed with an infrastructure error. Error: 18456, Severity: 14, State 11.
Have read many posts but no real fixes. Have tried creating a computer name account on SQL but receive:
Windows NT user or group 'domain\computername$' not found. Check the name again.
The computer does exist in the domain.
Any suggestions?
Friday, August 11, 2017 9:24 PM
Answers
-
I was able to solve. Case sensitivity was the issue.
CREATE LOGIN [domain\computername$] FROM WINDOWS;
Being a SQL ignoramus, I entered the above command all lower case. Works fine when using case as shown above.
Thanks everyone for their suggestions.
- Marked as answer by gakambac Monday, August 14, 2017 8:13 PM
Monday, August 14, 2017 8:12 PM
All replies
-
Hello Gakambac,
Here some hints of your problem. This is SQL related. Maybe this can help?
regards Holger Technical Specialist UC
Saturday, August 12, 2017 8:05 AM -
Hi gakambac,
User that login the SQL Server should be assigned to the CsArchivingAdministrator role.
According to your error message , the problem may caused by the "CONNECT SQL" permissions. you need the "CONNECT SQL" permissions for the security principle you’re using.The following document is for your reference.
You could check the steps that deploy Skype for Business Archiving Server
https://insidemstech.com/2015/07/13/deploy-skype-for-business-archiving-and-monitoring-server/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Leon-Lu
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com- Edited by Leon-LuMicrosoft contingent staff Tuesday, August 15, 2017 5:02 AM
Monday, August 14, 2017 7:47 AM -
I was able to solve. Case sensitivity was the issue.
CREATE LOGIN [domain\computername$] FROM WINDOWS;
Being a SQL ignoramus, I entered the above command all lower case. Works fine when using case as shown above.
Thanks everyone for their suggestions.
- Marked as answer by gakambac Monday, August 14, 2017 8:13 PM
Monday, August 14, 2017 8:12 PM