Virtualizing with App-V?
Has anyone been able to successfully Virtualize Maple 18.0.1? I am able to Sequence the app with the App-V Sequencer, and run it on that particular machine. However, when I deploy the application as an App-V package, I get a "too many recursions" error every time I try to do anything in the application.
Anybody have any ideas?
it starts as soon as I open the application.... See the attached photo....
Thanks!
10 Comments
[ + ] Show comments
Answers (0)
Please log in to answer
Be the first to answer this question
My first suspicion would be Java.... - anonymous_9363 10 years ago
I can't seem to find anything related to that version of Java... When I search for it and APP-V, the top two results are posts to to MapleSoft's threads which have no answer. - dafyre 10 years ago
If it's an MSI, open it up and check that you have all of files, registry etc in your sequence. If it isn't do a quick snapshot and compare.
You could use ProcMon to see what it's trying to access when you get the error, and compare that to a working physical install. It may just point you in the right direction at a file level. - dunnpy 10 years ago
I've also gone back and tried to allow the local access to stuff as well, and that doesn't get it either...
That actually is an excellent Idea that you have, Dunnpy... I'll give it a whirl and post back. - dafyre 10 years ago
If I start the locally installed Maple it works fine... If I leave the locally installed copy open and launch the APP-V copy? It works perfectly.
Close it all out and reboot... Now if I start the APP-V'd version of Maple, it still errors. If I leave the APP-V'd version open, and launch the local install, that one starts erroring out as well.
This leads me to a few conclusions... the two that make sense to me are :
a) After launching one instance of Maple (either Local or APP-V'd), and you try to start the next one, it sees the existing instance and just uses what is already there.
b) The problem likely lies somewhere in the mserver.exe process which does some network communication.
Note: I just realized something: I have *NOT* tried this with a local license file. We have a Network Activation server for Maple here.
Sill no solutoin... but got a few steps farther this time! - dafyre 10 years ago
An excerpt from his response:
"One thing to watch out for is if the file path becomes too large, it will cause problems with the application launcher as it passes a large string of options along to the JVM when it launches the Java interface. This string is limited in the amount of characters that it can accept, having it append 80 extra characters onto the file path multiple times can and will exceed this string limit. If you are seeing this, you should investigate if there is any way to reduce the size of this path name."
The file path to the Maple executable is about 90 characters long (the GUID is pretty long) for me, so this may be my problem. I'm waiting for support to confirm whether the error message indicates this is the issue. If it's not the file path, then I may consider installing the software on the image itself. - jal 9 years ago
When we need to push out a new package, I just install the software on the master image and hit "Go" and it redeploys the master image for me.
I am keeping my eyes on App-V for sure. Hopefully it keeps getting better and better! - dafyre 9 years ago
Depending on the software, uninstalling can leave remnants of the old and cause problems for a new version or other pieces of software (software conflicts and all that).
App-V works and it is getting better but it's not a solution for everything, especially for larger pieces of software. In this case, it's not App-V per se, but the software, which has a character limitation.
I don't know your setup, but it may be much better than mine. This is just from experience ;) Happy packaging! :) - jal 9 years ago