how to find what is calling MSOffice during execution of my package
Hi Guys,
I am using package studio to repackage Cisco Historical reporting (CRS) and development of the package was going well until this problem.
The package successfully installs the application, then when i execute the application, during the application startup it somehow it calls the MSOffice.msi from a cached install path.( why i dont know)
This does not happen if i run the application with local admin, and only does with a restricted user acocunt.
It trys to run the the Office setup every time i execute/startup the application and cant find the path. How and where can i check for what is calling/doing this in the package? I dont see any files relating to Office in my MSI, and it does`nt do it when running with local admin
any ideas what might cause this?
I am using package studio to repackage Cisco Historical reporting (CRS) and development of the package was going well until this problem.
The package successfully installs the application, then when i execute the application, during the application startup it somehow it calls the MSOffice.msi from a cached install path.( why i dont know)
This does not happen if i run the application with local admin, and only does with a restricted user acocunt.
It trys to run the the Office setup every time i execute/startup the application and cant find the path. How and where can i check for what is calling/doing this in the package? I dont see any files relating to Office in my MSI, and it does`nt do it when running with local admin
any ideas what might cause this?
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
There will be an entry in the Application event log, detailing the component ID which is triggering this activity. Trace the ID to the component in your MSI and work from there. Almost without question, that component will be user profile-based (either file or registry), as it's not being triggered by an admin user (who will be using the All Users profile).
Posted by:
mekaywe
13 years ago
If it is a setup capture, may be MSOffice Installer related registries are captured.
Checkout the registry table
Checkout the registry table
Posted by:
chris16v
13 years ago
Thanks VBSab. you were right. I checked in the application log, narrowed down a suspect component and removed the unwanted offender.
thanks ! !! !
thanks ! !! !
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.