Author Topic: OCM : Connection to DBMS Failed connection failed (Read 17157 times)

Alexandre · « **on:** July 25, 2006, 03:37:29 PM »

Hello

We have a strange behaviour with OCM : about Genesys, we can run any OCM as we want, but i have a limitation when i run between 30 and 40 OCM and i want to see the Calling List attached to a campaign. The number is variable but i can lauch 35 OCM and load, unload, stop, run and view the calling list with no problem. If i run the 36th OCM, i can load, unload and start any campaign, but if i see the Calling list, i have this error message "Connection to DBMS failed connection failed".

We have not any error reported from our database and no error from OCS_dbserver. It seems the problem comes from OCM and/or dbserver (ocs_dbserver).

Our System is :
- Siebel 7.7.2.4 ;
- Genesys 7.0 ;
- Ms SQL 2000 Service Pack 4 ;
- OCM V7.0.100.2 ;

We have a ticket opened in Genesys but they are found nothing until now...

Thank you in advance for any suggestion

Alexandre

Fra · « **Reply #1 on:** July 25, 2006, 04:08:26 PM »

Hello again

it may be related to the maximum number of simultaneous permitted connections in MSSQL.
Moreover, what's the OCM db_timeout option value? I'd try to increase it if set to default (60 s).

Vic · « **Reply #2 on:** July 26, 2006, 02:49:44 AM »

