/build/static/layout/Breadcrumb_cap_w.png

Asset directory

Hi All,

I had sequenced an application for two environment(Prod and PreProd). I first sequenced the application for preprod environment with asset directory as PRSC6260.v01. After that i reverted the virtual pc to clean pc. Again i sequenced the application for PROD environment with asset directory as PRSC6260.v01. I deployed the application for prod environment in SCCM server but when i launched the shortcut of the application(prod environment) in client pc it throws an error that asset directory already exists.Error code is 0000E019. Kindly advice what to do to overcome this error.

Regards,
S.Yuvaraj.

0 Comments   [ + ] Show comments

Answers (5)

Posted by: vkleiner 15 years ago
Orange Senior Belt
0
Hi S.Yuvaraj,

did you use SCCM for both enviroments or is your client member you tested on member on both goups?

The error indicate that two packages using the same root directory. (see KB930628 ).
I would clear the client cache and remove the first sequenced package out of the system, too.

Greetings

________
vkleinerde
Posted by: Yuvaraj_Subramanian 15 years ago
Senior Purple Belt
0
Hi Vkleiner,

Thanks for your reply. Does that mean the asset directory name for Prod and PreProd environment should be different? for eg for prod the asset directory name is PRSC.v01 and preprod environment the asset directory name should not be the same PRSC.v01.
Posted by: vkleiner 15 years ago
Orange Senior Belt
0
Hi,
It depended how your System is designed.

If you have 2 physical separated systems for prod and preprod ( so do I ) you can use the same names.
After testing the sequence I move it into the productive environment.

The App-V Client (Desktop or Terminal Server) could only handle one package root directory (PRD) - this must be unique per design.
If you load a package p.v1 into a PC, member of preprod, it´s loaded into local client Cache. When you now deploy a second one with same PRD via Prod to the same PC, you get this error.

The package is still in client cache and the second one cannot be import. Only if you remove the first package on the client, the new second one could be loaded.

________
vkleinerde
Posted by: kkaminsk 15 years ago
9th Degree Black Belt
0
Just think of it like this, why would you want two isolated virtual environments using the same virtual file system? It would defeat the purpose of virtualization so the product does not allow you to do this.
Posted by: Yuvaraj_Subramanian 15 years ago
Senior Purple Belt
0
Actually i am sequencing the apps for different environment since it is an client requirement.
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