Link to home
Start Free TrialLog in
Avatar of jahhan
jahhan

asked on

Timeclock Plus 5.0

I recently installed Timeclock Plus 5 on a Windows 2000 server which also has SQL 8.  Originally Timeclock 4 was installed which utilized MSDE. After upgrading to Timeclock 5 we switched the storage method to SQL.  Intranet clients are able to run the client executable in order to log in and out of the system, but Internet users are unable to connect to the Timeclock  server.  They receive an error message of 'Open failed: invalid connection string attribute'.  Before upgrading Timeclock 4 Internet clients were able to access the server by port 9001, but now with the upgrade they are unable to.  I checked the SQL database and I noticed that the port number it was listening to requests on was on port 1433.  I updated my firewall settings to include port 1433 so external Timeclock users requesting access would be permitted to key in there hours of work.  Unfortunately this change did not resolve my problem.  I am not to familiar with SQL so I am in need of some assistance.
Avatar of DonKronos
DonKronos
Flag of United States of America image

Sounds to me like you need to contact the Timeclock vendor.

If you have the connectionstring then post it here and we might be able to help.
Avatar of jahhan
jahhan

ASKER

I did contact the vendor but I have to pay some $$$ to get connected to their second level support.  How do I post the connectionstring?  Is that a txt file or something of that nature?
ASKER CERTIFIED SOLUTION
Avatar of DonKronos
DonKronos
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
In my case there was an issue with connectivity for SQL Server. I tested by trying to connect using the tc_user login from a different computer. I kept an error that my login is not associated with a trusted SQL connection. Once I worked out the connectivity quirks I was able to login using Enterprise Manager with tc_user.

After that everything worked fine.