Új hozzászólás Aktív témák

• #10925 gaborbol őstag bobsys #10920

  Új Válasz 2015-06-23 19:36:35 #10925

  Új hozzászólás

  Összes hozzászólása itt Válaszok az összes hozzászólására itt Válaszok erre a hozzászólásra

  Privát üzenet küldése

  

  gaborbol

  őstag

  válasz bobsys #10920 üzenetére

  Milyen DC-ez, 2003-2008-2012?

  Amit brd linkelt korabban patch-et 2003 es 2008 szerverhez, ott azt irjak, hogy akinek ilyen gondja van az hivja az MS supportot batran a reszletekert.
  Biztos, hogy van ingyen supportotok veluk, ha nincs akkor meg $200 az eseti ticket en fix, hogy hivnam oket aztan par ora mulva megvan a hivatalos magyarazat

  "If you suspect you are affected by this problem but you want to be positive that applying this hotfix will help you, we recommend that you contact Microsoft Customer Technical Support to investigate the state of the affected databases.

  In addition, these events can be caused by too many reference phantoms. These database records are placeholders for one-way object links (that have no backlink) in which the target object was deleted and the tombstone removed from the database. However, the reference is not changed. These references have to be cleaned up. You can do this by deleting the attribute value or by changing the reference to a valid object. One example attribute in this class is the "secretary" attribute.

  We recommend that you contact Microsoft Customer Technical Support to help you identify and remove these reference phantoms."

  A masik ket dolog amit irtnak a pacthen kivul:

  [link]

  Legutolso post:

  So - in summary, I *think* I have found the culprit of the version
  storage depletion issues, and it's having pre-Win2003 groups with >
  5,000 members (mas talalat is mutat erre a hibalehetosegre)

  vagy esetleg:

  What we found was that a process dump of the lsass.exe process pointed at a
  third-party change auditing software package, which was installed on the
  DCs. We removed this package temporarily on some DCs, and found that after
  doing so, the lsass.exe process was actually crashing, not hanging. We
  were no longer seeing any version store depletion, just lsass.exe crashing
  with an access violation.

  [ Szerkesztve ]

Új hozzászólás Aktív témák