Patch problem Access 2003 (SP2)
Hi!
We use Active Directory to publish our applications to users.
We have "patched" MSAccess2003 media with Office2003SP2-KB887616-FullFile-ENU
(msiexec /p <path>\Mainsp2ff.msp /a <path>\Acc11.msi /qb /lv* <path>\logfile
msiexec /p <path>\Owc11SP2ff.msp /a <path>\Owc11.msi /qb /lv* <path>\logfile)
According to log everything look to have worked out alright. If I install
the new media manually on a client everything works fine too, but now to our
strange problem.
If I publish this new media in Active Directory and installs it to a client,
when I start the application there is a selfrepair every time and then
nothing....
The application refuses to start at all and if I look in event viewer it
only says "Installation of Access2003 completed successfully" for every
attempt I made starting it and its been selfrepaired. No information of what
component triggers the selfrepair.
Why can't we publish this new media from Active Directory? It works fine if
we install it manually on clients.
// Regards Johan / HÃ¥kan
~Sweden~
We use Active Directory to publish our applications to users.
We have "patched" MSAccess2003 media with Office2003SP2-KB887616-FullFile-ENU
(msiexec /p <path>\Mainsp2ff.msp /a <path>\Acc11.msi /qb /lv* <path>\logfile
msiexec /p <path>\Owc11SP2ff.msp /a <path>\Owc11.msi /qb /lv* <path>\logfile)
According to log everything look to have worked out alright. If I install
the new media manually on a client everything works fine too, but now to our
strange problem.
If I publish this new media in Active Directory and installs it to a client,
when I start the application there is a selfrepair every time and then
nothing....
The application refuses to start at all and if I look in event viewer it
only says "Installation of Access2003 completed successfully" for every
attempt I made starting it and its been selfrepaired. No information of what
component triggers the selfrepair.
Why can't we publish this new media from Active Directory? It works fine if
we install it manually on clients.
// Regards Johan / HÃ¥kan
~Sweden~
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
nheim
18 years ago
Hi Johan,
what does MSI-Logging tell you about this?
You should be allmost certainly be able to find the problem in there.
Regards, Nick
what does MSI-Logging tell you about this?
You should be allmost certainly be able to find the problem in there.
Regards, Nick
Posted by:
clavdivs
18 years ago
Hi Nick
Im working with Johan on this problem. Yes we have logged the installation and probably there is some useful information in there. Its like finding a needle in a haystack. I cant find any hint in there what is the problem.
Our support told us to patch the whole pro media instead and deploy access with a transform to pro11.msi They told us its Microsoft best practise how to patch and deploy different parts of the Office pro applictions.
Must say i didnt liked that idea cause it will cause them to get same product codes!!!
Well i tryed it just to see, but the outcome was exactly the same.
Our system to install office core products (word,excel,oulook,powerpoint) on RIS-Installation and patch the media and run a script "reinstall all" when there is ServicePacks. And to deploy extra products like Access, Project, Publisher, Frontpage and Visio thruu GPO policy in our Active Directory (user and published) and patch that media with Service Packs and redeploy worked perfect with Service Pack 1 and also for Service Packs 2 for all of them but ACCESS.
For Access i have done a setupacc.exe /a first and after patched the administrative point with service pack.
And for Frontpage setupfpg.exe /a and patch that media etc...
With this method i publish Access with acc11.msi and frontpage with FP11.msi so i get a unique product code for each and every application. Also checked the outcome with office update that verifyes that all my office products is up to date.
If i install the Access msi-package manually on my client everything works perfect so there must be some issue with the Deployment through GPO Active Directory.
Regards /Hakan
Im working with Johan on this problem. Yes we have logged the installation and probably there is some useful information in there. Its like finding a needle in a haystack. I cant find any hint in there what is the problem.
Our support told us to patch the whole pro media instead and deploy access with a transform to pro11.msi They told us its Microsoft best practise how to patch and deploy different parts of the Office pro applictions.
Must say i didnt liked that idea cause it will cause them to get same product codes!!!
Well i tryed it just to see, but the outcome was exactly the same.
Our system to install office core products (word,excel,oulook,powerpoint) on RIS-Installation and patch the media and run a script "reinstall all" when there is ServicePacks. And to deploy extra products like Access, Project, Publisher, Frontpage and Visio thruu GPO policy in our Active Directory (user and published) and patch that media with Service Packs and redeploy worked perfect with Service Pack 1 and also for Service Packs 2 for all of them but ACCESS.
For Access i have done a setupacc.exe /a first and after patched the administrative point with service pack.
And for Frontpage setupfpg.exe /a and patch that media etc...
With this method i publish Access with acc11.msi and frontpage with FP11.msi so i get a unique product code for each and every application. Also checked the outcome with office update that verifyes that all my office products is up to date.
If i install the Access msi-package manually on my client everything works perfect so there must be some issue with the Deployment through GPO Active Directory.
Regards /Hakan
Posted by:
clavdivs
18 years ago
Solved!!
This article describes problem and alternative solutions.
Our solution was to simply add the missing regkey in our transform (method 2)
http://support.microsoft.com/?scid=kb;en-us;914830&spid=2488&sid=50
Thanks for your interest Nick appreciated.
Cheers
/håkan
This article describes problem and alternative solutions.
Our solution was to simply add the missing regkey in our transform (method 2)
http://support.microsoft.com/?scid=kb;en-us;914830&spid=2488&sid=50
Thanks for your interest Nick appreciated.
Cheers
/håkan
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.