*This article applies to InventoryControl and MobileAsset. This information applies only to Windows Vista.

When installing or running InventoryControl or Mobile Asset, you may get an error stating "Windows Security Message: Data execution protection error: The application you are trying to run is not a DEP compatible version. Please contact your vendor for a DEP compatible version."

We do not have DEP compatible versions of our programs available. You will need to turn off DEP for the Wasp program you are installing. Instructions for doing this can be found in Microsoft's knowledge base at http://windows.microsoft.com/en-US/windows-vista/Change-Data-Execution-Prevention-settings

More information about DEP can be found at http://windows.microsoft.com/en-US/windows-vista/Data-Execution-Prevention-frequently-asked-questions

*This article applies to InventoryControl and MobileAsset.

When printing a list, if the last printer used to print a list has been deleted or renamed, you will get an error "Settings to access printer '<name>' are not valid."

Go to Start, Run, type regedit and click OK.

For MobileAsset, navigate to HKEY_CURRENT_USER\Software\Wasp Technologies\MobileAsset\Grid Print Settings

For InventoryControl, navigate to HKEY_CURRENT_USER\Software\Wasp Technologies\InventoryControl\Grid Print Settings for InventoryControl

Right click PrinterName and select Modify, and delete the Value data.

The list will default back to the Windows default printer.

The Import Wizard will accept text files (.txt) and Comma Separated Values files (.csv)

Fields should be separated by one of these field delimiters:  

comma, dash, semicolon, slash, space or tab

If the WaspTimeServer Service starts, but then stops after a few seconds, or if you intermittently get errors in the program saying no connection could be made because the target actively refused it, we need to check the WaspTimeServer.log file in the WaspTime program directory on the server machine. Look for an error similar to:

2012-07-27 17:46:16.359          9 WaspTimeListenThread ERROR       | Error in WaspTimeListener Thread: System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted
                                    |    at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
                                    |    at System.Net.Sockets.Socket.Bind(EndPoint localEP)
                                    |    at Wasp.WtUdpClient.WtBind(IPEndPoint ep)
                                    |    at WaspTimeService.WaspTimeService.WaspTimeListenThread()

2012-07-27 17:46:16.359          9 WaspTimeListenThread ERROR       | Error in WaspTimeListener Thread: Application terminating

This error generally indicates a port conflict on the server. The service will attempt to restart itself when this happens, which is why the program can return to working after the brief pause.

If the server is also your domain controller, you will need to move the WaspTime Server service to a different machine. The database is unaffected, so it can remain on the existing server.

To move the service, run the installation cd or download on one of your other machines. If WaspTime is already installed on that machine, choose the Modify option when prompted. When asked for which components to install, add a check for the Time Server service. It will then prompt for the server's machine name, and the service will then make it's connection to the database.

On the server machine, go to Start > Run > Services.msc. Scroll down the list and locate WaspTimeServer. Right click on it and go to Properties. Set Startup Type to Disabled, then click Stop.

 When you open the client program, when it fails to reach the service on the old server, it will poll the network looking for the service, and will automatically connect to the new server.

If the server is not the domain controller, there may be a different program causing the port conflicts. There is a utility from Microsoft called TCPView that you can use to determine what is active on each port. Download the utility from http://technet.microsoft.com/en-us/sysinternals/bb897437 and follow their instructions to install and use it.

The default port for the WaspTimeServer service is 10002.

This utility is part of a larger suite called Sysinternals, which you can also view from http://technet.microsoft.com/en-us/sysinternals/bb842062 . Some of these utilities would allow you to damage your Windows installation, so use with caution if you are not sure what you are doing.

,Several of the reports in WaspTime display the pay period totals from the database for total hours and overtime. The reports do not calculate the totals. Because of this, these reports must be run for a single full pay period, or they will not display the correct amounts. The primary reason for this is because of overtime calculations. For example: if your employee works 9 hours on Monday and Tuesday, then 8 hours Wednesday through Friday, he/she would be in overtime after 3:00pm on Friday. If the Payroll Summary report was run for Thursday and Friday alone, it would show just 16 hours, and not report overtime, so it would give the wrong total.

