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 http://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
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.
Yes. You can either use a barcode terminal with 3G/4G capability, or use a “Pocket Wi-Fi Modem” from one of the mobile phone companies.
The barcode terminal only needs to connect to the ASPluris server when selecting what you want to work on, and when updating.
For example, if you want to perform a Stocktake, you need to be within Wi-Fi range when you select the Stock Count to work on, but you can then move out of Wi-Fi range while you do the count.
You will need to come back within Wi-Fi range to Submit the count.
The first thing to consider is whether you should update the RTP. Some updates to the service require the service and/or the scanner program to be updated as well, so you should take a whole-system approach to updates. Read the release notes for more information.
If you do decide to update the RTP, the latest V2.3x version is always available from this URL:
The first thing to consider is whether you should update the service. Some updates to the service require the RTP and/or the scanner program to be updated as well, so you should take a whole-system approach to updates. Read the release notes for more information.
If you do decide to update the service, the latest V2.3x version is always available from this URL:
The first thing to consider is whether you should update the scanner program. Some scanner program updates require the PC service and/or the RTP to be updated as well, so you should take a whole-system approach to updates. Read the release notes for more information.
If you do decide to update the ABM scanner program, follow these steps:
When a scanner counts an item, that count replaces the existing count. If another scanner counts the same item in the same location, the count from that scanner will also replace the count from the first scanner.
For example, if you have a bin containing 56 of an item, and the first scanner counts 55, that’s what the ABM count will be set to. If another scanner then counts the exact same item in the exact same bin, but counts 57, the count in ABM will be set to 57, replacing the previous scanner’s count. What this effectively means is that the last scanner wins – its count replaces any other count.
This option is used where, for accounting or other purposes, a company has two separate trading entities that share the same warehouse.
The following needs to be setup correctly:
From the scanner operator point of view, everything will work as if there is only one large database. Orders can be dispatched / combined and submitted etc. The operator can pick orders based on a customer which could be multiple orders from different databases. After picking, ASPLuris creates separate transactions for each database.
For order grouping, the customer/supplier names have to match. Codes are looked up during the processing of the order so they can be different. ASPluris works out which database needs to be processed based on the order number or product code (transfer etc), then the transaction is processed as per normal.
Since this message beings with a colon, the error is coming from ABM, not from ASPluris.
This error can happen in two ways. The first is that the user may not have the correct access privileges to allow them to perform the transaction. This can be fixed by setting the correct access privileges in ABM and then refreshing the user list in ASPluris.
The second way that the error can occur is a bit more difficult to explain. ABM has a hidden “control” database as well as the main SQL database. The control database is not accessible to ASPluris. When you add or remove users in ABM, ABM tries to keep these two databases in sync. Unfortunately, this sometimes fails, and if the user is in the SQL database but not in the control database, the user will be denied permission to write transactions to ABM, and that is what this ASPluris error message is showing.
This synchronisation problem can usually be fixed by deleting the user with the problem from ABM then adding the user back in again. This should result in the ABM databases resynchronising. You can then refresh the user list in ASPluris.
If the first line of the error message begins with a colon, the error message has come from the ERP/WMS system rather than from ASPluris – the scanner is just passing the message on.
There is no way to recover a forgotten username or password. However, if you delete (or rename) the file that contains the ASPluris usernames and passwords, you will be able to log on using the default username and password.
Unfortunately, if you have set up any other ASPluris administrator accounts, those accounts will be removed when you delete or rename this file.
Navigate to the C:\ProgramData\ASP Microcomputers\ASPluris V2.3\ folder and locate the accounts.ds file. Rename this file by adding .old to the end of the filename.
To register the ASPluris service, go to the computer where the service is installed. Open a web browser (for example, Internet Explorer), then type the following URL into the address bar:
Click on the Registration link at the bottom to display the ASPluris Registration Form.
To register the service, or to enter a new registration code to enable more users or different modules, you need to provide the Hardware Fingerprint and the name of the company that the service will be registered to.
This information, together with the number of users you want to have and which modules you want to use, will be used to create a Registration Code for this installation.
When you enter the Registration Name and the Registration Code into the fields at the bottom of this screen, the ASPluris Web Service will be registered and the licenced number of users and the licenced modules will be enabled.
Note that Registration Codes are specific to a particular program, the computer the program is running on, and the name the program is registered under. You cannot use a registration code on any other computer, or for any other program.
Please see the section starting on page 2 of your ASPluris Installation Manual.