Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Messages   |   Catalog List   |   Previous   |   Next

WEBGUI Messages 4000-4099

4002	ERROR: Illegal options : duplicate optval option
	Description	The tuxwsvr(1) portable webserver was executed with the optval option specified multiple times. As a result of this error, tuxwsvr(1) prints a usage message and exits.
	Action	Re-execute tuxwsvr(1) with proper options.
	See Also	tuxwsvr(1)
4003	ERROR: command network address not specified
	Description	The tuxwsvr(1) command was invoked without the required -l option and its associated network address. As a result of this error, tuxwsvr(1) prints a usage message and exits.
	Action	Reinvoke tuxwsvr(1) with a network address specified as an argument to the -l option.
	See Also	tuxwsvr(1)
4004	ERROR: Illegal options : duplicate optval option
	Description	The tuxwsvr(1) portable webserver was executed with the optval option specified multiple times. As a result of this error, tuxwsvr(1) prints a usage message and exits.
	Action	Re-execute tuxwsvr(1) with proper options.
	See Also	tuxwsvr(1)
4005	ERROR: Illegal options : duplicate optval option
	Description	The tuxwsvr(1) portable webserver was executed with the optval option specified multiple times. As a result of this error, tuxwsvr(1) prints a usage message and exits.
	Action	Re-execute tuxwsvr(1) with proper options.
	See Also	tuxwsvr(1)
4007	ERROR: Illegal options : duplicate optval option
	Description	The tuxwsvr(1) portable webserver was executed with the optval option specified multiple times. As a result of this error, tuxwsvr(1) prints a usage message and exits.
	Action	Re-execute tuxwsvr(1) with proper options.
	See Also	tuxwsvr(1)
4008	ERROR: Invalid option option_letter
	Description	The tuxwsvr(1) portable web server was executed with an invalid option option_letter. As a result of this error, tuxwsvr(1) prints a usage message and exits.
	Action	Re-execute tuxwsvr(1) with proper options.
	See Also	tuxwsvr(1)
4010	ERROR: Memory allocation failure
	Description	The tuxwsvr(1) portable web server was unable to allocate sufficient memory to store the contents of its initialization file in memory. As a result of this error, tuxwsvr(1) is unable to process requests and will exit.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
4011	WARN: Line line_number of initialization file has prefix of "slash_character" and is not last non-commentary line in file
	Description	The tuxwsvr(1) initialization file contained a line with a prefix of / prior to the last non-comment line in the file. When tuxwsvr(1) receives a request, it searches its in-memory copy of the initialization file and looks for the first initialization file line whose prefix matches the start of the received request. Since a line starting with / will match any request, any lines following such a line can never be chosen. tuxwsvr(1) reports a warning about this situation, but will continue to execute and process requests.
	Action	The customer should modify the web server initialization file so that a prefix of / does not occur prior to the last non-comment line in the file. At a later time when there are known to be no administrators accessing the Web GUI, the customer should kill and restart the tuxwsvr(1) process so that the changed initialization file will take effect. (Each line in the file consists of three fields. The first is the literal string HTML or CGI, the second is the prefix field, and the third is the file system path to which that prefix is mapped.)
	See Also	tuxwsvr(1)
4012	ERROR: Last non-commentary line in initialization file does not have prefix of "/"
	Description	The prefix field for the last non-comment line in the tuxwsvr(1) initialization file did not start with a /. When tuxwsvr(1) receives a request, it searches its in-memory copy of the initialization file and looks for the first initialization file line whose prefix matches the start of the received request. The prefix is then replaced with the pathname specified on the same line. So that every received request will map to some filesystem pathname, it is required that the last non-commentary line in the initialization file have a prefix of /. Because this is not the case, tuxwsvr(1) will exit.
	Action	Modify the web server initialization file so that the prefix field of the last non-comment line in the file is equal to /, and reexecute tuxwsvr(1) (Each line in the web server initialization file consists of three fields. The first is the literal string HTML or CGI, the second is the prefix field, and the third is the file system path to which that prefix is mapped.)
	See Also	tuxwsvr(1)
