Back to your phpLogCon instanceVendor: Adiscon
Software/device: phpLogCon
Error ID: 8
Link to KB Entry
Short Description:
No more records found
KnowledgeBase Event Repository
This site is the central interface to the Adiscon Event Repository-
- Details for this entry
-
- Vendor:
- Adiscon
- Software/device:
- phpLogCon
- Error ID:
- 8
- Full Description:
-
No more records found
If the logstream is not able to find any records, this error will occur. If filters were used, it is also possible that no log messages were found.
- Search for this Event::
- Search in Knowledge Base • Search in this Forum • Search on Windows-Expert.com
-
- Contributor: Andre Lorbach
- Software Vendor: Adiscon
- Accessed: 8548
Discuss the Event
Discussion for KB Entry 6877 - Error ID 8
This is the discussion thread for the Knowledge Base Entry 6877
Vendor: Adiscon
Software/device: phpLogCon
Error ID: 8
Link to KB Entry
Short Description:
Vendor: Adiscon
Software/device: phpLogCon
Error ID: 8
Link to KB Entry
Short Description:
-
knowledgebase - Frequent Poster
- Posts: 128
- Joined: Wed May 28, 2008 10:09 am
Re: Discussion for KB Entry 6877 - Error ID 8
if this Error appears what can i do?
- Illuminant
- New
- Posts: 9
- Joined: Mon Jul 27, 2009 9:27 am
Re: Discussion for KB Entry 6877 - Error ID 8
A good idea is to check the data source definitions. As far as I know, this error can also occur if there is data present, but the table structure is invalid. For example, I think, this is the case when you specify a monitorware schema (which is the default setting) but have syslog-ng database schema.
- rgerhards
- Site Admin
- Posts: 2831
- Joined: Thu Feb 13, 2003 11:57 am
Re: Discussion for KB Entry 6877 - Error ID 8
Ok I changed it to exactly this"syslogng" but nothing changed same error but its correct I use a syslog-ng server
- Illuminant
- New
- Posts: 9
- Joined: Mon Jul 27, 2009 9:27 am
About the KnowledgeBase Event Repository
This is a repository of known Windows Events, hopefully together with a description of what it means, when it appears and how to troubleshoot it. The event repository was initially provided as a tool for parser creation but has since evolved. It is now part of the overall knowledgebase in the hope that it provides a useful service to the community. Please add your comments and questions (which we try to answer), as this increases the event repository usefulness for all of us.
