Groupwise Error Database Maintenance In Progress
comprehensive list of all possible GroupWise error codes. It lists error codes for which solutions are readily available from GroupWise engineers and testers. You can search the Novell Support Knowledgebase to locate additional solutions documented by Novell Support as specific customer issues have been resolved. C050 Transaction aborted Source: GroupWise engine; database services. Explanation: Attempted operation after critical error; transaction aborted. Possible Cause: If this error occurs during domain-related activities, such as adding users or synchronizing domains, the domain database has been damaged. Action: Check and, if necessary, repair the domain database. See Maintaining Domain and Post Office Databases in Databases in the GroupWise 2012 Administration Guide. C055 Unexpected error Source: GroupWise engine; database services. Action: See C0xx Unexpected error. C057 Database maintenance in progress; please exit Source: GroupWise engine; database services. Explanation: Maintenance in progress error. Possible Cause: Database maintenance in progress (one of the databases is being recovered or rebuilt). Action: Exit GroupWise and try again later. Depending on the size of the database, the maintenance could take from a few seconds to several minutes. Possible Cause: If the condition continues for an extended period and no GroupWise maintenance is being performed, another program might already have the required file open with exclusive access. Action: Check the open/lock activity on GroupWise databases and other files. You might find that a backup program is holding the file open. Possible Cause: If this error occurs constantly from the POA, a damaged message file might be blocking its processing. Action: Check the priority subdirectories of the /wpcsout/ofs directory. See Post Office Directory in Directory Structure Diagrams in GroupWise 2012 Troubleshooting 3: Message Flow and Directory Structure. Move message files out to a temporary location until the damaged message file is eliminated. Undamaged message files can then be returned to their original subdirectories for processing. C059 Database file already exists Source: GroupWise engine; database services. Explanation: GroupWise attempted to create a user file, message file, or library file, but it could not create the file because the file already existed. Possible Cause: The ngwguard.db file has been renamed or deleted. When the POA detects the guardian database is missing, it creates a new one. The orig
OFS - C057 Database Maintenance in Progess on the POA constantly. Error 18 - MESSAGE database open error MAINT_IN_PROGRESS (0xC057) Error 22 - Database check error: MAINT_IN_PROGRESS (0xC057) Error 27 - DbRebuild error IO_PATH_NOT_FOUND (0x8209) cause The MAINT_IN_PROGRESS flag is stored in a GroupWise database to indicate that the database is currently being rebuilt. GroupWise users and administrators could see the error FERR_MAINT_IN_PROGRESS (C057) if GWCHECK was running doing a database rebuild and the GWCHECK process terminated abnormally. fix This error http://www.novell.com/documentation/groupwise2012/gw2012_guide_tsh1/data/b4k2crp.html will be seen until the rebuild process completes.The rebuild process works as follows: A backup database with a .$db extension is created in the same directory as the original database. This is a copy of the checked database. The MAINT_IN_PROGRESS flag is written to the header of the original database.The version number in the header of the https://support.novell.com/docs/Tids/Solutions/10063193.html original database is changed to 9.99Blocks of data are copied from the backup database to the original database, overwriting data in the original database. At this point the original database is not in a valid state, as the blocks of data being written might not match the data being overwritten.The version number in the header of the newly constructed original database is changed to the current flaim version.The MAINT_IN_PROGRESS flag is cleared.The backup database is deleted.If the rebuild process terminates abnormally during step 4, the flag and version are not reset. Possible reasons for this: Server abends, process aborted, loss of power, etc.To recover from this state verify that the backup database (.$db) still exists. If it still exists you should restart the rebuild on that database by running GWCHECK. The process will start with step 2 above.If the database backup file does not exist the rebuild process cannot be restarted and the database should not be used as it is in an invalid state. Either restore the database from ba
error 0007 Unexpected error 0008 Unexpected error 8xxx Engine Error Codes Range: 81xx 8101 Memory error Range: 82xx 8200 File I/O error 8201 Access to file denied 8202 Cannot access required file 8203 Cannot copy file or directory 8204 Disk full 8205 End http://www.novell.com/documentation//nwec/nwec/data/hfrsevmn.html of file 8206 Cannot open file 8207 Cannot locate file 8208 Cannot modify file 8209 Path not found 820A Cannot open any more files 820B Path too long 820D File too large 820E Cannot lock file 820F http://put.hk/article/nntp.novell.com/novell.support.groupwise.2012.gwia/790.html Cannot unlock file 8210 Cannot create path 8211 Cannot rename file 8212 Password incorrect 8213 Invalid file operation 8214 Unsupported encryption level 8215 Path root error 8216 Cannot encrypt or decrypt file 8218 Invalid path 8219 Cannot connect groupwise error to remote network resource Range: 85xx 8502 Cannot initialize protocol 8503 Cannot connect to specified IP address 8509 Cannot access TCP/IP services 850F Connection no longer valid 8555 Port in use 8562 Client/server request packet contained invalid identifier 8563 Client/server request packet contained invalid identifier 8568 HTTP port already in use 8569 SSL login required for this post office 8570 IMAP port already in use 8572 CAP port already in use Range: 88xx 8809 Unexpected groupwise error database error 880B Unexpected error 880C Unexpected error Range: 89xx 8901 Cannot use TCP/IP services 8902 Cannot load TCP/IP services 8903 Cannot use TCP/IP services 8906 Cannot use TCP/IP services 8907 Cannot use TCP/IP services 8908 Cannot connect to specified address 8909 Cannot use TCP/IP services 890A Cannot listen on specified port 890B Cannot accept incoming connection 890F Connection no longer valid 8910 Cannot read on connection 8911 Cannot write on connection 8912 Cannot read on connection; timed out 8913 Cannot write on connection; timed out 8916 Cannot use TCP/IP services 891A TCP/IP data is not ready for reading 891B No SSL certificate supplied 891C Bad SSL certificate 891D Bad SSL private key or password Range: 8Bxx 8B02 Unexpected error Range: 8Cxx 8C04 Unexpected error 8C09 Unexpected error 8C0A Unexpected error 8C88 Unexpected error Range: 8Fxx 8F03 Invalid configuration option 9xxx Engine Error Codes Range: 90xx 9007 Client not set up for SSL 9008 Server does not support SSL Range: 93xx 9302 Unexpected error 9304 Unexpected error 9305 Unexpected error 9307 Unexpected error 9308 Unexpected error 9309 Unexpected error Axxx Engine Error Codes Range A0xx A001 Unexpected error Range: A5xx A501 Unexpected error A502 Unexpected error A504 Unexpected error Range: A6xx A602 Unexpected error Range: A8xx A801 Auto-Date formula too long A802 Auto-Date formula has incorrect syntax A803 Auto-Date formula not specified A804 Auto-D
you see any stuck items in the MTA queue folders? (wpcsin, wpcsout, mslocal) .. or just to be sure, rename those directories, and restart the MTA Also.. how many domains are in the GroupWise system? You may want to also check the other MTA folders to be sure they don't keep sending items to the "problem" MTA -- Shane Nielson GroupWise TSE Check out the latest 'dsapp ' (https://github.com/snielson/dsapp_python/releases)for GMS administration / troubleshooting ------------------------------------------------------------------------ snielson's Profile: https://forums.novell.com/member.php?userid=160544 View this thread: https://forums.novell.com/showthread.php?t=498227