To ensure totals are correct, the following reports must be run for a single, full pay period:

• Pay Period Timecard Report
• Payroll Summary
• Time Summary
• Time Summary Details
• Timecard Summary by Supervisor.

When trying to import the employees or pay items from QuickBooks for the first time, QuickBooks should ask you to grant permissions to access the database. You need to allow this access for the import of the employee and pay items and export of payroll data to work properly.

If it does not prompt to allow access, you will need to check the Integrated Applications list in QuickBooks by going to Edit > Preferences > Integrated Applications > Company Preferences. If WaspTime is listed but unchecked, click on it and go to Properties, and check the box for Allow this application to read and modify this company file.

If WaspTime is not on the list, and QuickBooks is not prompting you to allow the access, you need to ensure that the QuickBooks company file you want to work with is open when trying to do the import, and you are logged in to QuickBooks as Admin.

For additional assistance if it is still not giving you the prompt, you will need to refer to QuickBooks support. We have found two links in QuickBooks's free support site regarding this: http://support.quickbooks.intuit.com/support/articles/SLN41168  and http://support18.quickbooks.intuit.com/support/articles/sln41168

Beyond that, you will need to contact them directly.

These instructions for exporting time to QuickBooks are correct for QuickBooks 2010 and 2011. They supersede all prior sets of instructions. You no longer need to disable QuickBooks Payroll Services. You will need to be logged in to QuickBooks as Admin to change these settings, and you will need to have it open in Single User mode for the export to work properly.

In Quickbooks, in the Edit menu, Preferences..., go to Time & Expenses, Company Preferences tab, and make sure 'Do you track time?' is set to Yes.

Under Integrated Applications, Company Preferences tab, there should be a listing for Wasp Barcode Technologies - WaspTime. It should be checked, and if you go to Properties, it needs to be set to 'Allow this application to read and modify this company file', and 'Allow this application to access Social Security Numbers, customer credit card information, and other personal data'.

Next, go to Employee Center. For each employee who will be receiving time from WaspTime, edit the employee, select Payroll and Compensation Info from the Change Tabs menu, and check the box for 'Use time data to create paychecks'.

In the Earnings group box are the payroll codes in effect for that employee. These are the payroll codes to be used later when setting the group’s regular, overtime and overtime 2 codes for the group that the employee is part of in WaspTime.

In WaspTime, if you have already set up Payroll Codes, make sure they are not named the same as the Pay Items in Quickbooks. Then go to Tools, Import. Select Import from QuickBooks, then Payroll Items. After it tells you it was successful, you will need to edit each Group whose employees will be exported. On the Edit Group screens, go to the Overtime tab and select the Payroll Codes for Overtime 1, Overtime 2, and Regular Hours to match what was shown for the employees in Quickbooks. Make sure you “Apply changes to prior pay periods’ and select the number of pay periods you want this applied to. This will ensure that time in the timecards will use the correct payroll codes when exported to QuickBooks.

Go back to Tools, Import, Import from QuickBooks, select Employees. When it shows you the 'Preview of QuickBooks imports into WaspTime', you have the options for <Add New>, <Do Not Import>, or if you have already set up the employees in WaspTime manually, you can select them from the drop down list to match them. If you are doing a new import, employees that have been previously imported will be already selected on the list.

On the Payroll Settings tab of System Setup, make sure Export Type is set to QuickBooks Export.

On the Payroll Export, select a test employee that you know has time for the period selected, and do the export. If everything has been set properly, it should complete. The export process will tell you if any Payroll Codes have not been selected, but will not be able to tell if the selected codes were imported from Quickbooks.

After completing the export, go to QuickBooks's Employee Center, select the employee, click Enter Time, then Use Weekly Timesheet. Pick the week you've just exported, and the time should be shown. If it is, you are ready to begin the full export for the other employees. Note that this employee should either have the time deleted from QuickBooks, or be excluded from the full export, as QuickBooks will accept the same time for the same employee multiple times. This should only be an issue during testing, as once the procedure is in place, you are less likely to do multiple exports for the same pay period.

