Installation guide

B-3
Application-Specific Log File Not Produced
If present, the mllog variable in matweb.conf ( see “matweb.conf” on page 3-8)
creates an application-specific log file. This file is not a MATLAB file; it is
controlled by the operating system. If this file is not produced, check that the
slashes in the pathname of your file are in the correct orientation for the
operating system you are using.
Network bind Error (Port in Use)
If matlabserver fails to start because of a bind error, as noted in
matlabserver_error.log or in the Event Viewer on Windows NT, the port
you are attempting to run
matlabserver on is busy. To fix this problem, you
need to change the port number that matlabserver listens on. See the section
“matlabserver.conf” on page 3-5 for a discussion on how to change the port
number. You may need to ask your system administrator to provide you with a
valid unused port number.
M-File Programming Considerations
Make certain that each line of your M-file application is terminated with a ;
character. Otherwise, the HTML output will be corrupted.
Connect() failure Error
There are two probable reasons why you may receive a
Error: connect() failure message:
-t
Terminal logging. The logging level is set to
2 (transaction and buffer logging). (If you
use this option with the
matlabserver
command on Windows NT, it must precede
all other options on the command line.)
-v [n]
Verbosity. Controls file logging. Default is 0
(no logging). Additional values are
1
(transaction logging) and
2 (transaction and
buffer logging).
Table B-1: matlabserver Logging Options (Continued)