Session Directory : Cluster Install

  • Thread starter Thread starter lozza
  • Start date Start date
L

lozza

Guest
Guys,

I have followed the Microsoft doc on this at
http://support.microsoft.com/kb/840695

and I seem to be getting problems...

My scenario: I have a MS Cluster configured with a cluster group that has 3
disks with SQL services, IP and name. I need to install the SessDir into this
group as I cant get any more disks presented to this cluster and I believe
the SessDir is very small anyway...

So I follow the guide, choose the options:
- Set the Session Directory services on both nodes to AUTOMATIC
- make it a generic service,
- Make both nodes in the cluster possible owners
- have dependancies on the IP, name and ONE of the disks in the group (the
one SQL uses for Backups... plenty of space there)...
- In Service parameters I type : TSSDIS and check the box
- In registry replication I hit add and type :
SYSTEM\CurrentControlSet\Services\Tssdis\Parameters

The resource creates succesfully and is in an offlined state.
I then add the 2 computer names to the session directory group thats been
created in the Local Groups of both nodes...

When I try and bring the resource online, the whole group goes crazy and
starts bouncing between the nodes and each time it tries to fire the SessDIR
resource it fails and initiates the whole to failover to the other node, and
then fires all resources again until it gets to the SessDir resource, fails,
and fails the group over again and this keeps happening, until I pause a
Node, so the whole group cannot fail over....

Has anyone experienced this?

Lozza
 
Re: Session Directory : Cluster Install

Lozza,

What happens with the session directory database files? They are located in
\Windows\System32\tssesdir and must also be replicated, otherwise both
clusters will have a different view the database.

Also, does this happen only when you bring the resource online? Or when
someone connects to one of the TS servers? Can you also make sure that the
TS servers don't have any errors in their eventlogs regarding joining the
farm? What about the SD? Any errors there?

Thanks,
Roman

"lozza" <lozza@discussions.microsoft.com> wrote in message
news:EE160B06-4707-420C-9C60-7CEFDB9BEBFF@microsoft.com...
> Guys,
>
> I have followed the Microsoft doc on this at
> http://support.microsoft.com/kb/840695
>
> and I seem to be getting problems...
>
> My scenario: I have a MS Cluster configured with a cluster group that has
> 3
> disks with SQL services, IP and name. I need to install the SessDir into
> this
> group as I cant get any more disks presented to this cluster and I believe
> the SessDir is very small anyway...
>
> So I follow the guide, choose the options:
> - Set the Session Directory services on both nodes to AUTOMATIC
> - make it a generic service,
> - Make both nodes in the cluster possible owners
> - have dependancies on the IP, name and ONE of the disks in the group (the
> one SQL uses for Backups... plenty of space there)...
> - In Service parameters I type : TSSDIS and check the box
> - In registry replication I hit add and type :
> SYSTEM\CurrentControlSet\Services\Tssdis\Parameters
>
> The resource creates succesfully and is in an offlined state.
> I then add the 2 computer names to the session directory group thats been
> created in the Local Groups of both nodes...
>
> When I try and bring the resource online, the whole group goes crazy and
> starts bouncing between the nodes and each time it tries to fire the
> SessDIR
> resource it fails and initiates the whole to failover to the other node,
> and
> then fires all resources again until it gets to the SessDir resource,
> fails,
> and fails the group over again and this keeps happening, until I pause a
> Node, so the whole group cannot fail over....
>
> Has anyone experienced this?
>
> Lozza
 
Re: Session Directory : Cluster Install

Hey Roman,

Okay, this only happens when I try and bring the resource online afer
following all the steps in the article. It's becuase it continues to fail all
resources in the cluster group over to the other node and back continously,
the only thing I can do is Pause one of the nodes and force the TS genric
resource to fail, and then delete it, otherwise if I try and fire it up
(bring it online) the whole cluster group continously starts failing over and
back.

I'm not fully sure I understand what you mean by:

"What happens with the session directory database files? They are located in
> \Windows\System32\tssesdir and must also be replicated"

As far as replication goes, I'd assume the registry replication was all I
had to do according to the article. Aside from this, becuase the resource
never comes online, i'd assume the actual session directory never get created
on the shared disk assigned to this cluster group. I'm assuming the SD would
get created on the shared disk resource in the cluster group. What file path
would it have on the shared disk resource?

I haven;t even got to the point yet where I have hooked any TS servers in to
use the SD, as the clustered SD resource (created as a generic resource)
doesn;t come online. Therefore this step would fail by default. If this
resource did come online then I could try and hook a TS server into using it.
But right now, no TS servers can be directed to use the SD as it is not
created, i assume?



"Roman Porter [MSFT]" wrote:

> Lozza,
>
> What happens with the session directory database files? They are located in
> \Windows\System32\tssesdir and must also be replicated, otherwise both
> clusters will have a different view the database.
>
> Also, does this happen only when you bring the resource online? Or when
> someone connects to one of the TS servers? Can you also make sure that the
> TS servers don't have any errors in their eventlogs regarding joining the
> farm? What about the SD? Any errors there?
>
> Thanks,
> Roman
>
> "lozza" <lozza@discussions.microsoft.com> wrote in message
> news:EE160B06-4707-420C-9C60-7CEFDB9BEBFF@microsoft.com...
> > Guys,
> >
> > I have followed the Microsoft doc on this at
> > http://support.microsoft.com/kb/840695
> >
> > and I seem to be getting problems...
> >
> > My scenario: I have a MS Cluster configured with a cluster group that has
> > 3
> > disks with SQL services, IP and name. I need to install the SessDir into
> > this
> > group as I cant get any more disks presented to this cluster and I believe
> > the SessDir is very small anyway...
> >
> > So I follow the guide, choose the options:
> > - Set the Session Directory services on both nodes to AUTOMATIC
> > - make it a generic service,
> > - Make both nodes in the cluster possible owners
> > - have dependancies on the IP, name and ONE of the disks in the group (the
> > one SQL uses for Backups... plenty of space there)...
> > - In Service parameters I type : TSSDIS and check the box
> > - In registry replication I hit add and type :
> > SYSTEM\CurrentControlSet\Services\Tssdis\Parameters
> >
> > The resource creates succesfully and is in an offlined state.
> > I then add the 2 computer names to the session directory group thats been
> > created in the Local Groups of both nodes...
> >
> > When I try and bring the resource online, the whole group goes crazy and
> > starts bouncing between the nodes and each time it tries to fire the
> > SessDIR
> > resource it fails and initiates the whole to failover to the other node,
> > and
> > then fires all resources again until it gets to the SessDir resource,
> > fails,
> > and fails the group over again and this keeps happening, until I pause a
> > Node, so the whole group cannot fail over....
> >
> > Has anyone experienced this?
> >
> > Lozza
>
>
 
Back
Top