Melbourne Lightning back online as of Dec 2013
Need a Website? Go Daddy has everything you need to get on the web!

Scan this with your SmartPhone

SIP Member

Hudson Software runs on 100% green power! With our solar panels, we generate more power than we use (and make a substantial profit) !

WHOS-IN Pro Support

Please select from the items below:

How to switch off Auto Updates Popup:
Automation Error after installing XP SP3:
Windows Vista - registering files: >>
Problem with HELP FILES (XP SP2 security update):
Detailed help on CHM files HERE >>
Screen & Lock Icons
3050 Error
Blurry Screen problem
Error 429 ActiveX error - unable to create object:
Network Script Problem
MSFLXGRD.OCX problem: - error 339?
XP Common Dialog problem:
XP Service Pack 1 causes error &H8007007E:
Windows 95 Workstation Installations:
Windows98 ActiveX problem:

If you do not see your problem listed here, please contact us.

How to switch off Auto Updates Popup:
The popup that can appear when a new version of WHOS-IN is released, is only seen by HIGH access users - as a reminder of the new release.
To switch this reminder off, run ADMIN.EXE (in your server WHOS-IN folder) and choose the TOOLS MENU / GLOBAL OPTIONS. Uncheck the option, and exit the screen, which will save the new choice). Users will not see the message next time they startup.

Automation Error after installing XP SP3: (2nd July 2008)
After installing Windows XP Service Pack 3, a user encountered the following runtime error: -2147319779 - Automation error - Library not registered.
Cause: This error occurs when the Window Script engine is missing from the computer.
Solution: Install the Windows Script engine. The fix for this is HERE

Problem with Help (.CHM) files - Windows XP SP2 security update:
Detailed help on CHM files HERE
Microsoft released a security update for Win XP around March 2005 which BLOCKS CHM files (Compiled Help Modules). This has been done to prevent the help files from executing possible VBScript code from gaining control of your PC. Full description here:

The fix for this problem is located at:;en-us;902225

WHOS-IN Help does not contain any embedded scripts, and is safe to run, so you can UNBLOCK both ADMIN.CHM and USER.CHM if required.

NOTE: This problem only seems to appear *IF* WHOS-IN has been installed AFTER the security patch has been applied. MS seem to think that any CHM files already on your system must be SAFE - which is optimistic in our opinion... Why should older CHM files be any safer than newer ones?

Screen & Lock Icons>
Q. I'm getting 'Screen & Lock' Icons appearing, replacing the colored buttons.
What are they?
Applies to: WHOS-IN Pro

This is the presence sensing feature (pictured above) in action. If a users screensaver is triggered, the Icon on the main display area will change from the standard colored button to a small 'screen' icon. If a users PC is 'locked' a lock icon will appear.
NOTE: The Icons changing do NOT change a users Status. When the user returns and moves the mouse / keyboard, the Icon (only) will revert back to its previous (colored) state.

3050 Error:
Applies to: WHOS-IN Pro - all versions.
This problem can be caused by a couple of things:
1. Anti Virus / Spam software misinterpreting the activity on the WHOSIN.LDB file as suspicious (most likely because the file is continuously being read & written to, which MAY appear to be an attack on the server). This is speculation, but that's how it appears to us. McAffee software seems to give the most trouble.
FIX: Exclude the WHOSIN.LDB file from the AV scan.

2. The server itself is locking the WHOSIN.LDB file (even after all users are logged out of WHOS-IN). In some cases, all attempts to unlock the file (using standard methods) can fail. It can also be impossible to delete the file, rename it, or move it. The server has it locked down tighter than Fort Knox - even the Server 'Computer Management' console can fail to release the lock.
If you find this happening to you, there is only one known method to fix the problem, and that is to use a free utility (UNLOCKER) to release the stuck 'lock'. You can download 'UNLOCKER' from the web site below.
NOTE: You MUST run Unlocker DIRECTLY on the server itself - do NOT try & run it remotely from a workstation (logged in as Network Admin) IT WILL NOT WORK !

Screen 'redraw' / blurry screen problem:
Applies to: WHOS-IN Pro, 2003, 2002, & 2000.
This problem below is caused by bugs in the Microsoft ListView control, and has been a problem for many many years. As of May 2008, we think we finally have the answer...

The problem lies with the drawing or 'painting' of the ListView control, however we discovered that if there is a BACKGROUND IMAGE in the control, then the error can happen. No background image - no problem.

WHOS-IN saves the screen position, size, and ListView column widths into the database when it shuts down (or when you hit the Refresh Button), and reloads those values when it restarts. If a combination of the form width and column width leaves the bottom scroll bar almost touching the right-hand edge, multiple copies of the text and grid can be drawn on-screen (although this does not seem to happen 'every' time)...

