XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''"> Error Messages
The following are possible error messages and their corresponding explanations and possible solutions. Only messages which are not self explanatory are elaborated upon. If you are having trouble, please check the QueMgr.log file usually located in the directory $P3_HOME/p3manager_files/<org>/log or in the directory that the was specified by the -log argument when starting the QueMgr. On Windows, check the Event Log under the Administrative Tools Control Panel (or a system log on Unix).
Note: | The directories (conf, log, proj) for each set of configuration file (organizational structure) must have read, write, and execute (777) permission for all users. This can be the cause of many task manager errors. |
Sometimes errors occur because the RmtMgr is running as root or administrator on Windows yet RmtMgr is trying to access network resources such as shared drives. For this reason it is recommended that RmtMgr (and QueMgr) be started as a normal user.
PCL Form Messages...
Patran Analysis Manager not installed.
Check for proper installation and authorization. Check with your system administrator. The Analysis Manager directory $P3_HOME/p3manager_files must exist and a proper license must be available for the Analysis Manager to be accessible from within Patran.
Windows
No doctemplate is loaded. Cannot create new document.
If you get a message saying, this is because you have not merged this file into the registry, or the path was incorrect. See
For Window machines: in
Queue Manager.
Job Manager Daemon (JobMgr) Errors
ERROR... Starting a JobMgr on local host.
JobMgr is unable to run most likely because of a permission problem. Make sure that the input deck is being submitted from a directory that has read/write permissions set.
================
311 ERROR... Unable to start network communication on server side.
335 ERROR... Unable to initiate server communication.
JobMgr is unable to create server communication. Possible reason is the host’s network interface is not configured properly.
================
312 ERROR... Unable to start network communication on client side.
ERROR... Unable to create and connect to client socket
JobMgr is unable to create client communication. Possible reason is the host’s network interface is not configured properly.
================
ERROR... Problem in socket accept
301 ERROR... Unable to accept network connection.
ERROR... Unable to accept message
ERROR... Unable to complete network accept.
JobMgr is unable to complete communication connection. Possible reason is the host’s network interface is not configured properly, or the network connectivity has been interrupted.
================
307 ERROR... Problem with network communication select.
ERROR... Select ready returned, but no data
ERROR... Problem in socket select
302 ERROR... Unable to read data from network connection.
306 ERROR... Data ready on network, but unable to read.
ERROR... Socket empty
327 ERROR... Data channel empty during read.
324 ERROR... Error with network communication select.
ERROR... Unknown error on select
JobMgr is unable to determine when data is available or reading. Possible cause is loss of network connectivity.
================
ERROR... Problem reading socket message.
326 ERROR... Timeout while reading message.
325 ERROR... Error in message received.
304 ERROR... Unknown receive_message error
305 ERROR... Timeout with no responses
JobMgr received an error while trying to read data or received a timeout while waiting to read data. Possible cause is loss in network connectivity or the sending process has terminated prematurely.
================
321 ERROR... Unable to contact QueMgr
ERROR... Timeout with no response from server.
JobMgr received an error or timeout while trying to contact the QueMgr. Possible cause is loss in network connectivity or the QueMgr process has terminated prematurely.
================
ERROR... Unable to accept connection from A/M
ERROR... Timeout with no response from A/M
ERROR... Unable to contact ANALYSIS MANAGER interface.
JobMgr received an error or timeout while trying to contact the Analysis Manager interface. Possible cause is loss in network connectivity or the Analysis Manager interface process has terminated (either prematurely or by user intervention).
================
339 ERROR... Unable to initiate config network communication.
328 ERROR... Unable to receive gen_config struct
329 ERROR... Unable to receive app_config struct
330 ERROR... Unable to receive app_submit struct
ERROR... Unable to receive general config info.
ERROR... Unable to receive application specific config info.
ERROR... Unable to receive application specific submit info.
JobMgr is unable to receive configuration information from the Analysis Manager interface for a submit job request. Possible cause is loss in network connectivity or premature termination of the Analysis Manager interface process.
================
340 ERROR... Unable to send general config info.
341 ERROR... Unable to send application specific config info.
342 ERROR... Unable to send application specific submit info.
JobMgr is unable to send configuration information to the [Aba,Gen,Mar,Nas]Mgr process. Possible cause is loss in network connectivity or premature termination of the [Aba,Gen,Mar,Nas]Mgr process.
================
ERROR... Out of memory
303 ERROR... Unable to alloc memory.
ERROR... Unable to alloc mem for file sys max
ERROR... Unable to alloc mem for file sys space
ERROR... Unable to alloc mem for file sys names
This indicates the workstation is out of memory. Free up memory used by other processes and try to submit again at a later time.
================
344 ERROR... Unable to determine mail flag from config struct
ERROR... Unable to determine mail config setting.
JobMgr is unable to query memory for the mail config setting. Contact support personnel for assistance.
================
345 ERROR... Unable to determine delay time from config struct
ERROR... Unable to determine delay time setting.
JobMgr is unable to query memory for the delay time config setting. Contact support personnel for assistance.
================
350 ERROR... Unable to determine disk req from config struct
ERROR... Unable to determine disk requirement.
JobMgr is unable to query memory for the disk req config setting. Contact support personnel for assistance.
================
349 ERROR... Unable to determine memory req from config struct
ERROR... Unable to determine memory requirement.
JobMgr is unable to query memory for the memory req config setting. Contact support personnel for assistance.
================
352 ERROR... Unable to determine pos prog from config struct
ERROR... Unable to determine pos program.
JobMgr is unable to query memory for the pos prog config setting. Contact support personnel for assistance.
================
351 ERROR... Unable to determine pre prog from config struct
ERROR... Unable to determine pre program.
JobMgr is unable to query memory for the pre prog config setting. Contact support personnel for assistance.
================
353 ERROR... Unable to determine job filename from config struct
ERROR... Unable to determine job filename.
JobMgr is unable to query memory for the job filename config setting. Contact support personnel for assistance.
================
337 ERROR... Unable to determine specific index from submit struct
338 ERROR... Unable to determine submit specific host index.
JobMgr is unable to query memory for the specific index config setting. Contact support personnel for assistance.
================
ERROR... Unable to determine submit index from submit struct
ERROR... Unable to determine submit host index.
JobMgr is unable to query memory for the submit index config setting. Contact support personnel for assistance.
================
ERROR... Unable to determine/execute message
JobMgr received an unrecognizable message. Contact support personnel for assistance.
================
323 ERROR... Unable to fork child process
ERROR... Unable to fork new process.
JobMgr cannot fork a new process. Perhaps the system is heavily loaded or the maximum number of per-user processes have been exceeded. Terminate extra processes and try again.
================
336 ERROR... Unable to send file receive setup info.
ERROR... Unable to accept connection on recv file
ERROR... Unable to recv file
334 ERROR... Unable to receive data file.
JobMgr is unable to set-up and/or receive the data file from the [Aba,Gen,Mar,Nas]Mgr. Possible cause is loss of network connectivity or premature termination of the [Aba,Gen,Mar,Nas]Mgr process.
================
ERROR... Unable to send file
333 ERROR... Unable to transfer data file.
JobMgr is unable to send data file to [Aba,Gen,Mar,Nas]Mgr process. The executing host or network connection may be down.
================
346 ERROR... Unknown state
347 ERROR... Inconsistant state.
JobMgr is in an inconsistent state. Contact support personnel for assistance.
================
310 ERROR... Unable to open log file.
JobMgr is unable to open log file. Check write permission on the current working directory and log file (if it exists).
================
348 ERROR... Unable to cd to local work dir.
JobMgr is unable to change directory to the directory with the input filename specified. Check existence and permissions on this directory.
================
314 ERROR... Unable to determine true host address.
315 ERROR... Unable to determine actual host address.
JobMgr is unable to determine its host address. Possible causes are an invalid host file or name
server entry.
================
316 ERROR... Unable to determine usrname.
JobMgr cannot determine user name. Check the passwd, user account files for possible errors.
================
322 ERROR... Unable to open stdout stream.
ERROR... Unable to open stderr stream.
JobMgr cannot open stdout, stderr streams.
================
331 ERROR... Application is NOT supported.
JobMgr is asked to submit a job which is not from a supported application. Check installation by running the basic and network tests with the Administration tool.
================
343 ERROR... Received signal.
JobMgr received a signal from the operating system. JobMgr has encountered an error or was signalled by a user.
================
354 ERROR... Invalid version of Job Manager.
The current version of JobMgr does not match that of the QueMgr. An invalid/incomplete installation is most likely the cause. To determine what version of each executable is installed, type JobMgr -version, and QueMgr -version and compare output.
=======================================================
User Interface (P3Mgr) Errors...
ERROR... <type> argument must be a number from 1 - 8
P3Mgr must be started with an initial interface type of 1 through 8 only.
================
ERROR... -runtype not acceptable.
P3Mgr was started with an invalid runtype for ABAQUS.
================
ERROR... Getting P3_HOME environment variable.
P3Mgr is unable to determine the P3_HOME environment variable. Set the environment variable to the location of the Patran install path (<installation_directory> for example).
================
ERROR... Obtaining ANALYSIS MANAGER licenses.
P3Mgr is unable to obtain necessary license tokens. Check nodelock file or netls daemons.
================
ERROR... Problem reading .p3mgrrc
ERROR... Unable to write to file <.../.p3mgrrc[_org]>
P3Mgr is unable to read/write to the “rc” file to load/save configuration settings. Check the owner and permissions on the designated file.
================
ERROR... Unable to determine QueMgr host or port
P3Mgr cannot determine which port to connect to a valid Queue Manager. The file QueMgr.sid is not actually used anymore. You should set P3_MASTER and P3_PORT environment variables, or use the org.cfg file.
================
ERROR... QueMgr host <> from org.cfg file inconsistent
ERROR... QueMgr port <> from org.cfg file inconsistent
P3Mgr has found the QueMgr host and/or port from the QueMgr.sid file to be different from that found in the org.cfg file. Check the org.cfg file and modify it to match the current QueMgr settings, or restart the QueMgr with the org.cfg settings. The QueMgr.sid file is no longer used so this message should never appear. Call MSC support personnel if this happens.
================
ERROR... Unable to determine address of master host <>
P3Mgr is unable to determine the address of the master host provided. Check the QueMgr.sid file for proper hostname and/or the org.cfg file and/or the P3_MASTER environment variable. Also check for an invalid host file or name server entry. The QueMgr.sid file is no longer used so this message should never appear. Call MSC support personnel if this happens.
================
ERROR... Unable to Contact QueMgr to determine version information.
P3Mgr is unable to contact the QueMgr. Check to see if the QueMgr is up and running, and the master host is up and running, and the P3Mgr host and the master host can communicate via the network.
================
ERROR... Problem creating socket to communicate with Queue Mgr
ERROR... Unable to send request to Queue Mgr. Is the Queue Mgr running
ERROR... #<> sending request to Queue Mgr.
ERROR... #<> receiving message back from QueMgr.
ERROR... In message back from QueMgr.
ERROR... Communicating with Queue Mgr.
ERROR... Invalid message received from QueMgr.
ERROR... Timeout Waiting For Message From QueMgr.
P3Mgr cannot create communication socket, or is unable to send request to the QueMgr process. Check the QueMgr process is up and running, the QueMgr host is up and running, and the network is connected.
================
ERROR... Creating Communications Socket For Job Monitor
ERROR... Establishing communication to Job Mgr with port <>.
ERROR... In Job Mgr Communication
P3Mgr cannot create communication socket, or is unable to send request to the JobMgr process. Check the JobMgr process is up and running, and the network is connected.
================
ERROR... Sending generic configuration structure to Job Mgr
ERROR... Sending application configuration structure to Job Mgr
ERROR... Sending submit structure to Job Mgr
P3Mgr cannot send configuration info to the P3Mgr process. Check that the P3Mgr process is up and running, and the network interface is configured properly.
================
ERROR... An incompatible version of the QueMgr is currently running.
P3Mgr has determined that the version of the QueMgr presently running is not compatible. An incomplete or invalid installation is most likely the cause. Type P3Mgr -version and QueMgr -version and compare the output. Re-install the software if necessary.
================
ERROR... No valid applications defined in QueMgr configuration
P3Mgr has been started with an application not supported by the current configuration used by the QueMgr. Update the configuration files to include the new application and restart the QueMgr before continuing.
================
ERROR... Org <> does not contain any defined applications.
P3Mgr has been started (or switched to) an organization (group) which does not contain any applications. Check the configuration files and restart the QueMgr process for the designated organization.
================
ERROR... Filename is too long. Shorten jobname
P3Mgr can only submit jobs with files no longer than 32 characters. Shorten the job filename to less than 32 characters and submit again.
================
ERROR... Job <> is not currently active.
P3Mgr was asked to monitor or delete a job with a given name (and owner) which cannot be located in the queue.
================
ERROR... File <> does not exist... Enter A/M to select file explicitly.
P3Mgr was asked to monitor a completed job (using the mon file) from the jobname information only and this file cannot be found. Use the Full Analysis Manager interface and the file browser (under Monitor, Completed Job) to select an existing mon file.
================
ERROR... Monitor file <> does not exist
P3Mgr was asked to monitor a completed job and the selected mon file does not exist. Select an existing mon file and try again.
================
ERROR... You must choose an A/M monitor file (.mon extension).
P3Mgr was asked to monitor a completed job, but no mon file was specified. Select a mon file and try again.
================
ERROR... Unable to parse Monitor File
P3Mgr encountered an error while parsing the mon file. Contact support personnel for assistance.
================
ERROR... than one active job named <> found. Request an active list
ERROR... More than one active job named <> found. Enter A/M to explicitly select job
ERROR... No jobs named <> owned by <> are currently active
P3Mgr is asked to monitor or delete a job from the job name (and owner) and no such job can be located in the queues. Select an active list of jobs from the Full Analysis Manager interface (Monitor, Running jobs)
================
ERROR... No Host Selected. Submit cancelled.
ERROR... No Queue Selected. Submit cancelled.
P3Mgr attempted to submit a job, but no host or queue was selected. Select a host or queue and try to submit again.
================
ERROR... QueMgr has been reconfigured. Exit and restart to continue.
P3Mgr has found the QueMgr has been reconfigured (restarted) and so the P3Mgr’s copy of the configuration information may be invalid. Exit the P3Mgr interface and restart to load the latest configuration information before continuing.
================
ERROR... Starting a Job Mgr on local host.
P3Mgr is unable to spawn a JobMgr process. Perhaps the system is heavily loaded or the maximum number of per-user processes has been met. Free up unused processes and try to submit again.
================
ERROR... Unable to alloc mem for load info.
ERROR... Unable to allocate memory for org structure
This indicates the workstation is out of memory. Free up memory used by other processes and try again.
================
ERROR... Unable to open log file
P3Mgr is unable to open a log file. Check file permissions if it exists, or check local directory access/permissions.
================
ERROR... Unable to open unique submit log file
P3Mgr is unable to open a submit log file. Check file permissions if it exists, or check local directory access/permissions.
================
ERROR... Unknown version of ANALYSIS MANAGER .p3mgrrc file
P3Mgr has attempted to read in a .p3mgrrc file but from an unsupported version. Remove the .p3mgrrc file and save configuration settings in a new .p3mgrrc file.
================
ERROR... Could not open file <>
P3Mgr is asked to submit a job, but no filename has been input. Selected an input filename and try to submit again.
================
ERROR... File <> does not exist.
P3Mgr has been asked to submit a file, but no such file can be found. Select an existing input file (or check file permissions) and submit again.
Additional (submit) Errors...
ABAQUS:
ERROR... JobName <> and Restart JobName <> are identical.
ABAQUS cannot have jobs where the job name and the restart job name are the same. Change one or the other and re-submit.
================
ERROR... Unable to open input file <>
P3Mgr is unable to open the designated input file. Check file permissions.
================
ERROR... JobName <> and Input Temperature File JobName <> are identical.
ABAQUS cannot have jobs where the job name and the temperature data file job name are the same. Change one or the other and re-submit.
================
ERROR... *RESTART, READ found but no restart jobname specified.
ABAQUS “RESTART” card encountered, but no filename specified. Add filename to this card and
re-submit.
MSC Nastran:
================
ERROR... File <> cannot contain more than one period in its name.
P3Mgr will currently only allow MSC Nastran jobs to contain one period in their filename. Rename the input file to contain no more than one period and re-submit.
================
ERROR... File <> must begin with an alpha character.
P3Mgr will currently only allow MSC Nastran jobs to start with an alpha character, and not a number. Rename the input file to start with a letter (A-z, a-z) and re-submit.
================
ERROR... Include cards are too early in file.
P3Mgr can currently only support MSC Nastran jobs with Include cards between the “BEGIN BULK” and “ENDDATA” cards. Place the contents of the include files before the “BEGIN BULK” card directly into the input file and re-submit.
================
ERROR... BEGIN BULK card present with no CEND card present.
P3Mgr has encountered a “BEGIN BULK” card before a “CEND” card. P3Mgr currently requires a “BEGIN BULK” card if there is a “CEND” card found in the input file. Add a “BEGIN BULK” card to the input file and re-submit.
================
ERROR... ENDDATA card missing.
P3Mgr has encountered the end of the input file without finding an “ENDDATA” card. Add an “ENDDATA” card and re-submit.
MSC.Marc:
================
ERROR... Unable to load MSC.Marc configuration info.
The network is unable to transfer the MSC.Marc config info over to the MarMgr from the JobMgr running on the submit machine. Check network connectivity and the submit machine for any problems.
================
ERROR... Unable to load MSC.Marc submit info
The network is unable to transfer the MSC.Marc submit info over to the MarMgr from the JobMgr running on the submit machine. Check network connectivity and the submit machine for any problems.
================
INFORMATION: Total disk space req of %d (kb) met
Information message telling that enough disk space has been found on the file systems configured for MSC.Marc to run.
================
WARNING: Total disk space req of %d (kb) cannot IMMEDIATLEY be met. Continuing on regardless ...
Information message telling that there is currently not enough free disk space found to honor the space requirement provided by the user. The job will continue however, because the space may be freed up at a later time (by another job finishing perhaps) before this job needs it
================
ERROR... Total disk space req of %d (kb) cannot EVER be met. Cannot continue.
There is not enough disk space (free or used) to honor the space requirement provided by the user so the job will stop. Add more disk space or check the requirement specified.
================
WARNING: Cannot determine if disk space req %d (kb) can be met. Continuing on regardless ...
Information message telling the disk space of the file system(s) configured for MSC.Marc cannot be determined. The job will continue anyway as there may be enough space. Sometime, if the file system is mounted over nfs the size of the file system is not available.
================
INFORMATION: No disk space requirement specified
If no disk space requirement is provided by the user then this information message will be printed.
================
ERROR... Unable to alloc ## bytes of memory in sss, line lll
The MarMgr is unable to allocate memory for its own use, check the memory and swap space on the executing machine.
================
ERROR... Unable to receive file sss
MarMgr could not transfer a file from the JobMgr on the submit machine. Check the network connectivity and submit machine for any problems.
Editing (p3edit) Errors...
ERROR... Unable to allocate enough memory for file list.
This indicates the workstation is out of memory. Free up memory used by other processes and try again.
================
ERROR... Unable to determine file statistics for <>
This indicates the operating system is unable to determine file statistics for the requested file. The requested file most likely does not exist. Select an existing file to view/edit and try again.
================
ERROR... File <> does not appear to be ASCII
P3edit can only view/edit ASCII files, and the requested file appears to be non-ASCII. Select an ASCII file to view/edit and try again.
================
ERROR... File <> is too large to view
Due to memory constraints, P3edit is limited to viewing/editing files no larger than 16 mb in size. (Except for Cray and Convex machines, where the max file size limit is 60 mb and 40 mb, respectively) Select a smaller file to view/edit and try again.
================
ERROR... Unable to open file <>
P3edit is unable to open requested file to load into viewer/editor. Select an existing file to view/edit and try again.
================
ERROR... File <> is empty
P3edit has found the selected file is empty. Currently P3edit can only view/edit files with data. Select a file containing data to view/edit and try again.
================
ERROR... Unable to seek to beginning of file <>
P3edit is unable to seek to beginning of selected file. Possible system error occurred during seek, or file is corrupted.
================
ERROR... Unable to read in file <>
P3edit is unable to read file data. Perhaps file is corrupted.
================
ERROR... System error while reading file <>
A system error occurred during file read. Try to view/edit file again at another time.
================
ERROR... Unable to read text
P3edit is unable to read file completely, or is unable to read text from memory to write file.
================
ERROR... Unable to scan text
P3edit is unable to scan text from memory to search for text pattern.
================
ERROR... Unable to write text to file
P3edit is unable to write text out to file. Perhaps the disk is full, or some system error occurred during the write call.
RmtMgr Errors...
RmtMgr errors are returned to the connection program and also printed in the OS system log (syslog) or Event Viewer for Windows.
================
RmtMgr Error RM_CANT_GET_ADDRESS
This should not happen, but if for some reason the OS / network ca not determine the network address of the machine RmtMgr is started on this will be printed before RmtMgr exits. Contact your system administrator for more information.
================
RmtMgr Error port number #### invalid
This should not happen, but if for some reason the program contacting the RmtMgr does not supply a valid port then this will be printed. The connection to the RmtMgr cannot be completed, but the RmtMgr will continue on listening for other connections.
================
RmtMgr Error RM_CANT_CREATE_SERVER_SOCKET
If the RmtMgr can not create its main server socket for listening then this error message will be printed before the RmtMgr exits.
================
RmtMgr Error accept failed, errno = ##
If the accept system call fails on the socket after a connection is established this will be printed. The error number should be checked against the system errno list for the platform to see the cause.
================
RmtMgr Error unable to end proc ## errno=%d",
If RmtMgr is asked to kill/end a process and it is unable to do so then this message is printed. The errno should give the reason.
================
RmtMgr Error Invalid message of <xxxxx>
An invalid message format/syntax was sent to RmtMgr. The message will be ignored and RmtMgr will continue, listening for other connections.
================
RmtMgr Error Invalid message status code = ##
The status on the receive message is not correct, the status code will help determine the cause, most likely invalid network connectivity is the reason.
================
RmtMgr Error Invalid NULL message
An invalid message format/syntax was sent to RmtMgr. The message will be ignored and RmtMgr will continue, listening for other connections.
================
RmtMgr Error unable to determine system type, error = ##
RmtMgr is unable to determine what kid of platform it is running on. RmtMgr will exit. Check the supported platform/OS list.
================
RmtMgr Error WSAStartup failed, code = ##
Windows network/socket communication initialization failed the code should be checked against the windows system error list for the cause.
================
RmtMgr Error WSAStartup version incompatible, code = ##
If a contacting program is of a different version than the RmtMgr then this message is printed. The RmtMgr will continue, listening for other connections.
QueMgr Errors...
Sometimes errors occur because the RmtMgr is running as root or administrator on Windows yet RmtMgr is trying to access network resources such as shared drives. For this reason it is recommended that RmtMgr (and QueMgr) be started as a normal user.
ERROR... Determining computer architecture
QueMgr is unable to recognize its host architecture. Check installation and OS version compatibility.
================
ERROR... Invalid -port option argument <>
ERROR... Invalid -usr option argument <>
QueMgr was started with an invalid port or user argument. Select a valid port or user name argument and try to start the QueMgr again.
================
ERROR... Can’t Find Job Number To Remove.
ERROR... Can’t Find Job Number To Resume.
ERROR... Can’t Find Job Number To Suspend.
ERROR... Can’t Find Job To Resume.
ERROR... Can’t Find Job To Suspend.
202 ERROR... Job to remove not found by the Que Manager.
QueMgr is unable to locate job in internal list to remove, resume or suspend. Contact support personnel for assistance.
================
ERROR... Can’t Resume Job unless its RUNNING and SUSPENDED.
ERROR... Can’t Suspend Job unless its RUNNING.
QueMgr received an invalid suspend/resume request. QueMgr can only suspend running jobs, and can only resume suspended jobs.
================
203 ERROR... Problem creating com file for Task Manager execution.
QueMgr is unable to create a com file on the eligible host(s) for execution. Possible causes are lack of permission connecting to the eligible host(s) as the designated user (check network permission/access using the Administration tool) or incorrect path/permission on the directory on the eligible host(s). (Use the Administration tool to check this.) The major cause of this error is that the specified user does not have remote shell access from the Master Host to the Analysis Host. Resolutions to this problem are to add the Analysis Host name to the hosts.equiv file or the user‘s.rhosts file on the Master Host.
================
ERROR... Creating host/port file <>.
QueMgr is unable to create the QueMgr.sid file containing its host and port number. Possible causes are invalid sid user name (with the -usr command line option), invalid organization (-org command line option) or invalid network or directory/file permissions. This file and -usr are no longer used and the message should not ever appear. Call MSC support if this happens.
================
ERROR... Opening log file <>
ERROR... Opening rdb file <>
ERROR... Seeking to end of rdb file <>
ERROR... Unable to determine next valid job number
RECONFIG ERROR... Unable to determine next valid job number
QueMgr is unable to open the log and/or rdb files. Check the owner and permissions of these files. If the rdb file is corrupted, QueMgr may not be able to seek to its end and determine the next available job number to use.
================
ERROR... Out Of Memory
ERROR... Problem Allocating memory for return string
ERROR... Unable to alloc mem for load info
ERROR... Unable to alloc memory for load information
RECONFIG ERROR... Unable to alloc mem for load info
The workstation is out of memory. Free up memory used by other processes and restart the QueMgr.
================
ERROR... Problem Creating Socket.
ERROR... Problem Binding Socket.
ERROR... Problem Connecting Socket.
ERROR... Problem Reading Socket Message.
ERROR... Problem Writing To Socket.
ERROR... Problem in socket accept.
ERROR... Problem in socket select.
QueMgr cannot create/complete/read/write network communication. Possible causes are invalid network interface configuration, or a loss in network connectivity.
ERROR... Unable to signal Task
QueMgr is unable to send signal to [Aba,Gen,Mar,Nas]Mgr. Check network permission/access using the Administration tool.
================
ERROR... Problem Telling JobMgr That Job Is Being Killed.
QueMgr has been requested to terminate a job, and cannot inform the JobMgr of this. Possible cause is network connectivity loss, or the JobMgr process has terminated unexpectedly, or the JobMgr workstation is down.
ERROR... Host Index <> Received, Max Index is <>,
ERROR... Queue Index <> Received, Max Index is <>
ERROR... Specific Index <> Received, Max Index is <>
QueMgr asked to submit a job with an invalid index. Contact support personnel for assistance.
================
ERROR... User: <> can not delete job number <> which is owned by: <>
201 ERROR... User can not kill a job owned by someone else.
QueMgr was asked to delete a job from a user other than the one who submitted the job. Only the user who submitted a job is eligible to delete it.
================
ERROR... You must be the root user to run QueMgr.
The QueMgr process must run as the root user. Restart the QueMgr as the root user.
================
209 ERROR... Unable to start Task Manager.
QueMgr is unable to start up an [Aba,Gen,Mar,Nas]Mgr process. Check network/host connections and access, and install tree path on the remote host. (Use the Administration tool to check network permissions.)
================
ERROR... Unable to start Load Manager on host <>
QueMgr is unable to start up a LoadMgr process. Check network/host connections and access, and install tree path on the remote host. Also, check admin user account access. (Use the Administration tool to check network permissions.) Obsolete. RmtMgr is now used.
================
205 ERROR... Error submitting job to NQS. See Que Manager Log.
211 ERROR... Unable to submit task to NQS queue.
QueMgr received an error while trying to submit a job to an NQS queue. Check the QueMgr.log file for the more detailed NQS error.
================
206 ERROR... Error submitting job to LSF. See Que Manager Log.
207 ERROR... Error in return string from LSF bsub. See Que Manager Log.
210 ERROR... Unable to submit task to LSF queue.
QueMgr received an error while trying to submit a job to an LSF queue. Check the QueMgr.log file for the more detailed LSF error.
================
214 ERROR... Unable to delete task from NQS queue.
QueMgr is unable to delete task from an NQS queue. Perhaps the task has finished or has already been deleted by an outside source.
================
213 ERROR... Unable to delete task from LSF queue.
QueMgr is unable to delete task from an LSF queue. Perhaps the task has finished or has already been deleted by an outside source.
================
217 ERROR... Job killed from outside queue system.
QueMgr cannot find job in queue when it is expected to be there. QueMgr can only assume the job was deleted from outside the Analysis Manager environment.
================
218 ERROR... Invalid version of Task Manager.
The current version of [Aba,Gen,Mar,Nas]Mgr does not match that of the QueMgr. An invalid/incomplete installation is most likely the cause. To determine what version of each executable is installed, type [Aba,Gen,Mar,Nas]Mgr-version, and QueMgr -version and compare output.
Application Manager (AbaMgr, GenMgr, MarMgr, NasMgr) Errors...
420 ERROR... Unable to determine host address.
[Aba,Gen,Mar,Nas]Mgr is unable to determine its host address. Possible causes are an invalid host file or name server entry.
================
ERROR... File <> is NOT executable
442 ERROR... Unable to execute specified application file.
ERROR... Unable to exec new application process
Executable to run is not executable. Check file/directory permissions.
================
ERROR... File <> is NOT found
424 ERROR... Unable to determine application executable path.
Executable file cannot be found. Check application installation.
================
ERROR... Inconsistant number of valid file systems
410 ERROR... Bad file system count.
[Aba,Gen,Mar,Nas]Mgr has received an invalid number of file systems.
================
436 ERROR... Application errors.
The application has terminated with errors. This is not an Analysis Manager error, but just indicates there are errors in the analysis. Check and modify the input file and try again.
================
ERROR... Pos_application fatal
434 ERROR... Application fatal in pos routine.
The application received a fatal error in the pos routine. Contact support personnel for assistance.
================
ERROR... Pre application error
435 ERROR... Application fatal in pre routine.
The application received a fatal error in the pre routine. Contact support personnel for assistance.
================
ERROR... Abort_application fatal
The application received a fatal error in the abort routine. Contact support personnel for assistance.
================
426 ERROR... Unable to alloc mem.
ERROR... Unable to alloc mem for File_Sys
ERROR... Unable to alloc mem for executable path
ERROR... Unable to alloc mem for file system names
The workstation is out of memory. Free up memory used by other processes and try again.
================
403 ERROR... Unable to initiate network communication.
413 ERROR... Unable to initiate file transfer network communication.
423 ERROR... Problem with network communication accept.
415 ERROR... Problem with network communication select.
404 ERROR... Problem with network communication select.
ERROR... Unknown error on select
[Aba,Gen,Mar,Nas]Mgr is unable to start/complete network connection/read. Possible causes are loss in network connectivity or premature termination of sending process.
================
431 ERROR... Unable to connect network communication.
422 ERROR... Unable to contact QueMgr
Process is unable to contact the QueMgr. Perhaps the QueMgr host is down, or the QueMgr process is not running or the network is down.
================
ERROR... Timeout with no response from JobMgr
ERROR... Unable to accept connection from JobMgr
430 ERROR... Unable to contact JobMgr
Process is unable to contact the JobMgr. Perhaps the JobMgr host is down, or the JobMgr process is not running or the network is down.
================
ERROR... Unable to create info socket
417 ERROR... Unable to initiate job info network communication.
414 ERROR... Unable to determine job info over network.
[Aba,Gen,Mar,Nas]Mgr is unable to start info socket communication. Check network interface configuration.
================
ERROR... Unable to determine job filename
Process is unable to determine job filename. Contact support personnel for assistance.
================
ERROR... Unable to determine number of clock tics/sec
425 ERROR... Unable to determine machine clock rate.
Process cannot determine the machine setting for the number of clock tics per second. Check machine operating system manual for further assistance.
================
ERROR... Unable to fork child process
418 ERROR... Unable to fork new process
[Aba,Gen,Mar,Nas]Mgr cannot fork a new process. Perhaps the system is heavily loaded or the maximum number of per-user processes have been exceeded. Terminate extra processes and try again.
================
ERROR... Unable to load file system info
409 ERROR... Unable to load file system information.
Contact support personnel for assistance.
================
408 ERROR... Unable to locate this host in config structure
ERROR... Unable to locate this host in config host list.
Contact support personnel for assistance.
================
440 ERROR... Unable to determine current working directory.
Process could not determine its current working directory. Check file systems designated for executing [Aba,Gen,Mar,Nas]Mgr.
427 ERROR... Unable to create work file system dirs.
ERROR... Unable to make proj sub-dirs off file systems
Process could not make directories off main file system entries in the configuration. Check file system/directory access/permission. (Use the Administration tool.)
================
428 ERROR... Unable to create local work dir.
ERROR... Unable to make unique dir off proj dir
Process is unable to make a unique named directory below the designated file system/directory it is currently executing out of. Check file system/directory access/permission. (Use the Administration tool.)
================
411 ERROR... Unable to cd to local work dir.
429 ERROR... Unable to cd to local work dir.
ERROR... Unable to cd to unique dir off proj dir
Process is unable to change directory to the unique directory created below the file system/directory designated in the configuration. Check owner and permission of parent directory.
================
400 ERROR... Unable to open log file.
412 ERROR... Unable to re-open log file.
401 ERROR... Unable to open stderr stream
421 ERROR... Unable to open stdout stream
[Aba,Gen,Mar,Nas]Mgr is unable to open, re-open log and/or stdout, stderr stream files. Check current directory permissions.
================
ERROR... Unable to place process in new group
Process is unable to change process group. Contact support personnel for assistance.
================
ERROR... Unable to obtain config info from QueMgr
402 ERROR... Unable to receive configuration info.
ERROR... Unable to receive gen_config struct
ERROR... Unable to receive app_config struct
ERROR... Unable to receive app_submit struct
405 ERROR... Unable to receive general config info.
406 ERROR... Unable to receive application config info.
407 ERROR... Unable to receive application submit info.
[Aba,Gen,Mar,Nas]Mgr is unable to receive configuration information from JobMgr. Possible causes are network connectivity loss, or the JobMgr host is down.
================
ERROR... Unable to determine configuration host index
ERROR... Unable to determine <> submit paramters
[Aba,Gen,Mar,Nas]Mgr is unable to query memory for either a host index or submit parameters. Contact support personnel for assistance.
================
416 ERROR... Unable to receive data file.
ERROR... Unable to recv file <> from JobMgr
Process is unable to receive file from JobMgr. Possibly the network is down, or the JobMgr host is off the network, or the JobMgr host is down.
================
ERROR... file: <> cannot be sent
Process can not send file to JobMgr. Possibly the network is down, or the JobMgr host is off the network, or the JobMgr host is down.
================
432 ERROR... Task aborted.
437 ERROR... Task aborted while executing.
438 ERROR... Task aborted before execution.
439 ERROR... Task aborted after execution.
The [Aba,Gen,Mar,Nas]Mgr has been aborted. This is not necessarily an Analysis Manager error, but an indication that the analysis has been terminated by the user.
================
441 ERROR... Received 2nd signal.
The Process has received a signal, either from an abort (from the user) or from an internal error, and during the shutdown procedures, a second signal has occurred, indicating an error in the shutdown procedure.
================
ERROR... Total disk space req of %d (kb) cannot be met
[Aba,Gen,Mar,Nas]Mgr is unable to locate the amount of free disk space on all designated file systems of this host for the analysis to be run. Either free up some disk space, reduce the amount of disk requested in the interface, or submit job to a different host (with a different set of file systems).
================
ERROR... Unable to temporarily rename input file
[Aba,Gen,Mar,Nas]Mgr is unable to rename input file temporarily. Contact support personnel for assistance.
================
ERROR... File <> cannot be found
ERROR... Unable to open input file
Process has transferred the designated file, but is now unable to locate it for opening or reading. Check network connections, JobMgr host, and file system permissions.
================
443 ERROR... Invalid version of Task Manager
The current version of [Aba,Gen,Mar,Nas]Mgr does not match that of the QueMgr/RmtMgr. An invalid/incomplete installation is most likely the cause. To determine what version of each executable is installed, type [Aba,Gen,Mar,Nas]Mgr -version, and QueMgr/RmtMgr -version and compare output.
Additional application specific Errors...
ABAQUS (AbaMgr):
ERROR... Unable to create local environment file
AbaMgr is unable to create a local abaqus.env file. Check file system/directory free space and permissions.
================
ERROR... Unable to load ABAQUS configuration info
AbaMgr is unable to load configuration information from internal memory. Contact support personnel for assistance.
================
ERROR... Unable to load ABAQUS submit info
AbaMgr is unable to load submit information from internal memory. Contact support personnel for assistance.
================
GENERAL (GenMgr):
ERROR... Unable to load GENERAL configuration info
GenMgr is unable to load configuration information from internal memory. Contact support personnel for assistance.
================
ERROR... Unable to load GENERAL submit info
GenMgr is unable to load submit information from internal memory. Contact support personnel for assistance.
================
MSC Nastran (NasMgr):
ERROR... ASSIGN statement <> contains relative pathname
MSC Nastran ASSIGN statements cannot contain relative pathnames, as this may point to different locations from invocation to invocation. Change ASSIGN statement to a full pathname and submit again.
================
ERROR... Bad card format
NasMgr cannot parse statement properly. Check card format.
================
ERROR... Include cards in the Executive Control section
NasMgr only allows Include cards to be within the BEGIN BULK and ENDDATA sections of the input file. Place the contents of the include cards which lie before the BEGIN BULK card directly in the input file, and submit again.
================
ERROR... Restart type file but no MASTER file specified
The input file appears to be a restart, as the RESTART card is found, but no MASTER file is specified. Use an ASSIGN card to designate which MASTER file is to be used, and submit again.
================
ERROR... Unable to add MASTER database FMS
ERROR... Unable to add DBALL database FMS
ERROR... Unable to add SCRATCH database FMS
When NasMgr is adding FMS, line length is found to be greater than the maximum of 80 characters. Decrease the filename (jobname) length or use links to shorten the file system/directory names.
================
ERROR... Unable to load MSC Nastran configuration info
NasMgr is unable to load configuration information from internal memory. Contact support personnel for assistance.
================
ERROR... Unable to load MSC Nastran submit info
NasMgr is unable to load submit information from internal memory. Contact support personnel for assistance.
================
ERROR... Unable to read file include <>
NasMgr has transferred the designated file, but is now unable to locate it for opening or reading. Check network connections, JobMgr host, and file system permissions.
================
ERROR... Unexpected end of file
NasMgr has encountered the end of the input file without finding complete information. Check input file.
MSC.Marc (MarMgr):
================
ERROR... Unable to load MSC.Marc configuration info.
The network is unable to transfer the MSC.Marc config info over to the MarMgr from the JobMgr running on the submit machine. Check network connectivity and the submit machine for any problems.
================
ERROR... Unable to load MSC.Marc submit info
The network is unable to transfer the MSC.Marc submit info over to the MarMgr from the JobMgr running on the submit machine. Check network connectivity and the submit machine for any problems.
================
INFORMATION: Total disk space req of %d (kb) met
Information message telling that enough disk space has been found on the file systems configured for MSC.Marc to run.
================
WARNING: Total disk space req of %d (kb) cannot IMMEDIATLEY be met. Continuing on regardless ...
Information message telling that there is currently not enough free disk space found to honor the space requirement provided by the user. The job will continue however, because the space may be freed up at a later time (by another job finishing perhaps) before this job needs it
================
ERROR... Total disk space req of %d (kb) cannot EVER be met. Cannot continue.
There is not enough disk space (free or used) to honor the space requirement provided by the user so the job will stop. Add more disk space or check the requirement specified.
================
WARNING: Cannot determine if disk space req %d (kb) can be met. Continuing on regardless ...
Information message telling the disk space of the file system(s) configured for MSC.Marc cannot be determined. The job will continue anyway as there may be enough space. Sometime, if the file system is mounted over nfs the size of the file system is not available.
================
INFORMATION: No disk space requirement specified
If no disk space requirement is provided by the user then this information message will be printed.
================
ERROR... Unable to alloc ## bytes of memory in sss, line lll
The MarMgr is unable to allocate memory for its own use, check the memory and swap space on the executing machine.
================
ERROR... Unable to receive file sss
MarMgr could not transfer a file from the JobMgr on the submit machine. Check the network connectivity and submit machine for any problems.
Administration (AdmMgr) Testing Messages...
ERROR... An invalid version of Queue Manager is currently running
The current version of AdmMgr does not match that of the running QueMgr. An invalid/incomplete installation is most likely the cause. To determine what version of each executable is installed, type AdmMgr -version, and QueMgr -version and compare output.
================
ERROR... <> specified as type for host, but <> detected.
ERROR... <> specified as type for host, but UNKNOWN is detected.
ERROR... Host Type <> is not a valid selection for host <>.
The AdmMgr program has discovered the host architecture for the indicated host is not the same as what is designated in the configuration, or no specific type has been given to this host. Change the host type to the correct one and re-test.
================
ERROR... A/M Host <> configuration file <> does not contain an absolute path.
The AdmMgr program has found an rc file entry, or an exe file entry in the host.cfg file, or a file system in the disk.cfg file to not be a full path. Change the entries to be fully qualified. (starts with a slash character ‘/’)
================
ERROR... A/M Host <> does not have a valid application defined. Run Basic A/M Host Test.
The configuration files do not contain any valid applications. Add a valid application and all its required information and run the basic test to verify.
================
ERROR... A/M Host <> filesystem <> does not contain an absolute path.
The file system designated for the host listed is not fully qualified. Change the entry to begin with a slash ‘/’ character.
================
ERROR... A/M Host <> runtime file <> does not contain an absolute path.
The rc file designated for the host listed is not fully qualified. Change the entry to begin with a slash ‘/’ character.
================
ERROR... A/M Host name <> is used more than once within application <>.
Each application contains a list of Analysis Manager host names (which are mapped to physical host names) and each Analysis Manager host name must be unique. The AdmMgr program has found the designated Analysis Manager host names is being used more than once. Change the Analysis Manager host name for all but one of the applications and re-test.
================
ERROR... Access to host <> failed for admin <>.
ERROR... Access to host <> invalid return string for admin <>.
ERROR... Access to host <> failed for user <>.
ERROR... Access to host <> invalid return string for user <>.
ERROR... Bad return string from physical host <>.
These errors indicate various problems when trying to execute a command on the designated host as the admin or user provided. Network access to a host for a user can fail for a number of reasons, among which are lack of network permission or the network/host is down. To check network permission, the user must be able to rsh (or remsh on some platforms) from the master host (where the QueMgr process runs) to each application host (not interface host, but where the defined application is targeted to run). Rsh (or remsh) access is denied if the user has no password on the remote host, does not have a valid .rhosts file in his/her home directory on the remote host, with the same owner and group ids, and file permissions of 600 (-rw-------) or there is no /etc/hosts.equiv file on the remote host, with an entry for the originating host. The RmtMgr replaces rsh. Call MSC if you get this error.
================
ERROR... Admin account can NOT be root.
The AdmMgr program requires an administrator account which is not the root account. Change the administrator account name to something other than root and continue testing.
================
ERROR... Unable to locate Admin account <>.
The AdmMgr program is unable to locate the admin account name in the passwd file/database. Make sure the admin account name provided is a valid user account name on all application hosts (and the master host as well) and continue testing.
================
ERROR... Application must be chosen for A/M Host <>.
The configuration requires each Analysis Manager host to reference an application. Add a reference for this AM host and re-test.
================
ERROR... Application name <> is not referenced by any A/M Host.
The application specified is not referenced by any Analysis Manager hosts. Add AM hosts or remove this application and continue testing.
================
ERROR... Application name <> is used more than once.
Only unique application names can be used. Re-name the applications so no two are alike and re-test.
================
ERROR... Application not specified for A/M Host <>.
Cannot do Unique A/M Host Test. The configuration requires each A/M host to reference an application. Add a reference for this A/M host and re-test.
================
ERROR... At least one filesystem must be defined for A/M Host <>.
The configuration requires each Analysis Manager host to reference a file system. Add a reference for this AM host and re-test.
================
ERROR... At least one host must be specified.
At least one physical host must be specified. Add a physical host entry and re-test.
================
ERROR... At least one application must be specified.
At least one application must be defined. Add an application and re-test.
================
ERROR... Could not determine host address for host <>.
The Admin program is unable to determine the host address for the designated host. Possible causes are an invalid name entered, or an invalid host file or name server entry.
================
ERROR... Detected NULL host name.
Provide a host name where specified and re-test.
================
ERROR... Executable test on host <> failed for user <>.
Either the Analysis Manager install tree is not accessible on the remote host, or network access to the remote host is denied. Make sure the Analysis Manager install tree is the same on all application hosts (either through nfs or by created identical directories) and try again.
If network access is the cause for failure, check network permission. (see the “ERROR... Access to host <> failed for admin <>” error description)
================
ERROR... Execution of command failed on host <>.
Either the command does not exist, or network access is denied. Most likely due to network access permission. (See the “ERROR... Access to host <> failed for admin <>” error description.)
================
ERROR... Failure Creating file <> on host <>.
ERROR... Failure Accessing Test File <> on host <>.
The user does not have permission to create/access a test file in the proj directory on the designated host. Check the permission of this directory on the remote host and re-test. If permission is not the problem, check network access to the remote as the user. (See the “ERROR... Access to host <> failed for admin <>” error description.)
================
ERROR... Failure Creating Test File <> on host <>.
The user does not have permission to create/access a test file in the file system/directory on the designated host as listed in the disk.cfg file. Check the permission of this directory on the remote host and re-test. If permission is not the problem, check network access to the remote host as the user. (See the “ERROR... Access to host <> failed for admin <>” error description.)
================
ERROR... Host <> and Host <> have an identical addresses.
Remove one of the host entries (since they are the same host) or change one to point to a different host and re-test.
================
ERROR... Host not specified for A/M Host <>. Run Basic A/M Host Test.
Each Analysis Manager host must reference a physical host. Provide a physical host reference and continue testing.
================
ERROR... Invalid A/M queue name <>.
ERROR... Invalid LSF queue name <>.
ERROR... Invalid NQS queue name <>.
Enter a valid queue name (no space characters, etc.) and re-test.
ERROR... LSF executables path <> must be an absolute path.
ERROR... NQS executables path <> must be an absolute path.
The pathname must be a fully qualified path name. Change the path to be fully qualified (starts with a slash ‘/’ character) and re-test.
================
ERROR... NULL A/M Host name is invalid.
Provide an A/M host name where specified and re-test.
================
ERROR... No queue defined for application <>.
Provide a queue where specified and re-test.
================
ERROR... Physical host has not been defined for A/M Host <>. Run Basic A/M Host Test.
Each Analysis Manager host must reference a physical host. Provide a physical host reference and continue testing.
================
ERROR... Physical host must be chosen for A/M Host <>.
Each Analysis Manager host must reference a physical host. Provide a physical host reference and continue testing.
================
ERROR... Remote execution of uname command failed on host <>.
Either the uname command (required by Analysis Manager) cannot be found on the remote host of the user’s default search path, or the network access to the remote host is denied. Check the existence, permission, and location of the uname command on the remote host. (Some Convex machines are shipped without a uname, but Analysis Manager provides one, just place a copy of the uname program (or link) into a default path directory, such as /bin.) If network access is the cause of failure, check as above. (See the “ERROR... Access to host <> failed for admin <>” error description.)
================
ERROR... Unable to start executable <.../bjobs> on host <> as user <>.
ERROR... Unable to start executable <.../bkill> on host <> as user <>.
ERROR... Unable to start executable <.../bsub> on host <> as user <>.
ERROR... Unable to start executable <.../qdel> on host <> as user <>.
ERROR... Unable to start executable <.../qstat> on host <> as user <>.
ERROR... Unable to start executable <.../qsub> on host <> as user <>.
Either the designated files do not exist on the remote host as indicated or the network access to the remote host to test each executable is failing. Check the file existence and change the path as required, or check network access as described above. (See the “ERROR... Access to host <> failed for admin <>” error description.)
================
ERROR... Zero A/M hosts defined. At least one required.
Define an Analysis Manager host and re-test.
================
ERROR... Zero queues defined. At least one required.
Define a queue and re-test.
================
ERROR... Queue <> must contain at least one selected host.
Select a host or hosts from the list for each queue and continue.
================
ERROR... configuration file <> not located on physical host <>.
ERROR... runtime file <> not located on physical host <>.
The AdmMgr program cannot locate the rc or exe file designated in the configuration on the specified host. Check the installation of the application or the rc/exe path and re-test.
================
ERROR... Unable to open unique submit log file
In the current working directory, there are more than 50 submit log files.