?
Solved

Any pointers for Payclock software

Posted on 2008-06-23
2
Medium Priority
?
590 Views
Last Modified: 2012-06-27
I have a client that is running Lathem's Payclock on a XP Pro box.  The time clock station, Quickbooks, and the Payclock software were all on the same box.  It would get the BSOD a few times a week.  Have ran tests and everything seems to check out.  Since then have pulled the time clock station off and put on another XP Pro computer and moved the Quickbooks databases to the server.  Now both computers are having problems with blue screens and the time clock keeps loosing connectivity to the pay clock database on the first XP box.
0
Comment
Question by:jlhunter1
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 44

Expert Comment

by:scrathcyboy
ID: 21859249
This is the kind of problem where you should be contacting www.lathem.com directly.  There may be an update you need for the software.   Software like this should not cause a BSOD if written correctly.

If the first XP machine was BSOD ing, you should not connect to it for time updates on the second machine, as this will guarantee that both fail.  Why not have the server, or the new XP machine poll for atomic time on the internet -- http://www.google.com/search?num=30&q=internet+atomic+time+clock  -- There are lots of them, which is why I gave a general link.

If you want to sync all systems, put atomic time software on all of them.  Then make the new machine independent of the old one, the BSODs should go away.  If not, the problem is likely in Payclock.  If not, then consider doing a clean XP install on the old machine, its setup may be corrupted.
0
 

Accepted Solution

by:
jlhunter1 earned 0 total points
ID: 21859489
I spent 8 hours on the phone with Lathem trying to fix the problem.  They are the ones that wanted me to put the time clock station on the other XP box.  The software is all updated.  Workstations sync back to the server which is sync'd to an atomic clock.  The time clock station just connects back to the first XP box that was blue screening to update the databases for Playclock.  I think it is a problem with the Payclock software itself, and was wondering if anyone was having the same problem or knew of a solution to fix it.  Lathem didn't, I went all the way to level 3 support.
0

Featured Post

Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article was originally published on Monitis Blog, you can check it here . If you have responsibility for software in production, I bet you’d like to know more about it. I don’t mean that you’d like an extra peek into the bowels of the sourc…
This month, Experts Exchange’s free Course of the Month is focused on CompTIA IT Fundamentals.
This video will demonstrate how to find the puppet warp tool from the edit menu and where to put the points to edit.
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…

765 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question