Windows Mobile 6 / 6.1 Freezes or Hangs when Unlocking

I recently experienced an issue where my Motorola Q9c from Verizon was hanging up for 1 – 2 minutes when I would try to unlock the screen.  Normally, you press the unlock soft key and the screen will display a prompt to press the * key to complete the unlock process.  With the problem I experienced, it was hanging before showing me that prompt and my phone would be unusable for about 1 – 2 minutes.  After this happened, I checked my task manager and found the “Text Messages” process consuming a good chunk of resources.  I forced this to quit and my phone would be fine until I wrote another text messsage and that process respawned. 

After trying a few things, I found that this issues was actually caused by the text prediction feature and the size of the text prediction history cache.  If you are having the same problem, try turning this feature off, or at least clearing the history.  Here’s how:

  1. Select “Text Input Settings” from the main settings menu.
  2. To Disable this feature, clear the “Suggest words when typing” option
  3. To clear the history, access the menu by using the right soft key and select “Clear Input History”

 

Word or Excel File Opens Slowly When Double Clicked

I recently experienced a strange issue with a client where office documents from Word and Excel (.doc and .xls) would open very slowly when double clicked.  If you first opened the respective application and then selected the document from the open menu, it would open almost instantly.  After exhaustive research, I found the issue was related to the Dynamic Data Exchange (DDE) settings for those applications.  More on DDE can be found here.

The corrective action was to modify the “Application used to perform this action” string in the DDE settings.  Here it is step-by-step:

  1. Open folder options from within the control panel.
  2. Select the tab for file types.
  3. From the list, select the document extension you are having trouble with (.doc or .xls)
  4. Click the advanced button
  5. Append the string “%1” including the quotes to the end of the existing “Application used to perform this action” string.  If the existing string ends with a “/dde” remove that.
  6. Click OK and try again.

 

Event: 0 Source: BMDS in Application Event Log

A recent eventlog entry was occurring very often and seemed to occur after an update of the Java runtime.  The error reported was :

======================
Event Type: Error
Event Source: BMDS
Event Category: None
Event ID: 0
Description:
The description for Event ID ( 0 ) in Source ( BMDS ) cannot be found. The local computer may not have the necessary registry information…
======================

I found that the soution was to modify the path used for the Java runtime files to the most recent version.  The registy key is:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesBlackBerry MDS Connection ServiceImagePath

This contains a long string.  Its easiest to copy the string to notepad to work with it.  Locate the path to the java runtime files within the string (it will look something like this: “Program FilesJavajre1.5.0_07”) and replace it with the most current path.  Restart the Blackberry MDS service and you’re done.

Backup Exec isn’t flushing Exchange Transaction Logs

I recently came across a client’s backup that was completing successfully daily but not flushing the transaction logs for Exchange as it should.  In the job properties of Backup Exec, the Exchange section declares that it will perform a full backup and flush the comitted logs but it simply never happens.

After some research, Veritas article 280659 had the answer…and it was a simple one.  In the job properties, review the options under Advanced Open File and make sure the option “Process Logical Volumes for backup one at a time” is not checked.   As its explained in the article, if this is unchecked, Backup Exec will use a different open file option (VSS) for the Exchange logs to allow it to flush them afterwards. 

A required installation file SKU011.CAB could not be found.

I recently came across a PC that prompted me for the SKU011.CAB file everytime I ran an Office application.  The verions of Office it listed was Office Professional 2003 so I popped in my Office 2003 Pro CD and tried to use that to replace the file.  I was unable to find SKU011.CAB on the CD and after checking the CD Key in use discovered that Office 2003 Pro Enterprise was the actual version installed.  Not having an Enterprise CD, I thought I was stuck.

Then I found the Local Installation Source Tool from Microsoft and was saved.  I downloaded the tool and used the “Delete and disable LIS” option to remove the local installation source and after the next attempt to start and Office App I was off and running.

You can get the tool here:
http://www.microsoft.com/downloads/details.aspx?familyid=10fa7aa3-695b-42c3-9045-b812ba0fed3e&displaylang=en

 

Missing Tabs In Display Properties

Some spyware may create a desktop background to replace your own.  After doing this, I’ve seen the display properties tabs for modifying the screensaver and wallpaper disappear to prevent the user from getting rid of the malicious wallpaper.  To bring these tabs back, navigate to the following Registry string:

HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionPoliciesSystem

Here, you will find the keys responsible.  They are:

NoDispBackgroundPage
NoDispAppearancePage

These will likely be set to 1.  Set them to 0 or delete them to get your tabs back. 

How to Find the Product Version in Exchange 2007

To find the product version in Exchange 2007, execute the following command in PowerShell:

Get-ExchangeServer | fl name,edition,admindisplayversion

Refer to the article below to find out how the build number corresponds to a product version:

http://blog.kazmarek.com/2008/07/04/exchange-server-version-and-build-numbers/

Exchange Server Version and Build Numbers

This microsoft article details the various Exchange Server versions, including service packs.

http://support.microsoft.com/kb/158530

Some recent ones:

Microsoft Exchange Server  2003                       6.5.6944                             October 2003
Microsoft Exchange Server  2003 SP1                 6.5.7226                             May 2004
Microsoft Exchange Server  2003 SP2                 6.5.7638                             October 2005

Microsoft Exchange Server  2007                       8.0.685.24 or 8.0.685.25    December 2006
Microsoft Exchange Server  2007 SP1                 8.1.0240.006                      November 2007

Problems Connecting Outlook 2007 with Exchange 2003 using RPC/HTTPs Outlook Anywhere

I came across a situation where an organization had been setup to use RPC/HTTPs “Outlook Anywhere” for some time and all the Outlook 2003 clients seemed to work fine. One user had Outlook 2007 and was unable to connect using this method. In the LAN and through OWA everything worked fine. I tried tons of different solutions online but in the end, the problem was with the configuration in Exchange. I looked over the suggested configuration here:

http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htm

and I discovered that the RPC ports hadn’t been configured as the article suggests. I used the recommended “RPCnofrontend” tool: http://www.petri.co.il/software/rpcnofrontend.zip and everything worked fine after that.

Repairing Windows98 File Associations

The issue:
Unable to open a file directly on the desktop or in explorer using double-click or right-click->Open.

Quick fix:
For example, to repair Excel’s file extension (.xls) type the following in Start –> Run…
“C:Program FilesMicrosoft OfficeOfficeExcel.exe” /Regserver