Groupwise Error D019
does not include a 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. D017 Too many users in address Source: GroupWise engine. Explanation: Reply buffer full. Possible Cause: When Reply to All is selected, personal groups and public distribution lists are expanded into a complete list of users. If the expanded list exceeds 6 KB, this error occurs. If the reply is sent, some of the users included in the original groups might not receive the reply. Action: To reply to all the users, create a personal group that contains the users and send the reply to that group. If replying to these groups is common, the personal groups could be made into public distribution lists and selected manually when replying to all users. D018 Unexpected error Source: GroupWise engine. Action: See Dxxx Unexpected error D019 Password incorrect Source: GroupWise engine. Explanation: Invalid password. Action: Type the correct password. Passwords are case sensitive. Possible Cause: The password information in the post office database (wphost.db) has been damaged. Action: Rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide. Action: If rebuilding the post office database does not resolve the problem, rebuild the domain database (wpdomain.db). D01A Password too long Source: GroupWise engine. Explanation: The password is too long. Passwords can contain a maximum of 64 characters. Action: Type a password with fewer than 64 characters. D01B Access to GroupWise denied Source: GroupWise engine. Explanation: Access to the user database required for this operation has not been granted. Possible Cause: You are trying to proxy to a user’s mailbox, or perform an action as a proxy on another user’s mailbox, but the mailbox owner has not granted you sufficient rights. Action: Ask the owner to grant you the necessary rights. The user should add your user ID to his or her access list to grant proxy access. Look up “proxy, rights” and “access” in GroupWise client Help. Possible Cause: You are trying to perform an action in a shared folder, but you do not have rights to perform the requested operation. Action: Ask the owner of the shared folder to grant you the necessary rights. Look up “shared folders” in GroupWise client Help. D
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 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 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 http://www.novell.com/documentation/groupwise2012/gw2012_guide_tsh1/data/b4k49xq.html 8219 Cannot connect 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 http://www.novell.com/documentation//nwec/nwec/data/hfrsevmn.html Range: 88xx 8809 Unexpected 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 synt
are running GW 5.2. The server https://forums.netiq.com/archive/index.php/t-24453.html is fully patched. In the Post Office agent running on the server we have been groupwise error coming up with this error \ message: "Error: D019 - Invalid password." We have checked out Novell's site and \ the references do not help us with our problem. Random groupwise error d019 users (usually one or two at a time) lose their ability to receive mail. This \ has happened repeatedly. We repair the PO database, and it works for awhile. We are running POP3 through the GWIA. We are not using the GroupWise client to \ receive and send mail. Ed Pickard Technology Coordinator Jefferson Area Secondary School 125 S. Poplar St. Jefferson, Ohio 44047 1-440-576-1731 1-440-576-7344 (fax) [prev in list] [next in list] [prev in thread] [next in thread] Configure | About | News | Addalist | SponsoredbyKoreLogic
in the correct newsgroup. NetWare 6.5sp2 GroupWise 6.5sp2 We are trying to get our GroupWise users to use their eDirectory passwords to access GroupWise (as users are not changing their GroupWise passwords but are being forced to change their eDirectory passwords). I have followed the official Novell documentation to change the POA to use LDAP, pointing it at the Novell server. This worked very well. I then changed it to enable change passwords through LDAP and users were able to change their passwords then in WebAccess. This all went well until we rebooted our Novell Server. Novell server rebooted and then noone could log into GroupWise - the POA was showing LDAP error 2. I tried to find some information about this and couldn't. As it was the day before Christmas Eve I took the decision to rollback to the original settings of using GroupWise passwords. Still noone could login! The POA was now giving D019 (incorrect password) messages. I ran a GWcheck on the user accounts and reset client options and this fixed the problem (and other problems we didn't know we had!). Now users can log back in fine. The problem is... We are unable now to go back to using LDAP authentication. When we try and change the settings to use LDAP we are getting a D019 error message on the POA when logging in using eDirectory passwords and not getting 'normal' LDAP error messages. Sounds as if LDAP on our server is a little screwey. I know this is all vague, but can anyone shed any light on why this happened/is happening? Has anyone else experiences similar problems? Is there a routine for 'refreshing/reinstalling' LDAP services on a Novell server? Richard Beels [SysOp]30-Dec-2004, 19:59sorry but this would best be asked (and will be answered) in the support.groupwise.6x.agents or ...install-setup groups. -- Cheers! Richard Beels http://www.dsi-consulting.com Collaboration without complication