Windows Server - OSE.exe Causes Problem on Upgrade to Office 2007 in GPO

Asked By baboo

24-Jan-07 03:21 PM

Hi -

I am testing the deployment of Office 2007 Enterprise to upgrade Office 2003
Enterprise, using a GPO for each package.
The test OU contains 3 XP machines and 1 Vista.  I successfully deployed the
Office 2003 package on all machines.  I created a package for Office 2007 and
set the Upgrade to replace the Office 2003 package.

On the Vista machine the upgrade is 100% successful.  (By the way, I was
kind of intrigued by the fact that Vista allows the user to log on while the
application is still being installed via the GPO.  You gradually see
shortcuts appear and eventually you stop getting error messages when you
click on the shortcuts, once the install completes.)

On the XP machines I am not having success -
When the machine boots, it says that it is uninstalling Office 2003, as it
should.  When that is finished it says that it is installing Office 2007, but
once I log on I find that it hasn't installed.  In fact Office 2003 is still
there.  In the Application Event Log there are failure entries for the
install, but I believe the most pertinent one is this:
Source: MsiInstaller, Event ID: 1025, "Product: Microsoft Office Enterprise
2007.  The file C:\.....\OSE.exe is being held in use by the following
process Name:OSE, ID 1476".  I know that this is the Office Source Engine,
but I have no idea why the XP machines won't give it up.

Thanks for any help on this.

25-Jan-07 01:03 AM

Hi,

Based on my research, this issue occurs if one of the following conditions
is true:

o The Microsoft Office Source Engine (Ose.exe) is disabled.
o The Ose.exe file is corrupted.

To resolve this issue, please refer to the following methods.

Method 1: Determine the status of the Office Source Engine service
======================================================
To determine the status of the Office Source Engine service, follow these
steps:

1. Click Start, click Run, type services.msc, and then click OK.
2. In the list of services, double-click Office Source Engine.
3. View the Startup type list.
4. If the startup type is set to Disabled, change the startup type to
Manual. To do this, click Manual in the Startup type list, and then click
OK.
5. Try to install the Office update again.

Method 2: Repair the Ose.exe file
==========================
To repair the Ose.exe file, copy the Ose.exe file from the Office 2003 CD.
To do this, follow these steps:

1. Determine where the Ose.exe file is located. By default, the Ose.exe
file is in the following location:
path:\Program Files\Common Files\Microsoft Shared\Source Engine\
2. Insert the Office 2003 CD in the CD drive.
3. Right-click Start, and then click Explore.
4. Use Microsoft Windows Explorer to locate the following folder on the
Office 2003 CD:
path:\Files\Setup
5. Right-click the Ose.exe file, and then click Copy.
6. Locate and then click to select the folder in which the Ose.exe file is
located on the computer. For example, locate and then click to select the
following folder:
path:\Program Files\Common Files\Microsoft Shared\Source Engine
7. Right-click the Source Engine folder, and then click Paste.
8. If you are prompted to replace an existing file, click Yes.

Hope this helps


Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
2003
the
and
the
it
but
still
Enterprise
Engine,

25-Jan-07 02:33 PM

Hi Vincent -

Thanks for the response.

I don't believe that this relates to my problem directly.  I have no problem
using Office 2003 on these machines.  I also have no trouble installing
Office Updates.
The problem is that I am trying to use group policy to upgrade Office 2003
to Office 2007 and that is when I get the error.  As I said, it happens on
all Windows XP machines that are getting the policy, but not on the Vista
machine that gets the policy.

If you still believe that the fix you mentioned might resolve the problem,
let me know and I will proceed.

Thanks much.

25-Jan-07 04:51 PM

Charlie,

I am having almost the exact same problem.  In fact i have been pulling
my hair out over this the last few days.  I have a few differences in
my experience.

1.  Says it is uninstalling Office 2003. (like you)
2.  Says it is installing Office 2007 (like you)
3.  Says "Applying managed software installation..."  (you did not
mention this, i discovered this is when it is reinstalling 2003)

When I login, only Office 2003 is installed.

Sometimes, I get a window asking me to submit an error report of
OSE0000.exe (Office Source Engine) crashing.

When I check the Application Log, i get the following events in the
order listed below.

What really worries me, is the fact that the TechNet article I was
using a few days ago to make sure I configured everything correctly has
been removed from the site
(http://technet2.microsoft.com/Office/en-us/library/efd0ee45-9605-42d3-9798-3b698fff3e081033.mspx).
You can still view it using google cache.

Hopefully we can figure something out.

Event Type:	Information
Event Source:	MsiInstaller
Event Category:	None
Event ID:	11724
Date:		1/25/2007
Time:		3:03:09 PM
User:		NT AUTHORITY\SYSTEM
Computer:	ALDENVIDEO
Description:
Product: Microsoft Office Professional Edition 2003 -- Removal
completed successfully.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type:	Information
Event Source:	Application Management
Event Category:	None
Event ID:	303
Date:		1/25/2007
Time:		10:08:10 AM
User:		NT AUTHORITY\SYSTEM
Computer:	ALDENVIDEO
Description:
The removal of the assignment of application Microsoft Office
Professional Edition 2003 from policy Microsoft Office 2007
Professional succeeded.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type:	Information
Event Source:	Application Management
Event Category:	None
Event ID:	301
Date:		1/25/2007
Time:		10:08:12 AM
User:		NT AUTHORITY\SYSTEM
Computer:	ALDENVIDEO
Description:
The assignment of application Microsoft Office Professional Plus 2007
from policy Microsoft Office 2007 Professional succeeded.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type:	Error
Event Source:	Application Error
Event Category:	(100)
Event ID:	1000
Date:		1/25/2007
Time:		10:09:48 AM
User:		N/A
Computer:	ALDENVIDEO
Description:
Faulting application ose00000.exe, version 11.0.5525.0, faulting module
NTDLL.DLL, version 5.1.2600.2180, fault address 0x000114b6.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type:	Information
Event Source:	DrWatson
Event Category:	None
Event ID:	4097
Date:		1/25/2007
Time:		10:09:48 AM
User:		N/A
Computer:	ALDENVIDEO
Description:
The application, C:\WINDOWS\TEMP\ose00000.exe, generated an application
error The error occurred on 01/25/2007 @ 10:09:48.488 The exception
generated was c0000005 at address 7C9114B6 (ntdll!wcsncpy)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type:	Information
Event Source:	MsiInstaller
Event Category:	None
Event ID:	1025
Date:		1/25/2007
Time:		10:10:01 AM
User:		NT AUTHORITY\SYSTEM
Computer:	ALDENVIDEO
Description:
Product: Microsoft Office Professional Plus 2007. The file C:\Program
Files\Common Files\Microsoft Shared\Source Engine\OSE.EXE is being held
in use by the following process Name: OSE , Id 3296.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type:	Error
Event Source:	Application Management
Event Category:	None
Event ID:	102
Date:		1/25/2007
Time:		10:10:01 AM
User:		NT AUTHORITY\SYSTEM
Computer:	ALDENVIDEO
Description:
The install of application Microsoft Office Professional Plus 2007 from
policy Microsoft Office 2007 Professional failed.  The error was :
Fatal error during installation.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type:	Information
Event Source:	Application Management
Event Category:	None
Event ID:	303
Date:		1/25/2007
Time:		10:10:02 AM
User:		NT AUTHORITY\SYSTEM
Computer:	ALDENVIDEO
Description:
The removal of the assignment of application Microsoft Office
Professional Plus 2007 from policy Microsoft Office 2007 Professional
succeeded.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type:	Error
Event Source:	Application Management
Event Category:	None
Event ID:	108
Date:		1/25/2007
Time:		10:10:02 AM
User:		NT AUTHORITY\SYSTEM
Computer:	ALDENVIDEO
Description:
Failed to apply changes to software installation settings.  Software
changes could not be applied.  A previous log entry with details should
exist.  The error was : Fatal error during installation.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

25-Jan-07 09:47 PM

Thanks for posting so I know I am not alone.

I just read the article you mentioned and I used that method when I set up
the package.  In fact, it's very simple.
If you look at the post in the Office.Setup Managed NG on 12/5/06 by
Jonathan Vella, he says that this method worked like a charm for him.  Also,
as I said, I tried this on a Vista machine with no trouble.  In fact, I tried
it on a couple of other Vista machines in a different environment about a
month ago, now that I think of it.

Yeah, you gotta wonder why they took down that article.  Would someone from
MS please let us know if this is a known problem?  I don't want to waste any
more time on it if that is the case.

08-Feb-07 05:18 AM

I have the same Problem

Application Microsoft Office Enterprise 2007 from policy Office 2007 test is
an upgrade of application Microsoft Office Professional Edition 2003 from
policy Office 2003 Test and will force application Microsoft Office
Professional Edition 2003 to be removed.

Product: Microsoft Office Professional Edition 2003 -- Removal completed
successfully.

The removal of the assignment of application Microsoft Office Professional
Edition 2003 from policy Office 2003 Test succeeded.

The assignment of application Microsoft Office Enterprise 2007 from policy
Office 2007 test succeeded.

The install of application Microsoft Office Enterprise 2007 from policy
Office 2007 test failed.  The error was : Fatal error during installation.

The removal of the assignment of application Microsoft Office Enterprise
2007 from policy Office 2007 test succeeded.

Application Microsoft Office Enterprise 2007 from policy Office 2007 test
was configured to upgrade application Microsoft Office Professional Edition
2003 from policy Office 2003 Test.  The assignment or  install of the upgrade
application Microsoft Office Enterprise 2007 from policy Office 2007 test
failed with error : Fatal error during installation.   The upgrade will be
aborted.

The assignment of application Microsoft Office Professional Edition 2003
from policy Office 2003 Test succeeded.

I to used the info from the office 2007 resource kit "use group policy
software installation to deploy the 2007 office system".

08-Feb-07 09:50 AM

I have worked out a fix. :)

