I am getting a warning in my | event log on every boot. Error 1355 is: The specified domain either does not exist or could not be contacted. If you have specified Local System to start the SQL Server service, AccountName represents the account that you use to log on to Microsoft Windows. Resolution: You can also edit the account's Access Control Settings permissions in the Active Directory directory service to enable the Read servicePrincipalName permission and the Write servicePrincipalName permission for the SQL

Try these resources. now when we try to connect to the new p4 machine using the windows authentication we are not getting errror "Cannot generate SSPI Context." You are not getting error? You can call product support to get a hotfix... Brian Kelley, CISA, MCSE, Security+, MVP - SQL ServerRegular Columnist (Security), SQLServerCentral.comAuthor of Introduction to SQL Server: Basic Skills for Any SQL Server User| Professional Development blog | Technical Blog |

It should be an informational message. So, removing users' SELECT permissions prevents users from performing these operations. http://support.microsoft.com/default.aspx?scid=kb;en-us;303411Haven't seen an 8344 error before.K. my review here Thank you for your feedback!

Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. now when we try to connect to the new p4 machine using the windows authentication we are not getting errror "Cannot generate SSPI Context." for solving it we have tried to If you are, then is your MSSQLServerADHelper service set to LocalSystem as its account?K. get redirected here In the ADSI Edit window, expand Domain [DomainName], expand DC= RootDomainName, expand CN=Users, right-click CN=AccountName, and then click Properties.

You cannot post HTML code. SuperSocket info: (SpnRegister) : Error 1355. The error code is described as follows: 1355 The specified domain either does not exist or could not be contacted. SQL Server isn't typically run under a domain admin account (obvious security reasons) nor a localsystem account (no access to network resources and full admin rights on the box).