Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Pls help urgent, error on Agresso frontend sql

Status
Not open for further replies.

onoski

MIS
Sep 1, 2004
66
GB
I was informed by users within our finance dept that none of the users can access our Agresso software running via sql server.

The error mgs reads, 08001 17 (microsoft sql server odbc) ip-tcp( (socket sql server does not exist) or acess denied.

I have tried everything within my knowledge to crack this but to no avail even our netadmin is scratching he's hair too. Have anyone encountered this in the past and how did you resolve problem. Thanks in advance.
 
Software does not run via SQL Server. It sounds like your users can not use Agresso to access SQL Server.

Have they ever been able to access SQL Server from Agresso?

-SQLBill
 
Thanks for the feedback sqlbill, I gather some more info today. Yes ur right Aggresso is installed via a short cut pointing with a path from a network on the server. I think the issue is more serious than early anticipated as it still does not work. I gather the whole problem lies within the Agresso server, strangely it has somehow been integrated to work seamlessly alongside SQL server hence the initial sql server error mgs. Thanks again.
 
Is there a firewall between the Agresso server and the SQL Server server? If so, check to see:
1. what port is SQL Server using? (default is TCP 1433 and UDP 1434)
2. does the firewall block those ports? (If SQL Server is not using the default ports, check the actual ports being used.)

-SQLBill
 
It was revealed to me that there was a firewall maintenance carried out by the providers over the weekend. Hence now all these problems, but the netadmin and the infrastructure manager are now looking into resolving this problem. Thanks for the valuable info.
 
Here's the steps you need to follow:

1. find the port that your SQL Server is using (if it's the default, I suggest changing it).

2. request that the firewall open those ports. Provide them with a list of client ip addresses so they can filter who is allowed access via that port.

-SQLBill
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top