Post reply

Triage for Client connect errors

  • May 18, 2006 at 4:42 pm

    #113033

    Folks,

    I am mostly a developer at my new job, but I also provide some lite DBA support in terms of maintenance tuning etc .

    My new company has which has never had a dba before. They are mostly a MySQL house and are starting to introduce SQL Server DB's.

    Today I got the call that some Sage reseller was in to train on a system  that they had installed themselves (including SQL Server) a week or so ago, and that the Sage client app was getting "cannot connect to sql server type" errors every 30 minutes or so. They had to restart the Sage client each time to get connected again.

    I checked the SQL instance and there were no problems in the error/event log, the server has only one user database on it, the sage DB, which is stilll only used for training, so no pressure on the server etc. lots of space and memory etc.

    We found out that the network admin had not set up time synchronisation right with the Domain controller and we thought that was the fix, but the dropping problem persists.

    Now, I dont think that SQL is to blame, but every half an hour a big ugly "Cannot connect to SQL Server" msgbox pops up in sage and therefore its my problem.

    Can you folks give me any advice on how to troubleshoot this, and maybe rule SQL Server out as the culprit?

    I have been monitoring the server and maintaining connections etc via odbc et. and I never see any dropping.

    Cheers

    K

     

  • May 18, 2006 at 4:55 pm

    #638894

    What is the timeout period for the applicatoin? Can you extend it?

    You could also set up a trace and monitor the database while they are running the application.

     

    THanks

    Susan

     

  • May 18, 2006 at 5:01 pm

    #638895

    Thanks Susan,

    They sent in a rep who knows very little about how to test the app. Ill look into extendint the timeout, but I dont not think that that is it.

    The connection gets lost every 30 minutes or so. This is a clean new server. No jobs running on it. We are a broadband provider so the bandwidth is huge etc.

    What should I look for in a trace regarding this problem. I have only ever run them to decide on indexing

     

     

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply