Patch problem Access 2003 (SP2)

microsoft.public.access.security

24 Aug 2006 6:31 AM

Johan L

Hi!

We use Active Directory to publish our applications to users.
I "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~

8 Sep 2006 7:12 AM

Peter Yang [MSFT]

Hello Johan,

I understand that you cannot publish patch of access properly via group
policy but it works fine if you run the command manually. If this is not
correct, please let me know.

To understand the issue better, I'd like to know ifyou also deploy Office
XP/Access via group policy? Also, does the issue only occurs Access update?
Does the issue occurs for owc update or office update?

Based on my knowledge, you can use group policy to deploy updates/fixes of
Office only if it was deployed by Office in the first place. You can
redeploy a package only if it is being managed by Group Policy — that is,
only if you originally installed it by using IntelliMirror software
installation and maintenance or if you brought it into a managed state
under Windows 2000. Please see "To deploy a QFE fix or service release"
part of the following link

http://office.microsoft.com/en-us/assistance/HA011363201033.aspx

More related information:

304953 How to deploy Office XP over a network
http://support.microsoft.com/default.aspx?scid=kb;EN-US;304953

BTW, this issue seems to be an Office setup issue other than an Access
problem, and you also want to post in microsoft.public.office.setup
newsgroup so you may get more qualified answers there.

If you have any questions or concerns, please feel free to let's know.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

8 Sep 2006 8:19 AM

Hakan Forslund

This is a recognized and validated problem by Microsoft.

http://support.microsoft.com/?scid=kb;en-us;914830&spid=2488&sid=50

I quote Microsoft: "This problem can occur if you use Group Policy to
install Office 2003 SP2 on a per-user basis."

Our solution was to add the failing regkey in our Transform

Cheers

/HÃ¥kan

Show quoteHide quote

"Peter Yang [MSFT]" wrote:

> Hello Johan,
>
> I understand that you cannot publish patch of access properly via group
> policy but it works fine if you run the command manually. If this is not
> correct, please let me know.
>
> To understand the issue better, I'd like to know ifyou also deploy Office
> XP/Access via group policy? Also, does the issue only occurs Access update?
> Does the issue occurs for owc update or office update?
>
> Based on my knowledge, you can use group policy to deploy updates/fixes of
> Office only if it was deployed by Office in the first place. You can
> redeploy a package only if it is being managed by Group Policy â€” that is,
> only if you originally installed it by using IntelliMirror software
> installation and maintenance or if you brought it into a managed state
> under Windows 2000. Please see "To deploy a QFE fix or service release"
> part of the following link
>
> http://office.microsoft.com/en-us/assistance/HA011363201033.aspx
>
> More related information:
>
> 304953 How to deploy Office XP over a network
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;304953
>
> BTW, this issue seems to be an Office setup issue other than an Access
> problem, and you also want to post in microsoft.public.office.setup
> newsgroup so you may get more qualified answers there.
>
> If you have any questions or concerns, please feel free to let's know.
>
> Best Regards,
>
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>