I have reported this to Alpha and they went home without resolving it, leaving me and the client stranded, I hope one of you guys have a solution.
The server saying it's Expired we have 5 licences available to us and none of them will hold, every 15 minutes it goes to demo version in the browser and states it's unlicensed. This has just happened out of nowhere.
Its says it's active until next year, 15 minutes later - it's expired.
Thanks Peter.
Update It is fortunate we use Zebrahost for our servers else we would have been stranded, they resolved the issue with their 24/7 support.
Here is the outcome:
Spoke to soon down again.. Zebrahost are back on it.
16 hours now -
The server saying it's Expired we have 5 licences available to us and none of them will hold, every 15 minutes it goes to demo version in the browser and states it's unlicensed. This has just happened out of nowhere.
Its says it's active until next year, 15 minutes later - it's expired.
Thanks Peter.
Update It is fortunate we use Zebrahost for our servers else we would have been stranded, they resolved the issue with their 24/7 support.
Here is the outcome:
Assuming the instances were setup using our standard protocol instance 1 would be .50 instance 2 would be .51 I have bound them in this way.
I have only seen this with one other client but for some reason when Alpha updated last time to the version with the new sessions tab it corrupted the .xml config files which establish the 2 instances. This is why none of your bindings were showing and why your license would not activate properly.
I have recreated the .xml config files, bound the instances as mentioned above, and left the webroot on c:\a5webroot, and everything seems to be working at this point. If you had any changes to the various Alpha settings please log back on and reset them.
I had not previously reported this problem to Alpha because it seemed like such a fluke thing to have happen but Len please let me know if you need any information about it? Out of all the clients we have running multiple instances this has only happened to two at this point.
I have only seen this with one other client but for some reason when Alpha updated last time to the version with the new sessions tab it corrupted the .xml config files which establish the 2 instances. This is why none of your bindings were showing and why your license would not activate properly.
I have recreated the .xml config files, bound the instances as mentioned above, and left the webroot on c:\a5webroot, and everything seems to be working at this point. If you had any changes to the various Alpha settings please log back on and reset them.
I had not previously reported this problem to Alpha because it seemed like such a fluke thing to have happen but Len please let me know if you need any information about it? Out of all the clients we have running multiple instances this has only happened to two at this point.
16 hours now -
Comment