conflict with remote desktop or fast user switching?

[vince100]

When I tried to remote control a PC running TeamViewer, I got the following error message:

"The screen cannot be captured at the moment. This is probably due to fast user switching or
a disconnected/minimized Remote Desktop session. "

Yes, I did connect to the remote PC using remote desktop to start the TeamViewer, but I disconnected afterward.

Is the error message saying that TeamViewer cannot work at all if a remote desktop session has been used?

So what do I need to do to make this work?

How can I make a TeamViewer connection after I've used Remote Desktop, without logging off or restarting the remote PC?

Is there a way to completely "stop" a remote desktop session" (as opposed to "disconnect" a remote desktop session), so it won't interfere with Teamviewer's delicate operations?

Oh, I think that to disable fast user switching is not a serious request, is it?

Thanks!  

P.S. I'm using the latest version of teamviewer in both server/client PC (XP SP3).

[TeamViewer]

Hello,
The black screen will come up if there was any previous RDP-connection and TeamViewer is not running as a Windows service.
Please configure TeamViewer to start automatically with windows.

Now it will be possible to get to the desktop even after RDP-connections have been opened up.

Regards
Inga, TeamViewer

[mbehmazia123]

Hello,

I am having the same issue however it has nothing to do with a previous session still open. I am trying to access my work computer from home. I know Team Viewer is still running in the background because I can still transfer files however I can not remote in.

[Paksheen]

What fixed it for me was restarting the Teamviewer 11 service, and opening up the Teamviewer GUI, there's a little light bulb next to the Your ID, that will pop up a message with the Teamviewer ID for the system. The one that displays apparently, is the one for the user currently logged in, so if that user goes idle on RDP, the session closes. Logging in with the Teamviewer ID for the system was my solution.

[rickncn]

What fixed it for me was restarting the Teamviewer 11 service, and opening up the Teamviewer GUI, there's a little light bulb next to the Your ID, that will pop up a message with the Teamviewer ID for the system. The one that displays apparently, is the one for the user currently logged in, so if that user goes idle on RDP, the session closes. Logging in with the Teamviewer ID for the system was my solution.

This seems to resolve it. Thanks Paksheen