Active Directory Replication Status Tool broken

[DSPatrick]

Describe the bug downloading the latest version here https://www.microsoft.com/en-us/download/details.aspx?id=30005 installs fine but when trying to run it reports "This version of the tool has expired"

To Reproduce Go here, download, install it on domain controller and try to run it. https://www.microsoft.com/en-us/download/details.aspx?id=30005

Expected behavior A clear and concise description of what you expected to happen.

Screenshots

Desktop (please complete the following information):

• OS: Server 2016
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

[red-erik]

Hello, do you have any update ? This tool is a MUST for a lot of people so why not to stop let it expiring ? Thank you. Regards, Red.

[Taomyn]

Really would like to have a working version of this tool to get some information on our domain.

[TonyClements]

I would also really like a working version to get info from our domain

[JtotheR]

I know this has previously been stated by others. This is a great tool and we would really like to have a working version of this tool. Hopefully with some work around application licensing that auto renews so we don't have this problem again in a few years.

[rdegennaro]

This is the tool that Microsoft points to for troubleshooting replication issues and downloaded on their site. It is crazy that it is released in an unusable state for new servers.

[Alpha-Soft-GmbH]

Hello MS, This tool is a MUST for a lot of people so why not to stop let it expiring ? Thank you.

[jleathlean]

I also concur - this is the 3rd/4th time the tool has expired, but the first time they haven't replaced it before the expiration. :(

There are a lot of us who use this tool on a regular basis - and I'm not aware of any other tools that work in the same manner.

[ii-batman]

Hi Everyone, Is there a workaround for this? Reallly need it now! 😚

[rdegennaro]

I searched and could not find anything that did the same thing. I tried command line tools to find out what objects were conflicting. I got no results, even though the tools also said replication was broken.

Warning, what I'm about to link to might not be for you! Please do your own due diligence. Once I flipped this regkey, after the next sync, I saw account objects that were conflicting. There was the account from the FSMO server (I think). And additional accounts from our remote sites with SIDs tacked on the end.

I waited a few days to make sure everything settled down. Then a bit of cleanup in removing & adding users/computers and it looks good. I'm waiting a few more days for things to settle down further. Then I'll flip the regkey back. And hope no more conflicts come up that prevent replication. The regkey should not be left in "loose" mode. I remember reading that even putting it into "loose" mode was not recommended.

[mitlyng]

Can confirm it is not working on Windows 10, 11, and Server 2016 to 2022.

[MrTroyH]

This tool is extremely handy, please don't set it to expire. Thank you.

[FL30FL]

Having the same problem, hopefully a we can get a quick fix

[mark-royds]

Another frustrated admin here. Why did this even have a time-limited license in the first place?

[barbarajoost]

Have the same problem. There are meanwhile lots of threads around concerning this. I don't understand why nobody at Microsoft seems to be interested in this problem. They insult their customers with ignorance.

[hadox]

Please fix. I need it for a AD Domain migration

[tinakane]

I would also like a fix for this as we use it in my company as well.

[bene-tleilax-werdna]

Is Microsoft going to grace us with any sort of acknowledgement that a tool that most AD administrators use to check their domain health or is this just going to sit in limbo?

[RussEfarmer]

This is an important tool for our environment and I would very much like it to be usable again.

[benmprojects]

@microsoftopensource Any Update?

[ra-ataka]

Same here, awaiting Microsoft comments

[jackvadan]

Hello, is there any other way to view repliation status of multi forest and child server environment.

[ii-batman]

Hi Everyone, While we wait for a new tool to be released, do you know of a good powershell script that does the same? Thanks M

[janweis]

Please deploy a new license for us @microsoft

Thanks, Jan

[rangaraj73]

@microsoft ,

Could you solve the issue of AD Replication status tool license getting expired.

[mitlyng]

There is a new published date of 7/18/2022 in the download link, testing. Thank you for fixing but please remove the expiration.

[mitlyng]

The new adreplstatusInstaller.msi version lacks a digital certificate so Edge will declare it unsafe. When attempting to install Windows will also give the pop up stating it is unsafe.

[bene-tleilax-werdna]

Hi Everyone, While we wait for a new tool to be released, do you know of a good powershell script that does the same? Thanks M

@ii-batman You could always run the old repadmin /showrepl and repadmin /replsummary in command line, as well as the dcdiag commands.

To add on @mitlyng 's comment - the newly published MSI file still does not work - I removed the previously installed replication status tool and installed the one release on 7/18/2022 and get the same result with the license expiration warning.

@microsoft - this has been an issue for 2 weeks, with the amount of money you charge for server licensing and CALs, there is no reason your customers should be experiencing this issue on a tool many admins use regularly coupled with a total lack of response on your end.