The Office 2007 installer is not copying the new OSE.exe over to the local
system if you have Office 2003 previously installed.
Office 2007 cant install using OSE (Office Source Engine) version 11.*
What you need to do is copy the OSE.exe from your MSI DIR. (EG Enterprise.WW
or ProPlus.WW)
This File is version 12*
Copy this to “c:\Program Files\Common Files\Microsoft Shared\Source Engine\”
and over right the OSE.exe that is in that directory.
After this the install of Office 2007 over GPOs will work.

Oliver Knight

Nonsuch High School For Girls
UK

10-Feb-07 08:15 PM

Thanks much for pinning down the problem.

Now the issue is how to automate the copy during the upgrade.  If you have
to visit every machine to do this, then that kind of defeats the purpose of
using Group Policy Software Installation.  I suppose a startup or shutdown
script may work, but that seems a little convoluted.

I'm surprised that the system allowed you to overwrite the previous ose.exe,
since that seems to be what is preventing it from being replaced in the first
place.

Interesting to note:  From my experience this only happens on XP 32 bit.  I
have been successful with XP 64 bit and both 32 and 64 bit versions of Vista.

Thanks again.

23-Apr-08 09:36 AM

I have found the solution to automate the process. I have made a MSI,
which places the ose.exe from the 2007 DVD to the directory where the
previous ose from Office 2003 was stored (c:\program files\common
files\microsoft shared\source engine)

Then i created 2 custom actions for the windows\temp directory, one
which kills the process ose00000.exe and one which looks if the file is
present in c:\windows\temp and it is, it first is renamed and then
deleted. After this MSI install the install of Office 2007 will start
and install without any problem.

I don't know if the copy part is neccessary to the source engine dir,
but to be sure i keep doing this.

KEEP IN MIND:

The GPO that i have created must install before the MSI of 2007 is
started. So in the GPO order the new created GPO must have an higher
link order number than the GPO of Office 2007

The Custom Actions you must created must execute just befor "Install
Finalize" with a Condition NOT REMOVE~="ALL" and must run in the
Deferred Execution - System Context with the processing option
Synchronous. The Kill Proces Custom Action must be executed before the
delete custom action, so it must be above the delete custom action
Custom Action

The Kill Process contains the following information
------
strComputer = "."
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" & strComputer &
Set colProcessList = objWMIService.ExecQuery _
("Select * from Win32_Process Where Name = 'ose00000.exe'")
For Each objProcess in colProcessList
objProcess.Terminate()
Next
------


The Delete action contains the following information
------
Option Explicit

Dim objFSO

Set objFSO = CreateObject("Scripting.FileSystemObject")

If objFSO.FileExists("C:\windows\Temp\ose00000.exe") Then
objFSO.MoveFile "C:\windows\Temp\ose00000.exe" ,
objFSO.DeleteFile("C:\windows\Temp\rename.txt")
Else
End If
------


I have just tested it, and it works :D
Keep in mind that the first part of the Office 2007 installation not
the actually install is, but the copy of files to a cache folder. After
the login screen appears the installation will start. So if you have
User Msiexec processes running at logon or a MSI script which is
executed at logon it can corrupt the installation of Office 2007.


Message sent by erwinvos from mombu the microsoft forum http://www.mombu.com/microsoft/

------------------------------------------------------------------------
erwinvos's Profile: http://www.mombu.com/microsoft/member.php?u=4330
View this thread: http://www.mombu.com/microsoft/Windows-Group-Policy/t-OSE-exe-Causes-Problem-on-Upgrade-to-Office-2007-in-GPO-690025.html