Link to home
Create AccountLog in
Avatar of Genersys
GenersysFlag for United Kingdom of Great Britain and Northern Ireland

asked on

(SAGE 200) Login/Authentication error :: "Timeout expired" :: [Win XP Pro, SBS 2003, SQL Server 2000]

We have a network over which our SBS2003 hosts the Sage 200 sql database.  Workstations are all connected through a Workgroup, and not Active Directory.  We have 2 workstations that have been using Sage 200. We have purchased and installed a third licence so that we can add a new user to the Sage system.

We have installed the Sage 200 client software on the workstation 'JODIE' using the sage200cd setup exe from the server 'SERVER'.  So far so good, the SPOOL and LOGON directories were correctly specified during installation and have been confirmed in JODIE's [Sage 200] Program Files directory.

The problem
JODIE can load Sage 200 and she can see the list of Companies; I believe this list is generated by Sage and does not represent a connection to sql.  However, any attempt to connect/open the company will result in one of two error messages:

"Timeout expired. The timeout period elapsed prior to completion or the server is not responding."
"Invalid operation. The connection is closed"

What's been done
JODIE can access SERVER with read/write permissions, and the Sage200 directory on SERVER. The JODIE user profile (logon/password) has been added to the SERVER as a local user.  We have tried installing Sage200 client software on other network computers and all fail to logon using the new 'Jodie' Sage username.  The Sage usernames are all present and correct in Sages System Administrator.  JODIE and all network computers can connect to Sage System Administrator successfuly.  JODIE can PING the server SERVER successfuly.  All computers on network are Win XP Professional.  JODIE is Win XP HOME.  No computer on network (XP Pro or 'Home) other than the two that are currently working with Sage can connect to Sage 200 using any Sage User other than the afforementioned Sage Users. The computer names of the two working computers are called JOHN and FELICITY.

What's being asked
Can anyone indicate what is at fault here, and offer a fix?  I am not a Windows Server expert but I know a bit.  This is not my fulltime job so I will appreciate any advice.  I have tried to give as much information as possible, I will be glad to provide more should you need it.

Thanks for your time,

Avatar of jerryscole

This is not a solution per se but it would be very useful to run SQL Profiler against the server while Sage is running on JODIE and look to see if you are spotting any logon events. If there is some problem, it usually becomes apparent in Profiler.
Avatar of Genersys


Thanks for the pointer, it seems promising.  I ran the SQL Profiler (after Googling around) and was able to see SERVER, FELICITY and JOHN's interaction.  However, nothing showed up [in SQL Profiler] whenever GARY or JODIE would attempt to login to Sage 200.

Does this indicate that the client computer [JODIE] is failing to point to the SERVER?

Perhaps this could lead to a solution?

Yes..if you are not seeing JODIE in Profiler then there is an underlying problem that is preventing the establishment of any connection at the SQL server level. Could be any number of issues unfortunately.
Thanks again for your prompt response!  Would you be able to list those number of issues, so that I could try them sequentially?  If any lead to a solution I'd be glad to accept your offering as a solution.


Avatar of jerryscole

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Your suggestion to use SQL Profiler combined with "...ODBC only works with Windows authentication to connect to the database unless the application is specifically passing a SQL username and password as part of its connection string..." lead to the fix, that and a bit og Google!

You did point me in the right direction, but it was an issue with the DSN being misconfigured.  The first step to resolving this was to specify 'SQL Authentication' and creating a Logon within Enterprise Manager with public, read and write permissions. Avoiding 'Windows NT' authentication seems far more logical, given our circumstances; namely a Workgroup network.

Using this method through up some new Sql error messages though, but at least SQL Profiler could identify that there were problems!  Googling the error codes (SQLState: '01000', SQL Server Error: 10061 and SQLState '08001', SQL Server Error: 17) I found this Microsoft KB Article:

The Microsoft KB suggested that the deeper problem was that, "By default, SQL Server will listen for incoming connections made by Named Pipes clients." I specified the connection types (through Data Sources) to 'Named Pipes' and it worked instantly!

It seems that XP HOME/Professional, Workgroup/AD and Sage200/SBS2003 are ultimately not an issue but the heart of the problem came from the DSN being misconfigured.  I think the DSN should have been specified by our Sage supplier, who failed to identify [the problem] or even the specify the correct settings during installation; hence why I am here!

Thanks again jerryscole for your help, your advice on SQL Profiler and pointer towards SQL Authentication and DSN configuration means I am glad to award you the points.

Thanks again!
Here was the SQL server errors I received when connecting via TCP/IP.  Switching to 'Named Pipes' was the final fix to our problem.

I have the same issue as the topic poster. How do I check the DSN Configuration and my system dosnt seem to have system profiler installed how can I add this to my server and how do I run it?