List Info

Thread: Return codes for Database Layer Monitor serice, kDbConnectionFailed error




Return codes for Database Layer Monitor serice, kDbConnectionFailed error
user name
2006-05-30 02:35:37
Does anyone know what a return code of 0x0000000B or
0x00000000 is on these errors, or have a list? 
The CCM system error doc doesn't seem to list them.

The trace file has other database connection failures with a
variety of return codes. Just trying to figure out what
happened (problem cleared itself up, it appears) and all the
servers have hosts and lmhosts file entries so name
resolution shouldn't be a issue unless there was a brief
network-issue. 

Event Source:    Cisco Database Layer Monitor
Event Category:    None
Event ID:    3
Date:        5/29/2006
Time:        7:50:36 PM
User:        N/A
Computer:    CCM
Description:
Error: kDbConnectionFailed - Database connection failed.
  Additional Information: Could not open connection.
ReturnCode=
[0x0000000B]
  App ID: Cisco Database Layer Monitor
  Cluster ID: StandAloneCluster
  Node ID: 10.1.1.1
Explanation: An attempt to connect to database failed.
Recommended Action: Enable trace for the database layer
monitor to get
specific error information.. 

Thanks

_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
Return codes for Database Layer Monitor serice, kDbConnectionFailed error
user name
2006-05-31 15:37:57
Unfortunately it is a generic error. There is a short list
of errors 
DCOM returns to DBL that are identified (but still not very
useful) all 
others are mapped to this generic error. 

/Wes

Erick Bergquist wrote:
> Does anyone know what a return code of 0x0000000B or
0x00000000 is on these errors, or have a list? 
> The CCM system error doc doesn't seem to list them.
>
> The trace file has other database connection failures
with a variety of return codes. Just trying to figure out
what happened (problem cleared itself up, it appears) and
all the servers have hosts and lmhosts file entries so name
resolution shouldn't be a issue unless there was a brief
network-issue. 
>
> Event Source:    Cisco Database Layer Monitor
> Event Category:    None
> Event ID:    3
> Date:        5/29/2006
> Time:        7:50:36 PM
> User:        N/A
> Computer:    CCM
> Description:
> Error: kDbConnectionFailed - Database connection
failed.
>   Additional Information: Could not open connection.
ReturnCode=
> [0x0000000B]
>   App ID: Cisco Database Layer Monitor
>   Cluster ID: StandAloneCluster
>   Node ID: 10.1.1.1
> Explanation: An attempt to connect to database failed.
> Recommended Action: Enable trace for the database layer
monitor to get
> specific error information.. 
>
> Thanks
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voippuck.nether.net
> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
>   
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
Return codes for Database Layer Monitor serice, kDbConnectionFailed error
user name
2006-05-31 20:05:48
Wes,  Thanks for the info. 

----- Original Message ----
From: Wes Sisk <wsiskcisco.com>
To: Erick Bergquist <erickbeyahoo.com>
Cc: ciscovoip <cisco-voippuck.nether.net>
Sent: Wednesday, May 31, 2006 10:37:57 AM
Subject: Re: [cisco-voip] Return codes for Database Layer
Monitor serice, kDbConnectionFailed error

Unfortunately it is a generic error. There is a short list
of errors 
DCOM returns to DBL that are identified (but still not very
useful) all 
others are mapped to this generic error. 

/Wes

Erick Bergquist wrote:
> Does anyone know what a return code of 0x0000000B or
0x00000000 is on these errors, or have a list? 
> The CCM system error doc doesn't seem to list them.
>
> The trace file has other database connection failures
with a variety of return codes. Just trying to figure out
what happened (problem cleared itself up, it appears) and
all the servers have hosts and lmhosts file entries so name
resolution shouldn't be a issue unless there was a brief
network-issue. 
>
> Event Source:    Cisco Database Layer Monitor
> Event Category:    None
> Event ID:    3
> Date:        5/29/2006
> Time:        7:50:36 PM
> User:        N/A
> Computer:    CCM
> Description:
> Error: kDbConnectionFailed - Database connection
failed.
>   Additional Information: Could not open connection.
ReturnCode=
> [0x0000000B]
>   App ID: Cisco Database Layer Monitor
>   Cluster ID: StandAloneCluster
>   Node ID: 10.1.1.1
> Explanation: An attempt to connect to database failed.
> Recommended Action: Enable trace for the database layer
monitor to get
> specific error information.. 
>
> Thanks
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voippuck.nether.net
> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
>   




_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )