Application requires a reboot but is not done by installer, and cannot get App-V to process reboot processes
- Hi All,
I'm currently having some issues with trying to get an app virtualized through App-V.
The app requires a reboot, there is a message at the end of the installation that recommends you reboot, but it does not initiate/send a reboot request itself to the OS. Thus there's no process for App-V to capture and cancel.
I've tried manually restarting, which App-V captures, and I then follow the normal procedure of clicking Stop Monitoring and then clicking Begin Monitoring again, but it does not seem to process whatever the reboot does.
I've tested the app-v version and a regularly installed version and the problems are indeed related to the reboot. If on the regularly installed version, I try to use it without rebooting, the exact same issues that I see happen on the App-V version occur. Once I reboot the regular version, everything works as it should.
Does anyone know how I can get App-V to capture the reboot process?
Answers
- My problem was that I wasn't receiving any errors. All indications were that it installed correctly and just didn't launch properly (no errors. the process just went to 99% cpu).
I've figured it out though :)
I used a program called TrackWinInstall and did a comparison on a before and after state for the machine when done via non-app-v. I was able to locate the 3 files that were changed during the boot process.
I just copied those 3 files from the post-boot state and copied them into the app-v during sequencing and reregistered them also in app-v and now it works fine!! :)
Thanks to everyone who helped me :)- Marked As Answer byj2 Global Wednesday, October 28, 2009 6:55 PM
All Replies
- Hello,
I don't believe that app-v actually tries to capture a process and its reboot, but more what the process told the system to do during a reboot.
It doesn't sound right at all when you describe the things you tried, as doing an actual reboot would be a big no-no.
Anyways, let the installer finish - stop monitoring and check the following log-file;
sftbt.txt
Provides information about computer restart tasks that occur during the Sequencer’s simulated restart.
Log file location: %windir%\Microsoft Application Virtualization Sequencer\Logs
Perhaps that can give you some ideas...
/ZNack - Have you tried if it actually works when this package is streamed to the client?
br,
Kalle - It unfortunately does not work when streamed to the client.
I've checked the logs and it said "The Sequencer did not find any reboot related tasks."
The app I think might add some system files that don't seem to take effect until after a reboot. Is there anyway to simulate such a thing via app-v? Bummer, then it really needs something more in the sequence. There isn't any other way to simulate a reboot as Stop Monitoring + Start Monitoring should process all actions that app queues for next reboot.
What are the exact symptoms for this application if it's not rebooted in-between? Is there possibility to trace with Process Monitor what application accesses just before it refuses to run?
/KalleThe app i'm trying to virtualize is Oracle ADI, btw.
I think the problem is that the app doesn't run or queue any actions for reboot. At the end of the installation it just says "some files could not be copied over because they are in use. Your app MAY (I added caps) not work properly until after reboot". The reboot is not a requirement, but a recommendation and then the installer quits.
If I don't reboot, the app gets stuck at 99% cpu usage and never goes through. If I do reboot, it goes through just fine. But once again I don't think the app itself queues up any actions to take place during reboot.
There's gotta be a way to simulate what would happen to the OS after a full reboot!! :(- Hello,
I would try to enable some type of logging for the installer - which should then hopefully tell you whats left todo...
/Znack - Hmm, could these files be VC++ runtime files as Sequencer itself is using VC++ 2005 runtime (in 4.5) and I have seen (long ago in previous versions) issue wherein application tried to update those very same files that Sequencer had as locked. And since installer detects them being in use, it does not try to queue file replacement operation for reboot (and Sequencer has nothing to process)..
Try to run that Process Monitor while install is in progress and stop immediately after getting the error message, that should show in the end of the log what files couldn't be replaced?
/Kalle - I just redid the installation with procmon on and did not notice anything weird (no access denied, or any other failures).
I've also gone over the log file the installer (Oracle Installer) generates, and unfortunately all that shows me is what scripts the installer called to perform the installations. It doesn't tell me the actual files copied, what operations are pending :(
How do you normally handle an app that requires a reboot to work, but the app itself never prompts you to reboot (i.e. rebooting is something you know from experience as being an unofficial requirement for the app to work)? - Hello,
Well - you could do a wise-capture and see what it gets. There are a couple of utilities that offer differences between boots (my head is blank at the moment) and well - you could just ask the vendor worst case scenario?
I mean - this probably just falls within the usual range of troubleshooting as any tool that can tell you the difference between "now" and "then" will suffice...
This is hilarious:
The official docs states the following;
Question: What does it mean if I get the message "Object variable or
with block variable not set Error Number:91" while signing on to ADI?
This is an indication that ADI is not installed correctly. This is probably because
Oracle Objects is not registered correctly, or your version of Required Support Files
(RSF) is incorrect. Run the Diagnostic Wizard and follow its recommendations.
There is also a reference to a oracle kb-article here;
http://forums.oracle.com/forums/thread.jspa?threadID=892974&tstart=31
/Znack
/Znack - Hi,
you could try to launch the "corrupt" package on a client and observe it with ProMon, perhaps it shows some errors there. Also, it _might_ help to do the following:
- Sequence the installation as you did before (manually initiate the reboot, let Sequencer intercept it, stop/start monitoring)
- Finish the Sequencing, save the (corrupt) Package
- physically reboot the sequencer
- open the package for Upgrade and see if that helps.
Additionaly I once came across an application (Boink) that created some sort of "notrebooted.txt" file. This file was not deleted by SequencerÄs Reboot Interception, so the program always noted that there is that text file and therefor always prompted it still would need the reboot. Simply deleting this file made the trick. There is a small chance that your application also queries such an "am I rebooted?" flag. However, the error message indicates somethjing else.
Falko - My problem was that I wasn't receiving any errors. All indications were that it installed correctly and just didn't launch properly (no errors. the process just went to 99% cpu).
I've figured it out though :)
I used a program called TrackWinInstall and did a comparison on a before and after state for the machine when done via non-app-v. I was able to locate the 3 files that were changed during the boot process.
I just copied those 3 files from the post-boot state and copied them into the app-v during sequencing and reregistered them also in app-v and now it works fine!! :)
Thanks to everyone who helped me :)- Marked As Answer byj2 Global Wednesday, October 28, 2009 6:55 PM
