VMhadi's Posts

I had them defined in package.ini and the vbs is inside %ProgramfilesDir%. I am guessing when excel run from the script it was running as a child process thus run in physical environment while running excel straight from an entry point defined in package.ini was a parent process in virtual environment. After a couple hours of trial and error I found if I removed folder "Microsoft SQL Server" from %ProgramFilesDir% which only have EULA inside. Excel run just fine and I didn't have to use ChildProcessEnvironmentDefault or ChildProcessEnvironmentExceptions. I'll do further testing just to make sure it does what we wanted to do that is importing files from an sql database using the driver in the ThinApp bubble. Thank you everyone for your help.

I am sorry I had a look at the log file but I could not find anything that I can really understand. They looked pretty encrypted to me but I attached it anyway in case you are interested to have a look at it. I stoped the capture as soon as it spawned SETUP.exe otherwise it will get quite large. I just found out that I have to use ChildProcessEnvironmentDefault=Virtual and ChildProcessEnvironmentException=Excel.exe for the vbs to work otherwise it behaves similar to running excel directly from package.ini. 

No, I just open up command prompt and run excel with the full path c:\program files\Microsoft office\Office12\Excel.exe. I then tried several working directories in package.ini %personal%; %program files common%\Microsoft Shared\OFFICE12; and %programfilesdir%\Microsoft office\Office12 but not successful. At the moment my work around is to execute a vbs script that run excel.

Just a tip I had similar situation a couple months ago and I look for any setting file(s) in the application that hardcoded the computer name and check if I can change it to something like localhost or * which luckily I can. You might want to check your vendor support too they might be able to help, well in my case they tried and could have found those files faster if I asked them in the first place.

Thanks Phil, I tried ProcessExternalNameBehavior=Original but it has no effect. I ran logging and found a few microsoft.windows.common.control.dll failure in potential errors while running process monitor didn't give me much, dr watson kicked off as soon as the ThinApp started and strangely process explorer bombed out with out of memory error as soon as the exe run...sounds like a hint to me. May I ask what do you look for in the thinapp logs normally? I must say my eyes goes teary everytime I look on it for more than 5 minutes. Hadi