4013	ERROR: Could not become a background process
	Description	Normally, the tuxwsvr(1) process starts as a background program automatically. The program could not be restarted in the background and will not run.
	Action	Check for other messages printed by the web server that may shed further light on the problem, and check the userlog to see if any other Tuxedo System/T processes have also experienced problems with OS resource limits. Determine if there is an OS resource that is exhausted and re-try the command when it is resolved.
4022	WARN: Got unknown message: 'message'
	Description	The tuxwsvr(1) portable web server received a network message which it did not understand. The start of the message is printed to the web server log so that the administrator can examine it.
	Action	If the message contains a request that is an extension to the basic HTML standard (i.e. is not GET, POST, or HEAD), modify your client requests so that they use only standard HTML. If the message contains incorrectly coded HTML, contact your web browser software manufacturer to report this as a browser problem. If the message contains bytes or text that are not HTML, attempt to determine which program is incorrectly connecting to the web server port and inform the person invoking this program that they are using an incorrect network address.
	See Also	tuxwsvr(1)
4025	WARN: Cannot change directory to "directory_name" (errno=number)
	Description	When tuxwsvr(1) received a client request, it was unable to change directory to the directory associated with the first initialization file line containing a matching prefix. If the administrator specifies only accessible directories in the web server initialization file, this error should not occur even if clients request URLs which do not exist. The directory name and operating system error code (if any) are printed as part of the message.
	Action	If there is a temporary problem accessing directory_name, have your system administrator fix the problem. If directory_name if not a valid directory, change your web server initialization file to specify only valid directories. Changes to the web server initialization file will take effect when the web server is stopped and restarted.
	See Also	tuxwsvr(1)
4026	WARN: Got unknown request type
	Description	tuxwsvr(1) received a request and the first line with a matching prefix in its in-memory copy of the web server initialization file did not have an associated type of HTML or CGI. Since tuxwsvr(1) checks its initialization file at startup time to ensure that the initialization file contains only valid types, this error should not occur. As a result of the error, the web server ignores the request which produced the error.
	Action	Contact BEA Customer Support.
	See Also	tuxwsvr(1)
4027	WARN: Attempted to reference .. in path
	Description	tuxwsvr(1) received a request for a URL containing a component of '..'. Since attempting to change directory to a higher directory is a potential security violation, an error is reported to the requesting client and this message is logged.
	Action	Examine other messages in the web server log to determine if there are frequent messages indicating potential security problems. If so, there may be an intruder attempting to compromise site security, and appropriate measures should be taken. If this message appears only infrequently, no action is required.
	See Also	tuxwsvr(1)
4028	ERROR: Memory allocation failure
	Description	The tuxwsvr(1) portable web server was unable to allocate sufficient memory to process a client request. As a result of this message, tuxwsvr(1) attempts to send an error response back to the client, though any subsequent errors may prevent it from doing so.
	Action	Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
	See Also	tuxwsvr(1)
4029	ERROR: Error placing variable into process environment
	Description	tuxwsvr(1) was unable modify its process environment to set environment variables related to HTML. In most cases, the root cause of this error is a memory allocation failure.
	Action	Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
	See Also	tuxwsvr(1)
4030	ERROR: Memory allocation failure
	Description	The tuxwsvr(1) portable web server was unable to allocate sufficient memory to process a client request. As a result of this message, tuxwsvr(1) attempts to send an error response back to the client, though any subsequent errors may prevent it from doing so.
	Action	Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
	See Also	tuxwsvr(1)
4031	ERROR: Error placing variable into process environment
	Description	tuxwsvr(1) was unable modify its process environment to set environment variables related to HTML. In most cases, the root cause of this error is a memory allocation failure.
	Action	Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
	See Also	tuxwsvr(1)
