MxServe™ is a Windows Service that runs on every Token Host computer.  It is the guardian of the Token Pool. The MxSuite uses Windows .NET Remoting over a TCP Channel for inter-process communication between MxSuite applications and MxServe. The default port is 1234. (This can be changed.) If your network environment supports and does not block this protocol, then MxVDev will be able to retrieve tokens from MxServe.

You should only run your primary instance of MxServe at any time.

hmtoggle_plus1Mx-Serve Log Files

Here are paths to the log folder for MxServe when it is run as a SYSTEM service (by default it is):

Operating System

Location of Log Files

Windows XP

\Documents and Settings\LocalService\Application Data\MicroMax\MxServe\Logs

Vista, Windows 7, or newer
(32 bit)

\Windows\System32\config\systemprofile\AppData\Roaming\MicroMax\Logs

If not found in this folder, check the 64-bit folder below.

Vista, Windows 7, or newer
(64 bit)

\Windows\SysWOW64\config\systemprofile\AppData\Roaming\MicroMax\Logs

If an error occurs in the MxServe service, a file named MxServe.log is created and the error written to it.

Leasing Log

Leasing log files show information about token requests, such as who took them, who tried and failed, and who was denied access. Leasing log files names have to this format: <port>_<yymmdd>_<hhmmss>.log. <yymmdd> and <hhmmss> represent the date and time the service started. For example:

1234_130402_080210.log

Transaction Log

Whenever tokens are lent or manually returned to a token pool, the transaction log is updated with relevant information to show what actions have been taken. This log is not updated when an item expires and the tokens are returned to the pool automatically.  The file name has the format: <port>Transactions.csv and is located in the MxServe install folder, for example:

C:\Program Files (x86)\MicroMax\MxServe\1234Transactions.csv

Token Pool Log

The file name has the format: <port>TokenPool.log and is located in the MxServe install folder, for example:

C:\Program Files (x86)\MicroMax\MxServe\1234TokenPool.log
hmtoggle_plus1Check that the MxServe Service is Running

The following errors usually indicate that the service is stopped or was not installed:

Mx-Serve-NotConnected

ClockMalfunction

CouldNotEstablish

The MxServe service is installed when the MxServe software is installed. If MxServe is not installed, see Installing the MxSuite.

To check that the MxServe service is running, press the Windows key + R, then run services.msc:

Run-Services

Services

If the Status is not Started, click "Restart the service."
hmtoggle_plus1Mx‑Serve Messages (Output Tab)

Use the Output tab to see messages from MxServe.

License-OutputTab
hmtoggle_plus1Releasing Tokens

By default, when MxVDev (or other MxSuite component such as MxTransIt or MxVDiff) starts, it gets a 120-second lease on a number of tokens.  It refreshes its claim on those tokens by contacting the Token Host computer every 60 seconds, extending the lease up back to 120 seconds each time.

Tokens are returned in a number of ways:

•If the MxSuite component is closed normally:

oThe tokens are returned to the pool immediately. The tokens become available immediately to other users.

•If the network connection is lost:

oThe server cancels the existing tokens leases for that client 120 seconds after the client last refreshed its lease. After that, the tokens are available to the next user.

oIf the Client re-establishes connection to the server in the 60 to 120 second window, it reclaims the tokens that it had leased. It does not attempt to lease new tokens.

•If MxVDev is terminated abnormally (by using the Task Manager for example) and restarted, then new token leases will be sought. The server will cancel the existing token leases for that client 2 to 3 minutes after the client last refreshed its lease.
hmtoggle_plus1Lost Licenses

There are cases where your system may lose a license for an MxSuite product.  In general this only happens with node-locked temporary licenses, and if a program or person modifies (or access in some way) the license files. If you need to replace a license, follow  the procedure for Establishing a Token Pool to acquire a new Site Code and License Key.

Here are a few notes which may help you figure out what happened:

•Temporary licenses are more vulnerable because they are designed to expire, and are more easily replaced.

•The MxSuite license files are stored in C:\Program Files\MicroMax\MxServe. You should not modify any files in this folder.

•Some of these files are created as system files.  You can see them only if you enable the setting under File Explorer->Tools->Folder Options->View.  You will find several files that begin with MXVDEV, including:

oMXVDEV.rst - Restriction File

oMXVDEV.ent

oMXVDEV.key - Site Key File

oMXVDEV.41s

•The main cause for lost licenses is anti-virus software. You should configure Anti-Virus software to exclude files in the MicroMax\MxServe folder that match the following filters:

oMxVDev*

oCRP*

•An out-of-memory condition can cause fixed licenses to be corrupted. See Memory Usage.

•If you receive the License Engine State Message: RESTRICTION FILE MOVED, it indicates that License Server detected that the file MXVDEV.rst was manipulated (moved, deleted or accessed) by another program.  A similar message may be seen if the Site Key File is manipulated by a program other than the license server.

