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.
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)
Please log in to answer
Posted by:
vkleiner
15 years ago
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
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
Posted by:
vkleiner
15 years ago
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
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
Posted by:
Yuvaraj_Subramanian
15 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.