The server failed to retrieve the SID of Session BRoker
in [Terminal Services]
|
From: Kristin L. Griffin on 25 Aug 2008 16:02 Hi Folks, I have a weird issue. Even through the session broker server says my terminal servers joined ok, the terminal server system logs say differently. I get this message: The server failed to retrieve the security identifier (SID) of the TS Session Broker server. Win32 error code: 0x534. All terminal services connections go to only one server - they are not dispersed. Here are some network details and things I have ruled out: This is a Win2k8 environment. I have a farm of terminal servers (obviously) This is a completely virtual server environment, using HyperV I am not having network, dhcp, dns issues. Everything is running fine in that respect. I have: Gotten rid of NLB and went back to round robin DNS reinstalled session broker rebooted all machines cleared dns cache on all machines checked pings and connectivity to each machine ruled out network firewall by removing it (even thoug no firewall is turned on on any servers. TS Team, any ideas here? Thanks, Kristin
From: Kristin L. Griffin on 25 Aug 2008 19:01 More info: Moving a terminal server into a workgroup and back into the domain did not help. Uninstalling SB on one server and installing it on another did not help. Changing the farm name; adding the terminal servers to another farm did not help Changing from using GPO to TS Configuration settings did not help. "Kristin L. Griffin" wrote: > Hi Folks, > > I have a weird issue. > Even through the session broker server says my terminal servers joined ok, > the terminal server system logs say differently. I get this message: > > The server failed to retrieve the security identifier (SID) of the TS > Session Broker server. > Win32 error code: 0x534. > > All terminal services connections go to only one server - they are not > dispersed. > > Here are some network details and things I have ruled out: > > This is a Win2k8 environment. > I have a farm of terminal servers (obviously) > This is a completely virtual server environment, using HyperV > I am not having network, dhcp, dns issues. Everything is running fine in > that respect. > > I have: > Gotten rid of NLB and went back to round robin DNS > reinstalled session broker > rebooted all machines > cleared dns cache on all machines > checked pings and connectivity to each machine > ruled out network firewall by removing it (even thoug > no firewall is turned on on any servers. > > TS Team, any ideas here? > > Thanks, > > Kristin >
From: Jeff Pitsch on 25 Aug 2008 21:30 How did you install the server? If it was from an image did you sysprep that image? I've had problems with Win2k8 and SID's when the image wasn't sysprepped correctly. Win2k8 has a much, much smaller tolerance for bad SIDs. -- Jeff Pitsch Microsoft MVP - Terminal Services "Kristin L. Griffin" <KristinLGriffin(a)discussions.microsoft.com> wrote in message news:9B67BD16-7AAA-4867-ABB2-346E749552B8(a)microsoft.com... > More info: > > Moving a terminal server into a workgroup and back into the domain did not > help. > Uninstalling SB on one server and installing it on another did not help. > Changing the farm name; adding the terminal servers to another farm did > not > help > Changing from using GPO to TS Configuration settings did not help. > > "Kristin L. Griffin" wrote: > >> Hi Folks, >> >> I have a weird issue. >> Even through the session broker server says my terminal servers joined >> ok, >> the terminal server system logs say differently. I get this message: >> >> The server failed to retrieve the security identifier (SID) of the TS >> Session Broker server. >> Win32 error code: 0x534. >> >> All terminal services connections go to only one server - they are not >> dispersed. >> >> Here are some network details and things I have ruled out: >> >> This is a Win2k8 environment. >> I have a farm of terminal servers (obviously) >> This is a completely virtual server environment, using HyperV >> I am not having network, dhcp, dns issues. Everything is running fine in >> that respect. >> >> I have: >> Gotten rid of NLB and went back to round robin DNS >> reinstalled session broker >> rebooted all machines >> cleared dns cache on all machines >> checked pings and connectivity to each machine >> ruled out network firewall by removing it (even thoug >> no firewall is turned on on any servers. >> >> TS Team, any ideas here? >> >> Thanks, >> >> Kristin >>
From: Kristin L. Griffin on 25 Aug 2008 22:28 I used an image, but I also used NewSID 4.1. I have not had any problems until now (and I have been running like this for over 8 months). I can try to reSID the servers and drop them back in to the domain.... The only other thing I can tell you is this started right when we remote controlled a ts session and somehoe looped it and crashed the terminal server (a behavior which I can reproduce...) Very very strange....I am reverting my images now, and will also try reSIDing. Will let you know how it goes if I get this working again. :) Thanks for your input, Kris "Jeff Pitsch" wrote: > How did you install the server? If it was from an image did you sysprep > that image? I've had problems with Win2k8 and SID's when the image wasn't > sysprepped correctly. Win2k8 has a much, much smaller tolerance for bad > SIDs. > > -- > Jeff Pitsch > Microsoft MVP - Terminal Services > > "Kristin L. Griffin" <KristinLGriffin(a)discussions.microsoft.com> wrote in > message news:9B67BD16-7AAA-4867-ABB2-346E749552B8(a)microsoft.com... > > More info: > > > > Moving a terminal server into a workgroup and back into the domain did not > > help. > > Uninstalling SB on one server and installing it on another did not help. > > Changing the farm name; adding the terminal servers to another farm did > > not > > help > > Changing from using GPO to TS Configuration settings did not help. > > > > "Kristin L. Griffin" wrote: > > > >> Hi Folks, > >> > >> I have a weird issue. > >> Even through the session broker server says my terminal servers joined > >> ok, > >> the terminal server system logs say differently. I get this message: > >> > >> The server failed to retrieve the security identifier (SID) of the TS > >> Session Broker server. > >> Win32 error code: 0x534. > >> > >> All terminal services connections go to only one server - they are not > >> dispersed. > >> > >> Here are some network details and things I have ruled out: > >> > >> This is a Win2k8 environment. > >> I have a farm of terminal servers (obviously) > >> This is a completely virtual server environment, using HyperV > >> I am not having network, dhcp, dns issues. Everything is running fine in > >> that respect. > >> > >> I have: > >> Gotten rid of NLB and went back to round robin DNS > >> reinstalled session broker > >> rebooted all machines > >> cleared dns cache on all machines > >> checked pings and connectivity to each machine > >> ruled out network firewall by removing it (even thoug > >> no firewall is turned on on any servers. > >> > >> TS Team, any ideas here? > >> > >> Thanks, > >> > >> Kristin > >> > > >
From: Jeff Pitsch on 26 Aug 2008 08:37
All I can say is that this exact same problem (or close enough) happened when it wasn't sysprepped. I would sysprep if I were you. I've had absolutely no problems since I've started using my base syspreppred image. -- Jeff Pitsch Microsoft MVP - Terminal Services "Kristin L. Griffin" <KristinLGriffin(a)discussions.microsoft.com> wrote in message news:B2C96422-CB4E-4423-8893-E0146260D1A2(a)microsoft.com... >I used an image, but I also used NewSID 4.1. I have not had any problems > until now (and I have been running like this for over 8 months). I can > try > to reSID the servers and drop them back in to the domain.... > > The only other thing I can tell you is this started right when we remote > controlled a ts session and somehoe looped it and crashed the terminal > server > (a behavior which I can reproduce...) > > Very very strange....I am reverting my images now, and will also try > reSIDing. Will let you know how it goes if I get this working again. :) > > Thanks for your input, > > Kris > > "Jeff Pitsch" wrote: > >> How did you install the server? If it was from an image did you sysprep >> that image? I've had problems with Win2k8 and SID's when the image >> wasn't >> sysprepped correctly. Win2k8 has a much, much smaller tolerance for bad >> SIDs. >> >> -- >> Jeff Pitsch >> Microsoft MVP - Terminal Services >> >> "Kristin L. Griffin" <KristinLGriffin(a)discussions.microsoft.com> wrote in >> message news:9B67BD16-7AAA-4867-ABB2-346E749552B8(a)microsoft.com... >> > More info: >> > >> > Moving a terminal server into a workgroup and back into the domain did >> > not >> > help. >> > Uninstalling SB on one server and installing it on another did not >> > help. >> > Changing the farm name; adding the terminal servers to another farm did >> > not >> > help >> > Changing from using GPO to TS Configuration settings did not help. >> > >> > "Kristin L. Griffin" wrote: >> > >> >> Hi Folks, >> >> >> >> I have a weird issue. >> >> Even through the session broker server says my terminal servers joined >> >> ok, >> >> the terminal server system logs say differently. I get this message: >> >> >> >> The server failed to retrieve the security identifier (SID) of the TS >> >> Session Broker server. >> >> Win32 error code: 0x534. >> >> >> >> All terminal services connections go to only one server - they are not >> >> dispersed. >> >> >> >> Here are some network details and things I have ruled out: >> >> >> >> This is a Win2k8 environment. >> >> I have a farm of terminal servers (obviously) >> >> This is a completely virtual server environment, using HyperV >> >> I am not having network, dhcp, dns issues. Everything is running fine >> >> in >> >> that respect. >> >> >> >> I have: >> >> Gotten rid of NLB and went back to round robin DNS >> >> reinstalled session broker >> >> rebooted all machines >> >> cleared dns cache on all machines >> >> checked pings and connectivity to each machine >> >> ruled out network firewall by removing it (even thoug >> >> no firewall is turned on on any servers. >> >> >> >> TS Team, any ideas here? >> >> >> >> Thanks, >> >> >> >> Kristin >> >> >> >> >> |