Skip to main content

Wasp services will not remain started with a numeric machine name - Knowledgebase / Discontinued Products / MobileAsset - Wasp Helpdesk

Wasp services will not remain started with a numeric machine name

Authors list

Symptom: If your machine name is entirely numeric, the Wasp service (WaspTimeServer, Wasp MobileAsset Windows Service, or Wasp Inventory Windows Service) will appear to start, but then will stop without error. It may try restarting itself repeatedly.

The Wasp program will not be able to start while this is occurring, sometimes giving a login error, or an Error 26: Cannot locate server/instance specified.

Cause: All versions of Windows since Windows 2000 will prevent you from using a numeric machine name, but an older machine that had a numeric machine name in Windows NT will keep that name when it is upgraded. Having a numeric name will prevent Windows from being able to properly route network traffic to that machine, because it will attempt to recognize the name as part of an IP address.

Solution: Rename your machine to have at least 1 letter in the name, and then either change the relevant registry entries/configuration files for your program as given in the articles linked below, or reinstall the program to alter the server name.

WaspTime: https://support.waspbarcode.com/kb/articles/908

MobileAsset: https://support.waspbarcode.com/kb/articles/10

InventoryControl: https://support.waspbarcode.com/kb/articles/931

Helpful Unhelpful

7 of 24 people found this page helpful