COM+ and Communicator R2 2007...

[jasoncassity]

My company pushed out Communicator 2007 a few months ago. There were about
2,000 users and of all of them, about 10 users were unable to start
Communicator. It appears that the COM+ was corrupt and I was unable to get
into Component Services on those computers. It would either close as soon as
I tried expanding MyComputer in Component Services or it would throw an error.

The resolution that I found was to set the following services to logon
locally:
COM+ Event System, COM+ System Application, Remote Procedure Call (RPC), and
Remote Procedure Call (RPC) Locator. Then confirmed that they have no
dependencies other that what is required with was RPC for the 2 COM+
services, RPC had none and RPC Locator had 'Workstation'. Then I rebooted the
computer and reinstalled COM+ by going to Add\Remove Programs and running
through the Add/Remove Windows Components Wizard. Then Communicator would
work.

Today, I had a user call with the issue of Communicator not opening, so I
followed the previous steps and it still does not work. The error logs show
the following warning and since this warning appeared is when the problem
with Communicator started.

The CRM log file was originally created on a computer with a different name.
It has been updated with the name of the current computer. If this warning
appears when the computer name has been changed then no further action is
required. MLANDELL2
Server Application ID: {02D4B3F1-FD88-11D1-960D-00805FC79235}
Server Application Instance ID:
{D68C6917-F69D-4D78-B65B-A9192186246E}
Server Application Name: System Application
comsvcs.dll file version: ENU 2001.12.4414.258 shp

Any suggestions would be greatly appreciated...

[jim]

On Mon, 29 Jun 2009 07:04:02 -0700, JasonCassity
<JasonCassity@discussions.microsoft.com> wrote:

>
>My company pushed out Communicator 2007 a few months ago. There were about
>2,000 users and of all of them, about 10 users were unable to start
>Communicator. It appears that the COM+ was corrupt and I was unable to get
>into Component Services on those computers. It would either close as soon as
>I tried expanding MyComputer in Component Services or it would throw an error.
>
>The resolution that I found was to set the following services to logon
>locally:
>COM+ Event System, COM+ System Application, Remote Procedure Call (RPC), and
>Remote Procedure Call (RPC) Locator. Then confirmed that they have no
>dependencies other that what is required with was RPC for the 2 COM+
>services, RPC had none and RPC Locator had 'Workstation'. Then I rebooted the
>computer and reinstalled COM+ by going to Add\Remove Programs and running
>through the Add/Remove Windows Components Wizard. Then Communicator would
>work.
>
>Today, I had a user call with the issue of Communicator not opening, so I
>followed the previous steps and it still does not work. The error logs show
>the following warning and since this warning appeared is when the problem
>with Communicator started.
>
>The CRM log file was originally created on a computer with a different name.
>It has been updated with the name of the current computer. If this warning
>appears when the computer name has been changed then no further action is
>required. MLANDELL2
>Server Application ID: {02D4B3F1-FD88-11D1-960D-00805FC79235}
>Server Application Instance ID:
>{D68C6917-F69D-4D78-B65B-A9192186246E}
>Server Application Name: System Application
>comsvcs.dll file version: ENU 2001.12.4414.258 shp
>
>Any suggestions would be greatly appreciated...

Contact your IT dept. ?

[nass]

"JasonCassity" wrote:

> My company pushed out Communicator 2007 a few months ago. There were about
> 2,000 users and of all of them, about 10 users were unable to start
> Communicator. It appears that the COM+ was corrupt and I was unable to get
> into Component Services on those computers. It would either close as soon as
> I tried expanding MyComputer in Component Services or it would throw an error.
>
> The resolution that I found was to set the following services to logon
> locally:
> COM+ Event System, COM+ System Application, Remote Procedure Call (RPC), and
> Remote Procedure Call (RPC) Locator. Then confirmed that they have no
> dependencies other that what is required with was RPC for the 2 COM+
> services, RPC had none and RPC Locator had 'Workstation'. Then I rebooted the
> computer and reinstalled COM+ by going to Add\Remove Programs and running
> through the Add/Remove Windows Components Wizard. Then Communicator would
> work.
>
> Today, I had a user call with the issue of Communicator not opening, so I
> followed the previous steps and it still does not work. The error logs show
> the following warning and since this warning appeared is when the problem
> with Communicator started.
>
> The CRM log file was originally created on a computer with a different name.
> It has been updated with the name of the current computer. If this warning
> appears when the computer name has been changed then no further action is
> required. MLANDELL2
> Server Application ID: {02D4B3F1-FD88-11D1-960D-00805FC79235}
> Server Application Instance ID:
> {D68C6917-F69D-4D78-B65B-A9192186246E}
> Server Application Name: System Application
> comsvcs.dll file version: ENU 2001.12.4414.258 shp
>
> Any suggestions would be greatly appreciated...


Hi,
Did these machines joined the domain after installing the CR2 2007?
Read the info below and try the solution before applying the Hotfix.
COM+-related events may be logged in Event Viewer when you install Windows
XP Service Pack 2 and join the computer to a domain

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

Availability of Windows XP COM+ Hotfix Rollup Package 9
http://support.microsoft.com/kb/895200

COM + Error after installing SP2
http://www.pcbanter.net/showthread.php?t=638854

Best if you mention what SP service pack these machine updated to!
HTH,
nass
---
http://www.nasstec.co.uk