Question
If an administrator logs onto a computer with Notification Server 6.0 with R8 via RDP without the /Console switch, when he or she is either already logged into that computer via RDP with the /Console or logs on afterwards, so that the administrator now has two RDP sessions running (one in each mode), the following errors and warnings will be logged:

Priority: 2
Date: 24/06/2008 09:15:24
Tick Count: 88314125
Host Name: NS Name
Process: AeXNSAgent.exe (3584)
Thread ID: 1640
Module: AeXAgentUI.dll
Source: SessionManager
Description: Failed to register session

Priority: 2
Date: 24/06/2008 09:15:24
Tick Count: 88314203
Host Name: NS Name
Process: AeXNSAgent.exe (3584)
Thread ID: 1640
Module: AeXAgentUI.dll
Source: CoSessionManager(187)
Description: Session already registered (-2147208704)

Priority: 1
Date: 24/06/2008 09:15:25
Tick Count: 88315984
Host Name: NS Name
Process: AeXAgentUIHost.exe (5624)
Thread ID: 1800
Module: AeXAgentUI.dll
Source: ClientSession
Description: Session failed to start: IDispatch error #12288 (-2147208704)

Priority: 2
Date: 24/06/2008 09:15:27
Tick Count: 88317421
Host Name: NS Name
Process: AeXAgentUIHost.exe (5624)
Thread ID: 1800
Module: AeXAgentUI.dll
Source: CoClientSession(56)
Description: IDispatch error #12288 (-2147208704)

Priority: 1
Date: 24/06/2008 09:15:27
Tick Count: 88317515
Host Name: NS Name
Process: AeXAgentUIHost.exe (5624)
Thread ID: 1908
Module: AeXAgentUIHost.exe
Source: AeXClientLaunchUI
Description: Launch client UI failed: IDispatch error #12288 (-2147208704)

Why is this?

Answer
This is only cosmetic, and is caused by some changes made in R8 to fix a different problem. User sessions are unaffected by this error, which can be confirmed by enabling the Notification Server Agent's Diagnostics and looking at the "User Sessions" console.

Similar messages are recorded when users that only have RDP rights (members of the RDP Group) log into a pre-R7 computer (see article 41987). This scenario, however, has been addressed in R8.