Version 8.3 > Avtivation blew up.
I just got this month's hot fixes on Windows 7. After reboot, I tried to start SSP, but it said it needed to be activated.
So I signed off with my user account and signed on with the admin account. I started SSP and it started fine.
So I signed back on as a user and got the activation message again.
So I signed back on as admin, started SSP and got the activation message again. I activated, but the license for our GfM machine wasn't available. So it grabbed our additional license that we haven't used in a while. But it doesn't have the h.264 and Bible plug ins included (ESV, NIV, NASB). So now I'm stuck.
The questions are
a) Why did Windows updates cause SSP activation to lose it's mind?
b) Where did the GfM license go?
c) What am I supposed to do on a Friday night and we have service tomorrow?
I guess I'll go home and deactivate the license on my laptop and see if I can activate that license here. IT should have all the needed plug ins.
Yuck!
Well, that worked, anyway. I was able to transfer the license (with plug ins) from my laptop to the projection machine at church.
Now I just have to figure out when I'll be able to call GoFish Media to get the licenses straightened out. I have work so I can afford this "hobby" of doing projection. 8-/
But, praise God I have a solution for tonight and tomorrow.
Update: looks like phone support is open until 5:00 PM Mountain time. I can generally get home at 5:00 PM Central time, so they may be a window there. whew!
Glad you were able to resolve this.
It is odd, but certainly possible, that the update caused the key change if it changed the way that devices are enumerated thus changing the system key. I would consider this a rare event.
The really odd thing is that it seemed that at least on the first login it was not affecting all users. Now it does appear that after logging in a second time it was "broken" and that would be expected in this case.
As far as the the "Why" - The root cause from our side is that something in the system devices that are used to ID the system changed, hence the activation change. The "Why" of the OS updated causing that is a mystery.
Do you recall exactly what the activation message said? In this case, what should have happened is that you were notified that there was a change and been offered to apply a temp license - did that not happen?
When I called support on Monday, they indicated that I should have gotten a message about temporarily activating with all the current plug ins, but I did not get that option. I wonder if that was because I was signed on as a standard user, not an administrator?
The fix that was installed was KB4014565.
Greg