Nachfolgend finden Sie eine nach Quellen sortierte Auflistung der wichtigsten Ereignisse, die der Operations Manager in das Eventlog 'Unicat OM' einträgt.
Category | Event Range | Description | |
---|---|---|---|
1 | Configuration | 10000-19999 | Problem in system setup or configuration |
2 | Security | 20000-29999 | Problem in security configuration, Access rights, System Policys |
3 | Process | 30000-39999 | Problem by processing requests, errors in business logic and processes |
4 | Information | 40000-49999 | General Information |
5 | Synchronisation/Discover Process | 50000-59999 | Information and problems belonging to Sync/Disc |
Color | |
Red | Indicates an error message |
Yellow | Indicates a warning |
Green | Indicates an information |
Event | No. | Category | Description | Action |
---|---|---|---|---|
12001 | 2001 | 1 | Error querying Registry | Check Registry key Software\UnicatGmbH |
32002 | 2002 | 3 | Dispatcher stopped | |
12003 | 2003 | 1 | Unable to delete c:\\temp\\omprocess\\nsfs | Check for file system rights |
12004 | 2004 | 1 | Critical Error getting Sync-DB | Check Registry key Software\UnicatGmbH\Dispatcher\SyncScope key, Server and database must exist |
42005 | 2005 | 4 | Dispatcher is configured for... | |
12006 | 2006 | 1 | Watching no DB's, please check DBScope in registry | Check SyncScope and DBScope Parameter in Registry Software\UnicatGmbH\Dispatcher |
42007 | 2007 | 4 | Init Service -> License configuration checked: | |
42008 | 2008 | 4 | Init Service -> Waiting for DB Connection... | |
12009 | 2009 | 1 | Init Service -> Unable to connect to database: | Check for databases and SQL-Server connectivity |
42010 | 2010 | 4 | Init Service -> Database list was created,... | |
42011 | 2011 | 4 | Init Service -> CleanUp was done! | |
42012 | 2012 | 4 | Init Service -> checking for interface file... | |
42013 | 2013 | 4 | Init Service -> new interface file required... | |
32014 | 2014 | 3 | Error Copying Modules from Base Server | can not copy if files are locked exclusive, not critical |
42015 | 2015 | 4 | Process started: | |
12016 | 2016 | 1 | Unable to create Interface, check for file: | check rights an ..\Dispatcher\modules |
42017 | 2017 | 4 | Timer elapsed, starting action... | |
42018 | 2018 | 4 | Entering InitService routine... | |
42019 | 2019 | 4 | Process slot free... | |
12020 | 2020 | 1 | Unable to connect to ... | Check database configuration and SQL-server |
42021 | 2021 | 4 | Found id Xin Queue... | |
12022 | 2022 | 1 | OM-Request Xstartet in Process: | Unable to start OMExecute.EXE via WMI, check rights for service account of Dispatcher service |
42023 | 2023 | 4 | OM-Request Xstartet in Process | |
32024 | 2024 | 3 | Skipping, no free Process slot... | check registry configuration for process count |
12025 | 2025 | 1 | Unable to connect to.. | Check database configuration and SQL-server |
42026 | 2026 | 4 | New Sync-Thread startet... | |
12027 | 2027 | 1 | SyncProcess failed: | Check DBSync key in registry |
42028 | 2028 | 4 | Process started: | |
42029 | 2029 | 4 | LogReader for ... Querying | |
12030 | 2030 | 1 | Error in Log-Reader Process | Check table tblLogEvent |
42031 | 2031 | 4 | Log reader checked for... | |
12032 | 2032 | 1 | Unable to connect to... | Check database configuration and SQL-server |
12033 | 2033 | 1 | Unable to inqueue Archive request for ... | Check Archive DB and Archive configuration |
12034 | 2034 | 1 | Unable to connect to... | Check database configuration and SQL-server |
12035 | 2035 | 1 | General failure in OMDispatcher: | Check log for corresponding messages |
12036 | 2036 | 1 | Error Initialising oNetUtil ! | Check for NetUtil.dll |
42037 | 2037 | 4 | Modules copied from Base Server: | |
12038 | 2038 | 1 | No Connection to Master-Server... | Check database configuration and SQL-server |
12039 | 2039 | 1 | Critical Error getting DB-Object (check registry Settings for DBScope): | Check Registry key Software\UnicatGmbH\Dispatcher\SyncScope key, Server and database must exist |
32040 | 2040 | 3 | Problem fetching Request Id from queue | check inqueue table for corrupt request |
42041 | 2041 | 4 | Entering start state for request... | |
32042 | 2042 | 3 | Reentering init phase for queueu | no action required |
12040 | 2040 | 1 | Error reading queue | check database ntadm2 |
42042 | 2042 | 4 | Queue cleanup | |
42043 | 2043 | 1 | FileRequest Inqueue processing fault | check File Request directory for corrupt inqueue files |
42044 | 2044 | 1 | FileRequest Queued processing fault | check File Request directory for corrupt inqueue files |
42045 | 2045 | 1 | FileRequest Archive processing fault | check File Request directory for corrupt inqueue files |
42046 | 2046 | 4 | FileReqeust Thread startet | |
42047 | 2047 | 1 | Unable to start FileRequests Thread | check File Request directory for corrupt inqueue files, check Registry file request settings |
12048 | 2048 | 1 | URI is empty for Mail-requests, please specify URI in Registry! | please specify URI in Registry! |
12049 | 2049 | 1 | Mailrequests: Error getting response from Mailbox | check Registry Mailbox settings |
12050 | 2050 | 1 | Mailrequests: Unable to parse mail | check format of mail request |
12051 | 2051 | 1 | Mailrequests: Wrong Parameters in Mail-body! | check format of mail request |
12052 | 2052 | 1 | Mailrequests: NTADM not connectable | check database connectivity |
12053 | 2053 | 1 | Mailrequests: Mail requestor address unknown! | check for rights of mail requestor |
12054 | 2054 | 1 | Mailrequests: Unable to queue | check format of mail request |
12055 | 2055 | 1 | Mailrequest: Unable to delete mail | check rights of dispatcher account for mailbox |
12056 | 2056 | 4 | MailRequest started | |
12057 | 2057 | 1 | MailRequest Process start failed | check request schema of mail request |
12056 | 2058 | 4 | MailRequest job started | |
32059 | 2059 | 3 | Unable to start request with StartDirect from PreProcess | Check Configuration of Web, WebService Server, WMI or access rights for executing batches remote |
12060 | 2060 | 1 | Unable to start DLL Updater | Check Configuration of Web, WebService Server, WMI or access rights for executing batches remote |
12061 | 2061 | 1 | Reduce dispatcher load because of deadlocks | Adjust dispatcher load in registry |
12062 | 2062 | 1 | LDAP Watcher problem stating ldapsearch | control sun one client installation |
12063 | 2063 | 4 | LDAP Watcher started LdapSearch utility | |
12064 | 2064 | 1 | Unable to read registry keys for configuration | control registry access |