[ii-batman]

Hi Everyone,

I have used the latest version fine, just needs .net 4.8 and I was able to check my DC's with the tool without any issues.

Thanks for the community effort to get up and running again.

[awstew1]

I installed .net 4.8, rebooted, still same error.

[mitlyng]

@chmura-werdna, Can confirm it works on on Windows 10 ENT, 11 ENT, and Server 2016 to 2022.

[awstew1]

have installed it on win10 ent, server 2016 & server 2019 - all running .net 4.8, no luck

[barbarajoost]

For me the new tool works too. It's "knitted with hot needles" because the version number is still 1.0 and it looks further like Windows 7 but it works.

Be aware to unblock the downloaded file before installing it. Edge warned me several times to download this unsafe file and that I must trust it before installing it. Maybe that's the issue for those ones where it doesn't work.

[barbarajoost]

The next time bomb is already implemented. This time the license is only valid until April 15, 2023. This is less than one year. How stupid are this people at Microsoft? What the heck have they planned for this tool?

[Taomyn]

I must be looking at a different download link to everyone else because although the date on the site is 18/07/2022 the version downloaded is still the same one from last year.

I've reclicked the one in the OP on several machines and caches cleared etc.

[awstew1]

This worked for me

https://www.microsoft.com/en-us/download/details.aspx?id=30005

[barbarajoost]

Klick on the download page on "details". There must be the date 7/18/2022. Otherwise you

I must be looking at a different download link to everyone else because although the date on the site is 18/07/2022 the version downloaded is still the same one from last year.

I've reclicked the one in the OP on several machines and caches cleared etc.

Klick on the download page on "details". Under "date published" must be the date 7/18/2022. Otherwise you have a wrong link.

During start the tool should show the build number 3.22.415.100.

[barbarajoost]

The tool is broken again. This time it looks like a problem with .NET. On Windows 10 the start screen appears wirh "initializing" and then - nothing. No event in the eventlog. On Server 2019 the following errors will be logged:

Faulting application name: repl.exe, version: 3.22.415.100, time stamp: 0x62593e89 Faulting module name: KERNELBASE.dll, version: 10.0.17763.3287, time stamp: 0x2637e772 Exception code: 0xe0434352 Fault offset: 0x0000000000039319 Faulting process id: 0x2920 Faulting application start time: 0x01d8cc4a39655838 Faulting application path: C:\Program Files (x86)\Microsoft Active Directory Replication Status Tool\repl.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 505793d3-dee9-45ec-9927-f5d01f148683 Faulting package full name: Faulting package-relative application ID:

---

Application: repl.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: Microsoft.Sirona.PackagingException at Microsoft.Sirona.Packaging.PackageHelper.ValidatePackage(System.IO.Stream, System.String, Boolean, Boolean) at Microsoft.Sirona.Packaging.PackageManager.LoadInternal(System.IO.Stream, Boolean, Boolean, System.String, System.String, Boolean) at Microsoft.Sirona.Packaging.PackageManager.Load(System.String, Boolean, Boolean)

Exception Info: Microsoft.Sirona.PackagingException at Microsoft.Sirona.Packaging.PackageManager.Load(System.String, Boolean, Boolean) at repl.MainWindow.LoadConfiguration(Microsoft.Sirona.Configuration.ConfigurationManager) at repl.MainWindow.SetupSironaComponents() at repl.MainWindow..ctor()

