TobyFruthParson's Posts

Can you test if anything changes in ThinApp 4.7 by setting the following in Package.INI: [BuildOptions] ;Disable some Data Execution protections for this particular application AddPageExecut... See more...
Can you test if anything changes in ThinApp 4.7 by setting the following in Package.INI: [BuildOptions] ;Disable some Data Execution protections for this particular application AddPageExecutionPermission=1 Granted, I'm not suggesting this as a permanent fix.  Just curious if the error changes or disappears.  Also, can you test turning off DEP?  My apologies if you've already tried all these things.
Has any other Outlook version ever been installed on the user's machine?
I see that Oracle is installed to a folder on the root of C:\ during the capture process.  Can you install the primary application to a folder on the root of C:\?  Sometimes this helps when imple... See more...
I see that Oracle is installed to a folder on the root of C:\ during the capture process.  Can you install the primary application to a folder on the root of C:\?  Sometimes this helps when implementing on Windows 7, especially if Windows 7 is 64-bit.
Sounds like something else is going on, because I always run build.bat from command prompt.  Must be a different issue. Technically, ThinApp doesn't have to be "installed" in order for it to w... See more...
Sounds like something else is going on, because I always run build.bat from command prompt.  Must be a different issue. Technically, ThinApp doesn't have to be "installed" in order for it to work.  You do need to define the THINSTALL_BIN environment variable. See this thread for more detail:  http://communities.vmware.com/message/1854821#1854821
The application runs properly, with the exception of the message. Have you tested the virtual app on the capture machine, with the native application still installed?
Can you save the project on your capture machine during the postscan?  You might be able to specify a capture/project storage path that uses a folder on the root of C:, like C:\capture.
On the surface this sounds more like a View question than a ThinApp question.  Are the VM's persistant?  Is the VM in question automatically created/destroyed?  I agree that in theory the applica... See more...
On the surface this sounds more like a View question than a ThinApp question.  Are the VM's persistant?  Is the VM in question automatically created/destroyed?  I agree that in theory the application would simply be reregistered on the VM.
Please provide the following detail (if possible): A brief description of LNS database technology A brief description of what you mean by "LON credit" Thanks
The main ThinApp licensing KB article: http://kb.vmware.com/kb/1006248
Regarding ThinApp, services, and, to an extent, MSI and/or Thinreg: http://blogs.vmware.com/thinapp/2010/08/vmware-thinapp-46-whats-new.html http://communities.vmware.com/message/1194778 ... See more...
Regarding ThinApp, services, and, to an extent, MSI and/or Thinreg: http://blogs.vmware.com/thinapp/2010/08/vmware-thinapp-46-whats-new.html http://communities.vmware.com/message/1194778 http://blogs.vmware.com/thinapp/2009/07/thinapp-services.html
Try turning off compression.  Worked for me with Adobe InDesign CS5.  Also, try all the various isolation modes, starting with Merged. Lastly, you did not specify where you are testing the app... See more...
Try turning off compression.  Worked for me with Adobe InDesign CS5.  Also, try all the various isolation modes, starting with Merged. Lastly, you did not specify where you are testing the application.  I suggest that the first test of a troublesome app be run on the VM where is was packaged.  Start by testing on the VM after the application capture and build.  If it runs fine, then move on to testing on the same VM reverted to pre-application condition.  If it does not run fine on the "dirty" VM that has the application natively then more troubleshooting remains. Here's a list of ThinApp troubleshooting links (listed chronologically): http://blogs.vmware.com/thinapp/2008/10/creating-window.html http://blogs.vmware.com/thinapp/2009/05/app-troubleshooting.html http://blogs.vmware.com/thinapp/2010/01/thinapp-troubleshooting---repost.html http://blogs.vmware.com/thinapp/2010/10/thinapp-troubleshooting-methods.html http://blogs.vmware.com/euc/thinapp-troubleshooting/ http://kb.vmware.com/kb/1030313 http://blogs.vmware.com/kb/2011/07/new-mind-map-troubleshooting-thinapp-issues.html
Have you read this thread:  http://communities.vmware.com/thread/331158
Have you tried ThinApp 4.7?
Forgot to mention that our IE8/Java/Flash package works on Winsows 7 Pro 64-bit with default UAC settings  which is "Default - Notify me only when programs try to make changes to my computer".
This is the ThinApp forum.  Is ThinApp part of your implementation?
I know you marked the thread "closed", but I wanted to comment.  Having packaged Internet Explorer, I can tell you that applications that retrieve files from the Internet and other places is a co... See more...
I know you marked the thread "closed", but I wanted to comment.  Having packaged Internet Explorer, I can tell you that applications that retrieve files from the Internet and other places is a common occurrence.  Sounds like you need to focus on sandbox management.
Have you considered creating two application packages, one for IE and one for Java?  Make the Java app a RequiredAppLink under IE.  IE package won't even launch unless it finds the Java app.  Thi... See more...
Have you considered creating two application packages, one for IE and one for Java?  Make the Java app a RequiredAppLink under IE.  IE package won't even launch unless it finds the Java app.  This way you at least know for sure that virtual IE sees virtual Java.  I think you are capturing both in application, which, in theory, means they absolutely should see each other.  I went the other route, using AppLink, and my virtual IE alwyas uses the virtual Java. I made the AppLink optional, but in your case I would recommend it be required.  The Package.ini line in IE would look something like this (adjust to accommodate your configuration): RequiredAppLinks=%ProgramFilesDir%\ThinApp\Java_6_Update_20.dat
Good to hear! Check out the following comments from myself and others regarding external child process ramifications: http://communities.vmware.com/message/1857756#1857756
These are my go-to links for ThinApp and Java: http://blogs.vmware.com/thinapp/2008/10/step-by-step-in.html http://blogs.vmware.com/thinapp/2011/03/the-power-of-applink.html http://blogs... See more...
These are my go-to links for ThinApp and Java: http://blogs.vmware.com/thinapp/2008/10/step-by-step-in.html http://blogs.vmware.com/thinapp/2011/03/the-power-of-applink.html http://blogs.vmware.com/thinapp/2010/01/step-by-step-instructions-on-how-to-thinapp-newer-java-versions.html http://blogs.vmware.com/thinapp/2010/06/java-16-tweaks.html http://blogs.vmware.com/thinapp/2010/04/java-pop-ups-slow-in-ie.html You may find the last link listed above to be the most helpful.
Two questions: 1.  Does the application work natively installed on your XP capture machine? 2.  Is the SQL Server instance on a server or are you also packaging SQL Server Express?