Home > Socket Error > Socket Error Groupwise

Socket Error Groupwise

Click Post Office Links, select the post office, then click Edit Link. at Friday, May 15, 2015 Email This BlogThis! See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 8 Administration Guide. The agent software cannot be successfully updated if the agent engine is still loaded. Check This Out

Action: Have the user log in through the GroupWise WebAccess login screen. Action: Make sure the Internet link between domains is set up correctly. Possible Cause: Some agent files have been updated but the update is not complete. WEBACC: No gateway alias was specified in NW Admin Source: GroupWise WebAccess Agent Explanation: The gateway alias type is not defined. http://www.thedarktimes.us/wordpress/?p=114

See WebAccess Security Requirements in Installing GroupWise WebAccess in the GroupWise 8 Installation Guide. GWMTA: Cannot create/read/write files/directories Source: GroupWise Message Transfer Agent; last closure reason. Action: Obtain a usable certificate file. Explanation: Cannot read on connection.

Explanation: Listen failed. Action: Provide the WebAccess Agent with rights to write to files in the log file directory or specify a different location for the log files. To resolve the issue you need to contact network administrator or ISP support before all data goes in accessible mode. Possible Cause: The server where the other agent was running went down.

Lengthen the timeout interval. The name ATT00001 is a generic file name and is... Action: Make sure the agent has rights to create files in the specified location. See Configuring the WebAccess Agent in WebAccess in the GroupWise 8 Administration Guide.

Action: Check, and if necessary, adjust the indirect links between domains in your GroupWise system. Action: Make sure the input queue directory exists and that the MTA has sufficient rights to create files there. Possible Cause: The /user and /password switches do not provide the correct information for the MTA to log in to the server. Possible Cause: The NetWare MTA cannot log into the server where a domain or post office is located because all available NetWare licenses are already in use.

UNKNOWN ERROR WHEN IT SAY UNKNOWN ERROR HAS OCCURRED 12. newsgator Bloglines iNezha Star Wars Celebration VIIIStar Wars Celebration VIII It will happen in 4 months and 10 days.Boy Scout National JamboreeIt will happen in 7 months and 22 days. Explanation: The MTA cannot access the domain database (wpdomain.db) in the directory specified by the /home switch. WEBACC: Logging: Disk is full - turning file logging off Source: GroupWise WebAccess Agent Explanation: The disk where the log files are stored is full.

WEBACC: File I/O error Source: GroupWise WebAccess Agent Explanation: The WebAccess Agent could not view a log file. his comment is here Action: Remove the damaged message from the MTA input queue so it can process subsequent messages. Possible Cause: Some agent files have been updated but the update is not complete. Action: Reestablish the connection to the domain directory and make sure the WebAccess Agent has sufficient rights.

WEBACC: No NetWare password was specified Source: GroupWise WebAccess Agent Explanation: The GroupWise WebAccess Agent requires an account and password that lets it log in to eDirectory or NetWare servers so Explanation: The MTA is attempting to communicate with another MTA or a POA by way of TCP/IP, but the other agent does not answer. See Encryption and Certificates in Security Administration in the GroupWise 2012 Administration Guide. this contact form Possible Cause: The SSL certificate that accompanies the private key file is not in the required format.

This probably occurred in Windows where the workstation is not connected to the network. Action: Make sure the WebAccess Agent’s user account provides the correct access and rights, or specify a different log file directory using the /log switch. GWMTA: File create error; disk logging turned off Source: GroupWise Message Transfer Agent.

Action: Run the GroupWise program on a more powerful machine. 8916 Cannot use TCP/IP services Source: GroupWise engine; TCP/IP communication.

  • WEBACC: Request aborted while waiting on locked conversation Source: GroupWise WebAccess Agent Explanation: During a conversation (or session), GroupWise WebAccess issues a request whenever the user performs an action in WebAccess.
  • Action: Make sure the server where the MTA is running has a drive mapped to the domain directory on the server where the domain is located if it is using a
  • Explanation: A GroupWise agent cannot establish an SSL connection because the SSL certificate file and the public key file cannot be used together.
  • The machine might have been exited while connections were active.

Action: Rebuild the post office database. Action: Make sure that the DNS name server is running. Right-click the GWIA object, then click Properties. WEBACC: No gateway directory was specified Source: GroupWise WebAccess Agent Explanation: The WebAccess Agent must know the path to its gateway home directory.

See Using Dynamic Internet Links in Connecting to Other GroupWise Systems in the GroupWise 8 Multi-System Administration Guide. Possible Cause: Another MTA is already running on the server where you are trying to start this MTA. Make sure each MTA is using a unique port. http://wipidigital.com/socket-error/how-to-fix-socket-error.html See Moving the MTA to a Different Server in Message Transfer Agent in the GroupWise 8 Administration Guide.

GWMTA: Command line parameter /home is required Source: GroupWise Message Transfer Agent. WEBACC: Startup file not found Source: GroupWise WebAccess Agent Explanation: The WebAccess Agent could not find the startup file specified by the @filename startup switch. DNS is not loaded and you are trying to resolve DNS names. Possible Cause: The agent was not able to access the startup file where the /home switch was specified.

Action: Make sure that the third-party application and the GroupWise agent are configured to use the desired TCP port. 8926 Unknown host Source: GroupWise engine; TCP/IP communication. Explanation: The MTA cannot access the domain database (wpdomain.db). Possible Cause: The /home switch has not been provided in the command to start the MTA. GWMTA: Cannot read post office database; insufficient memory Source: GroupWise Message Transfer Agent.

Action: Retype the command line or edit the startup file to include valid switches only. GWMTA: Unable to initialize message log database Source: GroupWise Message Transfer Agent; message transfer protocol. Possible Cause: The server that the agent is running on is not functioning normally. Action: Check the directory structure of the closed Internet gateway.

Action: Free up memory or add additional memory. Passwords are case sensitive. Action: Check the status of the server where the specified directory is located. Action: Check the network address information of the MTA.

Explanation: The MTA cannot move message files from its input queue (domain\wpcsin or post_office\wpcsin) to its in progress" queue (gwinprog). Possible Cause: Low memory resources.