Exception Info: System.Windows.Markup.XamlParseException at System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri) at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri) at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri) at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean) at System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext) at System.Windows.Application.DoStartup() at System.Windows.Application.<.ctor>b__1_0(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at repl.App.Main()

[coppolaf]

Guys, same here!!

my trace is exactly as barbarajoost reported... exactly same errors.... here running on 2012 R2 servers (6 DCs none actually working) if i check replication manually with repadmin /showrepl and repadmin /replsummary it fortunately reports no errors but... checking that with a GUI is simple to analyze than read a long text file!

news?? waiting....

[mbanks850]

The tool is broken again. This time it looks like a problem with .NET. On Windows 10 the start screen appears wirh "initializing" and then - nothing. No event in the eventlog. On Server 2019 the following errors will be logged:

Faulting application name: repl.exe, version: 3.22.415.100, time stamp: 0x62593e89 Faulting module name: KERNELBASE.dll, version: 10.0.17763.3287, time stamp: 0x2637e772 Exception code: 0xe0434352 Fault offset: 0x0000000000039319 Faulting process id: 0x2920 Faulting application start time: 0x01d8cc4a39655838 Faulting application path: C:\Program Files (x86)\Microsoft Active Directory Replication Status Tool\repl.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 505793d3-dee9-45ec-9927-f5d01f148683 Faulting package full name: Faulting package-relative application ID:

Application: repl.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: Microsoft.Sirona.PackagingException at Microsoft.Sirona.Packaging.PackageHelper.ValidatePackage(System.IO.Stream, System.String, Boolean, Boolean) at Microsoft.Sirona.Packaging.PackageManager.LoadInternal(System.IO.Stream, Boolean, Boolean, System.String, System.String, Boolean) at Microsoft.Sirona.Packaging.PackageManager.Load(System.String, Boolean, Boolean)

Exception Info: Microsoft.Sirona.PackagingException at Microsoft.Sirona.Packaging.PackageManager.Load(System.String, Boolean, Boolean) at repl.MainWindow.LoadConfiguration(Microsoft.Sirona.Configuration.ConfigurationManager) at repl.MainWindow.SetupSironaComponents() at repl.MainWindow..ctor()

Exception Info: System.Windows.Markup.XamlParseException at System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri) at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri) at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri) at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean) at System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext) at System.Windows.Application.DoStartup() at System.Windows.Application.<.ctor>b__1_0(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at repl.App.Main()

I am seeing this same error on a 2019 DC.

[MrTroyH]

The solution is to edit the Microsoft.Sirona.dll file as noted by the awesome "Brandhor" in this Reddit post: https://www.reddit.com/r/sysadmin/comments/xpfune/ad_replication_status_tool_broken_again_in_early/ Posted what my dll looks like here(troyheiss): https://community.spiceworks.com/topic/2462722-active-directory-replication-status-tool-broken

[barbarajoost]

Thanks to @MrTroyH ! And to the guy who shared his edited version of the dll on spiceworks. I'm not a programmer or developer. I looked in this tool dnSpy like a pig in a clockwork. But the shared file works.

[ra-ataka]

Cheers @MrTroyH brilliant contribution

[bene-tleilax-werdna]

While I can appreciate the ingenuity of the community for the suggested work-around, whatever happened to the idea that when you pay a company like Microsoft to use their products, there's a reasonable expectation the software company acknowledge and fix said issues when their customers report them? This is an issue reported by a number of system administrators for business customers who continue to be ignored by @microsoft - who has neither acknowledged the latest issue with the tool, nor attempted to fix it in any meaningful way. Nor have they addressed the fact that the license (why is there a license to use this tool?) expires on April 15, 2023.

[schittli]

Most Customer related M$ "Services" like feedback, docs, and UserVoice, is just one thing: a big shame. user feedback is getting ignored for years (google for the next Outlook-Error you'll get and you'll note that the Bug is well known for many years and if you look further, you'll find the information that the bug was reported by customers many times during all those years).

There is just one workaround:

1. Setup Hybrid cloud, e.g. Azure & AWS or Google, which is anyway a great idea to not get locked in
2. For each User SW, always evaluate alternatives. For example, we have just rolled out Cisco Webex for our 750 employees to replace M$ Teams

If enough customers do this, then M$$ will soon get back to being Customer friendly. I know, this probably never happens. Why should they, if they earn billions every quarter?

[gauravelearn]

The solution is to edit the Microsoft.Sirona.dll file as noted by the awesome "Brandhor" in this Reddit post: https://www.reddit.com/r/sysadmin/comments/xpfune/ad_replication_status_tool_broken_again_in_early/ Posted what my dll looks like here(troyheiss): https://community.spiceworks.com/topic/2462722-active-directory-replication-status-tool-broken

Thank you very much. It's very useful.

[cjramseyer]

It's a shame that a company like Microsoft provides a tool that has a certificate that has already expired. The certificate expired September 1, 2022.

The suggested fix above, has resolved the issue

[barbarajoost]

We can now await the next time the tool will no longer work. The license will run out on April 15, 2023.

[MrTroyH]

Yeah, not looking forward to this tool expiring again. I use it nearly daily. I checked the Spiceworks thread and @christope posted recently on March 22nd:

https://community.spiceworks.com/topic/2462722-active-directory-replication-status-tool-broken

one of the team members created his own version of the tool and made it available on GitHub: GitHub - ryanries/ADReplStatus: AD Replication Status Tool

this tool is NOT supported by Microsoft, but could be a good temporary solution until the new official tool is released.

It looks pretty awesome and I'll be checking that out later today.

[barbarajoost]

Thanks for the link.

[ecoidan]

Hello Microsoft!!! Are you there??? Again your tool has expired. Please get the new verison out there. please!