Screen shot of problem area in WHOS-IN 2000, however the same problem can appear in WHOS-IN 2002, 2003 & WHOS-IN Pro because Microsoft have ignored reports of the bug in the control.

At present, the only solutions we know of are to remove the logo.gif file from the WHOS-IN folder, resize a column, then 'refresh' the screen (by hitting the refresh button on the toolbar), minimizing & restoring, or moving the mouse around on the toolbar so that the tooltips are displayed - there may be others as well). To prevent the problem, try to ensure that when you exit WHOS-IN, the bottom scroll bar is either not visible, or not close to the right hand edge.

Error 429 ActiveX error - unable to create object:

After checking the Microsoft site for this error, we found the following info:
''You may receive this error message may when you attempt to use Microsoft Visual Basic code to access the Data Base Engine version.''   CAUSE   This issue can occur when DAO dynamic-link library (DLL) files are mismatched or when there are incorrect registry entries.

Assuming you are using XP on your PC's, you should be able to correct this
problem by copying the DAO360.DLL file from:
to your server WHOS-IN folder.   You MAY need to manually register the DLL. If so, follow the instructions on the above page.

Network Script Problem:
Some sites have reported that their login script 'hangs' when the WHOS-IN user.exe file executes. This problem has now been solved by a user... If you experience this problem, please modify the WHOS-IN entry in your login script from:
\\YourServer\YourShare\YourPathToWhosIn\USER.EXE -UID:%USERNAME%
START \\YourServer\YourShare\YourPathToWhosIn\USER.EXE -UID:%USERNAME%

(Ensure there is a SPACE between START and the double backslash)

NOTE: You may need to modify the above script example to suit your particular server installation.

The 'start' command calls the program outside of the batch script, therefore allowing the script to continue to the next line.


The Microsoft Flex Grid has been added to WHOS-IN 2003 & higher, and in some cases MAY need to be manually 'registered' if it has not been used previously. If so, please perform the following:
(Excluding Vista, Win 7 and Win 8 - follow appropriate link)
From the users PC, Select the START / RUN command, and enter:
REGSVR32 \\yourserver\yourshare\yourpath\MSFLXGRD.OCX where \\yourserver\yourshare\yourpath is the path to the WHOS-IN folder on the server. (Use REGSVR if REGSVR32 does not exist on the users PC)

XP Common Dialog problem:

Some sites have reported that one or more users may receive the following error when attempting to run WHOS-IN.
''Failed to load control 'CommonDialog' from COMDLG32.OCX. Your version of COMDLG32.OCX may be outdated. Make sure you are using the version of the control that was supplied with your application.''

This problem appears to be 'permission' related (the OCX is included with WHOS-IN as one of the 'core' files, and should always reside in the server WHOS-IN folder). To fix the problem, you need to log on to the PC in question as an ADMINISTRATOR, then run WHOS-IN. This will 'self-register' the OCX so that the 'normal' access user can use it. Log back on as the normal access user, and the problem should be solved. If not, please try the following:
From the users PC, Select the START / RUN command, and enter:
REGSVR32 \\yourserver\yourshare\yourpath\COMDLG32.OCX where \\yourserver\yourshare\yourpath\ is the path to the WHOS-IN folder on the server.

XP Service Pack 1 causes error &H8007007E:

The above error was discovered by a user, who performed the following tests...

1. If you have a machine with XP, then you install Service Pack 1, then you install WHOS-IN - Everything works OK.
2. If you have a machine with XP, then you install WHOS-IN, then you install the Service pack - you get the error. If you Uninstall the SP1, Delete all mention of WHOS-IN from the Registry, then re-apply the SP1, then rerun WHOS-IN user.exe - it works OK.
3. If you have a machine with XP, then you install WHOS-IN, then you install the Service pack - you get the error. If you delete all mention of WHOS-IN from the registry then rerun WHOS-IN user.exe - it works OK.

Another user further narrowed down the problem to XP Service Pack 1 altering the registry entry for ZTRAY.OCX. When the registry entry for ZTRAY was edited to point to the correct WHOS-IN server location, then the error was fixed.

NOTE: ZTRAY.OCX is no longer used (as of WHOS-IN version 2005-1A), so this problem should no longer appear.

Windows95 Workstation Installations:

Windows 95 is not officially supported with WHOS-IN however some sites have reported that it does work correctly *IF* the MSVBVM50.DLL file resides in the server WHOS-IN folder (this file is now installed by default).

Windows98 ActiveX problem:

Windows 98 is no longer officially supported with WHOS-IN (as of 1 July 2006) due to potential problems with a 'fresh' install of Win98. We have discovered that ActiveX errors are the result of some missing components that are added during the install/uninstall of Office/Access 2000. The only known cure for the above error is to install/uninstall MS Access 2000, OR to install the MS Access Jet 4 Service Pack (even though Access may not actually 'be' on the workstation).