A Puzzle of a Problem with APP-V 4.5 & MsAccess 2000 & MsWord 2003..
We have a legcey application that runs under MS Access 2000 on a XP sp3 platform , that we are having to make virtual, as there is a technology refresh going on at present by the client , we have now come across a problem, we can sequence the app fine i.e install ms access 2000 and start up app, and can talk to the back end data base ok during sequenceing (note seq machine runs on MS Vitural server 2005) and is a fresh build of XP Pro sp3 no office installed at that point, the problem comes when we deploy to a windows XP – Pro sp3 system that has office 2003 installed localy we are using offline deploy, and generating a msi to be run on a APP-V 4.5 Client, as part of the ms access application word is called, i.e vitural ms access, will call local word, via vb code in the application, so you have ms access 2000 vitural application calling ms word 2003 on local machine when this happens we are getting some strange results the msi installer starts up, every time, and tries to install something in word 2003 on the local machine, we did find that is was trying to install speech files, due to region and langurage settings now fixed , now it is trying to install something else, but canot find what it is looking for and giving us a error about dll and in event log we can see messages about ProductNonBootFiles (see below) message in the msi installer debug log, note target machine is built from a images, so office install files are not available. Has any one got any ideas? As we are not sure if it’s a office/app-v problem or a windows problem, or how we are trying to seq application and deploy, any help much valuled
MSI Instller log.
=== Verbose logging started: 01/05/2009 16:05:23 Build type: SHIP UNICODE 3.01.4001.5512 Calling process: D:\PROGRA~1\MICROS~1\OFFICE11\WINWORD.EXE ===
MSI (c) (C8:2C) [16:05:23:968]: Resetting cached policy values
MSI (c) (C8:2C) [16:05:23:968]: Machine policy value 'Debug' is 0
MSI (c) (C8:2C) [16:05:23:968]: ******* RunEngine:
******* Product: {91110409-6000-11D3-8CFE-0150048383C9}
******* Action:
******* CommandLine: **********
MSI (c) (C8:2C) [16:05:23:968]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (C8:2C) [16:05:24:046]: Cloaking enabled.
MSI (c) (C8:2C) [16:05:24:046]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (C8:2C) [16:05:24:046]: End dialog not enabled
MSI (c) (C8:2C) [16:05:24:046]: Original package ==> C:\WINDOWS\Installer\63eaf.msi
MSI (c) (C8:2C) [16:05:24:046]: Package we're running from ==> C:\WINDOWS\Installer\63eaf.msi
MSI (c) (C8:2C) [16:05:24:109]: APPCOMPAT: looking for appcompat database entry with ProductCode '{91110409-6000-11D3-8CFE-0150048383C9}'.
MSI (c) (C8:2C) [16:05:24:109]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (C8:2C) [16:05:24:125]: Couldn't find local patch ''. Looking for it at its source.
MSI (c) (C8:2C) [16:05:24:125]: Resolving Patch source.
MSI (c) (C8:2C) [16:05:24:125]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (C8:2C) [16:05:24:125]: User policy value 'DisableMedia' is 0
MSI (c) (C8:2C) [16:05:24:125]: Machine policy value 'AllowLockdownMedia' is 0
MSI (c) (C8:2C) [16:05:24:125]: SOURCEMGMT: Media enabled only if package is safe.
MSI (c) (C8:2C) [16:05:24:125]: SOURCEMGMT: Looking for sourcelist for product {375F080F-88E9-4EA1-A177-C0F091546AC8}
MSI (c) (C8:2C) [16:05:24:125]: Note: 1: 1706 2: {375F080F-88E9-4EA1-A177-C0F091546AC8} 3:
MSI (c) (C8:2C) [16:05:24:125]: SOURCEMGMT: Failed to resolve source
The installation source for this product is not available. Verify that the source exists and that you can access it.
C:\WINDOWS\Installer\63eaf.msi
MSI (c) (C8:2C) [16:05:24:125]: Note: 1: 1708
MSI (c) (C8:2C) [16:05:24:125]: Note: 1: 2729
MSI (c) (C8:2C) [16:05:24:125]: Note: 1: 2729
MSI (c) (C8:2C) [16:05:24:125]: Product: Microsoft Office Professional Edition 2003 -- Installation failed.
MSI (c) (C8:2C) [16:05:24:140]: MainEngineThread is returning 1612
=== Verbose logging stopped: 01/05/2009
All Replies
- Hello,
Any possible conflicts in shortcuts / file-associations?
Any chance to know if the installer is executed within the virtual environment or outside?
/Znack - Hello Znack,
we are sure installer is running from local machine, as vitural app has only ms access installed, and installer only come up when word starts. and vb code just does a call to word application so i do not thing its file assoc, we have also tried app talking to Word 2007 same problem, but when we do every thing locally it works, problem only appers when using Vitural app and msi log show office2003 being called..
Calling process: D:\PROGRA~1\MICROS~1\OFFICE11\WINWORD.EXE
Andy_d - Hello,
If you remove the virtual-app - by uninstalling it. Does the MSI repair start then?
/Znack - Hello,
Anyways, how did you sequence this app?
Since there is a requirement for the Word-integration I suppose you had Word installed locally before starting to sequence?
Have you tested the functionality while sequencing?
/Znack - I had a similar problem few weeks ago. As the machines that you use already have Office 2003 installed, the ideal would be sequence the app on a machine with Office 2003 already installed and install Access 2000 witch the best practices (install on drive q:, etc.) and check if the script call the virtualized Office 2000 as mentioned by andy_d
Alexandre Gomes- Proposed As Answer byznack Friday, August 07, 2009 9:07 AM
