Skip to main content

Is there a place where I can find the meaning of the different "Errno" for "ASLM: Semaphore failures"?

In this particular case I have a customer that reports that he gets "Errno=1008" after a Windows upgrade - can't find anything around 1008 anywhere...

Is there a place where I can find the meaning of the different "Errno" for "ASLM: Semaphore failures"?

In this particular case I have a customer that reports that he gets "Errno=1008" after a Windows upgrade - can't find anything around 1008 anywhere...

If the message is accurate, the "Errno" value ought to be a Windows error code on Windows, or a system errno value on UNIX.

Windows error numbers are documented in various places, such as the WinError.h header file that comes with the Windows SDK or any of the Microsoft C compilers. Windows error 1008 is ERROR_NO_TOKEN: "An attempt was made to reference a token that does not exist."

So either this 1008 is not, in fact, a Windows error number, but something that is meaningful only to people with access to the ASLM source; or it's ERROR_NO_TOKEN, which is meaningful only to people with access to the ASLM source.

In short, you need to contact MF support to raise an RPI.


Is there a place where I can find the meaning of the different "Errno" for "ASLM: Semaphore failures"?

In this particular case I have a customer that reports that he gets "Errno=1008" after a Windows upgrade - can't find anything around 1008 anywhere...

The 1008 Error is an internal ASLMF error code.

The code indicates that the file is locked by another process and licensing can not open.

I am not sure why upgrading windows would produced this error, although its not a scenario we have tested.

I would suggest deleting the file "c:\\mfaslmf\\semfile" or were ever licensing is installed on the machine.

Then copy the file from the product install directory "Server X.X\\bin\\semfile" back into the mfaslmf area.