Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Django on February 19, 2020, 08:18:29 AM
-
Hi all,
I am not able to connect config server 8.5 with MSSQL. Scripts i have executed.
'Cannot connect to Database 'ConfigDB' at host 'WIN-XXXXXXXX, port -1, reason 'Server not found'.
is the error i am getting. Any one please help me from where it is taking port -1.
-
Did you configure the confserv.conf file with proper connection string information?
-
Yes I have configured it. Below is the detail of dbserver section of this file. Do I need to add some more configuration in this section?
[dbserver]
dbengine =mssql
dbserver =WIN-XXXXX
dbname =ConfigDB
username =
password =XXXX
response-timeout=
-
I do not see any MSSQL port configured within dbserver section. I suggest you to check your configuration again as it seems there is something wrong
-
This is all the configuration which i defined inside confserv.cfg file
[confserv]
port =2020
management-port =4581
server = dbserver
encryption = false
encoding = utf-8
multi-languages = true
langid = 1033
[log]
verbose = all
all = C:logsconfigserverconfsip
[dbserver]
dbengine =mssql
dbserver =WIN-xxxx
dbname =ConfigDB
username =xx
password =xxxx
response-timeout = 600
-
Have you tried to connect to server with MSSQL Studio using exactly same information?
-
Are u using standard sql instance?
TCP ip enabled?
Enviado de meu SM-N9600 usando o Tapatalk
-
@Janis- yes i am able to connect mssql studio with the same creds.
@cavagnaro- yes TCP IP is enabled
Have you faced this issue at the deployment of framewore 8.5?
-
Yes, when encryption was true with unencrypted password. :) Error message was same as yours, nothing about wrong password.
-
I'd recommend to use Wireshark on port 1433. You will see more information about your problem.
-
I've had similar problems after some hardening done by the administrators of MSSQL 2014. I've even could not connect from HeidiSQL from the configuration server host or add new ODBC connection from that CS host to DB. I've had to update Microsoft OLE DB 18.3.0 Driver for SQL Server and Microsoft SQL Server 2012 Native Client and use alternative version of ODBC client as described here: https://docs.genesys.com/Documentation/FR/Current/DBConn/MSSQL#nextVersion
Even now I've in the logs [i]port -1[/i], so I think this is not a source of a problem. Can you post detailed logs from dbthread?
05:24:38.803 Trc 04500 Connecting to Database 'cfg_db' at host 'cxxxs3xxx1', port -1
05:24:39.787 Std 04503 Connected to Database 'cfg_db' at host 'cxxxs3xxx1', port -1
-
In MSSQL ERRORLOG I am getting below error
14:35:50.77 Logon Login failed for user 'sa'. Reason: Failed to open the explicitly specified database 'ConfigDB'. [CLIENT: xx.xx.xx.xx]
2020-02-20
14:36:00.80 Logon Error: 18456, Severity: 14, State: 38
is there some more configuration for MSSQL for connecting with dbserver except the script part which i have executed.
-
Nothing to do in Genesys. Check MSSQL side.
-
The user you are using is as dbo or db_owner?
Enviado de meu SM-N9600 usando o Tapatalk
-
[quote author=Django link=topic=11542.msg52544#msg52544 date=1582193909]
In MSSQL ERRORLOG I am getting below error
14:35:50.77 Logon Login failed for user 'sa'. Reason: Failed to open the explicitly specified database 'ConfigDB'. [CLIENT: xx.xx.xx.xx]
2020-02-20
14:36:00.80 Logon Error: 18456, Severity: 14, State: 38
is there some more configuration for MSSQL for connecting with dbserver except the script part which i have executed.
[/quote]
Looks like the sa user does not have proper security access to the ConfigDB database.
-
Thanks.
-
Fixed?
Enviado de meu SM-N9600 usando o Tapatalk
-
[quote author=Janis link=topic=11542.msg52541#msg52541 date=1582182605]
I'd recommend to use Wireshark on port 1433. You will see more information about your problem.
[/quote]SQL is encrypted... You can't see the negotiation using standard Wireshark
Enviado de meu SM-N9600 usando o Tapatalk
-
I was able to get the error from there when password was wrong in the .cfg file.
-
Wasn't SQL Profiler?
Enviado de meu SM-N9600 usando o Tapatalk
-
No. But you are very likely right in case when login was successful but later do not have some internal rights in MSSQL like it was in this case. Checking MSSQL logs would be more universal method.
-
Not because rights, it is because sql natively encrypts all communications even before login... So... Kinda hard to imagine how you could catch a wrong password using Wireshark. Because of the protocol, not because of the negotiation.
Enviado de meu SM-N9600 usando o Tapatalk
-
Made a quick test. Here is the content of captured packet received from MSSQL server:
[code]H*~
)CT%E\@:_C9 jPhmTHLogin failed for user 'sa'. MSSQL2012[/code]
-
[emoji102] Welp... Hehe what a surprise
Thanks for taking the time to show me! Appreciate it
Thanks!
Enviado de meu SM-N9600 usando o Tapatalk