THX.Casper said:Hi vakpal,
Did you try to set up a secondray broker for sql connections? Most likely your servers are ocupied with 4GL connections and so there is no more room for sql92 clients.
See also:
KB 20415
KB p7834
HTH,
Casper.
Windows Server 2003 + SP1Casper said:What OS?
What version of Progress?
What version of datadirect driver?
Make sure the startup script for the secondeory broker looks like:
-db databasename
-H Hostname
-S ServicenameSqlconnection (different port from primary broker)
-N TCP
-Mpb #sqlservers needed
-m3
-ServerType SQL
What is the error number you get when connecting with odbc?
Is there anything in de db log?
Regards,
Casper.
NOTE: I previous post I meant KB p7843 instead of p7834
:awink: I know how work services, and yes wessql_t_q and weseb2_t_q is exist on service fileBONO said:Hello,Are sure wessql_t_q is on the services file (windows\system32\driver\etc), with the correct port number. Have you tried to connect with -S <portnumber>.
To know if the service is ok u can use telnet, on progress knowledge base u've some example to determine where is the problem. Then the access permission denied can provide from a bad database param:
These 3 param are dependant :
Database and defaut configuration
-Mn = nb server (4 if the two broker are both l4g and sql)
-n = nb client (addition of Number of client/server of each server) + 1 for the watch dog)
L4G broker (1 server if only l4g, 2 if sql and l4g)
Number of client/server
SQL Broker (1 server if only l4g, 2 if sql and l4g)
Number of client/server
But with progress explorer tools it's easier to param than old procontrol.
U can have another kind of problem, user sysprogress is created on database ?
Casper said:What if you try to put
-ServerType 4GL to your primary broker?
Casper