Error starting MAS
Brought to you by:
jcochrane
I just installed MAS on Win2000Pro and I get the
following error messages:
1
<<"The system cannot find the file specified"
OK>>
2
<<Error encountered - main routine:
WSAEINVAL The scoket is already bound to an address.
Exception occured:
"WSAEINVAL The scocet is already bound to an address"
Type of Exception: Developer exception.
OK>>
Would you please let me know how I can resolve this
issue?
Thanks.
error report
Logged In: YES
user_id=39996
Patrick -
Does this problem happen consistently - every time you start
of the program (e.g., double-click on the MAS icon)?
There are two things you can try to start with - either or
both of these:
First, assuming the main "MAS Control Panel" window starts
up and remains on the screen, click on "Start a MAS Session"
and see whether or not you get the same error. If this
fails, try clicking on Start ... twice, rapidly - almost a
double-click. If it still fails, try this a couple more
times. (My thinking here is that the socket the MCT wants
to use to start the server is already reserved by another
program, so we're trying to start new sessions with
different port numbers, until we find one that's not used.)
It it works, it's ugly, of course, but we'll know what's
wrong and can fix it.
The other thing to try is run in debug mode and send me the
results. However, I'm rather busy and can't guarantee I'll
be able to respond in a timely manner, unless, perhaps the
solution is simple:
(Note: These instructions are for NT. This procedure may be
slightly
different on XP or Windows 2000.)
Left-click on the "MAS" icon.
Click on "Properties".
Select the "Shortcut" tab.
In the "Target" slot, add: " -debug".
(Add everything within the double quotes, including the
leading space - but
not the quotes.)
Click OK.
Then start up the program by double-clicking on the "MAS" icon.
A "DOS" window will appear with debugging information.
Unfortunately, Windows does not provide a straightforward
way to save the
debugging output. So you will need to note what is printed
on the resulting
"DOS" window and manually copy it into a file, or at least
provide a
good summary (unless you can figure out a way to redirect
the information
automatically into a file).
Then click on "Start a MAS Session".
This will result in more info. being printed in the "DOS"
window.
Include this additional info. in your report.
Email me the resulting report.
To turn off the debugging, follow the same procedure as
above and remove
" -debug" from the "Target" slot and hit "OK".
Logged In: YES
user_id=856007
Hi Jim,
Thanks for your quick reply and for taking the time to help. I
have addressed your questions and suggestions below--I
hope it is clear. Let me know if you need additional info. Also,
I fully understand if you are unable to spend time on this
issue.
Thanks again,
Patrick
==============
Date: 2004-02-14 23:48
Sender: jcochrane
Logged In: YES
user_id=39996
Patrick -
Does this problem happen consistently - every time you start
of the program (e.g., double-click on the MAS icon)?
---------------------------
Yes, every time.
---------------------------
There are two things you can try to start with - either or
both of these:
First, assuming the main "MAS Control Panel" window starts
up and remains on the screen, click on "Start a MAS Session"
and see whether or not you get the same error.
-----------------------------------
It does stay on the screen, along with the error message, but
all screens disappear when I try to 'start a session'. Also, I
notice that this action will load another instance of 'mas.exe.
So, I then have two 'mas.exe' running in the process list.
---------------------------------------
If this
fails, try clicking on Start ... twice, rapidly - almost a
double-click. If it still fails, try this a couple more
times. (My thinking here is that the socket the MCT wants
to use to start the server is already reserved by another
program, so we're trying to start new sessions with
different port numbers, until we find one that's not used.)
It it works, it's ugly, of course, but we'll know what's
wrong and can fix it.
---------------------------------------
I tried this a few times (20) but with the same result.
---------------------------------------
The other thing to try is run in debug mode and send me the
results. However, I'm rather busy and can't guarantee I'll
be able to respond in a timely manner, unless, perhaps the
solution is simple:
(Note: These instructions are for NT. This procedure may be
slightly
different on XP or Windows 2000.)
Left-click on the "MAS" icon.
Click on "Properties".
Select the "Shortcut" tab.
In the "Target" slot, add: " -debug".
(Add everything within the double quotes, including the
leading space - but
not the quotes.)
Click OK.
Then start up the program by double-clicking on the "MAS"
icon.
A "DOS" window will appear with debugging information.
Unfortunately, Windows does not provide a straightforward
way to save the
debugging output. So you will need to note what is printed
on the resulting
"DOS" window and manually copy it into a file, or at least
provide a
good summary (unless you can figure out a way to redirect
the information
automatically into a file).
------------------------------------------
This is the full contents of the DOS window between << >>:
<<executing [MEC]: C:\Program Files\mas1.6.6q\bin\mas -o -
f , -b 7777 *.txt -report_back localhost^41512
<current directory: C:\Program Files\mas1.6.6q\lib\data>
executing [MEC] java -cp "C:\Program
Files\mas1.6.6q\lib\classes\mascharts.jar" MA_Client localhost
7777
<current directory: C:\Program Files\mas1.6.6q\lib\classes>>>
---------------------------------------------
Then click on "Start a MAS Session".
This will result in more info. being printed in the "DOS"
window.
Include this additional info. in your report.
Email me the resulting report.
----------------------------------
This is the additional content of the DOS window:
<<executing [MEC]: C:\Program Files\mas1.6.6q\bin\mas -o -
f , -b 10101 *.txt -report_back localhost^41512
<current directory: C:\Program Files\mas1.6.6q\lib\data>
executing [MEC]: java -cp "C:\Program
Files\mas1.6.6q\lib\classes\mascharts.jar" MA_Client localhost
10101
<current directory: C:\Program Files\mas1.6.6q\lib\classes>
mct.exe: system execution failed.
Following is the set of recorded exeptions:
------------------------------------------------------------
------------------
Class / Object Routine Nature of
exeption Effect
------------------------------------------------------------
------------------
MCT root's creation The system
cannot find the f:
<00E5002C> Developer
exception Exit
------------------------------------------------------------
------------------
MCT root's creation
<00E5002C> Routine failure.
Exit
------------------------------------------------------------
------------------
---------------------------------------------
To turn off the debugging, follow the same procedure as
above and remove
" -debug" from the "Target" slot and hit "OK".
==================
Logged In: YES
user_id=39996
OK. the original error message led me to think that the
problem might be that the socket port number mas was using
was already in use, but it looks like that was not the case.
To fix this, I think I'm going to need to find a win2k box
and try to duplicate the problem and then find out what is
going wrong. I'm not sure when I'll be able to do this, but
feel free to send me a reminder in a couple weeks if you've
not heard from me.
Thanks for the report.
Jim
Logged In: YES
user_id=856007
Hey Jim,
Thanks for your efforts. No rush--in your own time. Although I
am egar to try out the system :-) It sounds much more
comprehensive than most that are available; at least, that I'm
aware of.
Patrick
Logged In: YES
user_id=1019348
Hello,
This is the exact same error message I received when trying
to install on W2K. (As per request for correct W2K version of
MAS).
Did you find a way to resolve ?
Nordic
Logged In: YES
user_id=39996
For those who might be following this issue - problems
installing 1.6.6q on W2000, there is some good and some bad
news.
The good news is that at least one person (and I suspect
there may be others who have not reported it) has been able
to install and run the 1.6.6q version on W2000 wth no
problem. Because of this, I suspect that it may be possible
for those who had problems with the install to get it working.
The bad news is that I don't currently have time to
investigate the problem or help people get 1.6.6q working on
W2K (at least, not without a fee!). (If anyone who was able
to get it to work would be willing to attempt to help those
who are having problems with it, I'm sure the latter group
would be very grateful.)
However, I suspect the problem is not major and expect to be
able to find a solution "reasonably" soon - I'm guessing at
least by the end of this year, and most likely quite a bit
before then. No guarantees, of course.