Hi,

In a previous post it was stated that in order to have a redundant session
broker, the service needs to be installed on a cluster.

And yet I found out today that the tssdis service won't start when the
cluster service is started.

It exits and the trace log states the following:
NEW INSTANCE
4444: 20:26:54 INFO: Session Broker plugin is not registered
4444: 20:26:54 Unable to find the resource with service name tssdis

When the cluster service is down, the tssdis service starts splendidly.

Also there is no documentation on how to cluster the session broker on 2008
server. (What data needs to be replicated? How to redirect the database files
to the shared storage?)

Any input would be greatly appreciated

Thanks!

Solved!
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3057160&SiteID=17

"Eyal Weinreb (Pcentra)" wrote:

> Hi,
>
> In a previous post it was stated that in order to have a redundant session
> broker, the service needs to be installed on a cluster.
>
> And yet I found out today that the tssdis service won't start when the
> cluster service is started.
>
> It exits and the trace log states the following:
> NEW INSTANCE
> 4444: 20:26:54 INFO: Session Broker plugin is not registered
> 4444: 20:26:54 Unable to find the resource with service name tssdis
>
> When the cluster service is down, the tssdis service starts splendidly.
>
> Also there is no documentation on how to cluster the session broker on 2008
> server. (What data needs to be replicated? How to redirect the database files
> to the shared storage?)
>
> Any input would be greatly appreciated
>
> Thanks!
>