Archive for January 2009

Outlook 2007 Crashes Using the Scheduling Assistant

January 30, 2009

My friend and I just got bit by the Microsoft .NET Framework 3.5 Service Pack 1 and .NET 3.5 Family Update (KB951847) x64 patch. It was applied to our Exchange 2007 server last night and then Outlook 2007 crashed everytime someone used the Scheduling Assistant. There is a private hotfix (http://support.microsoft.com/kb/958934) from Microsoft which fixes this issue.

Microsoft Word 2007 Locks Up When Exiting

January 29, 2009

Well, my boss is at it again! Microsoft Word 2007 locks up when he clicks the ‘X’ button in the upper right-hand corner of the application. Finally resolved it by running a repair on Microsoft Office. On Windows XP, open Control Panel and Add/Remove Programs (Program and Features in Vista). Click Microsoft Office and click Change. When prompted by the Microsoft Office setup wizard for a choice select Repair and continue.

Paper Jam when Printing from Outlook

January 29, 2009

So, everytime my boss printed from Outlook 2007 to his HP DeskJet 4160 it would start to process the print job and then report a paper jam. It would print from other Microsoft Office applications. The long and short of it is somehow (probably my boss’ fault) the paper type and paper size settings in the Page Setup | Memo Style of Outlook 2007 was changed to Custom. Changing this back to letter resolved the issue.

Windows 7 64-Bit Beta Running on VMware Fusion

January 22, 2009

Well, I couldn’t get the BSODs resolved with the 32-bit Windows 7 running on VMware Workstation 6.5.1. So, I decided to switch to the Mac and install the 64-bit version of Windows 7 on VMware Fusion. This was successful.

Windows 7: BSOD Stop Error 0x0000008E

January 21, 2009

My friend, John (Twitter and Blog), inspired me to install the beta version of Windows 7. So, I decided to install on VMware Workstation 6.5.1 on my HP Pavilion Windows Vista laptop running Windows Vista Ultimate SP1. I managed to get my first BSOD on Windows 7 during the installation. In particular, during the ‘expanding files’ process. The possible causes for this BSOD Stop Error are insufficient hard drive space, memory problems, video driver issue and/or other device driver problems.

win7beta-bsod1

The problem I encountered was caused by a ‘phantom’ monitor. I normally use my laptop with an external monitor. However, in this case, I attempted the install with the external monitor disconnected. Although I was able to get VMware Workstation to display on the laptop monitor, it thought the other monitor was there. I attempted to change the Display setting for the VM in VMware Workstation from ‘Auto Detect’ to ‘Specify monitor settings: Number of monitors: 1’ but this also resulted in the same BSOD.

I thought the resolution for me was to plug in the second monitor and continue the installation. This allowed the installation to complete but now I’m having more BSODs. 😦 More to come…

Microsoft Tag

January 18, 2009

Get the Microsoft Tag reader software for Windows Mobile at http://www.microsoft.com/tag or checkout the AppStore to download for iPhone. Check out the text embedded in the tag below:

barcode-1

It should open the text in your Smartphone’s text editor/viewer. Also, check out this cool site for more information: http://www.istartedsomething.com/.

“Unable to install or run the application. The application requires that the assembly be installed in the Global Assembly Cache (GAC) first.”

January 2, 2009

I recevied this error while compiling my first C# production application. I had to do the following in Visual Studio for the project:

  1. In Solution Explorer, expand the References node and click the assembly listed in the error. Ensure Copy Local in the Properties grid is set to ‘True’.
  2. In the properties of the project, Publish | Application Files Tab, ensure the Publish Status for the assembly listed in the error is set to ‘Include’