What this means is that the console either 1) cannot detect your database server because there is a port blockage, or 2) the database server service is not started, or 3) the SQL Browser service (if you are using SQL Server) is not started and your database server is on a foreign box in relationship to your connection server. Ensure or 4) your sql server name changed and the console's expressed SQL Server name is now erroneous. There might be a few other reasons too, but I wanted to make the post short.

Can you verify that the services are started and that you can make a connection from your application server to the sql server? You can do that through a couple different means:

1. You can drop to a command prompt and using SQLCMD to issue a connection to the server.

2. You can check your application server's ODBC DSN. Run through the wizard and see if it can complete using the database information entered within the DSN settings. Near the end of the wizard you will see a test button.

3.  You can use a use a Universal Data Link file to check connection as well (UDL). Here are the details:

msdn.microsoft.com/.../e38h511e%28v=vs.71%29.aspx

If any one of those techniques work from the perspective of the application server then perhaps there is a permissions error of some type, we would need more information to go on at that point.

One other point, if you can log into Sage ERP X3 then you know everything is working, it's just the management console that can no longer talk to the server. This is not as critical as you would normally not need the console for day-to-day operations.

Hope this helps,

Bob

Could you please assist me. I have this exact issue in the management console. There is no ports blocking me and all the services is up and running

Could you please assist me. I have this exact issue in the management console. There is no ports blocking me and all the services is up and running