WaspTime: B2000, BC100, RF200, HD300 clock is not detected as the correct model

In some cases, the B2000, BC100, RF200, HD300 clocks are not able to be detected properly. They will report that they are a different model if you try to save them, and instead will report that they are a B1100/B1000.

In these cases, you can try going into the menu on the clock to Comm. > Security, reset the DeviceID to 1 and password to 0 and save it. If this doesn't allow the software to communicate, you will need to go back into the menu to System > Reset > Reset All Default Settings. After the clock finishes rebooting, you will need to re-enter the IP address information, and then WaspTime should be able to communicate with it properly.

The cause of the error is that the database is showing duplicate badge numbers when it tries to open that list, causing an error. Usually this is due to an employee having been removed, then a new employee given the same badge number.

Download and extract http://dl.waspbarcode.com/wasp/SupportFiles/DuplicateBioscanTableEntry.zip on the server machine, then run Update.bat to correct the issue. The batch file will create a backup of the database in the default SQL backup folder (usually C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup) with filename WaspTime_<date stamp>.bkp prior to making any changes in the database.

We have also seen an instance where there were 2 active employees with the same name and same badge number. This should not be allowed by the software, but if you find the same situation has occurred, determine which one has been receiving the current punches, and archive the other.

If the issue persists, there will be a DuplicateBioscanTableEntry.log file created in the same directory where you run update.bat. Please send me that file and let me know of any new errors.

The Absence report shows the absences that were entered into each time card per person for a time period. This one gives the employer a view into an employee's habits and possibly points out an employee abusing the system. It can also be used to help keep track of vacation.

The Absentee report shows employees who did not punch in on a day their schedule in their group says they were scheduled to work. This can be used as a way to look at gaps in positions for today like at a school or it can be used to identify employees who fail to show up for work.

Both reports are most useful for managers who may not see every employee every day or who are looking at trends over time.

If the server machine running the WaspTimeServer service has multiple network connections, you may experience trouble communicating with the clocks.

To force the card that is in the same IP range as the clocks to be used for that communication, go to Start, Run, type regedit and click OK. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wasp Technologies\WaspTime5\Options. Right click and select New > String Value. Name it UseIP. Right click on UseIP and select Modify, and for the value enter the IP address of the network connection to use.

Note that for this to work, you must be running version 6.1.11 or newer. Please verify the application version in Help > About, and if it is not current, download the current patch from http://dl.waspbarcode.com/wasp/WaspTime6Patch.exe and install it on the server and all client machines.

When exporting times to Quickbooks, if there are no payroll codes selected in the Group setup, the export will not proceed.

If your export says it has completed successfully, but the times do not appear on the employee's Weekly Timesheet, then the codes used were created in WaspTime, rather than imported from Quickbooks.

In Quickbooks, either edit an employee and check the Payroll and Compensation Info, or go to the Employee Defaults, and make sure there is at least one item name for their regular hours pay item, and additional pay items if you pay overtime.

In WaspTime, go to Tools, Import, Import from Quickbooks, and select Payroll Items. Once finished importing, go to the Groups List, edit the group and go to the Overtime tab, and select the correct payroll codes for Overtime, Overtime 2, and Regular Hours Payroll Code.

Export the time again, and the times should now appear.

To resolve this issue, apply payroll codes to overtime and absences in WaspTime then try to re-export your information.

Extract the attached files on the server, then run BackupDB4WT6.bat to create a backup file in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\. The filename will be WTbackup_<date.stamp>.bkp.

If you need to change the path or filename, edit BackupDB4WT6.wql with Notepad to change the line starting SET @FileName. If you are changing the file path, it must be directed to a local folder that already exists on the server, or the script will fail.

