DavidH asked a question.
Since the upgrade to SLM 9.18 I've been seeing a lot of this:
The error in the log seems to be similar to a problem we were getting a few versions back (see below). I think it was around SLM 9.14 (ish?) that we struggled a lot and we'd find that SLM was down every morning, this looks similar to me.
Just wondering if anybody else is having the same problem?
In case anybody is interested, here is the error from the log:
An error occurred while attempting to automatically activate registration 'Activator = RebusMessageBus (ReflectionActivator), Services = [SnowSoftware.LicenseManager.MessageBus.IMessageBus, AutoActivate], Lifetime = Autofac.Core.Lifetime.RootScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope'. See the inner exception for information on the source of the failure. --->
...
INNER EXCEPTION: An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = RebusMessageBus (ReflectionActivator), Services = [SnowSoftware.LicenseManager.MessageBus.IMessageBus, AutoActivate], Lifetime = Autofac.Core.Lifetime.RootScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope --->
An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = IBus (DelegateActivator), Services = [Rebus.Bus.IBus], Lifetime = Autofac.Core.Lifetime.RootScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope --->
Could not resolve Rebus.Transport.ITransport with decorator depth 0 - registrations: Rebus.Injection.Injectionist+Handler (See inner exception for details.) (See inner exception for details.) (System.Object Activate(System.Collections.Generic.IEnumerable`1[Autofac.Core.Parameter]), Autofac)]
Sorry for not really being a relevant answer to your question, but 13 days between release of 9.17 and then 9.18, what is the point of that? How are you able to deliver quality? You will not even be able to measure it with this short cycles. Being a system that you use to ensure compliance and being the proof in audits, how can you trust it when there is always a new version or some SRS stuff to fix things?
/Preben
Hey @David Hobbs,
Spent a lot of time looking at Snow Activation (for uh, interesting reasons). Snow does an activation check every morning at around about the same time, are you seeing the error in the log start at the same time every morning?
If so, it might be worth getting an offline activation key and putting that into the system, and checking if it' still happens. I had this on my demo environment on I believe 9.14 as you've mentioned, and the only way I got around it was offline activation and blocking *.snowsoftware.com in my hosts file to go to localhost to stop it activating over the internet.
Whatever is happening during the activation, the response it's getting back isn't what it's expecting and it seems to cause the entire thing to fall over.
Why it does an activation check every single morning, I'll never understand. Some of our platforms are even doing it hourly.
Laim
Hey @Laim McKenzie
That's really interesting. It makes total sense, I think we're seeing this error whenever the first person tries to use SLM in the morning. After that it goes offline for an hour or so and then starts working again. It felt very much like the behavior we had at the start of the summer. I didn't realise we could get an offline activation key. Did you have to raise a support ticket for that? Thanks!
Regards, David
Hi David,
yes, raise a support ticket for this and add your License key and the Hardware ID visible in Web Configurator.
Regards, Axel
Thanks @Axel Lamparth will do.
The issue has came back but with lower frequency. Still very annoying.
My recommendations is for one who experiences the same error: check the current log file under C:\Program Files\Snow Software\Snow License Manager\Web\Logs\Application while you have the inaccessibility error. Then open a session with your favourite web browser in Private mode. This is a way for me to get around. I hope it helps for others.
Yes, same for us, we have a ticket open for it. I will try the 'Private' mode next time, in case that helps. We moved our DUJ so it starts 3 hours earlier, I don't think it solves the problem, but it means the problem doesn't happen during working hours in my timezone. Thanks.
Hi,
We don't have that version so I'm unable to give you any feedback on this, but I would recommend you to update your SLM to the v.9.20.1 or newer because of the High vulnerability that's present in previous versions like yours (more info here: https://community.flexera.com/s/feed/0D5690000BwjZIhCQM).
So by doing that you could solve your issue as well as improving your security posture :)
Hope this information was helpful.
Thanks, it's good to mention that. But we're already on SLM 9.21 so that vulnerability is not a problem for us.
I got an answer from our support ticket about this. Apparently there's a PRB for this problem (PRB# 04582261) and it's related to the NATS Service. Snow Support noticed that there were errors in our Event Log from the NATS Service, so they think that's the root cause of the problem. I'm experimenting by scheduling the NATS service to restart during the night, maybe that will help. Hopefully the PRB will result in a fix though.