I am not sure what is wrong here or where to start trouble shooting, so any suggestions are welcome.

I deployed a test AppV Server. I defined the test server under Publishing Server on a client (4.5) workstation.
I was able to launch the "Default Application" so I thought I had everything setup correctly. I noticed the default application uses the RTSPS protocol & port 322. We happen to use RTSP / port 554 in production, but I didn't think anything of that.

So I sequenced (version 4.5) an application and copied it to the content directory of my new test server and imported it.

I refreshed the server on my client but when I launch the application from the new icon I get this error:

Application Virtualization Error
The Application Virtualization Client could not launch vSphere_4_Client_Test 4.0.0.10021.
The system cannot find the path specified.
Error code: 4534C18-14200A2A-00000003

I tried with RTSP / 554 and RTSPS/ 332 but get the same error. Not sure why the "Dafault Apllication" is working from my Test server to my client, but the one I sequenced won't.

I sent the same package to my production server and it works fine from there.

Any suggestions where to start?

Thanks!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
This could help
Answered 03/03/2011 by: package_aligator
Orange Belt

Please log in to comment
0
Also check the management server log. If you made an error filling out the package folder name in the sequencer or if the folder the sequence is in does not match the name specified in the sequencer then the management server will not be able to deliver the sequence.
Answered 03/04/2011 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
0
Thanks for your responses.

I have resolved my "The system cannot find the path specified" issue.

-The short answer: My AppV Client had our PRODUCTION server defined in the "Application Source Root" field during the client installation. This overrides the SFT file location specified in the OSD file.

-The details if anyone is interested:
By checking the Event Viewer, I found my client was trying to access my PRODUCTION server for the application I imported/ published through my TEST server. At first I was afraid I may have accidently entered the wrong server name somewhere, but I tripled checked and that is not the case. It appears that my client is causing the trouble. This client was originally installed when only my PRODUCTION server existed so the only server listed under "publishing servers" was my PRODUCTION server. I added my TEST server to the client by right clicking and selecting "new server". I gave the information relating to the TEST server and thought that was all that would be needed.

My new "TEST" applications that I imported/ published from the TEST server were displayed on my client's desktop when I did a publishing server / refresh server, but I got the "Cannot find the path specified" error.

To troubleshoot, in the client, I expanded APPLICATION and right clicked on one of my new TEST applications and found:
The GENERAL TAB shows my TEST server on SOURCE
but
The PACKAGE TAB shows my PRODUCTION server on the "Package URL" line.
So it is looking in the content folder of my PRODUCTION server for my TEST application.

The package was sequenced correctly with the TEST server name.

I uninstalled the AppV Client, rebooted, and reinstalled the AppV Client. (I was not the person who originally installed the client, but I had documentation on how they said it is to be installed.)

The issue appears to have resulted from the fact that during the AppV 4.5 Client install "Runtime Package Policy Configuration" step. It asks for "Application Source Root" where our local instructions say to specify \\PRODUCTION Server\content

I found this TechNet reference: http://technet.microsoft.com/en-us/library/cc817122.aspx

14.In the following sections of the Runtime Package Policy Configuration screen, you can change the parameters that affect how the Application Virtualization client behaves during runtime:

a.Application Source Root. Specifies the location of SFT files. If used, overrides the protocol, server, and port portions of the CODEBASE HREF URL in the OSD file.


So, since our client had in fact specified our PRODUCTION server here, no matter what, it will always look to the PRODUCTION server for the SFT files.

During my reinstallation, I left the "Application Source Root" field blank.

I added my TEST publishing server and my TEST applications work fine.

I added my PRODUCTION publishing server and now all my applications appear to work and are able to get their files from the correct server and will modify our AppV Client installation documentation as such.
Answered 03/07/2011 by: snj2000
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity