AnsweredAssumed Answered

SRS license error

Question asked by DavidHobbs

on Dec 3, 2018
Latest reply on Dec 21, 2018 by Samuel

Like • Show 2 Likes2
Comment • 11

Hello!

We've got a high priority ticket open with Snow Support about this ... but it's taking a while, so I thought that I'd reach out to the community in the meantime. Perhaps we're not the only ones to have this problem.

Recently, we've noticed that we cannot sync our SRS database from our SLM server. We get this "license validation" error in SUS:

It definitely hasn't been like that since March! The date seems somewhat misleading. But I don't think the SRS sync is working because of that.

Does anybody else have this problem? Or does anybody have any advice?

Thanks, David

DavidHobbs

Dec 6, 2018 2:08 AM

Correct Answer

Getting a new SRS license key from Snow Support solved the problem. We owe thanks to Geoffrey Macquet for helping to get it resolved (thanks Geoff!). After installing the key, we had to do a massive SRS sync, which took quite a long time ... but it's all back to normal now.

Thanks everybody!

See the reply in context

No one else had this question

Outcomes

11 Replies

geoffrey.macquet Dec 3, 2018 3:53 AM
Mark Correct
Correct Answer
Hi David,
do you have any more information in the (debug) log?
You can check within SMACC the last time you have gotten SRS updates: Open up Software recognition -> Application definitions, right click any column in the bottom left window and open the "column chooser". Add 'Created Date' and drag it to the window - you should see the latest created applications with a recent date.

/Geoff
2 people found this helpful
Like • Show 2 Likes2
Actions
- DavidHobbs @ geoffrey.macquet on Dec 4, 2018 2:24 AM
  Mark Correct
  Correct Answer
  Hi Geoffrey,
  
  The SUS log doesn't actually give us much more information, it says:
  
  2018-12-04 03:15:23,359 [1] WARN SnowSoftware.Srs.Client.SrsHarvestManager [(null)] - License has expired! Expired 3/31/2018 12:00:00 AM.
  
  The most recent "Globally Generated Application" in our SMACC is 21st November, so we've been cut off from SRS for a few weeks now. Let's hope that Snow Support can get this sorted soon. I will chase them up.
  
  Thanks for your help, David
  Like • Show 0 Likes0
  Actions
  - geoffrey.macquet @ DavidHobbs on Dec 4, 2018 3:26 AM
    Mark Correct
    Correct Answer
    Hi David you absolutely seem to be cut off from SRS sync. I've informed the assigned engineer as well the back office to have this sorted out asap.
    /Geoff
    1 person found this helpful
    Like • Show 1 Like1
    Actions
    - DavidHobbs @ geoffrey.macquet on Dec 5, 2018 2:30 AM
      Mark Correct
      Correct Answer
      Thanks Geoff, I really appreciate your help. David
      Like • Show 1 Like1
      Actions
stuart.lee Dec 3, 2018 5:15 AM
Mark Correct
Correct Answer
Hi David

I had the same issue occurring at one of our customers in the last couple of weeks, it was working fine on November 20th 2018 and then after that it started saying that the SRS license key had expired in January 2017, despite being used without issue for over 18 months and maintenance still being valid.

2018-11-27 23:07:28,309 [1] WARN SnowSoftware.Srs.Client.SrsUpdateManager [(null)] - License has expired! Expired 1/31/2017 12:00:00 AM.

When I raised a ticket, the support reply was that the License key that had been working wasn't associated with the customer in the SRS license key database and gave me a license key that was one for the customer that we had originally been given more than 2 years ago and had several other SRS keys since then. So I was puzzled too.

The key they said should work did, but I'm not sure clear as to why it all occurred in the first place

Stuart
3 people found this helpful
Like • Show 3 Likes3
Actions
BMEpsilon Dec 3, 2018 2:55 PM
Mark Correct
Correct Answer
Hi David,

I have the same issue currently and they gave me a new license key. My SRS is still not working properly and I've been dealing with this for 3 months. I pushed for a conference call to have them walk me through the process and trouble shoot the issue before we ended the call. I should be up an going soon.
1 person found this helpful
Like • Show 1 Like1
Actions
DavidHobbs Dec 6, 2018 2:08 AM
Unmark Correct
Correct Answer
Getting a new SRS license key from Snow Support solved the problem. We owe thanks to Geoffrey Macquet for helping to get it resolved (thanks Geoff!). After installing the key, we had to do a massive SRS sync, which took quite a long time ... but it's all back to normal now.

Thanks everybody!
1 person found this helpful
Like • Show 2 Likes2
Actions
- geoffrey.macquet @ DavidHobbs on Dec 6, 2018 3:34 AM
  Mark Correct
  Correct Answer
  Glad it worked - you're most welcome! Must've been a hiccup at our end, but that is now fixed
  2 people found this helpful
  Like • Show 2 Likes2
  Actions
andreas.leeraar Dec 6, 2018 9:41 AM
Mark Correct
Correct Answer
Had the same issue. The SRS License did show green/validated in Snow Web Configurator but got the same error in the logfile stating the license was valid to a date somewhere last year.
Very strange if you ask me as it worked until the end of November 2018.

Do keep in mind that if you've been cut off for some days and there has been a lot of application updates since then that your Daily Update Job can take considerably longer than normal.
3 people found this helpful
Like • Show 2 Likes2
Actions
- DavidHobbs @ andreas.leeraar on Dec 7, 2018 1:30 AM
  Mark Correct
  Correct Answer
  Hi Andreas,
  
  It's comforting to know when we're not the only ones, thanks! This was quite a strange one...
  
  After fixing it with the new license key, our SRS update did take a long time! I actually sat and monitored it, because I was afraid that it might timeout. But it was fine, it just took a long time to bring us up to date again.
  
  Thanks, David
  2 people found this helpful
  Like • Show 1 Like1
  Actions
Samuel Dec 21, 2018 3:58 AM
Mark Correct
Correct Answer
I assume that, as a result of this glitch, we had a few Licenses that were left hanging, still pointing to an old ApplicationID.
The consequence is that our recently purchased Windows Server 2019 Standard and Datacenter licenses could not be viewed or edited anymore in SLM.
If you think you might have licenses with this issue and you feel confident with querying your database, you can look for such licenses in Snow by running this query that Snow Support support provided to us:
SELECT * FROM SnowLicenseManager.dbo.tblLicense
WHERE ApplicationID NOT IN (
SELECT ApplicationID FROM SnowLicenseManager.dbo.tblApplication
)
If that brings some records, contact Snow Support so they can give you a fix.
1 person found this helpful
Like • Show 1 Like1
Actions

SRS license error

Outcomes

Related Content

Recommended Content