PDA

View Full Version : Invalid Slave Node



Mark Powers
16-Sep-2005, 01:30 PM
We have a load balancing Master and Slave Web App setup and is working
correctly on our primary webapp application. We have added a new
application to it today and the new applicatio is not working and we are
getting the following error on the master node:

Web Service Error
There is a problem with the page you are trying to reach and it cannot
be displayed.

--------------------------------------------------------------------------------

Technical Information (for support personnel)

More information:
Error during Web Application Server session initialization, please try
again later. Invalid slave node Web Application: RMS2005. Please verify
that the spelling is correct and that the specific Web Application has
been correctly configured on the slave node. Please check the Windows
event log for further information about the problem.


--------------------------------------------------------------------------------

HTTP 500 - Internal server error
Visual DataFlex Web Application Server


The main problem looks like the "Invalid Slave Node Web Application".
We have done as suggested on checking the spelling and it all looks
correct. Does anyone have any suggestions on what we could try.

Thanks
Mark

Sonny Falk
16-Sep-2005, 06:09 PM
> Error during Web Application Server session initialization, please try
> again later. Invalid slave node Web Application: RMS2005. Please verify
> that the spelling is correct and that the specific Web Application has
> been correctly configured on the slave node. Please check the Windows
> event log for further information about the problem.
>
> The main problem looks like the "Invalid Slave Node Web Application".
> We have done as suggested on checking the spelling and it all looks
> correct. Does anyone have any suggestions on what we could try.

Did you verify that the specific Web Application is configured properly on
the _slave_ machine? The specific Web Application must be configured as
master on the Master node, and as slave on the slave node. If the
application is not properly configured as Slave on the slave node, you'd get
this error message.

-Sonny Falk (DAC)

Mark Powers
19-Sep-2005, 11:35 AM
Sony:
The slave has the check box set on the slave as "This Web Application is
controlled by a load balancing Master Node" and the master has the "This
Application is load balanced ove rthe following machines:" and the IP of
the machine is entered in the box.

Any other suggestions please??

Thanks
Mark

Sonny Falk wrote:
>>Error during Web Application Server session initialization, please try
>>again later. Invalid slave node Web Application: RMS2005. Please verify
>>that the spelling is correct and that the specific Web Application has
>>been correctly configured on the slave node. Please check the Windows
>>event log for further information about the problem.
>>
>>The main problem looks like the "Invalid Slave Node Web Application".
>>We have done as suggested on checking the spelling and it all looks
>>correct. Does anyone have any suggestions on what we could try.
>
>
> Did you verify that the specific Web Application is configured properly on
> the _slave_ machine? The specific Web Application must be configured as
> master on the Master node, and as slave on the slave node. If the
> application is not properly configured as Slave on the slave node, you'd get
> this error message.
>
> -Sonny Falk (DAC)
>
>

Sonny Falk
19-Sep-2005, 12:29 PM
> The slave has the check box set on the slave as "This Web Application is
> controlled by a load balancing Master Node" and the master has the "This
> Application is load balanced ove rthe following machines:" and the IP of
> the machine is entered in the box.

Did you verify the spelling (case sensitive) on the slave node?

The error: Invalid slave node Web Application: RMS2005, simply means that
there is no web application configured for slave operation on the particular
slave node called "RMS2005". Either there is no web application called
"RMS2005" on the slave node at all, or it's not configured as a slave. As
far as I can see, that's the only reason this error message would be
displayed.

-Sonny Falk (DAC)