If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Application error OSE00000.exe when upgrading Office 2003 to 2007
I'm testing upgrading our managed Office 2003 installations to Office 2007
Enterprise on Windows XP via Group policy and i keep getting this error after it removes Office2003 and then in the middle of installing Office 2007: OSE00000.exe - Application Error The instruction at "0x7c9114b6" referenced at "0x00162155" The memory could not be "written"' I've gotten this on the 2 computers i'm testing with so far. Has anyone seen this before? Thanks! |
#2
|
|||
|
|||
Application error OSE00000.exe when upgrading Office 2003 to 2007
anyone?
"tkmlee" wrote: I'm testing upgrading our managed Office 2003 installations to Office 2007 Enterprise on Windows XP via Group policy and i keep getting this error after it removes Office2003 and then in the middle of installing Office 2007: OSE00000.exe - Application Error The instruction at "0x7c9114b6" referenced at "0x00162155" The memory could not be "written"' I've gotten this on the 2 computers i'm testing with so far. Has anyone seen this before? Thanks! |
#3
|
|||
|
|||
Application error OSE00000.exe when upgrading Office 2003 to 2
I think i'm slowing narrowing this down... So far what it looks like is when
office 2003 is removed via group policy before office 2007 is installed, it drops that ose00000.exe in the windows\temp directory. then when office 2007 is installing, it uses that ose00000.exe which is from office 2003. i haven't figured out a way to remove it yet as its locked when its removing office 2003, then there is only a very short time before office 2007 starts installing and locks it again. "Brian" wrote: I've received this same error on a few machines myself but haven't figured it out yet. It seems to only be happening on user's machines that have Administrative rights. We are also not "upgrading" but pushing both versions (03 and 07) out to every machine and removing the previous package of 2003 that included Outlook 2003. We did this because letting 2007 install over Outlook 2003 caused major issues and eventually ended up crashing Outlook 2007 all-together. If you figure this one out, though, let me know. "tkmlee" wrote: anyone? "tkmlee" wrote: I'm testing upgrading our managed Office 2003 installations to Office 2007 Enterprise on Windows XP via Group policy and i keep getting this error after it removes Office2003 and then in the middle of installing Office 2007: OSE00000.exe - Application Error The instruction at "0x7c9114b6" referenced at "0x00162155" The memory could not be "written"' I've gotten this on the 2 computers i'm testing with so far. Has anyone seen this before? Thanks! |
#4
|
|||
|
|||
Application error OSE00000.exe when upgrading Office 2003 to 2
I've received this same error on a few machines myself but haven't figured it
out yet. It seems to only be happening on user's machines that have Administrative rights. We are also not "upgrading" but pushing both versions (03 and 07) out to every machine and removing the previous package of 2003 that included Outlook 2003. We did this because letting 2007 install over Outlook 2003 caused major issues and eventually ended up crashing Outlook 2007 all-together. If you figure this one out, though, let me know. "tkmlee" wrote: anyone? "tkmlee" wrote: I'm testing upgrading our managed Office 2003 installations to Office 2007 Enterprise on Windows XP via Group policy and i keep getting this error after it removes Office2003 and then in the middle of installing Office 2007: OSE00000.exe - Application Error The instruction at "0x7c9114b6" referenced at "0x00162155" The memory could not be "written"' I've gotten this on the 2 computers i'm testing with so far. Has anyone seen this before? Thanks! |
#5
|
|||
|
|||
Application error OSE00000.exe when upgrading Office 2003 to 2
have you tried creating a custom action script and executing that after a
successful removal of Office 2003? I don't know which package development technique you use but we use AdminStudio here and you can embed custom actions into an msi or mst and then execute them at given times or events. I might give this a try later today to see if it works. I'll let ya know. "tkmlee" wrote: I think i'm slowing narrowing this down... So far what it looks like is when office 2003 is removed via group policy before office 2007 is installed, it drops that ose00000.exe in the windows\temp directory. then when office 2007 is installing, it uses that ose00000.exe which is from office 2003. i haven't figured out a way to remove it yet as its locked when its removing office 2003, then there is only a very short time before office 2007 starts installing and locks it again. "Brian" wrote: I've received this same error on a few machines myself but haven't figured it out yet. It seems to only be happening on user's machines that have Administrative rights. We are also not "upgrading" but pushing both versions (03 and 07) out to every machine and removing the previous package of 2003 that included Outlook 2003. We did this because letting 2007 install over Outlook 2003 caused major issues and eventually ended up crashing Outlook 2007 all-together. If you figure this one out, though, let me know. "tkmlee" wrote: anyone? "tkmlee" wrote: I'm testing upgrading our managed Office 2003 installations to Office 2007 Enterprise on Windows XP via Group policy and i keep getting this error after it removes Office2003 and then in the middle of installing Office 2007: OSE00000.exe - Application Error The instruction at "0x7c9114b6" referenced at "0x00162155" The memory could not be "written"' I've gotten this on the 2 computers i'm testing with so far. Has anyone seen this before? Thanks! |
#6
|
|||
|
|||
Application error OSE00000.exe when upgrading Office 2003 to 2007
simply renaming/deleting the C:\Program Files\Common Files\Microsoft Shared\Source Engine\ose.exe before running the install fixes this issue. so maybe you can just script that somehow -- cooperx ------------------------------------------------------------------------ cooperx's Profile: http://forums.techarena.in/members/109793.htm View this thread: http://forums.techarena.in/office-setup/669274.htm http://forums.techarena.in |
Thread Tools | |
Display Modes | |
|
|