It depends on what you are wanting to achieve. Here are the factors
While an order is being picked, the pick is stored in the physical scanner that is being used. Provided that they use the same scanner, they can continue scanning the next day.
Symptoms:
After installing ASPluris, the scanner may show an error message saying:
Client found response content type of ‘text/htim; charset=utf-8’, but expected ‘text/xml’.
When running the following URL https://localhost:5172/ in the browser on the PC where ASPluris is installed, the following error may be displayed:
HTTP Error 500.21 - Internal Server Error Handler "StaticFile" has a bad module "StaticFileModule" in its module list
Solution:
Go to the “Turn Windows features on off” in the programs and features section of the Windows Control Panel.
Untick the default document option and press OK.
Go back to the “Turn Windows features on off” in Programs and Features and tick the following items:
on Windows 10, or
on Windows 7.
Click the OK button, and once completed, open IIS and navigate to ASPluris V2.3, then click on the restart button.
ASPluris does not restrict orders by time. Instead, the system downloads all orders that have not been completed. Uncompleted orders are those that have one or more lines that have not been picked.
You will not normally need to perform a full reset on your barcode terminal. You should contact ASP before doing so.
Resetting the terminal will definitely cause any un-submitted data to be lost, and it cannot be recovered. However, data already submitted to ASPluris will not be lost, and programs and settings that are stored in the Flash ROM should be unaffected.
Use the stylus to press the reset button on the back of the terminal. This starts the reset operation. Do not use a toothpick or pencil or other sharp object whose tip may break off the reset button.
Because the ASPluris Service is a system program, the ASPluris configuration file cannot be changed unless your text editor is running in Administrator mode.
The easiest way to do this is to right-click on your editor’s icon and select Run As Administrator from the menu that pops up, then open the ASPluris configuration file and make your changes.
Unfortunately, some text editors do not detect this problem, and simply don’t save your changes instead of displaying an error message.
If any hardware or network changes have been made on your PC/server, the program may detect this and create a different Hardware Finger Print, which will require a new (re-activation) key to be entered.
Yes. ASPluris is compatible with Windows Vista and later desktop operating systems, and Windows Server 2008 and later server operating systems.
ASPluris is not compatible with Windows XP or earlier, or Server 2003 or earlier.
A CAL is a Client Access Licence. You need one CAL for every barcode terminal that you will use at the same time.
The ASPluris server has a “pool” of licences (ie CALs). Each time a terminal logs in, the server checks first to see if that terminal has already been granted a licence. If it has, the terminal is allowed to log in. If not, the server then checks to see if there are any “free” licences available. If so, that terminal is granted a licence, and the terminal is allowed to log in Otherwise, the terminal is refused.
So, if the server has five licences (CALs), and five terminals have logged in, a sixth terminal will be refused. However, it is possible to “release” an existing licence, and the sixth terminal could then log on. The “released” terminal would then be refused.
The main reason for recommending that ASPluris be installed on the same server as the Ostendo database is performance – ASPluris will run faster and more efficiently on the same server.
If you install ASPluris on a different server, that server must have a TCP/IP connection to the server running the Ostendo database.