DBLib error:Db-library network communciations layer not loaded.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2014 01:29 PM - edited 03-14-2019 01:51 PM
Any idea why the error "DBLib error:Db-library network communciations layer not loaded." is occurring in SQL 2005/HDS on ICM 7.5? ICM processes do not connect to databases but ODBC connections test successfully.
- Labels:
-
Other Contact Center
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2014 03:03 AM
Hi,
can you please tell us what ICM process shows this error message?
G.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2014 09:54 AM
dis-rpl
07:32:39:133 dis-rpl DB-Lib Fatal Error: Db-library network communciations layer not loaded.
07:32:40:133 dis-rpl Trace: Unable to connect to SQL Server: try again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2014 10:49 AM
Hi,
can you please turn up tracing for that process?
G.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2014 02:42 PM
tracing is enabled at ffffffff and logs show same output before process exits/crashes.
16:38:45:283 dis-rpl Trace: Node Manager thread received ping message
16:38:45:673 dis-rpl Trace: Unable to connect to SQL Server: try again.
16:38:45:673 dis-rpl DB-Lib Fatal Error: Db-library network communciations layer not loaded.
16:38:46:673 dis-rpl Trace: Unable to connect to SQL Server: try again.
16:38:46:673 dis-rpl DB-Lib Fatal Error: Db-library network communciations layer not loaded.
16:38:47:673 dis-rpl Trace: Unable to connect to SQL Server: try again.
16:38:47:673 dis-rpl DB-Lib Fatal Error: Db-library network communciations layer not loaded.
16:38:48:673 dis-rpl Trace: Unable to connect to SQL Server: try again.
16:38:48:689 dis-rpl DB-Lib Fatal Error: Db-library network communciations layer not loaded.
16:38:49:689 dis-rpl Trace: Unable to connect to SQL Server: try again.
16:38:49:689 dis-rpl DB-Lib Fatal Error: Db-library network communciations layer not loaded.
16:38:50:689 dis-rpl Trace: Unable to connect to SQL Server: try again.
16:38:50:689 dis-rpl DB-Lib Fatal Error: Db-library network communciations layer not loaded.
16:38:51:689 dis-rpl Trace: Unable to connect to SQL Server: try again.
16:38:51:736 dis-rpl DB-Lib Fatal Error: Db-library network communciations layer not loaded.
16:38:52:736 dis-rpl Trace: Unable to connect to SQL Server: try again.
16:38:52:752 dis-rpl DB-Lib Fatal Error: Db-library network communciations layer not loaded.
16:38:53:752 dis-rpl Trace: Unable to connect to SQL Server: try again.
16:38:53:752 dis-rpl DB-Lib Fatal Error: Db-library network communciations layer not loaded.
16:38:54:752 dis-rpl Trace: Unable to connect to SQL Server: try again.
16:38:54:752 dis-rpl DB-Lib Fatal Error: Db-library network communciations layer not loaded.
16:38:55:283 dis-rpl Trace: Node Manager thread received ping message
16:38:55:564 dis-rpl Trace: Node Manager thread received shutdown message
16:38:55:564 dis-rpl Trace: Node Manager thread sending NM_MSG_SHUTDOWN_REPLY_OK to Node Manager.
16:38:55:564 dis-rpl Trace: NMLib waiting for pipe to break before exiting process
16:38:55:564 dis-rpl Trace: NMLib received error as expected reading from pipe.
Last API Error [109]: The pipe has been ended.
16:38:55:564 dis-rpl Trace: Node Manager thread completed clean shutdown dialog with Node Manager. Exiting process.
