If you need to relocate the WaspTime database and service to a new machine, do the following:

1 Run the installation on the new machine to install the Database, Time Service, and Client. This will set it up with a blank database.

2 On the existing server, create a backup. For Standard or Pro versions, this will be done from Tools > Database Backup. Filename will be WaspTime6_<date>.bkp by default, but you can change it in that window. The backup folder will be C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\ (or \Program Files (x86)\ for 64 bit version of Windows). You can change this location with the Set Backup Location button, if needed, but it must be a path on the local hard drive. After clicking Backup, the process will be scheduled to begin in about 2 minutes, and the database should appear in that directory. For larger databases, it may take a minute or two for the file to be created. For Enterprise versions, you can use the above instructions or create the backup from SQL Server Management Studio.

3 After ensuring that the backup file was created, go to Control Panel > Administrative Tools > Services. Scroll down to WaspTimeServer, right click and go to Properties. Change the Startup Type to Disabled, then click Stop. Once it is stopped, click OK.

4 Copy the backup file created in step 2 to the same folder on the new server machine. To restore it, open the program and go to Tools > Database Restore. Enter the filename if it is different than what is displayed, and Set Backup Location if you are using something other than the default location. After clicking Restore and confirming, you will have an hourglass and portions of the Confirm message will remain on screen for several seconds. When it completes, it will go back to the Restore Database screen. Click Close, then close and reopen the program.

For Enterprise users, if you would prefer to restore the backup in SQL Server Management Studio, you will need to run C:\Program Files\Wasp Technologies\WaspTime\Database\FixUpRestoredUsers.sql after restoring the database.

5 When opening the client program on any other client machines, they will attempt to poll your network to find the location of the new WaspTimeServer service when they first run and are unable to connect to the old server. If the polling is successful, the program will open without further prompt. 

If the polling returns multiple results, you will be prompted for which server to connect with. If it fails to connect to any new server, you will receive a message giving possible reasons it failed to connect, and the option to edit the service settings. If you manually enter the new server name and it still fails to connect, you will need to ensure that the WaspTimeServer service is Started on the new server and you have the correct server name, and if there is a firewall running on the new server, try disabling it.

WaspTime logs a lot of information, especially when Loglevel is set to 0. Because of this, when a customer notices an error, the log files may have already cycled through to the point that the error is no longer recorded in the logs. Typically this is only a concern for intermittent issues that cannot be replicated as needed, such as an error when the rules were running to process the timecards. In those cases, we would not be able to determine the cause of the error without increasing the length of the log files, then waiting for the error to occur again before collecting new logs.

In those cases where longer log files are required, please do the following:

• On the machine where the WaspTimeServer service is running, go to Control Panel > Administrative Tools > Services. Right click WaspTimeServer and select Stop.
• From Start > Run, open Regedit. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wasp Technologies\WaspTime5\Options (or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Wasp Technologies\WaspTime5\Options if it is a 64 bit version of Windows). Right click Loglevel and select Modify, then set it to 0.
• In the same registry folder, right click on some empty space in the window and select New > String Value. Name the new value Logfilesize. Right click Logfilesize and select Modify, then set the value to 20. Close the Registry Editor.
• Go back to your Services list, right click WaspTimeServer and select Start.

