"Open XML Converter...1.1.3" -- keeps showing up in MAU? Microsoft Office for Mac |
- "Open XML Converter...1.1.3" -- keeps showing up in MAU?
- New Microsoft Office crashes / will not launch
- how to recover the file which was not saved?
- replicating birthdays from contacts to calendar
- Russian language
- Document Connection - Office Live Workspace
- Open XML File Converter - Snow Leopard compatibility
- Upgrade office mac
- Running both Office 04 and Office 08
- Font Size Problem
- Hotmail
- Suddenly cannot create or print envelopes
| "Open XML Converter...1.1.3" -- keeps showing up in MAU? Posted: 10 Nov 2009 10:57 AM PST In article <1j8z41b.g6pfhvpun2qN%mvps.org>, Corentin Cras-Méneur <mvps.org> wrote: Not as yet. I'm compiling something that will need to run overnight. I can try that in the a.m. However another user here showed me the same thing on his Mac. I think whoever got the first XML update installed when it appeared in MAU is probably in this same predicament. The fact that *manually* running the XML 1.1.3 updater changes permissions on the folder, though, sounds like the bug regardless -- if you never had the XML update installed, everything is owned by "root". Otherwise, if you did, it's owned by the admin account used to install this. - Steve |
| New Microsoft Office crashes / will not launch Posted: 04 Nov 2009 11:15 PM PST Version: 2008 Operating System: Mac OS X 10.6 (Snow Leopard) Processor: Intel I get send into this loop of Microsoft Error Reporting. "Microsoft Word has encountered a problem and needs to close." I click send report and the box pops up over again. i'm not sure why word won't start up. The same happens for excel and powerpoint. When i log onto the guest account on my computer, word works fine. This is what the error report shows: Microsoft Error Reporting log version: 2.0 Error Signature: Exception: EXC_BAD_ACCESS Date/Time: 2009-11-04 23:12:45 -0800 Application Name: Microsoft Word Application Bundle ID: com.microsoft.Word Application Signature: MSWD Application Version: 12.2.0.090605 Crashed Module Name: MicrosoftOLE Crashed Module Version: unknown Crashed Module Offset: 0x000076a6 Blame Module Name: MicrosoftOLE Blame Module Version: unknown Blame Module Offset: 0x000076a6 Application LCID: 1033 Extra app info: Reg=en Loc=0x0409 Thread 0 crashed: # 1 0x019a96a6 in _RegInitialize + 0x000008CE (MicrosoftOLE + 0x000076a6) # 2 0x019a98e6 in _RegInitialize + 0x00000B0E (MicrosoftOLE + 0x000078e6) # 3 0x019a8010 in _RegFlush + 0x00000506 (MicrosoftOLE + 0x00006010) # 4 0x019a8daf in _RegOpenKey + 0x00000045 (MicrosoftOLE + 0x00006daf) # 5 0x01a9a2d3 in _IsolateFilename + 0x00000095 (MicrosoftOLEAutomation + 0x0003e2d3) # 6 0x01a9c585 in _LoadRegTypeLibOfSzGuid + 0x00000057 (MicrosoftOLEAutomation + 0x00040585) # 7 0x01a9c9c8 in _LoadRegTypeLib + 0x000000CE (MicrosoftOLEAutomation + 0x000409c8) # 8 0x041f78bc in _ChartInitialize + 0x00000078 (MicrosoftChartPlugin + 0x001c18bc) # 9 0x01715196 in _McpGetIMcpCtrlFromControl + 0x00000520 (MicrosoftComponentPlugin + 0x0012e196) # 10 0x017153e9 in _McpGetIMcpCtrlFromControl + 0x00000773 (MicrosoftComponentPlugin + 0x0012e3e9) # 11 0x0065a502 in _wdCommandDispatch + 0x003362CE (Microsoft Word + 0x00659502) # 12 0x00adfecc in _wdGetApplicationObject + 0x003A17C6 (Microsoft Word + 0x00adeecc) # 13 0x00002902 in __mh_execute_header + 0x00001902 (Microsoft Word + 0x00001902) # 14 0x00002829 in __mh_execute_header + 0x00001829 (Microsoft Word + 0x00001829) X86 Thread State: eax: 0x00000000 ebx: 0x019a962a ecx: 0xa0a11fa4 edx:0x04b3d930 edi: 0x00000001 esi: 0x04b3d93c ebp: 0xbffff358 esp:0xbffff320 ss: 0x0000001f eip: 0x019a96a6 cs: 0x00000017 ds:0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 eflags:0x00010213 Thread 1: # 1 0x97d6b10a in __dispatch_hw_config + 0x97BAE182 (libSystem.B.dylib + 0x0002710a) # 2 0x97d6ace1 in __dispatch_hw_config + 0x97BADD59 (libSystem.B.dylib + 0x00026ce1) # 3 0x97d6aa86 in __dispatch_hw_config + 0x97BADAFE (libSystem.B.dylib + 0x00026a86) # 4 0x97d6a511 in __dispatch_hw_config + 0x97BAD589 (libSystem.B.dylib + 0x00026511) # 5 0x97d6a356 in __dispatch_hw_config + 0x97BAD3CE (libSystem.B.dylib + 0x00026356) X86 Thread State: eax: 0x0000016b ebx: 0x97d6b75e ecx: 0xb0080d5c edx:0x97d6b10a edi: 0xa09cd1ac esi: 0xb0080ed8 ebp: 0xb0080ef8 esp:0xb0080d5c ss: 0x0000001f eip: 0x97d6b10a cs: 0x00000007 ds:0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000246 Thread 2: # 1 0x97d6a1a2 in __dispatch_hw_config + 0x97BAD21A (libSystem.B.dylib + 0x000261a2) # 2 0x97d6a356 in __dispatch_hw_config + 0x97BAD3CE (libSystem.B.dylib + 0x00026356) X86 Thread State: eax: 0x00100170 ebx: 0x97d6a399 ecx: 0xb0102f6c edx:0x97d6a1a2 edi: 0x05013750 esi: 0xb0103000 ebp: 0xb0102fc8 esp:0xb0102f6c ss: 0x0000001f eip: 0x97d6a1a2 cs: 0x00000007 ds:0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037 eflags:0x00000286 Thread 3: # 1 0x97d44a0e in __dispatch_hw_config + 0x97B87A86 (libSystem.B.dylib + 0x00000a0e) # 2 0x97de5344 in __dispatch_hw_config + 0x97C283BC (libSystem.B.dylib + 0x000a1344) # 3 0x01b27d7d in _MerpCreateSession + 0x00000B07 (merp + 0x00002d7d) # 4 0x01b273e5 in _MerpCreateSession + 0x0000016F (merp + 0x000023e5) |
| how to recover the file which was not saved? Posted: 04 Nov 2009 05:37 PM PST If the file was never saved to disk there is nothing to recover. Time Machine doesn't store what existed only in RAM, nor does even the best file recovery software & AutoRecover not only doesn't begin to kick in until you save at least once but only retains temp files in the event of a critical failure. I'm afraid you're out of luck. Regards |:>) Bob Jones [MVP] Office:Mac On 11/4/09 8:37 PM, in article caR9absDaxw, "com" <com> wrote: |
| replicating birthdays from contacts to calendar Posted: 03 Nov 2009 08:15 PM PST Sorry, it's not possible. Tip: the next time you have problems with events, export calendar events as ..rge file and select to delete after exporting. You can try importing the file to see if the corruption was cleared in the export/import process. -- Diane |
| Posted: 03 Nov 2009 07:53 AM PST Bob Greenblatt <com> wrote: It's not. There used to be a workaround using custom dictionaries, but for some reason I can't understand, we can't in Office 2008 anymore. FYI, you can install (free) Russian spelling support for MacOS X allowing you to spell-check in any application using the MacOS X spelling support. That includes TextEdit (which can open Word files...) -- --- Office:Mac MVP http://www.cortig.net/wordpress/ --- http://www.mvps.org - http://mvp.support.microsoft.com MVPs are not MS employees - Les MVP ne travaillent pas pour MS Remove "NoSpam" to e-mail me - Retirez "NoSpam" pour m'écrire |
| Document Connection - Office Live Workspace Posted: 02 Nov 2009 05:26 PM PST Well, whatever the problem was, it was fixed with the 12.2.3 update. Thanks Microsoft! |
| Open XML File Converter - Snow Leopard compatibility Posted: 02 Nov 2009 02:33 PM PST Thanks Diane, nuked all caches and removed duplicate fonts but still getting the error. |
| Posted: 02 Nov 2009 09:48 AM PST On 11/4/09 8:10 AM, in article com, "Howard Brazee" <net> wrote: Can you expand on this? I'm not sure I understand your question. See if this links helps: <http://www.entourage.mvps.org/version/license_version.html#upgrade_update> or <http://tinyurl.com/ydar74m> -- Diane |
| Running both Office 04 and Office 08 Posted: 02 Nov 2009 08:23 AM PST Brilliant, thanks for your help. Becky |
| Posted: 02 Nov 2009 05:49 AM PST I used an HP Scanjet G3010 with HP Scanpro 7.4.5 (software up to date) to scan into Mac Office 2008 12.2.0 (090605) Latest update 12.2.1 which uses I.R.I.S. OCR. Scan is to rtf. After removing extraneous stuff (text had handwritting on it - an old edited manuscript) there are two size texts. Usually several sentences of the smaller size. Word says both sizes are 12 pt but of course they can't be. When I highlight everything and change fonts the problem exists. When I change font sizes the problem exists. I am assuming that the larger looking type is the correct size because that is the font size I use to begin retyping. I can copy the entire thing to Textedit and then back and that fixes the problem (I discovered this after my original posts) but don't understand why Word has the original problem. Hope that I have enough information this time. Sorry about that. |
| Posted: 01 Nov 2009 09:11 AM PST This is a good alternative to get Windows Live Hotmail IMAP support on your MAC http://fluentfactory.com/mboxmail-for-mac/ "AML Global" wrote: |
| Suddenly cannot create or print envelopes Posted: 28 Oct 2009 03:08 PM PDT On Oct 28, 4:08*pm, com wrote: My first question actually is whether or not envelopes worked before? I would also want to know whether you modified the envelope orientation making it impossible to print. DId you modify the envelope orientation at the printer level (using the printer driver)? If you have another user in the household have them try printing envelopes to the same printer from Word on their machine (Mac or PC). If this is indeed a document problem - i. e. the envelope document is bad in some way then you should be able to solve the problem simply by creating a new envelope document. Good luck, dfwenigma |
| You are subscribed to email updates from TextNData Forums - Microsoft Office for Mac To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google Inc., 20 West Kinzie, Chicago IL USA 60610 | |
