/build/static/layout/Breadcrumb_cap_w.png

APP-V DSC issue

i packaged 2 applications as a APP-V. app A and app B. B is dependency for A.
B is took captured in Q:\BBB\ directory. and when taking capture for app A , installed app B source in Q:\BBB\ location. then took captured. DSC implemented (in app A osd file added dependencies CODEBASE of app B). after installed streming working . when i launch the app A shortcut, it got some .dll error. this dll having in app B installtion direcoty.
why its not intaract with app B INSTALLDIR (Q:\BBB) ?
Any body help...


0 Comments   [ + ] Show comments

Answers (2)

Answer Summary:
Posted by: dunnpy 10 years ago
Red Belt
0

Sounds like you need to do some in 'bubble' troubleshooting.

Launch sequence A using an alternative executable from a command prompt:

SFTTRAY /EXE CMD /LAUNCH "<appname>"

<appname> can be found by running in a command prompt:

SFTMIME QUERY OBJ:APP /SHORT

This will output a list of appnames for all sequences installed.

The SFTTRAY command will give you a command prompt in the 'bubble', as B is a dependency for A the 'bubble' will be a combined one with both virtual environments for A & B.

Try registering that dll in that command prompt (regsvr32.exe <pathtofile>\<file.dll>), exit and relaunch application A and see if that works.

If it does, then you'll need to register the dll in the sequence for application B and retest.

If that doesn't you have the commands to run the alternative executable 'bubble' and troubleshoot some more.

Hope that helps,

Dunnpy

 

Posted by: vjay 10 years ago
Second Degree Blue Belt
0

Finally foud it.

app B having enironment variable in osd file. app A shortcut is launching fine, after add environment variables in app A osd file.

 
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