I possibly did not reboot both nodes after the setup and after the SP3 installation.
"Geoff N. Hiten" <SRDBA@Careerbuilder.com> wrote in message news:<etnIem6EEHA.3372@TK2MSFTNGP10.phx.gbl>...
> That definitely looks like something wrong in the SQL server install. Since
> the physical disks and the network name come online, I would focus on the
> SQL install. Perhaps you didn't get the service pack installed correctly on
> the new node or you didn't get SQL installed correctly. I would uninstall
> SQL and then add the node back in. Use the SQL Install CD. Select 'AdvanceD
> Options'. See BOl for details on maintaininga failover clister for
> instructions on adding and removing SQL from a cluster node cleanly.
>
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
>
> I support the Professional Association for SQL Server
>
www.sqlpass.org >
> "Stefan M." <sminderm@rz-online.de> wrote in message
> news:b4f690dc.0403261150.11bff04a@posting.google.com...
> > Hi,
> > thanks for the response,
> > the actuall failover process happens as follows:
> > 1. Disk is comming online
> > 2. IP Address is comming online
> > 3. Networkname is comming online
> > 4. SQL Server Service fails including those 2 other resources which are
> > depentend to the SQL Server Service
> >
> > Can you specify further what I should troubleshoot???
> >
> > Thanks for your help
> >
> >
> >
> >
> >
> >
> > "Geoff N. Hiten" <SRDBA@Careerbuilder.com> wrote in message
> news:<eQo6JB0EEHA.1228@TK2MSFTNGP11.phx.gbl>...
> > > It looks like the physical disks are not failing over completely. Try
> > > taking the virtual server offline and manually moving to the offending
> node.
> > > The try bringing the resources online in dependancy order. If it
> cannot
> > > bring the disk resources online, then you have a cluster configuration
> issue
> > > and might need to talk to your storage or system vendor. If it is the
> SQL
> > > service, then there is probably a setup problem. I would remove SQL
> (use
> > > the Install CD), evict the node, re-cluster and re-install SQL.
> > >
> > > --
> > > Geoff N. Hiten
> > > Microsoft SQL Server MVP
> > > Senior Database Administrator
> > > Careerbuilder.com
> > >
> > > I support the Professional Association for SQL Server
> > >
www.sqlpass.org > > >
> > > "Stefan M." <sminderm@rz-online.de> wrote in message
> > > news:b4f690dc.0403260041.3fbda0cd@posting.google.com...
> > > > Hi,
> > > >
> > > > I have installed SQL 2000 Enterprise Edition SP3 on a Windows 2000 SP3
> > > > Cluster. Everything went perfect. The database server is running.
> > > > But when I initiated a failover to the other node, the SQL Server
> > > > Cluster Resource fails.
> > > > In the event log on the node where the resource failed I get the
> > > > following events:
> > > >
> > > > MSSQLSERVER Event ID: 17052
> > > > [sqsrvres] StartResourceService: OpenService (MSSQLSERVER) failed.
> > > > Error: 3e5
> > > >
> > > > MSSQLSERVER Event ID: 17052
> > > > [sqsrvres] OnlineThread: ResUtilsStartResourceService failed (status
> > > > 3e5)
> > > >
> > > > MSSQLSERVER Event ID: 17052
> > > > [sqsrvres] OnlineThread: Error 3e5 bringing resource online.
> > > >
> > > >
> > > >
> > > > The Error 3e5 which is in each eventlog is a hexadecimal value, which
> > > > is in decimal 997. Typing C:\net helpmsg 997 displays the message
> > > > "overlapped I/O is in progress".
> > > >
> > > > A failback to the first cluster node works fine.
> > > >
> > > > Does anyone know, why I am not able to perform a failover to the other
> > > > cluster node?
> > > >
> > > > Thanks in advance.
> > > >