This post is more than 5 years old
37 Posts
0
217900
October 1st, 2013 15:00
No available terminal servers error
Hiya All,
Environment:
vWorkspace Farm consists of one Windows Server 2008 R2 Server setup with RDSH and Quest vWorkspace 8 - One Windows Server 2003 R2 (32-bit) Server with Terminal Services.
Workstations are a mix of 32 and 64 bit machines running Windowws 7 and XP
Situation:
Users are using AppPortal to run published apps. As long as the app is published on the 2008R2 Server all is good and doesn't really fail. Issue comes with the apps that are being published from the 32bit 2003R2 Server. It seems that quite often I have to reboot the server to get those published apps to work again. End user will go to run the app and comes up with the error " Error launching application [appname] - There are no available terminal servers to connect to at this time. Please report this message to your sys admin. (-2147019860)"
I cannot reproduce the problem manually. If I simply reboot, or even just restart the Quest services on the server users can connect up again. The system can go days without an issue, or this issue can occur multiple times in a single day.
The clients are auto-configured using an XML file that actually does not enable NAT Support for Firewall Transversal. So, Knowledge Article 107875 does not seem to apply.
DELL-Andrew W1
378 Posts
0
October 10th, 2013 13:00
Hi MIke,
I've raised a case for you and will send you the log information through the case.
Thanks.
hfmike1
37 Posts
0
October 1st, 2013 15:00
The only thing I see is in the Application Event log on the server.
Source pnmpts
ID 2
Brief Description: MetaProfiles Agent service failed to read the configuration: Server'< My Server > is currently not a member of any MetaProfiles-IT Agent Server Group. etc..." (Full error pasted at bottom).
When I tested to see if a simple restart of the services would get things working - I did notice a couple of the services were set to Automatic and not running; however, of course my brain is not working today and I forgot to note which ones. I will try to see if I can notice that again.
Full Event Log Warning:
Event Type: Error
Event Source: pnmpts
Event Category: None
Event ID: 2
Date: 10/1/2013
Time: 11:15:52 AM
User: NT AUTHORITY\SYSTEM
Computer: << My Server >>
Description:
MetaProfiles Agent Service failed to read the configuration: Server '<< My Server >>' is currently not a member of any MetaProfiles-IT Agent Server Group. It must be added to an Agent Server Group, otherwise user profile settings will not be saved on logoff. Please refer to the MetaPtofiles-IT documentation for further information.
Debug information:
(Database=ODBC;DSN=vWorkspace Database;UID=pnadmin;PWD=**********;. SQL:SELECT DmStorageServers.ServerName AS StorageServer, DmStorageServers.TCPPort AS TCPPort, DmSiloMembership.SiloGUID AS SiloID FROM ((DmStorageServers LEFT JOIN DmSilos ON DmSilos.MPStorageServerGUID = DmStorageServers.RecordGUID) LEFT JOIN DmSiloMembership ON DmSiloMembership.SiloGUID = DmSilos.RecordGUID) LEFT JOIN DmServers ON DmServers.RecordGUID = DmSiloMembership.MemberGUID WHERE (DmSiloMembership.MemberType = 0) AND (DmServers.ServerName = '<< My Server >>'))
DELL-David Y
228 Posts
0
October 1st, 2013 15:00
Hi Mike,
The "Error launching application [appname] - There are no available terminal servers to connect to at this time" can be seen for a number of reasons. If as you say a reboot resolves the issue for a time I think we can rule out a configuration problem, in which case it may be that the server is no longer accepting remote RDP connections.
Have you reviewed the Windows event log on the server to see if this has recorded any service issues?
Alternatively next time the problem happens see if you can RDP directly to the server and check the relevant services are running.
Let us know what you find,
David
DELL-David Y
228 Posts
0
October 2nd, 2013 07:00
Hi Mike,
The error message in your post above is not really an error in the usual sense, it is just recording the fact that your server is not confirgured for MetaProfiles. This will not be the cause of your problems, if you are not using MetaProfiles then you will see this same message on your other Terminal Servers.
Were you able to make an RDP connection to the server when users are seeing the "no available terminal servers" message?
When you tested the service restart did this resolve the issue or did you have to resort to a server restart?
David
hfmike1
37 Posts
0
October 10th, 2013 12:00
Sorry about the delay in replying.
Anyway, yes I can RDP directly to the server - the server functions perfectly well outside of the Quest parts of it.
Yes, doing a simple service restart is working. However, it would be nice to figure out why this is happening anyway. I am not even really seeing any errors in the event logs that might be causing this.
hfmike1
37 Posts
0
October 10th, 2013 13:00
I was wondering where I would find logs other than event logs from Quest.
Now, where would I find the DataCollector, and the Broker logs?
DELL-Andrew W1
378 Posts
0
October 10th, 2013 13:00
Hi Mike,
We need a DataCollector log from the terminal server (s) that have this issue.
This and a Broker log will show why the TS was marked as "unavailable" when it was really working.
Probably the best bet would be to raise a case with support so they can take you through creating this log and seeing what was wrong at the time of the error.
Thanks, Andrew.