4032	ERROR: Memory allocation failure
	Description	The tuxwsvr(1) portable web server was unable to allocate sufficient memory to process a client request. As a result of this message, tuxwsvr(1) attempts to send an error response back to the client, though any subsequent errors may prevent it from doing so.
	Action	Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
	See Also	tuxwsvr(1)
4033	WARN: Open failed on "filename"
	Description	tuxwsvr(1) was unable to open file filename. This error will occur if a client requests an HTML document that does not exist.
	Action	If a client requested an HTML document that does not exist, no action is required. If the requested HTML document should exist, make sure that it exists and that the user ID under which tuxwsvr(1) is running has permissions to access the document.
	See Also	tuxwsvr(1)
4034	WARN: "filename" does not exist
	Description	tuxwsvr(1) was unable to obtain file status for filename. As a result of this error, an error return is sent to the client which requested this file.
	Action	Make sure that filename exists and that tuxwsvr(1) has permission to access this file.
	See Also	tuxwsvr(1)
4035	ERROR: Network send to requesting site failed
	Description	tuxwsvr(1) encountered a network error while responding to a client request.
	Action	Look for any immediately proceeding messages in the web server log which may provide further details on the cause of the error. Make sure that the network is functioning properly.
	See Also	tuxwsvr(1)
4036	ERROR: read failed on "filename"
	Description	tuxwsvr(1) was unable to read file filename, although a previous open on this file succeeded.
	Action	Make sure that no disk errors have occurred, that filename was not suddenly deleted, and that tuxwsvr(1) still has permission to access the file.
	See Also	tuxwsvr(1)
4037	ERROR: Network send to requesting site failed (internal code internal_code)
	Description	tuxwsvr(1) encountered a network error while responding to a client request. The internal_code indicates which of several locations in the web server code the error occurred at.
	Action	Look for any immediately proceeding messages in the web server log which may provide further details on the cause of the error. Make sure that the network is functioning properly.
	See Also	tuxwsvr(1)
4038	ERROR: More than number non-comment lines in initialization file.
	Description	tuxwsvr(1) allows at most 50 separate URL prefixes to be mapped to distinct HTML directories. This number is more than adequate for the BEA Tuxedo WEB GUI and for most other applications as well. This limit was exceeded in the current initialization file.
	Action	Recode the web server initialization file to contain no more than 50 non-comment lines.
	See Also	tuxwsvr(1)
4039	ERROR: Bad initialization file line; type must be HTML or CGI
	Description	Each line in the tuxwsvr(1) initialization file must either be a comment line beginning with #, or must begin the literal string HTML or CGI, indicating that the associated prefix and directory path contain either HTML documents or CGI programs. The current initialization file did not obey this restriction.
	Action	Modify the web server initialization file so that each non-comment line begins either with the string HTML or with the string CGI.
	See Also	tuxwsvr(1)
4041	WARN: Network device does not exist
	Description	The device specified for the -d option of tuxwsvr(1) does no exist or is not a character special device. If the sockets network provider is being used, the device is not needed and will be ignored. If the TLI network provider is being used, the network open will fail.
	Action	If TLI is being used, specify the correct network device parameter. If sockets is being used, do not specify a -d option when tuxwsvr is invoked in the future.
	See Also	tuxwsvr(1)
4042	ERROR: Network send to requesting site failed
	Description	tuxwsvr(1) encountered a network error while responding to a client request.
	Action	Look for any immediately proceeding messages in the web server log which may provide further details on the cause of the error. Make sure that the network is functioning properly.
	See Also	tuxwsvr(1)
4043	ERROR: Cannot open initfile
	Description	tuxwsvr(1) was unable to open the file specified in the -i option as the web server initialization file. As a result of this error, tuxwsvr(1) will exit.
	Action	Make sure that the file specified by the -i option exists and can be read.
	See Also	tuxwsvr(1)
