How should I solve this conflict between different Office versions (2003/2013)?
Hello,
I ran into a pretty rare situation. I have a client that has 2 packages for different office applications:
1. Access 2013: Installated locally/unattended installation
2. Access+Excel 2003: In one package, virtualized with App-V 5.0.
The first package works fine, but as soon as I publish the second package (without even starting it), there is a repair triggered every time Access 2013 starts. After the repair, Access 2013 works fine, but the repair takes half a minute, and it's very annoying. I suspect there are some registry keys set by the App-V client to handle FTA's, which conflict with Access 2013. I tried removing all FTA's from the second package (not as a solution, but just to test my hypothesis), but no luck so far.
Does anyone have an idea how to solve this? Would it be possible to disable the repair in the Access 2013 package?
Any sugestions are welcome.
Answers (2)
Was the second package created on a system that had Office 2013 installed or was it a "clean machine"?
What version of Access is in the second package?
To run multiple version of Office, the oldest version has to be installed first so in this case, you'll probably have to change the install process amd update the second package.
Just out of curiosity, why do they need the second package on a system?
Comments:
-
The second package contains both Access 2003 and Excel 2003. A collegue of mine created the package, I am assuming it was made on a clean machine.
The customer has applications that require access 2003. Some employees require Access 2013. A few of them use both. - cubefreak 10 years ago
It is not good to disable repair for locally installed access 2013. As you are suspecting there might be a conflict between registries for FTA's.You can also check if any other files or registries have conflicts with locally installed access.