[quote author=Alexandre link=topic=1761.msg5552#msg5552 date=1153841849]
Hello

We have a strange behaviour with OCM : about Genesys, we can run any OCM as we want, but i have a limitation when i run between 30 and 40 OCM and i want to see the Calling List attached to a campaign. The number is variable but i can lauch 35 OCM and load, unload, stop, run and view the calling list with no problem. If i run the 36th OCM, i can load, unload and start any campaign, but if i see the Calling list, i have this error message "Connection to DBMS failed connection failed".

We have not any error reported from our database and no error from OCS_dbserver. It seems the problem comes from OCM and/or dbserver (ocs_dbserver).

Our System is :
- Siebel 7.7.2.4 ;
- Genesys 7.0 ;
- Ms SQL 2000 Service Pack 4 ;
- OCM V7.0.100.2 ;

We have a ticket opened in Genesys but they are found nothing until now...

Thank you in advance for any suggestion

Alexandre
[/quote]

My initial guess would be the number of simultaneous connections to SQL server is probably maxed out.
Can you please post the log for DB server that OCM is using to connect to SQL?

Thanks,
Vic

Alexandre · « **Reply #3 on:** July 26, 2006, 01:15:42 PM »

[quote author=Fra link=topic=1761.msg5555#msg5555 date=1153843706]
Hello again

it may be related to the maximum number of simultaneous permitted connections in MSSQL.
Moreover, what's the OCM db_timeout option value? I'd try to increase it if set to default (60 s).
[/quote]

Hello Fra,

Thank you for your reply...

The maximum of simultaneous permitted connections is 32767 (2 bytes) on our database. The "user connection" in msql has "32767" as value.

Genesys furnished a response with the same problem but with a DB2 database : Genesys recommended to increase the "maxapps" parameter to value 50 (30 by default) and increase the OCM db_timeout. We have done the second recomandation , the first is not avalaible in mssql

. We have not resolved our problem.

We think the dbclient_msql.e uses the OLEDB interface to connect with the database, not ODBC driver. So we think OLEDB has a max limitation to connect a msql database. We are testing a .net application using the OLEDB interface to reproduce this problem.

Alexandre

Fra · « **Reply #4 on:** July 26, 2006, 03:22:29 PM »

Hello Alexandre,

it's strange..anyway I would drill down DBServer logs when the 36th OCM tries to access a calling list.

Alexandre · « **Reply #5 on:** July 28, 2006, 02:38:33 PM »

Hello,

sorry for may late reply

I install the dbserver in version 7.02 on my integration server. So with a verbose parameter to value "all" in a Log subsection of Options, i have the folowing log when i try to launch the 45th OCM on my computer and i want to display the calling list attached to a campaign (The OCM display an error message (The connexion to DBMS failed) :

------------------------------------------------------------------------------------------------------------------------------------
16:00:37.520 Dbg 10749 Forwarding response '6700.1' from 'MS SQL: 1.1' to 'App: 1'
16:00:44.957 Trc 04521 New client 2954 connected from '145.42.9.158'
16:00:44.957 Dbg 10745 'App: 145.42.9.158:2954' registered; protocol version '1.2' [b]id '75'[/b]
16:00:44.957 Dbg 10734 Send message 'MSG_EXTPACKETS' to 'App: 75', request id '0'
(conn_adjust_rlimit) get_sbh_threshold=1016
16:00:44.957 Dbg 10750 Start client request, dbprocesses per client '1'
16:00:44.957 Dbg 10734 Send message 'MSG_CLIENTSTARTED' to 'App: 75', request id '2'
16:00:44.957 Std 05022 Process './dbclient_msql' started
16:00:45.003 Std 05020 Cannot start process './dbclient_msql', [b]error code 128[/b]
16:00:45.003 Dbg 10734 Send message 'MSG_DISCONNECTED' to 'App: 75', request id '-1'
/./dbclient_msql
pid = 3320
id = 74
expiration_time = 2006-07-28T16:01:14
client copy = 0
/Statistics
name = App: 75
req_rcvd = 2
req_sent = 3
data_rcvd = 121
data_send = 60
invalid_params = 0
abandoned_req = 0
abandon_req_fail = 0
error_start_client = 0
invalid_register_req = 0
msg_error = 0
pending_requests = 0
pending_queue_size = 0
max_pending_requests = 0
max_pending_queue_size = 0
------------------------------------------------------------------------------------------------------------------------------------

I note i had a error code in Ocs_dbserver log file with value of "128" and i note the id of the new instance of dbclient_msql.e was 75. So i think the Ocs_dbserver can not open more of 75 instances of dbclient_msql.e.
So if i check the real number of instance in Management console on my server, i have 67 instances of dbclient_msql.e. But if i add the 7 instances of multiserver (run file attached to the dbserver), the result is 74 applications launched by dbserver...

Genesys recomended to create a second ocs dbserver in a primary CTI server to share the number of instance of dbclient_msql.e (max 67) used in campaign mode. this solution is a patch but for us, it's not a final solution

Thank you for any suggestions

Alexandre

Fra · « **Reply #6 on:** July 28, 2006, 03:39:11 PM »

Alexandre wrote:
[quote]i have the folowing log when i try to launch the 45th OCM
...
So if i check the real number of instance in Management console on my server, i have 67 instances of dbclient_msql.e. But if i add the 7 instances of multiserver (run file attached to the dbserver), the result is 74 applications launched by dbserver...
[/quote]

Well well

1. in one of your previous message you said the problem occurred with the 36th OCM
2. if you are running Windows, have you ever read about this?:
[i]
Management Framework 7.2 Release Advisory:
"Microsoft Windows limits each local system account by default to approximately 120 processes that are started by, or running as, Windows services. Any attempt to start additional processes will fail when the number of running processes reaches this limit. 120 processes can quickly become too low a limit for Genesys applications, since Windows will count each DB Server's DBClient process as a separate process.
This issue can affect Outbound Contact deployments due to Outbound Contact's use of calling lists. Outbound Contact Server opens a new connection to the DBServer for every calling list that it loads into memory. Consequently, DBServer internally starts a new DBClient process for every calling list, and can potentially start multiple DBClient processes for the same calling list if it is attached to different campaigns or to different groups.
To increase the number of processes allowed in a Windows environment, follow the procedure described in this Microsoft Knowledge Base article."[/i]

So if the issue does not happen always at 36th OCM, it might be what I have here reported: the number of processes running on the machine varies like so consequently the max number of OCMs simultaneously accessing the db. Check the total number of processes as suggested in the advisory.

victor · « **Reply #7 on:** July 31, 2006, 06:03:12 AM »

Ok, before you do anything, make sure you backupu your registry!

Here is what you want to do:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows

chances are you do not even have anything there or you have something lthere, but with SharedSection having only TWO values. You want to have three

According to MS:

"if only two SharedSection values are present, you can add ",512" as the third value to specify the size of the desktop heap for desktops created in noninteractive window stations."

What you want to do is have something like this:

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows
SharedSection=1024,3072,1024 Windows=On SubSystemType=Windows
ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3
ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off
MaxRequestThreads=16

(courtesy of http://www.kbalertz.com/kb_870655.aspx)

default is 512, if I understand this correctly, so go for 1024 off-the-bat. This will give you about 180 services.

According to microsoft, 512 will allow for about 90 services - so I don't know where Genesys came up with the 120 figure.
(http://www.myitforum.com/articles/1/print_view.asp?id=2059)

As for the best explanation of what is needed to be done that I have seen is right here: http://forums.firedaemon.com/viewtopic.php?t=34

check it out.

Do tell us if it fixed your problem!

Alexandre · « **Reply #8 on:** July 31, 2006, 10:04:42 AM »

Hello,

Thank you foru your reply, Fra and Victor

I think the max number of services launched by Windows 2000 server is a good reason for my problem. So i'm going to test the modification of registry database in my integration server this afternoon and i will post my feedback...

Thank you very much...

Alexandre

Alexandre · « **Reply #9 on:** July 31, 2006, 01:59:12 PM »

Thank you for your reply.

I changed the value in Registry base and i can launch 124 OCM

.
You have right, your reply fix my behaviour...

Thank you, i will receive a wage increase for that

Alexandre

Fra · « **Reply #10 on:** July 31, 2006, 02:24:23 PM »

Well, share it with us

Alexandre · « **Reply #11 on:** July 31, 2006, 02:55:26 PM »

Hello FRA,

Thank you for your solution

Our Genesys Support is very angry to not give a solution on this problem. So i mail it the adress of this forum because i think it's not very sure that kind of forum could be exist...

For wage increase, it's a joke, i just avoid a ass kick (i can share it if you want)

This forum stay in my pagemark of my Firefox...

Alexandre

victor · « **Reply #12 on:** August 01, 2006, 01:01:47 AM »

Glad to hear that this has worked! Fra did a great job noticing it!

[u]About Genesys Support being angry:[/u]

tell them to join and just start typing away: we are all here to help each other and they can all join in!

[u]About your wage increase[/u]
We will be posting a big announcement regarding this and I am sure you will find yourself with a lot of new and adoring fans

Fra · « **Reply #13 on:** August 02, 2006, 03:33:04 PM »

Victor, Alexandre,

thanks

anyway Victor posted the fix

And about Genesys Support: IF ONLY they joined in!

Vikram_Joshi · « **Reply #14 on:** January 07, 2011, 07:40:27 AM »

[quote author=victor link=topic=1761.msg5603#msg5603 date=1154394107]
Glad to hear that this has worked! Fra did a great job noticing it!

[u]About Genesys Support being angry:[/u]

tell them to join and just start typing away: we are all here to help each other and they can all join in!
[/quote]

Thanks for this great information..
Even though this was posted in 2006, Gen Tech Support still yet dont understand this problem.

Genesys CTI User Forum

News: