Fences Local License Server Service Issue

from Stardock Forums

We were running a Fences License Server (version 2.12 - yes, its old) running on Server 2008 R2.  I migrated the server over to another server running Server 2019 and if I run the LicenseServiceApp locally it works perfectly fine.  However, when I register it to run as a service like this:

 

LicenseServiceApp.exe action=install

 

The service registers fine, however, it does not actually bind to the port and so obviously it is not working.


The Windows Event Viewer shows this error for the CyrptoLicensingService when I start it:

 

System.IO.FileNotFoundException: Could not load file or assembly 'LicenseServiceApp, Version=9.0.0.0, Culture=neutral, PublicKeyToken=4a3c0a4c668b48b4' or one of its dependencies. The system cannot find the file specified.

File name: 'LicenseServiceApp, Version=9.0.0.0, Culture=neutral, PublicKeyToken=4a3c0a4c668b48b4'

   at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)

   at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)

   at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)

   at System.Reflection.Assembly.Load(String assemblyString)

   at System.UnitySerializationHolder.GetRealObject(StreamingContext context)

   at System.Web.Hosting.HostingEnvironment.CreateInstance(Type type)

   at System.Web.Hosting.ApplicationHost.CreateApplicationHost(Type hostType, String virtualDir, String physicalDir)

   at A.c699fd9982bc616c7034b1cf345df51a0.c72a06687b11280cb7af99771f5b18c9e()

 

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

 

 

Any assistance would be greatly appreciated.

fences
10,987 views 10 replies
Reply #1 from WinCustomize Forums Top

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

AzDude
Stardock Community Assistant

Reply #2 from Stardock Forums Top

Any update from the support team on this issue?  I am still having to manually run the application on the new server.  It worked perfectly fine running as a service on the previous server.

Start11 - Customize the Start Menu and Taskbar in Windows 10/11.
Reply #3 from Stardock Forums Top

Hello,
I have forwarded your questions/problems again to the Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate you feedback and patience.

Thank You,
Basj
Stardock Community Assistant.

Reply #4 from Stardock Forums Top

Hello,

Sorry to hear you are having trouble.

The service registers fine, however, it does not actually bind to the port and so obviously it is not working.
End of quote

The server will not run as a service on any Win server version greater than 2008. 

We did not write that server and your issue is one of the reasons we no longer offer it.  If Internet is available to your end users, so they can activate via it, we have another solution for you.

If so, you can place a ticket here to start the process:

https://esupport.stardock.com/index.php?/Tickets/Submit

Note, however, that Fences 2 is no longer sold (or supported).  Any new deployment model you use will have to be with a purchase of Fences 3.  You can work up a quote here that will include volume discounts:

https://store.stardock.com/corporatepricing

Sean Drohan
Stardock Support Manager

Reply #5 from Stardock Forums Top

Hey Sean,

 

Thank you for the reply.  Our fences is deployed in a non-persistent virtual desktop environment, meaning that on a regular basis the computers that fences is installed on would be deleted and recreated.  Is there a deployment model that would support this environment?

 

Reply #6 from Stardock Forums Top

Imadsen,

Quoting lmadsen, reply 5

Thank you for the reply.  Our fences is deployed in a non-persistent virtual desktop environment, meaning that on a regular basis the computers that fences is installed on would be deleted and recreated.  Is there a deployment model that would support this environment?
End of lmadsen's quote

Yes but some deactivation scripting on log off would have to happen (we have clients that do).  Also, if that failed to happen (PC instance blew up or was destroyed before log off), you can true up activations with this process:

https://forums.stardock.com/486311/accounts-and-activation-support-faq#deactivateproduct

Sean Drohan
Stardock Support Manager

 

Reply #8 from Stardock Forums Top

Quoting lmadsen, reply 7

Okay, thank you.
End of lmadsen's quote

You are most welcome.

If you needed a test key, create that ticket and I can work with you on it.

Sean Drohan
Stardock Support Manager

Reply #9 from Stardock Forums Top

I had a similar problem at the beginning of my career and I didn't know how to deal with it at all. Since I know nothing about programming, I could not even think that my problem was the low quality of the hosting provider. I've written a message to the support service, but haven't received any response. While looking for alternative help I came across 28msec.com, a site that provides a list of reliable hosting companies. I figured what was the problem and delt with it. Everything went back to normal. You would never guess that the problem could be in the hosting provider sometimes.

Reply #10 from Stardock Forums Top

Quoting AmberWilkins, reply 9

I would like to know how soon I can get help from the support service?
End of AmberWilkins's quote

Email support is baked into all corp products. The SLA is 24 business hours but it is almost always answered in less time (by me).

Sean Drohan
Stardock Support Manager