{"id":7677,"date":"2025-01-27T11:07:22","date_gmt":"2025-01-27T11:07:22","guid":{"rendered":"https:\/\/howtogeek.blog\/lv\/?p=7677"},"modified":"2025-01-27T11:07:22","modified_gmt":"2025-01-27T11:07:22","slug":"fixing-server-error-sid-mismatch-628-0x274-a-comprehensive-guide","status":"publish","type":"post","link":"https:\/\/howtogeek.blog\/lv\/fixing-server-error-sid-mismatch-628-0x274-a-comprehensive-guide\/","title":{"rendered":"Servera k\u013c\u016bdas SID neatbilst\u012bbas 628 (0x274) nov\u0113r\u0161ana: visaptvero\u0161a rokasgr\u0101mata"},"content":{"rendered":"

Sastap\u0161an\u0101s ar ERROR_SERVER_SID_MISMATCH var b\u016bt bied\u0113jo\u0161s izaicin\u0101jums sist\u0113mas administratoriem, bie\u017ei izraisot kaitino\u0161as piek\u013cuves probl\u0113mas. Tom\u0113r lab\u0101 zi\u0146a ir t\u0101, ka \u0161\u012bs probl\u0113mas atrisin\u0101\u0161ana ir piln\u012bb\u0101 iesp\u0113jama. Izpildiet \u0161o detaliz\u0113to rokasgr\u0101matu, lai atjaunotu servera procesu funkcionalit\u0101ti un atg\u016btu piek\u013cuvi.<\/p>\n

Efekt\u012bvi risin\u0101jumi ERROR_SERVER_SID_MISMATCH<\/h2>\n

1. Restart\u0113jiet servera procesus un p\u0101rbaudiet servera procesa SID<\/h3>\n
    \n
  1. Palaidiet komandu uzvedni ar administratora ties\u012bb\u0101m.<\/li>\n
  2. Izpildiet komandu, lai restart\u0113tu attiec\u012bgo pakalpojumu: net stop <service_name> && net start <service_name><\/strong><\/code> \"Restart\u0113jiet <\/li>\n
  3. P\u0101rbaudiet pa\u0161reiz\u0113jo SID, ievadot komandu:whoami \/user<\/strong><\/code><\/li>\n
  4. Sal\u012bdziniet par\u0101d\u012bto SID ar paredzamo SID, ko klients izmantos, lai nodro\u0161in\u0101tu l\u012bdzin\u0101\u0161anu.<\/li>\n<\/ol>\n

    2. Atjauniniet pakalpojuma pieteik\u0161an\u0101s lietot\u0101ja akredit\u0101cijas datus<\/h3>\n
      \n
    1. Nospiediet Windows<\/kbd> + R<\/kbd>, ierakstiet services.msc<\/strong> un nospiediet Enter<\/kbd>.\"Atveriet<\/li>\n
    2. Atrodiet pakalpojumu, kur\u0101 ir radu\u0161\u0101s probl\u0113mas, ar peles labo pogu noklik\u0161\u0137iniet uz t\u0101 un atlasiet Rekviz\u012bti<\/strong>.\"\"<\/li>\n
    3. Atlasiet cilni Pieteikties<\/strong> un p\u0101rbaudiet vai atk\u0101rtoti ievadiet pakalpojuma konta akredit\u0101cijas datus.<\/li>\n
    4. Saglab\u0101jiet izmai\u0146as, noklik\u0161\u0137inot uz Labi<\/strong>.<\/li>\n<\/ol>\n

      3. Not\u012briet ke\u0161atmi\u0146\u0101 saglab\u0101tos akredit\u0101cijas datus<\/h3>\n
        \n
      1. Atveriet dialoglodzi\u0146u Palaist, nospie\u017eot Windows<\/kbd> + R<\/kbd>, ierakstiet control<\/strong> un nospiediet Enter<\/kbd>.\"Piek\u013cuve<\/li>\n
      2. Dodieties uz akredit\u0101cijas datu p\u0101rvaldnieku<\/strong>.\"Akredit\u0101cijas<\/li>\n
      3. Izdz\u0113siet visus saglab\u0101tos akredit\u0101cijas datus, kas saist\u012bti ar problem\u0101tisko serveri.<\/li>\n<\/ol>\n

        4. Apstipriniet Active Directory konfigur\u0101ciju<\/h3>\n
          \n
        1. Apstipriniet, ka attiec\u012bgais lietot\u0101ja konts ir der\u012bgs un akt\u012bvs.<\/li>\n
        2. Atveriet komandu uzvedni.<\/li>\n
        3. Izmantojiet \u0161o komandu, lai p\u0101rbaud\u012btu dom\u0113na uzticam\u012bbas statusu: nltest \/sc_verify:<domain_name><\/strong><\/code>\"Dom\u0113na<\/li>\n<\/ol>\n

          5. P\u0101rre\u0123istr\u0113jiet pakalpojuma galveno nosaukumu (SPN).<\/h3>\n
            \n
          1. Komandu uzvedn\u0113 p\u0101rbaudiet eso\u0161o SPN ar:setspn -L <service_account><\/strong><\/code><\/li>\n
          2. Ja tr\u016bkst SPN, re\u0123istr\u0113jiet to, izmantojot:setspn -A <service\/hostname> <account><\/strong><\/code><\/li>\n
          3. P\u0113c re\u0123istr\u0101cijas pabeig\u0161anas p\u0101rbaudiet, vai probl\u0113ma joproj\u0101m past\u0101v.<\/li>\n<\/ol>\n

            \u0145emiet v\u0113r\u0101, ka \u0161\u012b pieeja ir \u012bpa\u0161i piem\u0113rota, ja izmantojat Kerberos autentifik\u0101ciju.<\/p>\n

            6. Papildu probl\u0113mu nov\u0113r\u0161anas padomi<\/h3>\n
              \n
            1. Atsvaidziniet grupas politikas, izpildot:gpupdate \/force<\/strong><\/code><\/li>\n
            2. P\u0101rbaudiet, vai nav SID dublik\u0101tu, izmantojot r\u012bku PsGetSid<\/strong> :psgetsid <machine_name><\/strong><\/code><\/li>\n
            3. Nodro\u0161iniet, lai visiem atbilsto\u0161ajiem lietot\u0101jiem un grup\u0101m b\u016btu nepiecie\u0161am\u0101s at\u013caujas.<\/li>\n
            4. Izmantojiet notikumu skat\u012bt\u0101ju<\/strong> gan klient\u0101, gan server\u012b, lai prec\u012bzi noteiktu visas novirzes.<\/li>\n
            5. Lai lietotu un atsvaidzin\u0101tu iestat\u012bjumus, restart\u0113jiet gan klientu, gan serveri.<\/li>\n
            6. Visu konfigur\u0101ciju p\u0101rbaude ir \u013coti svar\u012bga, lai izvair\u012btos no turpm\u0101k\u0101m komplik\u0101cij\u0101m.<\/li>\n
            7. Ja str\u0101d\u0101jat klaster\u012b, nodro\u0161iniet, lai mezglu konfigur\u0101cijas b\u016btu sinhroniz\u0113tas un SID b\u016btu konsekventi.<\/li>\n<\/ol>\n

              Ir svar\u012bgi saprast, ka ERROR_SERVER_SID_MISMATCH bie\u017ei tiek pievienots \u0161\u0101ds zi\u0146ojums: 628 (0x274) Servera process darbojas ar SID, kas at\u0161\u0137iras no klienta piepras\u012bt\u0101.<\/strong> Parasti \u0161\u012b probl\u0113ma rodas konfigur\u0101cijas k\u013c\u016bdu d\u0113\u013c. Veicot \u0161\u012bs darb\u012bbas, varat veikt nepiecie\u0161amos labojumus.<\/p>\n

              Ja v\u0113laties atrisin\u0101t citas probl\u0113mas, apsveriet iesp\u0113ju padzi\u013cin\u0101ti izp\u0113t\u012bt t\u0101das probl\u0113mas k\u0101 ERROR_CLIENT_SERVER_PARAMETERS_INVALID<\/strong> vai Nepiecie\u0161ama k\u013c\u016bdu sinhroniz\u0101cija<\/strong>, kas ar\u012b ir bie\u017ei sastopamas serveru administratoru probl\u0113mas.<\/p>\n

              Bie\u017ei uzdotie jaut\u0101jumi<\/h2>\n

              1. Ko noz\u012bm\u0113 ERROR_SERVER_SID_MISMATCH?<\/strong><\/h3>\n

              K\u013c\u016bda ERROR_SERVER_SID_MISMATCH nor\u0101da, ka servera process darbojas ar dro\u0161\u012bbas identifikatoru (SID), kas neatbilst klienta sagaid\u0101majam.\u0160\u012b neatbilst\u012bba var izrais\u012bt piek\u013cuves probl\u0113mas, un to parasti izraisa konfigur\u0101cijas neatbilst\u012bbas.<\/p>\n

              2. Vai varu nov\u0113rst ERROR_SERVER_SID_MISMATCH ra\u0161anos?<\/strong><\/h3>\n

              Lai gan ir gr\u016bti garant\u0113t, ka \u0161\u012b k\u013c\u016bda nekad nenotiks, j\u016bs varat mazin\u0101t riskus, nodro\u0161inot, ka pakalpojumu konti un lietot\u0101ju at\u013caujas ir pareizi konfigur\u0113ti programm\u0101 Active Directory, un regul\u0101ri p\u0101rbaudot servera iestat\u012bjumu neatbilst\u012bbas.<\/p>\n

              3. K\u0101das darb\u012bbas man vispirms j\u0101veic, saskaroties ar \u0161o k\u013c\u016bdu?<\/strong><\/h3>\n

              S\u0101ciet ar servera procesu restart\u0113\u0161anu, lai p\u0101rbaud\u012btu, vai k\u013c\u016bda tiek nov\u0113rsta. Ja n\u0113, turpiniet p\u0101rbaud\u012bt Active Directory konfigur\u0101ciju un p\u0101rliecinieties, vai pakalpojumu kontiem ir pareizi akredit\u0101cijas dati. Ke\u0161atmi\u0146\u0101 saglab\u0101to akredit\u0101cijas datu not\u012br\u012b\u0161ana var ar\u012b pal\u012bdz\u0113t atrisin\u0101t probl\u0113mu.<\/p>\n

              Avots un att\u0113li<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

              Sastap\u0161an\u0101s ar ERROR_SERVER_SID_MISMATCH var b\u016bt bied\u0113jo\u0161s izaicin\u0101jums sist\u0113mas administratoriem, bie\u017ei izraisot kaitino\u0161as piek\u013cuves probl\u0113mas. Tom\u0113r lab\u0101 zi\u0146a ir t\u0101, ka \u0161\u012bs probl\u0113mas atrisin\u0101\u0161ana ir piln\u012bb\u0101 iesp\u0113jama. Izpildiet \u0161o detaliz\u0113to rokasgr\u0101matu, lai atjaunotu servera procesu funkcionalit\u0101ti un atg\u016btu piek\u013cuvi. Efekt\u012bvi risin\u0101jumi ERROR_SERVER_SID_MISMATCH 1. Restart\u0113jiet servera procesus un p\u0101rbaudiet servera procesa SID Palaidiet komandu uzvedni ar administratora […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[9],"class_list":["post-7677","post","type-post","status-publish","format-standard","hentry","category-how-to","tag-windows"],"acf":[],"_links":{"self":[{"href":"https:\/\/howtogeek.blog\/lv\/wp-json\/wp\/v2\/posts\/7677","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/howtogeek.blog\/lv\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/howtogeek.blog\/lv\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/howtogeek.blog\/lv\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/howtogeek.blog\/lv\/wp-json\/wp\/v2\/comments?post=7677"}],"version-history":[{"count":1,"href":"https:\/\/howtogeek.blog\/lv\/wp-json\/wp\/v2\/posts\/7677\/revisions"}],"predecessor-version":[{"id":7678,"href":"https:\/\/howtogeek.blog\/lv\/wp-json\/wp\/v2\/posts\/7677\/revisions\/7678"}],"wp:attachment":[{"href":"https:\/\/howtogeek.blog\/lv\/wp-json\/wp\/v2\/media?parent=7677"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/howtogeek.blog\/lv\/wp-json\/wp\/v2\/categories?post=7677"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/howtogeek.blog\/lv\/wp-json\/wp\/v2\/tags?post=7677"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}