Client AW - (-9986) Session to Local Database could not be opened

Answered Question
Jul 28th, 2008

Hi All,

I have a Server which has a Client AW installed (NGMICMAWC1). For some reason the software is now unable to connect back to either the Primary HDS (NGMICMAWD1) or the Secondary HDS.

The HDS can see the request from the Client AW but the UAW process returns the following error:

*********

11:35:41 dis-uaw Trace: New trace client: Launcher(upcc) on pipe 0x224.

11:35:41 dis-uaw Trace: [client: Launcher(upcc)] Real-time Client cannot connect to database using ServerName: ngmicmawd1, UserName , SqlCode 2.

11:35:41 dis-uaw Trace: [client: Launcher(upcc)] Session to local database could not be opened. Aborting...

11:35:41 dis-uaw Trace: Info: Trace client on pipe 0x224 disconnected.

Last API Error [109]: Unknown status code 109. GetLastError() after FormatMessage() returned 317

*********

I suspect that the issue is authentication. Looking at the Registry Setting within the CLient AW they are:

**********

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\ICM\cap1\AW\RealTimeClient\CurrentVersion\LocalDB

Class Name: <NO CLASS>

Last Write Time: 28/07/2008 - 11:34

Value 0

Name: DBMS_PROVIDER

Type: REG_SZ

Data: MSDASQL

Value 1

Name: SQLServerUserName

Type: REG_SZ

Data: sa

Value 2

Name: DBMS

Type: REG_SZ

Data: MSS Microsoft SQL Server 6.0

Value 3

Name: SQLServerDBName

Type: REG_SZ

Data: cap1_awdb

Value 4

Name: SQLServerPassWord

Type: REG_SZ

Data:

Value 5

Name: RtDistributorName

Type: REG_SZ

Data: ngmicmawd1

Value 6

Name: SQLServerUNCName

Type: REG_SZ

Data: ngmicmawd1

*********

The Client AW receives the following error:

**********

(-9986) Session to Local Database could not be opened

**********

Can anybody point me in the right direction?

Thaks

Dan

Correct Answer by CT.Anderson about 8 years 6 months ago

I ran into this and fixed it by changing the client configuration of the ODBC connection to named pipes. It was set to TCP/P

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
cisco@bloy.me.uk Sun, 08/03/2008 - 00:11

Hi irisrios,

Thank you for the guide.

I'm running a Enterprise ICM but went through the guide anyways.

I can confirm that under my Cust OU I already have both the LOGGERA.... and LOGGERB doamin accounts which are already included within the SERVICE group...

Any more thoughts?

I'm strugglying to see the link for the account that my Client AW uses to log into the HDS (I'd guess that it uses the account the the users logged onto the box with? If so does this mean that all the users accounts need to be part of the SERVICE group?)

Thanks

Dan

geoff@hp.com Sun, 08/03/2008 - 11:48

I assume your client AW is in the ICM domain and you are logged in as the domain admin?

Regards,

Geoff

cisco@bloy.me.uk Mon, 08/04/2008 - 00:40

Hi Geoff,

Correct - All the servers are within the same ICM Domain and I am using a Domain Admin account to login with.

When I open Script Editor I get a slightly different Error:

****

Error trying to open the database connection to initalize the security system.

The following database errors were retirned:

**

Database error reading the user ReadOnly flag.

The following database errors were retirned:

**

Session to local database couldn't be opened

****

Thanks

Dan

Correct Answer
CT.Anderson Mon, 08/18/2008 - 11:22

I ran into this and fixed it by changing the client configuration of the ODBC connection to named pipes. It was set to TCP/P

samuel.barnhouse Mon, 08/18/2008 - 19:29

Try adding the domain accounts to the User List within Configuration Manager, with Configuration rights, and any Feature Control Sets, if you have them.

cisco@bloy.me.uk Tue, 08/19/2008 - 06:39

THANK YOU CT.Anderson

Amending from TCP/IP to Named Pipes did the trick :0)

Thanks Again

Dan

Actions

This Discussion