Has Anyone Created an APPstack with Medical Applicatoins????

[Super6VCA]

Trying to test drive AppVolume and keep running into snags.  We are test driving ver 2.11 and seem to have some issues with our medical apps.  Doing Firefox, chrome, adobe, and simple apps like that seem to work fine but that doesn't do us any good unless we can virtualize the medical apps.  After a lot of effort i appeared to get it to install however when i try to launch teh app from a desktop pool it appears to work until it tries to access a client record on the database.  Then the error occurs.  The applications I am trying to do are Me PACS (Image Viewer Software for x-Rays and MRI's) and Greenway Intergy.  If anyone has experience with this and can help out i would appreciate it!  Thanks

[Lakshman]

I have no experience with medical applications. Can you provide more details about the error? Is it related to database or specific to app volumes?

If database, can you check whether the ODBC connectivity is working as expected and the database server is reachable from the deployment VM?

[Super6VCA]

The current app i am working on seems to open up fine but we try to access a patient record (which is on the db) an error comes up then closes the app. 

[Lakshman]

Please check if any manual ODBC configuration steps are required that might have missed during provisioning the AppStack.

To narrow down the problem, can you install the application manually on a test VM and check the database connectivity please.

[mellicott]

I'm in local government, and have the same issues when trying to package specialist software.

I would approach the issue as if it was happening on a physical PC, and maybe contact the software vendors to help track down the issue.  Then apply the knowledge to installing the software differently if necessary.

I've found, quite a lot, especially if the software is quite old (10 years or more), then files can be installed into the Windows folder, which then require specific permissions to work in the App Vols environment.

There is no manual for packaging old software :smileylaugh:

[Super6VCA]

Lakshman,

There are no ODBC configs during this setup.  The only thing close is during the initial install it wants to know the location of the Intergy server.  I did once again reinstall the app and try to Appvol it.  So starting from scratch here is what i did so give me your thoughts.  I go the base VM all patched up with MS patches.   Setup the AppVol to provision the APP, Went thru the install process like normal (it takes an hour to install), and once i was completed with the install i went into the app to make sure that everything worked as planned.  At that point everything did work the way it is supposed to.  So I completed the app and assigned it to some test VM's.  Once i get into the test VM and try to launch the app i get teh same error message when trying to access the patient records.  The Company is not very coperateive knowing that this is in a VMware environment and they don't even know that I am trying to virtualize the application.  If they knew that they would probably halt right there.  They say they donot support the APP in a VM.  I say BS!!!  Any thoughts are welcome. 

Also, do you think that having a writable volume would help this situation at all??

[Super6VCA]

Mellicott,

Thanks for the reply.  This is not an old app at all and trying to get this company to support Anything in a virtual environment is near impossible. 

[Lakshman]

Perry,

Guess we need to have a look at the App Volumes log files to figure out what is happening. Could you attach the App Volumes Agent log please.

Location of VMware App Volumes log files (2091590) | VMware KB

[Super6VCA]

Lakshman,

Her is the agent log.  Hope it's the correct one.  Thanks

[Lakshman]

I have gone through the log file where i could not find anything related to database connection error. There are couple of errors at the bottom, related to fonts.

[2016-12-12 17:10:47.267 UTC] [svservice:1300] ReplicateFile: CopyFileW("C:\SnapVolumesTemp\MountPoints\{5957aef8-be49-11e6-abc2-806e6f6e6963}\SVROOT\Windows\Fonts\FRE3OF9X.ttf") to ("\\?\Volume{9329b9d8-f1ec-11e3-a147-806e6f6e6963}\SVROOT\Windows\Fonts\FRE3OF9X.ttf") failed, error:2.

[2016-12-12 17:10:47.267 UTC] [svservice:1300] ReplicateFonts_Install: Replication failed "C:\SnapVolumesTemp\MountPoints\{5957aef8-be49-11e6-abc2-806e6f6e6963}\SVROOT\Windows\Fonts\FRE3OF9X.ttf" -> "\\?\Volume{9329b9d8-f1ec-11e3-a147-806e6f6e6963}\SVROOT\Windows\Fonts\FRE3OF9X.ttf"

[2016-12-12 17:10:47.267 UTC] [svservice:1300] ReplicateFile: CopyFileW("C:\SnapVolumesTemp\MountPoints\{5957aef8-be49-11e6-abc2-806e6f6e6963}\SVROOT\Windows\Fonts\FREE3OF9.ttf") to ("\\?\Volume{9329b9d8-f1ec-11e3-a147-806e6f6e6963}\SVROOT\Windows\Fonts\FREE3OF9.ttf") failed, error:2.

Suggest to please file a support request with VMware to look into this in detail.

[Smoke14]

You could try installing the app natively and then mount the appstack of the app to see if it works with the native app installed.

If it works, you must likely are missing user settings that you will need to track down, could be User ODBC of something else like %APPDAT% population.

[Super6VCA]

This is just a guess but i'm guessing that it would probably work.  I can get teh imaging to work to osme extent but nothing i can put into production.  As for the Greenway app.  The main product will not work.  I will try to install it natively but my guess is that it's gonna work.  Thanks for the suggestion