Adaxes Service becomes unavailable multiple times a week

Question

Hello,

We have been using Adaxes for a couple of weeks now. We have observed that occassionally the Softerra Adaxes Service errors out and the service stops working. This usually requires us to login and restart the service to resolve the problem. Ocassionally the issue has been able to correct itself after some small downtime. Can we identify why this happens to being with? I have shared some screenshots of the logs when the service errors out and when it resolves itself.

Service Stopped Event Log -

Service Started Event Log -

This is the error the team is getting when running scripts and being unable to connect to the service -

Answer 1

Hello,

For troubleshooting purposes, please, provide us with a screenshot of the Multi-server environment dialog. The dialog displays how many Adaxes services you have and what their versions are. For information on how to view it, see https://www.adaxes.com/help/MultiServerEnvironment.

Also, please, provide us with a copy of the Adaxes Event Log in EVTX format. For information on how to view the log, have a look at the following help article: https://www.adaxes.com/help/ServiceEventLog.

Please, send the details to support@adaxes.com. Any additional details will be much appreciated.

Comments

Hello,

I have sent an email a couple days ago regarding this. I messaged Serge via email regarding this and shared the event logs. The issue happened again on Sunday night The event logs indicate a fatal error exception and then the service restarting a minute afterwards.

Is there any other information I could provide for this. The service seems to hit this fatal error once every couple of weeks and causes the service to restart.

---

Hello Kole,

We replied to your email on January 3 and received no response. Please, check your spam/junk folder and follow the recommendations. If you did not receive our email, check your filters and get back to us in the ticket. We will resend the email.

It is hard to see the text in your screenshots (the text is unreadable), but according to the general view, there were no such errors in the Event log you provided.

---

We are having similar issues. I have sent in the Event Log and I was told that a port was being blocked.

I am not sure how a port is becoming blocked all of a sudden, and I have asked which event record was indicating this, but so far I have had no response.

My Support Ticket # is 2025021910000164 if you need to view the log.

I just found two error in the log:

2025-02-19 3:23:48 Application: Softerra.Adaxes.Service.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Management.Automation.Runspaces.RunspaceOpenModuleLoadException at System.Management.Automation.Runspaces.LocalRunspace.DoOpenHelper() at System.Management.Automation.Runspaces.RunspaceBase.CoreOpen(Boolean) at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.CreateRunspace() at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.ServicePendingRequests(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.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch()

2025-02-19 3:23:49 Faulting application name: Softerra.Adaxes.Service.exe, version: 3.16.21906.0, time stamp: 0x65202108 Faulting module name: KERNELBASE.dll, version: 10.0.20348.3089, time stamp: 0x2841fd35 Exception code: 0xe0434352 Fault offset: 0x000000000003f47c Faulting process id: 0x1680 Faulting application start time: 0x01db7ca016dec40b Faulting application path: C:\Program Files\Softerra\Adaxes 3\Service\Softerra.Adaxes.Service.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: f8c56d20-6f4d-4bc8-993f-759fc6607b37 Faulting package full name: Faulting package-relative application ID:

---

Hello Joe,

As we mentioned previously, there are no log records pointing specifically to the fact that some port is blocked. However, there are a lot of log records like below. As long as the Adaxes service was running, the only option for such a thing to occur is something blocking the connection. The errors you pointed out cannot cause such a behavior.

Failed to get the Web Interface configuration due to the following error: Softerra.Adaxes.Adsi.Exceptions.SelectNearestServiceException: Adaxes service connection failed.
   at Softerra.Adaxes.Web.Infrastructure.Common.NoCredentialDirectoryObjectProvider.GetAdaxesService()
   at Softerra.Adaxes.Web.Infrastructure.Common.DirectoryObjectProvider.GetWellKnownObject[T](WellKnownDirectoryObject alias)
   at Softerra.Adaxes.Web.App.Configuration.UseCommonSignInSettingsModifier.GetCommonSignInConfig()
   at Softerra.Adaxes.Web.App.Configuration.UseCommonSignInSettingsModifier.ModifierChangesTracker.IsUpToDate(Object stateSnapshot)
   at Softerra.Adaxes.Web.Core.AdaxesConfiguration.WebInterface.Provider.WebUIConfigurationProvider.IsModifiersCacheUpToDate(WebUIConfigurationModifiersCache lastKnownCache, WebUIConfigurationModifiersCache& newCache)
   at Softerra.Adaxes.Web.Core.AdaxesConfiguration.WebInterface.Provider.WebUIConfigurationProvider.CheckModifiersCache(Boolean forceCheckCache)
   at Softerra.Adaxes.Web.Core.AdaxesConfiguration.WebInterface.Provider.WebUIConfigurationProvider.GetConfiguration(String configurationName, GetConfigurationOptions options)
   at Softerra.Adaxes.Web.App.Core.Controllers.HomeController.Index(String configurationName)

---

Can you address the following error, which is An Adaxes module that failed “The process was terminated due to an unhandled exception” which means an error in the code.

The reason the Adaxes service is not running is because it failed. If a port was blocked it might create a communication problem, but it should not cause the service to terminate.

This is a bug in the Adaxes code.

2025-02-19 3:23:48 Application: Softerra.Adaxes.Service.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Management.Automation.Runspaces.RunspaceOpenModuleLoadException at System.Management.Automation.Runspaces.LocalRunspace.DoOpenHelper() at System.Management.Automation.Runspaces.RunspaceBase.CoreOpen(Boolean) at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.CreateRunspace() at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.ServicePendingRequests(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.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch()

---

Hello Joe,

Your assumption is incorrect. Neither does the error mean that there is a bug or an issue in the Adaxes code, nor is it related to Adaxes itself. The fact that Adaxes service got stopped is just the result. Generally, something happened in Windows or .NET backend, it caused the exception that forced .NET Framework to stop Adaxes service. The fact that Adaxes service was stopped produced the errors like the one from the previous post. Unfortunately, we cannot be more specific. We did see such errors before, but never got feedback on them.