none
NTFRS 13508 errors and "The procedure entry point NtfrsApi_ForceReplication" error with few clues RRS feed

  • Question

  • Out of Google's billions of pages, I only found three hits for this error, none of which offers any guidance:

    The procedure entry point NtfrsApi_ForceReplication could not be located in the dynamic link library NTFRSAPI.DLL

    In a special Windows 2003 domain, we have an unusual setup with two Win2003 DC's on one side of a firewall, and one Win2003 DC on the "inside". (That's the way it needs to be for it's purpose.)

    We are seeing 13508 errors, with no 13509. On the "inside" DC, which happens to also have the PDC role, running the "ntfrsutl version dc3.sub.domain.net" command yields:

    NtFrsApi Version Information
       NtFrsApi Major      : 0
       NtFrsApi Minor      : 0
       NtFrsApi Compiled on: Feb 16 2007 20:01:19
    NtFrs Version Information
       NtFrs Major        : 0
       NtFrs Minor        : 0
       NtFrs Compiled on  : Feb 16 2007 20:01:30
       Latest changes:
       Install Override fix
    OS Version 5.2 (3790) -
    SP (2.0) SM: 0x0110  PT: 0x02
    Processor:  INTEL Level: 0x0006  Revision: 0x0f08  Processor num/mask: 4/0000000f


    When this command is run on this same DC against both of the "outside" DC's, the command shows a different NtFrs Compilation date:

    NtFrsApi Version Information
       NtFrsApi Major      : 0
       NtFrsApi Minor      : 0
       NtFrsApi Compiled on: Feb 16 2007 20:01:19
    NtFrs Version Information
       NtFrs Major        : 0
       NtFrs Minor        : 0
       NtFrs Compiled on  : Mar 24 2003 22:03:35
       Latest changes:
       Server 2003 01-07-2003
    OS Version 5.2 (3790) -
    SP (0.0) SM: 0x0110  PT: 0x02
    Processor:  INTEL Level: 0x0006  Revision: 0x0f08  Processor num/mask: 4/0000000f


    When trying to run the NTFRSUTL command on either DC1 or DC2 (on the "outside"), the command yields the error: "The procedure entry point NtfrsApi_ForceReplication could not be located in the dynamic link library NTFRSAPI.DLL".

    This kind of seems to indicate a problem with the OS or NTFRS-related software/libs.

    Another wierd thing is that file replication and user account replication is definitely working, and running DCDIAG or NETDIAG doesn't really yield anything helpful for this.

    I am still checking for missing updates, but I was wondering if anyone could shed any light on this.

    [added later...]
    The two "outside" DC's have no service packs, while the inside DC has SP2. We will be installing SP2 on the other two DC's after our Quarted-End Freeze has lifted.
    Perhaps the 13508 errors with no 13509 are due to some issue with the different NTFRS versions.


    Thanks!!


    Rob Ingenthron


    Saturday, December 13, 2008 4:17 AM

Answers

  • I'd try loading the latest NTFRS rollup hotfix and see if that clears things up. Sounds like there is some sort of binary version mismatch. The way some of the AD/NTFRS interaction works is it calls LoadLibrary() on the NTFRS DLL and invokes the code that way as opposed to being linked against the libraries.
    Thanks, Brian Desmond Active Directory MVP www.briandesmond.com
    Sunday, December 14, 2008 2:54 AM