/build/static/layout/Breadcrumb_cap_w.png

Softgrid App-V Launch Failed can't connect

Hi,

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

0 Comments   [ + ] Show comments

Answers (12)

Posted by: DannyC 14 years ago
Orange Belt
0
Hi LP,

It sounds to me like the path of the package hasn't been set correctly - the log shows that the server is looking for the package in the root of the content share - if you look in the OSD file for the app you will see a line similar to:

<CODEBASE HREF="RTSP://%SFT_SOFTGRIDSERVER%:554/bar.sft"

Which means the server is expecting the SFT file to be in the content directory itself but it should read something like:

<CODEBASE HREF="RTSP://%SFT_SOFTGRIDSERVER%:554/AppFolderName/bar.sft"

This will because the PATH parameter on the deployment tab of the sequencer wasn't filled in. You can test this by amending the path in the OSD file to include the folder name (alternatively you could just copy the package files to the root of the content share, but this is certainly a "quick and dirty" approach!)

Hope that helps,
Cheers,
Danny
Posted by: larsengstrom 14 years ago
Senior Yellow Belt
0
The path is correct, it was just me who made it somewhat shorter.
The problem is I can't seem to connect to the streaming server in any possible way, it seems 'shut off' more or less and I can't seem to start it in any way.
Posted by: DannyC 14 years ago
Orange Belt
0
At least that's that ruled out then!

Does the problem occur across the board or is it just this user/app that's affected?

If the former, then is the VAS service started successfully? If so, is the content share configured correctly (i.e. does the reg value match that shown in the Management Console?)
Posted by: larsengstrom 14 years ago
Senior Yellow Belt
0
This is just a single application, the only one running through SoftGrid.
I posted more information on Serverfault, a glimpse there would be very appriciated.
[link]http://serverfault.com/questions/197674/softgrid-app-v-launch-failed-cant-connect[/link]
Posted by: ribzon 14 years ago
Senior Yellow Belt
0
1. Hi, ive seen that error pretty often, usually when i forget to set the path to the application in the sequencer and i correct it by editing the imported application in AVMC
2. You also get this error if you "upgrade" the package and the forget to import it again in AVMC

so my best educated guess is that the path in some way to the application is missmatching.

Hope it helped[:)]
/Ribzon
Posted by: larsengstrom 14 years ago
Senior Yellow Belt
0
ORIGINAL: ribzon

1. Hi, ive seen that error pretty often, usually when i forget to set the path to the application in the sequencer and i correct it by editing the imported application in AVMC
2. You also get this error if you "upgrade" the package and the forget to import it again in AVMC

so my best educated guess is that the path in some way to the application is missmatching.

Hope it helped[:)]
/Ribzon


Hi, thank you very much for your replies.
Unfortunately I'm very new to this so I don't even know what the sequencer is ... :-(
... And since I can't connect to anything using either client or management, can I even see these inputs?

The problem just "popped up" and I'm certain it's some very easy fix to it since nothing have been changed since it worked.
Posted by: DannyC 14 years ago
Orange Belt
0
Have you checked out http://support.microsoft.com/kb/930614 - one of the potential causes is if the app isn't actually published to the user. Do you know how they get the icon? Is it delivered natively via App-V?

It might be worth deleting and recreating the app in the management console if you're certain that the path in the OSD file is correct..
Posted by: larsengstrom 14 years ago
Senior Yellow Belt
0
ORIGINAL: DannyC

Have you checked out http://support.microsoft.com/kb/930614 - one of the potential causes is if the app isn't actually published to the user. Do you know how they get the icon? Is it delivered natively via App-V?

It might be worth deleting and recreating the app in the management console if you're certain that the path in the OSD file is correct..


Yes, I saw that KB and I've run through it a couple of times but it doesn't seem to be that either.
I saw in the .OSD file that the icons path is %SFT_MIME_SOURCE%.

But, I should be able to connect to the SoftGrid server anyway with the management console anyway right? Couse I think something else is broken
Posted by: DannyC 14 years ago
Orange Belt
0
Yes, you should be able to connect to the management console - if you can't then I'd definitely concentrate on that first.

If you try to launch the console (from the server itself, not remotely), what happens? Do you get a C800 error?
Posted by: larsengstrom 14 years ago
Senior Yellow Belt
0
I've now launched the Management Console (MMC) on the SoftGridserver itself, choose 127.0.0.1 aswell as localhost in the hostfield and tried to log on using my currently logged in administratoraccount.
This account is placed in the SoftGrid Admins group in the AD, so it definitly should be able to log on.

Unable to log into the SoftGrid System.
The specified user is not authorized to administer this system.
Error code: 0000C803


Regards
Posted by: DannyC 14 years ago
Orange Belt
0
OK; couple more thoughts:

Is your account a domain account?

Have you logged off/on since adding your account to the group?

Do you know for a fact that the system is configured with "SoftGrid Admins" group as the right group for administering the system? You could reset the administrators (if you know the SA account of the database).
Posted by: larsengstrom 14 years ago
Senior Yellow Belt
0
ORIGINAL: DannyC

OK; couple more thoughts:

Is your account a domain account?

Have you logged off/on since adding your account to the group?

Do you know for a fact that the system is configured with "SoftGrid Admins" group as the right group for administering the system? You could reset the administrators (if you know the SA account of the database).


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 extremely much!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