•When trying to validate a new License Key you get Error 103.  The message is AUTHORIZATION BAD SITEKEY CRC and REPLY FROM NETWORK DRIVER IS BAD.  This has been seen after automatic adjustment for daylight savings time.  The problem is that a file in C:\Windows\System32 called esnecil.ind is corrupt.  Delete this file and regenerate the Site Code.  You will now need to request a new License Key, but the next attempt to validate will work.
hmtoggle_plus1Resetting the License Files

Only in the event of license file corruption should this be necessary. It can be dangerous because loaned tokens cannot be returned to the pool. We recommend that you reset your license only if instructed by the MxSuite Support Team.

1.Stop the MxServe service.

Services

2.Delete <port>etats.loop and <port>etats.loopA from the MxServe installation directory. Normally MxServe is installed in one of the following folders:

•C:\Program Files (x86)\MicroMax\MxServe

•C:\Program Files\MicroMax\MxServe

Note: These files should not be deleted or modified unless you are resetting your licenses.

3.Start the MxServe service.

4.After the service has been restarted, generate a new site code and send it to mxsupport@danlawinc.com for replacement tokens.

If it is necessary to reset the license and clean up all license files, use this procedure:

1.Stop the MxServe service.

2.Stop the Crypkey License service.

3.Look in Task Manager for instances of crp32002.ngn.  Kill any instances.

4.In the folder: C:\Program Files\MicroMax\MxServe, delete the following files:

•MXVDEV.rst - Restriction File

•MXVDEV.ent

•MXVDEV.key - Site Key File

•MXVDEV.41s

•MXVDEV.tb2

Note that some of these files are System Files. You can see them only if you uncheck the option called 'Hide protected operating systems files' under File Explorer->Tools->Folder Options->View

5.In the folder c:\Windows\System32 delete the files:

•esnecil.ind

•esnecil.nlp

6.Start Crypkey License service.

7.Start MxServe service.
hmtoggle_plus1Command Line Parameters

You can use the following command line parameters to control the way the MxServe Monitor starts and runs:

/min - starts the manager minimized

/notray - MxServe Monitor will not run from the tray, so closing the form also closes the program

/parallel, /p - allows more than one instance of MxServe Monitor to run at one time on the same machine.

hmtoggle_plus1Mx-Serve 1.0

This information applies only to versions of MxServe previous to 2.0.

If the MxVDev process on a client computer is killed (or an unexpected crash takes MxVDev down) the licenses are not returned instantly. A timeout period has to expire. You can cause the license to become available immediately by deleting the file MxVDev.tb2.  This file is located in the same folder as the other license files:

•For floating licenses - go to the following folder located on the License Server: C:\Program Files\MicroMax\MxSuite License Manager\ServerFiles

•For fixed licenses - go to the following folder located on the Client PC: C:\Program Files\MicroMax\MxVDev\bin

This information applies only to versions of MxServe previous to 2.0.

The Crypkey Service that runs on the License Server can be manipulated from the command line as follows:

SetupEx.exe [/S /U /F /D]

< No Options>

Installs the Crypkey service. (The License Service will not install if you rerun Setupex.exe after a deinstall, but before rebooting.)

/S

Provides a 'silent mode' for command line automation of the SetupEx utility.  Notification dialog boxes are not displayed.

/U

If you wish to uninstall even if there are other programs using the service, you can use this command.   This leaves the other registered directories without a Service to serve them. It is recommended that /D be used in release versions, and /U be used for test purposes only.

/F

Forces an install if a newer version is already installed

/D

This uninstalls the service. You receive a notification that a reboot is required before another install can be done.

If you are uninstalling, you need to reboot before the uninstall is complete.

More information is available in the file README.TXT

This information applies only to versions of MxServe previous to 2.0.

You may want to perform a step by step installation of the Crypkey service to ensure that each step is successful, or determine which step fails.  Here are the command line steps.  They should be performed from the folder: C:\Program Files\MicroMax\MxServe

net stop "MxServe"

net stop "Crypkey License"

sc delete "CrypKey License"

cks -overwrite -times=all

copy crypserv.exe c:\windows\system32

copy ckldrv.sys c:\windows\system32

copy ckrfresh.exe c:\windows

copy ckconfig.exe c:\windows

copy setup_ck.exe c:\windows

Rem If access is denied then try attrib c:\windows\setup_ck.exe; attrib -r c:\windows\setup_ck.exe

copy setup_ck.exe c:\windows

copy setup_ck.dll c:\windows

sc create "CrypKey License" binpath= "c:\windows\system32\crypserv.exe" start= auto

net start "CrypKey License"

net start "MxServe"

Note that on Windows 2000 Server the 'sc' command is not available, and it is necessary to reboot the server in order to install a new service over a deleted service.

This section does not apply when using MxServe 2.0 or newer.

The only cause of license issues is adverse reactions to MxSuite license files by anti-virus software.  To avoid problems, configure your anti-virus software to ignore certain files in the folder: C:\Program Files\MicroMax\MxServe. The files to be ignored are:

•MxVDev*

•CRP*

Note that some of the files that begin with MxVDev are hidden system files.  If you plan to explicitly exclude each file, ensure that they are visible first.

 

 

Related Topics:

MxSuite Files and Folders

Managing Token Pools

Troubleshooting Installation

How Licenses Work