Softgrid App-V Launch Failed can’t connect

app-vrtspterminal-servervirtualization

I've just been assigned a task of troubleshotting a softgrid setup, and since I've never worked with softgrid it's quite a steep learning curve.

A customer called in and said she couldn't start her simple application and that the softgrid icon said "Launch Failed" with the errorcode was "xxxxxx-xxxxxx0A-20000194".

After looking in the sftlog.txt at the terminalserver this is what I found:

The Softgrid Client could not connect to stream URL 'rtsp://foo:554/bar.sft' (FS status: 16D1380A-0000E005).

The Client was unable to connect to a SoftGrid server (rc 16D1380A-0000E005)

After this I've tried connecting to our SoftGrid server using both the SoftGrid Client Management software aswell as the Softgrid Management Console but to no avail.

Any thoughts on where to start looking? Couse I'm stuck.
All machines (Terminalserver, SG-server, SQL-server) are running and working on all ports, I've doublechecked all the services aswell and can't seem to find anything.

(A reboot has been made on all machines aswell)
The eventviewer doesn't show anything either.

Best Regards
LP

Best Answer

The solution was too close to notice, the users windowsprofile had completely got fubar, so I rebuilt the profile and everything is sorted out. (As a sidenote, I could not log on the Managementprogram couse my user was only part of Softgrid Admins, I added myself to Softgrid Users and could instantly log on)

Thank you very much!

Related Solutions

Can symbolic links be used within App-V packages

I had a similar problem with another application. We are presenting ours via RDS and RemoteApps. Ended up creating a duplicate folder structure on the root OS C:\folder of the App-V client system. Only the folders! The used a symbolic link on one of the sub-folders to the share location where the updated files were being kept.

I sequenced the App-V package C:\folder. In VFS I merged the folder structures. Since the local folder was an symbolic link to the location where the files were updated/new the app-v package saw the files.

You can deploy the mklink via computer startup script since it runs with system account privs.

PXE bootable image for terminal server

Get Software Assurance licensing for the 300 PCs, install Windows Thin PC. Use GPO to configure:

Windows Firewall
Certificates (To install your Code Signing Cert)
RDP Pass-Through Authentication.
I like to also configure the Remote Registry service to Auto Start (Delayed), makes some maintenance easier.

Set the users shell to a script in the netlogon folder:

Set shell = CreateObject("WScript.Shell")
shell.Run "mstsc.exe /multimon \\yourdomain\netlogon\term_serv.rdp", 1, true
shell.Run "logoff"

You may want to configure some other basic security stuff, like not caching credentials locally. Configuring the Write Filter is a good idea too (then WinTPC doesn't need AV and can't save a virus). Don't forget to sign the RDP file with rdpsign.

We use both old PCs and HP ThinClients to run the above configuration.

Terminal Server licensing is necessary, and unfortunately a barred topic here as the specifics for each businesses are unique, you really need to contact a MS Reseller who can walk you through the process (TS CALs cost about $100/user last I looked; IIRC per-device licensing was slightly more).

Running a Terminal Server Farm for 300 clients isn't exactly trivial. Depending on your needs it can be quite a bit cheaper than buying 300 new desktops (on a 3-4 year averaged basis); or in the wrong situations can cost several times more (really depends on how similar your desktop configurations are, and how much CPU/RAM/GPU each user requires - in general lower requirements fit TS/VDI better than high requirements).

WinPE is licensed strictly for Installation and Maintenance only. While mstsc.exe can be grafted into it, you're not allowed to use it for "production" purposes. Also, the difficulty in installing drivers, changing most settings (like monitor resolution), and the lack of WiFi or graphics acceleration support (particularly RemoteFX features) makes it a pain the work within.

Related Topic