This will set the program to use verbose logging, and sets the file size for each log file to 20 MB. Allow the program to run this way for a few pay periods. If the error is seen again, use the Wasp Support Utility ( http://dl.waspbarcode.com/wasp/WaspSupportUtility.exe ) to Zip All Logs, including a database backup in the zip file, to send us the new data.

If it is determined that the issue was isolated, or if we have seen your new log files and given you a resolution, go back to Regedit to set Loglevel back to 3 and delete the Logfilesize entry, then stop and restart the WaspTimeServer service. This will set it back to non-verbose logging with a 1 MB file size.

To backup the WaspTime database, go to Tools, Database Backup. By default, it will create a backup with filename WaspTime5_<date stamp>.bkp. You can change the filename on this screen if you desire. When you click Backup, it will schedule the backup to be created within 2 minutes.

You can also click Schedule Backup on that window to set it to automatically make backups once, daily or monthly at a specified time.

The backup files will be located in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup on the database server machine. If you need to change that location, you can click Set Backup Location on this window. If this is being done from the database server machine, you can browse to the folder. Otherwise, you must type in the desired path.

Example: If the Round To field was set to 15 (minutes), and the Round Up After field was set to 7 the following rules would apply: An employee clocks in at 7:52 – time is rounded to 7:45.

An employee clocks in at 7:53 – time is rounded up to 8:00.

This rounding happens on final calculation of time.

The actual clock in and out times will be shown on the timecard.

Beginning with a blank timecard or day, uncheck the Auto Calculate button.

Next, let’s enter a pair of punches for our selected day (with no previous punches). We’ll use 6:00pm and 6:00am for our example.  The employee’s schedule is set up to match this-so today they arrived precisely on time and left on time.  Notice that the times get reversed immediately – this is normal even without automatic calculation.

Click on the AM time (it’s on the top now) and click Next Day.

Now you can click to Recalculate Now.  The correct time should calculate and display.

When trying to run WaspTime, if it immediately responds "Failed to connect to the Time Server. The program can not run without the Time Server so it will exit. Check the log file for more details", check the WaspTime5.log file on that machine. In Windows XP, it will be located in C:\Documents and Settings\<username>\Local Settings\Application Data\Wasp Barcode Technologies. In Windows Vista/7, it should be in C:\Users\<username>\AppData\Local\Wasp Barcode Technologies.

If the log file shows any of these errors:

Exception calling IsServiceUp: Configuration system failed to initialize

Exception connecting to the service: Configuration system failed to initialize

Error logging out: Configuration system failed to initialize

or anything else with the phrase Configuration system failed to initialize, there may be a conflict with the installed versions of Microsoft .NET Framework on that machine. Check in the Control Panel > Add / Remove Programs to see if there are multiple listings for Microsoft .NET Framework. If there are, you may need to find out if other applications require a certain version of .Net to work properly. If possible, uninstall all existing versions, newest first. Once they are uninstalled, reinstall the version from the WaspTime cd's DotNet folder. Once it has finished, try the WaspTime program again.

If WaspTime now opens properly, but you need the other versions of .Net reinstalled, you can try installing them one at a time and see if the error returns. If the error returns, there is a conflict with the most recently installed version. You can try downloading a fresh copy of that installer from Microsoft if you need that version on this machine, but you may need to either relocate WaspTime or the other program that requires that version to a different machine.

 This document uses a timeline to show how WaspTime can include and exclude time worked from paid hours, based on group settings.

Some of the features discussed are new to WaspTime v6, but a lot of the information also applies to Wasp Time.

When adding the clock to connect to the ESI system, if it says it is unable to communicate with the clock, the first thing to do is have ESI verify that the Time and Attendance Management Interface (TAMI) option is turned on in the ESI system.

 If TAMI is already enabled, and you are able to ping the clock from the server machine, the next thing to verify is the base UDP port for your system. This should be listed in your ESI documentation. Most systems use a default base of 59, but we have reports of some using 39. Your documentation may also show it as 39000, or if there is a suggestion that you set firewall exclusions for ports 39000 - 39100, or something of that nature, then that is the number we need to use. The specific ports we use are XX005 and XX094, with the XX being replaced by your system's base number.

ESI TimeLine will use 59 as the default. If your system is using 39, or any other base, then you will need to create a registry entry to change it.

1 Go to Start > Run > regedit.exe

2 In the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wasp Technologies\WaspTime5\Options

3 In the right hand pane, right click and select New > DWORD Value. Name the new entry ESIClock Port Prefix

4 Right click ESIClock Port Prefix and select Modify. Set the Base to Decimal, then set the Value Data to 39, or whatever base port number your documentation dictates

5 Go to Control Panel > Administrative Tools > Services

6 Right click WaspTime Server and select Stop. Wait 15 seconds, then right click it and select Start

7 Reopen ESI TimeLine and try again to verify the clock

If you are having an error communicating with the biometric clock and the WaspTimeServer log contains this error: 

ERROR       | Determine Clock Type - BIO - Connect - Exception: Unable to connect to device, Error Code: -6

Log into the Administrative menu with supervisor rights, go to Options, System Opt, Adv Option, and Reset Opts.

Beginning in Wasp Time v7 with the BC100, RF200, and HD300 badge clocks, the badge numbers will need to be sent from the software to the clocks. This can be done from the clock utility within the software to update all at once, but it is also done each time you edit an employee. If you are creating or editing several employees at once, this can slow down your process as you will need to wait for the clock to update each time you click Save.

To prevent this, before starting the edits, go to Clocks and edit each clock to set it to Inactive. Edit or create all of the employees, then edit the clocks to set them back to Active, and use the Clock Utility to update all of the badge numbers on the clocks at once.

The badges do not need to be registered on the clocks directly. If they are enrolled on the clock directly, but do not match up with an employee in the database, you will get a message each time you communicate with the clock asking you to delete them from the clock. Instead, they should just be entered in the software, then pushed out to the clock.

On the Clock Utility screen, all of the active clocks will need to have the Download box checked, or the Next button will not activate.

 In order to allow your employees to log in to the WaspTime Web using their Active Directory credentials, do the following:

1 In directory C:\Program Files (x86)\Wasp Technologies\WaspTime Web, edit the web.config file. Locate the line for WTAttemptAutoLogin and set it to True:
<add key="WTAttemptAutoLogin" value="TRUE"/>

2 From Control Panel > Administrative Tools, open the IIS Manager. Click Sites, then WaspTime Web. Under the IIS heading, double click Authentication. Disable Anonymous Authentication, then Enable Windows Authentication. You cannot have both enabled; it will not work.

3 In WaspTime, edit the employees, and on the Security tab, their Login Name must match their Active Directory login. You do not need to enter the correct password, but you will not be able to save and close the window without entering something. Windows Authentication will handle that when they log in to the web page. If this is an admin or manager user who will ever be logging in to the pc client rather than the web module, then the password entered on this screen will be the one they need to enter.

Program Directory:
C:\Program Files\Wasp Technologies\WaspTime   (32 bit Windows)
C:\Program Files (x86)\Wasp Technologies\WaspTime  (64 bit Windows)

Default Backup Location:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup  (32 bit Windows)
C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Backup (64 bit Windows)

Log Files:
WaspTimeServer.log - in program directory, see above
WaspTime5.log, all others -
C:\Documents and Settings\<username>\Local Settings\Application Data\Wasp Barcode Technologies (XP)
C:\Users\<username>\AppData\Local\Wasp Barcode Technologies (Vista/7)

Registry Entries:
HKEY_LOCAL_MACHINE\SOFTWARE\Wasp Technologies\WaspTime5\Options  (32 bit Windows, only on server machine)
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Wasp Technologies\WaspTime5\Options (64 bit Windows, only on server machine)
HKEY_CURRENT_USER\Software\Wasp Technologies\WaspTime5\Options

 When trying to open the Biometric Clock Utility, if it fails with an error "Employees failed to load into the biometric utility. This may be caused by duplicate badge numbers or duplicate employee ID's. Please check your data", we need to check the WaspBioUtil.log file for the correct cause of the error.

The WaspBioUtil.log will be located in C:\Documents and Settings\<username>\Local Settings\Application Data\Wasp Barcode Technologies for Windows XP, or C:\Users\<user>\AppData\Local\Wasp Barcode Technologies for Windows Vista/7.

In that log, look for the following error:

ERROR       | System.Data.SqlClient.SqlException: The EXECUTE permission was denied on the object 'getEmpLName', database 'WaspTime', schema 'dbo'.

If this error is present, the function getEmpLName has not been configured with the proper rights.

To correct this, open Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio Express. Set Authentication to Windows Authentication and click Connect. Go to File > Open > File. Browse to C:\Program Files (x86)\Wasp Technologies\WaspTime\Database and open Upgrade6ToLatest.sql, then click Execute. Once it has completed, reopen the program and you should be able to open the Manage Biometric Clocks utility.

You cannot put an employee into multiple departments.

This is more of a job costing function than a strict time and attendance function.

 When using Semi-Monthly pay periods with California Overtime rules applied, overtime was being reported incorrectly on weeks where the pay period ended in the middle of the week, causing the week to appear in 2 pay periods. On those weeks, only the daily overtime was being reported. As of the patch for client version 6.1.15, server version 4.1.11, these weeks will now continue to show the daily overtime as required, but will also correctly include the weekly overtime for straight pay > 40 hours for the week in the pay period that includes the last day of the week.

This patch is a manual update only, not posted to the Updates and Patches page. The next time there is a full patch released, this fix will be included. Until that time, the instructions to manually update are as follows:

1 Close all running instances of the WaspTime6 client application. On the machine running the WaspTimeServer service, go to Control Panel > Administrative Tools > Services. Right click WaspTimeServer and select Stop.

2 Download the patch file from http://dl.waspbarcode.com/wasp/supportfiles/WaspTime6Patch_6115_4111.zip

3 On the computer where the WaspTimeServer service is running, replace the following files in the program directory (C:\Program Files\Wasp Technologies\WaspTime or C:\Program Files (x86)\Wasp Technologies\WaspTime) with the ones from the downloaded zip file:

JobCostingCommon.dll

WaspTimeServer.exe

WaspTimeRemoteInterface.dll

WaspTimeServer.vshost.exe

4 On all computers running the WaspTime6 client application, replace these files in the program directory with the ones from the downloaded zip file:

WaspTime6.vshost.exe

WaspTime6.exe

WaspTimeRemoteInterface.dll

5 On the machine running the WaspTimeServer service, go back to the Services list, right click WaspTimeServer and select Start. Once it is started, you should be able to launch the program.

Before testing the program, go to Help > About and verify the following version information is shown:

Application Version 6.1.15

Server Version: 4.1.11

To see the changes, you must go to the timecard(s) in question, uncheck "Auto Calculate", then click "Recalculate Now". The timecard will refresh with the newly calculated

In the WaspTime install certain files in your Windows and Windows32 folder may be replaced if needed. The following files are possibly replaced as part of the WaspTime install. It is possible for permissions to get changed depending on the permissions of the folder they are copied into and the permissions of the user logged in durring install. Check the permissions on the files below and make sure that they are correct. The most likely file is msvcr71.dll. It has been known to cause these problems if one of the permissions is missing. The most usual permission to be lost is the <local>\Users permissions for read and execute.

mfc42.dll

msvcp60.dll

pg32conv.dll

sscsdk80.dll

msvcr71.dll

msvcrt.dll

filecontrolp.ocx

sc.exe

'SpPayPeriodTimecardCA', database 'WaspTime', schema 'dbo'.":

Open Microsoft SQL Server Management Studio Express on the server, select <server>\WASPDBEXPRESS for the server name and Windows Authentication, then click Connect. Click + next to Databases, then right click WaspTime and select Properties.

On the Permissions page click TimeUser, then scroll down the list of Permissions and check the Grant box for Execute, then click OK.

SQL Server Setup Log

This log shows which SQL server components were detected, the operating system environment, the command-line parameters that were specified, the values that were specified, and the overall status of each MSI and MSP file that was executed.

Filename: Summary.txt

Location: %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG



SQL Server Error Log

This is one of the most useful logs.  SQL Server retains 6 previous logs.  A new error log is created each time an instance of SQL Server is started

File name: ERRORLOG

SQL 2005 Location: %Program-Files%\Microsoft SQL Server\MSSQL.1\MSSQL\LOG

SQL 2008 Location: %Program-Files%\Microsoft SQL Server\MSSQL10.x\MSSQL\LOG

To Open: Start > Run > SSMS > Expand Databases > Management



Windows Event Log

The Event Viewer is an important resource for resolving SQL Server errors.  There are 3 helpful logs.

Application Log: Logs SQL Server and SQL Server Agent events

Security Log: Records authentication information

System Log: Logs startup and shutdown info.

To Open: Control Panel > Administrative Tools > Event Viewer

This applies to all software.

For installation failure problems, check the following things:

1.  Ensure that you are attempting to install the application on one of the approved operating systems.

2.  For most products, you will need to be an administrator on the local machine. This is especially true for InventoryControl and MobileAsset.

3.  It is suggested that you turn off all firewall and anti-virus software prior to installing.

4. If you downloaded the installer, move the installer file out of the Downloads folder, then install again.