Event id 3 in system log on OCS FE server. RRS feed

  • Question

  • Hi all,

    I don't know if anyone encounter this before but the OCS FE server that I look after start generating event id 3 very 15 mins. The setup is

    1. 1x OCS FE

    2. 1x Archive

    3. 1x SQL 2008

    Each server is running on separate server. Initial (from my knowledge) the DBA set up SQL by using dynamic ports and last Friday, he added a static port 1433 and since then the event id 3 keeps coming up. I know it's a SPN issue but the only 2 things that has been changed recently is the SQL port and introduced Windows 2008 servers into a Windows 2003 domain.

    Below is the same error being generated very 15mins on the OCS FE box.

    A Kerberos Error Message was received:

     on logon session 

     Client Time: 

     Server Time: 0:51:47.0000 2/9/2011 Z


     Extended Error: 0xc0000035 KLIN(0)

     Client Realm: 

     Client Name: 

     Server Realm: domain.local

     Server Name: MSSQLSvc/sql.domain.local:1433

     Target Name: MSSQLSvc/sql.domain.local:1433@domain.local

     Error Text: 

     File: 9

     Line: e2d

     Error Data is in record data.

    Thanks for your help in advance.

    Wednesday, February 9, 2011 2:23 AM

All replies

  • Dear Friend ,

    Check the ports using this command on  CMD - netstat -s  and netstat -a , use this cmd and check ur ports are already open or not.

    Try and let me know

    madushka - http://uctechi.blogspot.com/ | Live - madushka@live.com | If got your answer don't forget to Rate as an Answer
    Thursday, February 10, 2011 4:47 AM
  • Thanks Madushka.

    I found the problem. The DBA set the SPN security on the back end and screw the OCS FE over. Once the DBA remove the SPN entries, it fixed the problem.

    Monday, February 21, 2011 10:57 PM
  • Hi Mike,

    Could you please xplain a bit more?

    Did you remove the following spn from the backend ?

     Server Name: MSSQLSvc/sql.domain.local:1433

     Target Name: MSSQLSvc/sql.domain.local:1433@domain.local



    ------Exchange, OCS------
    Monday, March 21, 2011 6:04 AM
  • Hi Dr.RPC,

    It seems that the DBA assigned a service account to the spn on the sql box. This basically broke all access to the sql server.

    As you mentioned above that is what was done to fix the problem by removing the spn by running the following command

    SetSpn -d mssqlsvc/servername.domain.local domainname\serviceaccount

    Thursday, March 24, 2011 7:17 AM
  • thanks!
    ------Exchange, OCS------
    Thursday, March 24, 2011 2:10 PM