Feb 17 2014

Microsoft Office programs (Excel, Word, Outlook, PowerPoint) closes directly when starting

Hi and welcome back!
I just found out that I haven’t posted a new blog for over year by now…. busy, busy…. ;-)

So without further ado, a new blog post!

 

Recently there was an issue with Microsoft Office 2010 on one of the Windows Server 2008 R2 SP1 Remote Desktop servers I manage.

When starting a Microsoft Office 2010 application (Word, Excel, Outlook, PowerPoint) it would immediately close after showing the splash screen (a blank document can be seen in a split second).
This happened with a normal user account as well as with an Administrator account.

As an avid Internet searcher, I found different kind of suggestions:

  • Start Office without add-ins
    Starting Office in safe mode, thus starting without loading the add-ins, did not resolve the issue. Word, Excel etc. still closed directly after opening.
  • Others suggested to reset the Office registry entries in the user/machine profile.
    Didn’t like that solution.
  • Some advised to reinstall or repair the Office installation.
    Didn’t like that solution either.

So it was time to investigate the cause of this issue by myself.

I started by looking in the eventlogs.
In the Application Eventlog I found the following similar and multiple entries after each other of the following event:

Log Name: Application
Source: Office Software Protection Platform Service
Date: 21-1-2014 10:04:57
Event ID: 1003
Task Category: None
Level: Information
Keywords:
Classic User: N/A
Computer: server.mydomain.local
Description: The Software Protection service has completed licensing status check.
Application Id=59a52881-a989-479d-af46-f275c6370663
Licensing Status= 1: 11b39439-6b93-4642-9570-f2eb81be2238, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
2: 1f76e346-e0be-49bc-9954-70ec53a4fcfe, 1, 1 [(0 [0xC004E002, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 [0x8007000E, 0, 0], [(?)(?)(?)(?)(?)(?)])(2 )]
3: 36756cb8-8e69-4d11-9522-68899507cd6a, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
4: 5980cf2b-e460-48af-921e-0c2a79025d23, 1, 1 [(0 [0x00000000, 1, 0], [(?)(?)( 1 0x00000000 30 0 msft:rm/algorithm/hwid/4.0 0x00000000 0)(?)(?)(?)])(1 )(2 )]
5: 5dc7bf61-5ec9-4996-9ccb-df806a2d0efe, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
6: 92236105-bb67-494f-94c7-7f7a607929bd, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )] 
7: 9da2a678-fb6b-4e67-ab84-60dd6a9c819a, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
8: 9ed833ff-4f92-4f36-b370-8683a4f13275, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
9: b6e9fae1-1a0e-4c61-99d0-4af068915378, 1, 1 [(0 [0x00000000, 1, 0], [(?)(?)( 1 0x00000000 30 0 msft:rm/algorithm/hwid/4.0 0x00000000 0)(?)(?)(?)])(1 )(2 )]
10: cab3a4c4-f31a-4c12-afa9-a0eecc86bd95, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )] 
11: dd457678-5c3e-48e4-bc67-a89b7a3e3b44, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
12: e558389c-83c3-4b29-adfe-5e4d7f46c358, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]

 

Well that’s odd. I see this event ID regularly, but not multiple entries after each other. 

So my tentative conclusion was that this issue was caused by a license issue.

After some more reading about the Office Software Protection Platform service (osppsvc) I did the following:

Related files for this tool can be found in %ProgramData%\Microsoft\Office Software Protection

Typically %ProgramData% points to C:\ProgramData or for Windows XP/2003 to the ALLUSERSPROFILE in C:\Documents and Settings\All Users\Application Data.

In the folder C:\ProgramData\Microsoft\OfficeSoftwareProtectionPlatform\Cache I found a file called cache.dat.

Well, let’s see what will happen if I rename this cache.dat file to cache.old.
After renaming this file, the Office programs still closed immediately after starting…
Hmm, maybe I should restart the Office Software Protection Platform service (or restart Windows) as well!

After restarting this service, I started an Office program and it stayed open!

No need to reinstall Microsoft Office 2010 or investigating add-in issues

When you look in %ProgramData%\Microsoft\Office Software Protection, you will notice that a new cache.dat file has been created.

So my first conclusion seems to be correct.

 

Hope you liked this post and that this is the solution for your problem as well!

 

Jan 28 2013

Redirected printing doesn’t work anymore on a Windows Server 2008 R2 RDS server

m4s0n501

 

Out of the blue some users reported that redirected printing didn’t work anymore on a Windows Server 2008 R2 RDS farm.
Upon further investigation the problem only occurred on one specific Remote Desktop Services server in the farm.

 

The local printer was still being redirected to their Remote Desktop session. This was the case with both the Easy printer driver as well as a native printer driver (if available).
The print job appeared in the print queue of the redirected printer in the remote desktop session, but was not transferred to the local printer queue of the user’s computer.

 

Restarting the spooler services, removing all of the (3rd-party) print drivers and rebooting the RDS server didn’t solve the issue.

 

After much trouble-shooting and searching on the Internet I found out it was caused by inactive TS ports.
Every time that an Remote Desktop session is created, the Remote Desktop Device Redirector service creates a new port.
However inactive ports are not removed.

 

A list of currently active and inactive TS ports can be found under the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\##?#Root#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}

Each TS port is represented as a subkey like #TS001; #TS002; #TS003 etc. In some cases it can be up to #TS1000 or more.

 

Microsoft has confirmed that this is a bug and have released a hotfix for it.

Long logon time when you establish an RD session to a Windows Server 2008 R2-based RD Session Host server if Printer Redirection is enabled.

This article also describes under which scenario this issue will likely occur.

The hotfix can be downloaded by clicking the next link: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2655998&kbln=en-us
After installing this hotfix inactive TS ports will no longer be accumulated.

 

However after installing this hotfix you will notice that the problem hasn’t been solved… yet.

The inactive TS ports under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\##?#Root#RDPBUS#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}
must be removed.

 

This can be tedious task in some cases to do manually because hundreds of TS ports exist, both active and inactive.
Every registry key must be checked for the Port Description value. If it equals Inactive TS Port, it can be removed.

Therefore Microsoft has released a fix it tool to automatically cleanup the inactive TS ports only, download it by clicking the following link:

Fix It tool for Inactive TS Port cleanup (Microsoft Fix it 50833)

After performing this cleanup (and installing the hotfix) reboot the server and redirected printing will work again.

 

Older posts «