| Event Information | According to Microsoft :
Cause :
This event is logged when the RpcBindingFromStringBinding function call failed with Win32 error code.
Resolution :
Check firewall settings and try to join TS Session Broker again
To resolve this issue, do the following:- Check firewall settings to ensure that RPC communication is not blocked between the terminal server and the TS Session Broker server.
- Try to join the terminal server to a farm in TS Session Broker again.
If the problem persists, restart the Terminal Services Session Broker service on the TS Session Broker server and then try to join the terminal server to a farm in TS Session Broker again. If the problem still persists, restart the terminal server and then try to join the terminal server to a farm in TS Session Broker again.
To perform these tasks, refer to the following sections.
Check firewall settings
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To check firewall settings:- On the terminal server, click Start, and then click Control Panel.
- Click Security, click Windows Firewall, and then click Change Settings.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- In the Windows Firewall Settings dialog box, click the Exceptions tab.
- Under Program or port, ensure that the Terminal Services check box is selected. If the Terminal Services check box is not selected, select it, and then click OK.
- On the TS Session Broker server, click Start, and then click Control Panel.
- Click Security, and then click Windows Firewall.
- Click Change Settings, and then, in the Windows Firewall Settings dialog box, click the Exceptions tab.
- Under Program or port, ensure that the Session Broker Service check box is selected. If the Session Broker Service check box is not selected, select it, and then click OK.
Note : To view more detailed information about Windows Firewall settings, use the Windows Firewall with Advanced Security snap-in.
Try to join the terminal server to a farm in TS Session Broker again
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To join the terminal server to a farm in TS Session Broker:- On the terminal server, open Terminal Services Configuration. To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- Under TS Session Broker, double-click Member of farm in TS Session Broker.
- On the TS Session Broker tab, do the following:
- Under TS Session Broker server name or IP address, enter the computer name or IP address of the TS Session Broker server.
- Under Farm name in TS Session Broker, enter the name of the farm to join.
- Click OK to close the Properties dialog box.
If the problem persists, restart the Terminal Services Session Broker service on the TS Session Broker server and then try to join the terminal server to a farm in TS Session Broker again.
Restart the Terminal Services Session Broker service on the TS Session Broker server
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To restart the service:- On the TS Session Broker server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- In the Services pane, right-click Terminal Services Session Broker, and then click Properties.
- On the General tab, ensure that Startup type is set to Automatic. If it is not, click Automatic, and then click OK.
- Right-click Terminal Services Session Broker, and then click Restart.
- Confirm that the Status column for the Terminal Services Session Broker service displays Started.
Try to join the terminal server to a farm in TS Session Broker again. To perform this task, refer to the previous section.
If the problem still persists, restart the terminal server and then try to join the terminal server to a farm in TS Session Broker again. Verify :
To verify that the terminal server has successfully joined a farm in TS Session Broker, use either of the following methods:
Method one
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority. - On the terminal server, open Event Viewer. To open Event Viewer, click Start, point to Administrative Tools, and then click Event Viewer.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- In the left pane, expand Windows Logs, and then click System.
- Look for an event with a Source of TerminalServices-SessionBroker-Client and an Event ID of 1005. This event indicates that the terminal server has successfully joined a farm in TS Session Broker.
Method two- On the terminal server that has been joined to a farm in TS Session Broker, start a new Terminal Services session by using the IP address of the terminal server.
- After the session is established, disconnect the session.
- To connect to a different terminal server that is also a member of the same farm, use the IP address of that terminal server and the same user credentials that you used to connect to the first terminal server. If you are able to reconnect to the existing session on the first terminal server, the terminal server is successfully joined to a farm in TS Session Broker.
|