Adding 2nd node fails

hi all ,
I tried several times to install sql clustering on
two sql nodes but when it tries to configure the resources on virtual server
after configuring sql server resource.
then I tried to configure it with single node it succeeded.
but when I want to add the 2nd node again it cannot configure the sql agent
and search resources on the 2nd node. if I remove the agent and search
resources from the first node and then add the 2nd node to the cluster it
runs.
but is this the way. should n't sql agent and search resouces be running on
a cluster?
the account I use is the local administrator on both machines. I followd
everything just as it was said in the microsoft documentations. what else
should i do? does it have a trick or what?
any idea whould be greatly appreciated.
When you say that you're using the local admin, do you mean that you're
using it for your SQL Server and SQL Agent services? You really need a
domain account for this and it should be part of the local admin group on
each node.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Alireza G." <csspcman@.hotmail.com> wrote in message
news:OO5X1FyjEHA.592@.TK2MSFTNGP11.phx.gbl...
hi all ,
I tried several times to install sql clustering on
two sql nodes but when it tries to configure the resources on virtual server
after configuring sql server resource.
then I tried to configure it with single node it succeeded.
but when I want to add the 2nd node again it cannot configure the sql agent
and search resources on the 2nd node. if I remove the agent and search
resources from the first node and then add the 2nd node to the cluster it
runs.
but is this the way. should n't sql agent and search resouces be running on
a cluster?
the account I use is the local administrator on both machines. I followd
everything just as it was said in the microsoft documentations. what else
should i do? does it have a trick or what?
any idea whould be greatly appreciated.
|||The SQLSTP.log on the setup node and the SQLSTPn.log (where highest value
for n is the most recent setup) from each node will contain the details of
the virtual SQL Server setup. Also check the last few entries in the
SQLCLSTR.log.
You can also try setting up a virtual SQL Server on one node, then re-run
the setup in maintenance mode and add the second node. Sometimes this
helps get past the virtual SQL Server creation setup.
Chris Skorlinski
Microsoft SQL Server Support
Please reply directly to the thread with any updates.
This posting is provided "as is" with no warranties and confers no rights.

Added /3GB to boot.ini and OS will not start

Here is a new one for me. I added the /3GB switch to the boot.ini, restarted the server and now receive a number of messages when the OS tries to load.

Explorer.exe - Application Error

The application failed to initialize properly.

If I click OK the server sits on a blue screen with no information on the screen.

The other messages are the result of me trying to do anything within Task Manager, with the exception of rebooting the server. These messages make sense since Explorer.exe had a problem.

The server has the following configuration.

HP DL580

Windows Server 2003 Enterprise Edition - SP2

SQL Server 2000 Enterprise Edition - SP3a

14GB Memory

(4) dual core procs

PAE is enabled in the boot.ini

If I remove the /3GB the OS starts without a problem. Any suggestions?

Thanks, Dave

Hey Dave,

I don't recommend adding the 3GB switch for this server. You're running 14GB of memory, with PAE enabled.

This means Windows has got to use a lot more phsyical memory to house the PAE memory mappings, and when you set 3GB you're dropping the amount of memory Windows can use from 2GB down to 1GB, and from the sound of it it's just not enough for Windows.

Microsoft actually say not use 3GB with PAE in a server which has 16GB or greater RAM. But I've found anything more than 12 - 14GB and it's best not to use 3GB.

Hope that helps.

Cheers, Reece.