[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::mailworks-vms

Title:MailWorks for OpenVMS
Notice:kit info notes 3-6; policies note 2; reporting bugs note 7
Moderator:KOALA::LAVASH
Created:Wed Jul 28 1993
Last Modified:Mon Jun 02 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1583
Total number of notes:6814

1530.0. "Causes of %MUAS-E-SVRUNAACC ?" by GALVIA::JFEGAN (Joe Fegan@ilo) Tue Jan 28 1997 12:44

I am trying to debug a TeamRoute for OpenVMS (MailWorks) problem where
the TeamRoute installation fails because the error message

	%MUAS-E-SVRUNAACC, Server unable to accept calls at present

is returned at one point. What type of situation can cause this error
to appear and what exactly does it mean? I should mention that the
TeamRoute installation script has restarted the mail servers using
X4MAN shortly before the point at which this error is returned.

Any help or pointers would be appreciated.

Joe.
T.RTitleUserPersonal
Name
DateLines
1530.1KOALA::LAVASHWed Jan 29 1997 13:095
    I'm not sure what a short while before means.  Is it possible
    the MUAS server was not completely up and running when an attempt
    to connect to MUAS was made?
    
    -diana
1530.2short with a capital SGALVIA::JFEGANJoe Fegan@iloWed Jan 29 1997 14:4019
    I think it's REAL short, like a couple of lines earlier in the same
    installation script. Having said that, this installation script hasn't
    changed for a couple of years and I've never heard of anybody having
    problems with this before.
    
    It seems that something went wrong with the restart of MailWorks
    because the customer says MailWorks was fine until he did the
    installation. After it failed he had to restart MailWorks as TeamLinks
    users could no longer connect (although all the MailWorks processes
    were present).
    
    I'm going to get them to try the installation again and hope the first
    time was an anomaly (as they say at NASA when their rockets explode :-)
    If this doesn't work I'll try putting a "WAIT" into the installation
    after the restart to give the server a reasonable time to get up and
    running.
    
    Joe.