To schedule this process to run automatically, you can make use of the Windows Task Scheduler, as follows:

 In Windows XP, go to Start > All Programs > Accessories > System Tools > Scheduled Tasks. Double click Add Scheduled Task. Click Next on the welcome message, then Browse. Locate the BackupDB4WT6.bat file and select it. Chose how often you wish the process to run from the list, then click Next to enter the details. Depending on how often you selected, you will be prompted to enter the day of the week or month and the time to run the process. You will then be prompted for the username and password of a Windows user, and the task will run as that user. You should enter a user who has sufficient rights in Windows to run the bat file and write into the specified directory. If you choose to open the advanced properties for the task, you will be able to specify several additional things, like whether to run the task when the computer is on battery power, etc. Usually the default settings will be fine. The task will now be shown in the Scheduled Tasks window, should you wish to check/change the properties or verify the status of when it will run, when it last run, and whether it failed when last attempted.

In Windows 7, go to Start > All Programs > Accessories > System Tools > Task Scheduler. It may spend a few seconds adding a snap-in to the management console, then it will open. On the Actions pane at the right, select Create Basic Task. Provide a name for the task, like WaspBackup, then click Next. Chose how often you wish the process to run from the list, then click Next to enter the details. Depending on how often you selected, you will be prompted to enter the day of the week or month and the time to run the process. On the next page, it will ask what action you want it to perform. Click the radio button for "Start a program" and click Next, then Browse. Locate BackupDB4WT6.bat, select it and click Open, then Next. If you check the box for "Open the Properties dialog for this task when I click Finish", it will open an interface with many additional conditions for the task. This is where you can specify a different user for the task to run as, as well as options for whether to run when the user is logged in only, or whether the user is logged in or not. It does default to only when the user is logged in. Also, on the Settings tab, there are boxes for "Run task as soon as possible after a scheduled start is missed" and "If the task fails, restart every:", which you should look at. This Properties window is the same as what opens if you initially choose Create Task rather than Create Basic Task, so you may start here, but the initial rule creation may be easier in Basic Task. To see the task, click Task Scheduler Library at the top left. Click on the task in the top center pane, and the Properties will be shown in the bottom center pane for verification. If you need to change any of the settings, you will need to right click the task and select Properties.

**This script will work for v6 or v7 of the program.**

Symptom: After a new install or upgrade to WaspTime v6, none of the reports will work. Trying to view the report comes up with an error: "Show Report viewer exception: Could not load file or assembly 'CrystalDecisions.CrystalReports.Engine, Version=10.5.3700.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified."

Cause: The Crystal installer on some of the first run of CDs is bad and so the Crystal driver is not getting installed.

Solution: Download, unzip and double click to install the Crystal Reports Runtime from our FTP. It is a quick silent install with just a progress meter.

http://dl.waspbarcode.com/wasp/crredist2008_x86.zip

You must be running at least Windows 98SE for the reports to run.  Also, WaspTime is not supported on Windows 98.  It is only supported on Windows 98 SE and higher

You cannot import a Quickbooks Employee file into Wasp Time from a network location.  Copy the .iif file to your local system and import from there.

If you are running WaspTime version 5: HTTP://dl.waspbarcode.com/wasp/FixTimecardReportAbsenceCodesV5.zip

If you are running WaspTime version 6: HTTP://dl.waspbarcode.com/wasp/FixTimecardReportAbsenceCodesV6.zip

Download the appropriate file for your version on the database server.

Extract it and run the .bat file to update the database. When you re-open WaspTime, the report should display the current absence code.

Please let us know if it does not.

Click Start > Run.  Type REGEDIT in the provided blank and click OK.

Click the + next to HKEY_CURRENT_USER \ Software \ Wasp Technologies \ WaspTime5

Click on the Options folder.

Right-click in open space on the right after clicking on the Options folder.

Select New > String Value.

Change the name to "Time Server Name" (without the quotes).

It's value needs to be the name of the computer that has your WaspTime database.

Right-click again in open space and click New > DWORD value.

It needs to be named "Time Server Port" (again without the quotes).

Like the value above you can double-click to change it's value.

Make sure you have the bullet for Decimal selected.

Type "10002" (as usual, without the quotes) for the value and click OK.

Close the registry editor and re-start PC Punch

 When trying to connect to the WaspTime web module, if you get an error page saying HTTP Error 500.19 - Internal Server Error, there could be an issue with the ASP.NET role in your IIS configuration. To make sure the ASP.NET role is added correctly, please follow the steps given by Microsoft at