WAsP 11: Could not create the licence server

[CharlieBra7o]

* OS: Windows 10 Pro N (64 bit) - fresh installation
* WAsP: both 11.0 (C) and 11.4 (E)

* Internet access: existent (no proxy)
* Firewall/Anti-Virus: disabled

The installation (both versions) did not give me any errors. However, I am getting the below error when trying to run WAsP for the first time. The error message window is only visible when I run Wasp11.exe as admin - otherwise the splash screen flashes for a second and then the program terminates with code 0.

Same behavior occurs on another Windows 10 machine. On a third one it opens just fine without error. Not really sure what the issue here might be...

------------------------------------------------------------------------------------
Exception report produced at 2016-01-10 21:20:03

Local exception: Could not create the licence server raised at: 2016-01-10 21:19:48
2016-01-10 21:19:48: Message added: Could not refresh the licence information
2016-01-10 21:19:48: Exception raised in: Rvea0176: cLicenceInformation:Refresh
2016-01-10 21:19:48: Message added: Could not refresh the licence status
2016-01-10 21:19:48: Exception raised in: WAsP: cLicenceInformation:Refresh
2016-01-10 21:19:48: Message added: Could not display the splash startup window
2016-01-10 21:19:48: Exception raised in: WAsP: fNoLicenceSplash:DisplayAndPerformLicenceCheck
2016-01-10 21:19:48: Message added: Could not start the application
2016-01-10 21:19:48: Message added: Please contact the WAsP team at Risø for assistance
Latest thread started in:
------------------------------------------------------------------------------------

[Marko]

Hi,


WAsP startup fails here as neeeded prerequisite is not enabled by default in latest Windows Operating system beginning from Windows 8.


So could you please follow this.
Run "Turn Windows features on or off" function and check if .NET Framework 3.5 is turned on. If it is not please follow these steps:


-uninstall WAsP
-enable .NET Framework 3.5
-install WAsP


WAsP should work fine now.


Kind regards,
Marko

[CharlieBra7o]

Thank you for the quick answer! I thought that maybe a dependency was missing, but could not find anything about that on the website... Installing .NET 3.5 fixes the problem. Reinstalling WAsP was not necessary though. Thank you!

[Keegan]

I had this same issue but my .NET Framework 3.5 was already enabled.

I disabled and re-enabled the .NET Framework 3.5 and uninstalled and re-installed WAsP.
However, I get the same error.
What else can be done to resolve this issue?

 

Keegan

[Rogier]

Hi Keegan,

For license issues it is probably better to use the form on the website:

https://www.wasp.dk/support

because we can check your license status there.

Regards

[Frank Weber]

Hi,

I ran into this problem with WAsP 11 and also WEng 3.1 the first time in 2023. I am running both programs from within WindPro and, when contacted, the WindPro support advised this:

"Open the Windows update history. Please check whether an update with the number KB5011048 has been installed in the LAST category. If so, please uninstall it using the link at the top of the same window. Then restart your computer and see if this has helped.

Background: This update causes the described behaviour in some (but not all) users. We do not yet know what is causing this, except that it is probably related to the contact between windPRO and WAsP." --- citation end ---

As I found out, the Microsoft .NET Framework updates are indeed the culprit: when I delete these updates, WAsP 11 and also WEng 3.1 again recognise my licence, regardless if I start them individually or WindPro is calling them. That is, alas, not really a proper fix since Windows keeps installing these updates, along with others, like security updates. And after each new update the licence check fails again during start of WAsP 11 and also WEng 3.1. 

Also in 2023, I have had a call with WAsP support; they said that WAsP 12 and WEng 4 and higher do not have this problem with the Windows  Microsoft .NET Framework updates. Can I ask if anybody knows this to be truly the case?

Thank you, Frank

Edited 12 hours ago by Frank Weber