4044	ERROR: Cannot write CGI program POST input to temporary file tempfile
	Description	While processing a CGI POST request, tuxwsvr(1) was unable to write the POST program input to temporary file tempfile.
	Action	Make sure that the file system on which tempfile exists has adequate space available, that this user has permissions to create files in the directory where tempfile resides, and that a file named tempfile has not already been created by some other program.
	See Also	tuxwsvr(1)
4045	ERROR: Memory allocation failure
	Description	The tuxwsvr(1) portable web server was unable to allocate sufficient memory to process a client request. As a result of this message, tuxwsvr(1) attempts to send an error response back to the client, though any subsequent errors may prevent it from doing so.
	Action	Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
	See Also	tuxwsvr(1)
4048	ERROR: Cannot create HFS Temporary File
	Description	An error occurred attempting to create a temporary file in QTEMP.
	Action	Contact your IBM System Administrator
4049	ERROR: Cannot create IFS link to HFS Temporary File
	Description	An error occurred while creating IFS link from HFS file in QTEMP.
	Action	Contact your IBM System Administrator
4050	INFO: Terminating tuxwsvr process
	Description	The tuxwsvr(1) web server is exiting. This message is printed on both normal and abnormal terminations in the User Log file.
	Action	This is only an informational message. No action is required from the user for this message.
	See Also	tuxwsvr(1)
4052	WARN: Characters after third group of white space ignored
	Description	While reading the initialization file for tuxwsvr(1), extra characters were found after the third field. Only first 3 fields per each line are valid entries.
	Action	Edit the initialization file to conform to the file format.
	See Also	tuxwsvr(1)
4053	WARN: Extraneous characters after third field on initialization file line val
	Description	While reading the initialization file for tuxwsvr(1), extra characters were found after the third field. Only first 3 fields per each line are valid entries.
	Action	Edit the initialization file to conform to the file format.
	See Also	tuxwsvr(1)
4054	WARN: Extraneous characters after third field on initialization file line val
	Description	While reading the initialization file for tuxwsvr(1), extra characters were found after the third field. Only first 3 fields per each line are valid entries.
	Action	Edit the initialization file to conform to the file format.
	See Also	tuxwsvr(1)
4055	WARN: Initialization file line val does not have closing double quote
	Description	While reading the initialization file for tuxwsvr(1), a starting double quote(") was not matched with a closing double quite (").
	Action	Edit the initialization file to match double quotes on the line mentioned in the message.
4056	WARN: Embedded null character in file path on initialization file line val
	Description	In the initialization file for tuxwsvr(1) there is an escaped null character within a file path. This is not a valid input in the file.
	Action	Edit the initialization file and remove the null character on the line mentioned in the message.
4057	WARN: Octal character escape val does not fit in character on initialization file line val
	Description	In the initialization file for tuxwsvr(1) there is an octal value that is larger than 255 (maximum character value). This is not a valid input in the file.
	Action	Edit the initialization file and modify the octal value to be within the single byte character size, on the line mentioned in the message.
4058	WARN: Embedded null character in file path on initialization file line val
	Description	In the initialization file for tuxwsvr(1) there is an embedded null character within a file path. This is not a valid input in the file.
	Action	Edit the initialization file and remove the null character on the line mentioned in the message.
4059	WARN: Hexadecimal escape 0val not followed by valid hexadecimal digits on initialization file line val
	Description	In the initialization file for tuxwsvr(1) there is an invalid hexadecimal character after the hexadecimal escape sequence.
	Action	Edit the initialization file and remove the invalid hexadecimal character on the line mentioned in the message.
4060	WARN: Dubious escape val on initialization file line val
	Description	In the initialization file for tuxwsvr(1) there is an invalid escape sequence after at the specified line.
	Action	Edit the initialization file and remove the invalid escape sequence on the line mentioned in the message.
4061	ERROR: Could not become a background process
	Description	An attempt to become a background process failed for tuxwsvr(1) process.
	Action	Please consult the user log for more details on this failure.