Office 2008 shows errors in system.log

[netnothing]

I'm on 10.5.1 and I just installed Office 2008. I, as well as others, have noticed that Office 2008 apps are spewing error message to the system.log.

I don't have to do anything, other than just open an app.

Here are some examples:

Jan 28 15:49:57 computername Microsoft Excel[35241]: CGBitmapContextGetData: invalid context
Jan 28 15:49:58: --- last message repeated 29 times ---
Jan 28 15:49:58 computername Microsoft Word[35225]: CGBitmapContextGetData: invalid context
Jan 28 15:49:59: --- last message repeated 14 times ---
Jan 28 15:49:59 computername Microsoft Excel[35241]: CGBitmapContextGetData: invalid context
Jan 28 15:50:22: --- last message repeated 49 times ---
Jan 28 15:50:22 computername Microsoft Word[35225]: CGBitmapContextGetData: invalid context
Jan 28 15:50:30: --- last message repeated 100 times ---
Jan 28 15:50:30 computername Microsoft Excel[35241]: CGBitmapContextGetData: invalid context
Jan 28 15:51:00: --- last message repeated 189 times ---
Jan 28 15:51:00 computername Microsoft Excel[35241]: CGBitmapContextGetData: invalid context
Jan 28 15:51:14: --- last message repeated 59 times ---
Jan 28 15:51:14 computername Microsoft Word[35252]: CGBitmapContextGetData: invalid context
Jan 28 15:51:44: --- last message repeated 324 times ---

I think this need to be addresses as this many error messages are going to bloat the system.log.

-k

 

[William Smith]

I'm on 10.5.1 and I just installed Office 2008. I, as well as others,
have noticed that Office 2008 apps are spewing error message to the
system.log.

I don't have to do anything, other than just open an app.

Here are some examples:

Jan 28 15:49:57 computername Microsoft Excel[35241]:
CGBitmapContextGetData: invalid context
Jan 28 15:49:58: --- last message repeated 29 times ---
Jan 28 15:49:58 computername Microsoft Word[35225]:
CGBitmapContextGetData: invalid context

You'll actually find that in the logs of many non-Microsoft Office
applications as well. Unless you're running critically low on disk
space, which is a more major issue than this one, don't worry about the
amount of information being spewed to the log files. Mac OS X rotates
and deletes log files on daily, weekly and monthly cycles. If you
shutdown your Mac overnight then you may want to adjust the rotation
schedules or use a utility like Cocktail to manually rotate them.

Hope this helps!

--

bill

William M. Smith, Microsoft Interop MVP - Mac/Windows
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>

 

[netnothing]

The problem isn't with diskspace, it's with the new way Leopard handles logs.

Everything is stored in the asl.db database. The issue with that is that if the asl.db gets too large, Console.app has a problem displaying the log files. It's a display problem in Leopard. I've had Adobe installers fill the logs and have Console.app have problems.

While this is more a Leopard bug, I'm hoping that MS can fix this.

I have received confirmation from a MacBU member that they are aware of the issue and it stems from a change in Leopard.

-Kevin

 

[nKhester]

The problem isn't with diskspace, it's with the new way Leopard handles logs.<br>
<br>
Everything is stored in the asl.db database. The issue with that is that if the asl.db gets too large, Console.app has a problem displaying the log files. It's a display problem in Leopard. I've had Adobe installers fill the logs and have Console.app have problems.<br>
<br>
While this is more a Leopard bug, I'm hoping that MS can fix this.<br>
<br>
I have received confirmation from a MacBU member that they are aware of the issue and it stems from a change in Leopard.<br>
<br>
-Kevin

I am experiencing the same problem... all I have to do is just open Word
2008 and the system log is immediately populated with repeated instances of
this message:

2/5/08 11:44:56 AM Microsoft Word[618] CGBitmapContextGetData: invalid
context

Before I found this discussion thread, I went through all of the "trouble
shooting" provided by MS --- and ultimately (still following MS advice) I
uninstalled/re-installed MS Office 2008.

The problem continues to persist!

Please, Apple/Microsoft, get this "glitch" fixed!