Прекращена работа программы communicator exe как исправить

Содержание

• 1. Что такое Communicator.exe?
• 2. Communicator.exe безопасный или это вирус или вредоносная программа?
• 3. Могу ли я удалить или удалить Communicator.exe?
• 4. Распространенные сообщения об ошибках в Communicator.exe
• 5. Как исправить Communicator.exe
• 6. Январь 2023 Обновление
• 7. Загрузите или переустановите Communicator.exe

Обновлено в январе 2023 г .:

Мы рекомендуем вам попробовать это новое программное обеспечение, которое исправляет компьютерные ошибки, защищает их от вредоносных программ и оптимизирует производительность вашего ПК. Этот новый инструмент исправляет широкий спектр компьютерных ошибок, защищает от таких вещей, как потеря файлов, вредоносное ПО и сбои оборудования.

• Шаг 1: Скачать PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista — Microsoft Gold Certified).
• Шаг 2: Нажмите «Начать сканирование”, Чтобы найти проблемы реестра Windows, которые могут вызывать проблемы с ПК.
• Шаг 3: Нажмите «Починить все», Чтобы исправить все проблемы.

(опциональное предложение для Reimage — Cайт | Лицензионное соглашение | Персональные данные | Удалить)

Answers

• Answered in another thread.

All replies

• I saw this before when using older beta versions of MOC 2007.

  Can you verify what version of MOC you are using? It should match your server version. The public beta version is 6090.

• Yes. 6090 is the build I’m using.

• Hi Nori,

  I have been trying to get some more help on this, but have not been able to yet. Can you give a status of your situation? Have you tried reinstalling communicator? What version of Outlook are you using?

• We’re using Outlook 2007. This is happening on newly built laptops so I doubt a reinstall will make any difference.

• Are you able to upgrade to RTM?

• Answered in another thread.

• Same situation here.

  Have a mixed deployment of Outlook 2003 / 2007, all OSes are Windows XP SP2 on a domain.

  It’s somewhat annoying since Communicator doesn’t auto exit properly all the time; and that stops the logoff process. That leaves user’s account wide open with no password-protected screensaver, and blocks updating of roaming profiles.

  It’s pretty easy to repeat the scenario. Just have the following opened: Outlook, a Sharepoint site, and Communicator 2007. All should have been signed in with same credential. Then try logging off your Windows account and you’ll see Communicator 2007 cannot quit itself. It will sign off, but cannot end the process. Somehow it’s locked with Outlook/Sharepoint site until Outlook and Sharepoint are exited.

  That «minor» issue and lack of support for Mac Messenger 6.0.3 are factors of why we are still on an evaluation phase for this product. Searching for archived messages on the OCS 2007 isn’t convenient too.

• We are experiencing this problem as well.  We have Office 2007 and Office Communicator 2007 deployed to about 900 users and most users get the Communicator.exe hanging on the shutdown problem.  This is not only an application issue but also a security issue since some users walk away not noticing the hang problem and leave their pc’s vulnerable.

  We get this problem without a Sharepoint site being involved at all.

  We consider this a «major» issue as well as a security threat.

  We’ve applied this OCS 2007 hotfix and still have the problem: http://www.microsoft.com/downloads/details.aspx?familyid=1ad57f8f-78f7-45f6-a8c0-805936f46645&displaylang=en

• I have the same problem and also notice that i cannot exit the communicator if the outlook is open. Sometime when I logout of my pc communicator logs out automatically but most often it hangs.

  Nori said this was answered on another thread, can we get the link of that tread?

•   We recently upgraded over 900 users from Office Communicator 2005 to 2007.  After the upgrade to the new version of Communicator 2007, some users began experiencing the following problem:  When shutting down their PC at night (either Shutdown or Restart) the Communicator.exe program hangs.  So if the user walks away after shutting down…the machine will just hang there.  This can leave the machine unprotected since the screen saver never kicks in.  We are attempting to resolve this issue but at this point, no resolution has been found. 

  We give users the following two options as a workaround:

  1. When you attempt to shut down your machine and then get the message that communicator.exe is still running, just click the End Now button.  Your machine should shut down correctly after that.
  2. Before you shut down your machine, right click on the Communicator Icon (in the system tray in the lower right corner of your machine) and choose Exit.  Then shut down your machine.

  We’ve discovered that an Office Communicator Hotfix was released on 12/17/2007.  The hotfix alone doesn’t solve the Hang problem.  Next, we tried this one other setting* but the problem persists.

  *In connection with the hotfix, we tested that if this checkbox (Microsoft Office SharePoint Server Colleague Import Add-in) is unchecked in the COM Add-Ins section of the Outlook Trust Center, the Communicator Hang problem might go away.  We found that this did not solve the problem. 

  Question:

  Are you aware of this issue or any possible solution?  Can you direct this issue to someone who can help?

  This comment on the blog represents our problem well:

  It’s somewhat annoying since Communicator doesn’t auto exit properly all the time; and that stops the logoff process. That leaves user’s account wide open with no password-protected screensaver.

  Thanks for your time.  -KDOT R

• We’re still seeing this even with the December hotfix. People get really annoyed when they have to check their OST file as a result of ending communicator.exe abnormally. Checking 2-4GB mailboxes can take a while

  Although it seems our Vista users aren’t experiencing this. But I’ll have to investigate further.

  Regards,

  Nóri

• The MS Outlook team states that the ost file (your Exchange cache) can get the “dirty flag” set to where it will never clear and that can cause the shutdown hang.  The solution they want us to try first is to clear the ost file and let Outlook build a new one.  First step is to shutdown Outlook.  Just to be sure, hit Ctrl-Alt-Del and click on Task Manager, then on the Processes tab, click on image name to sort alphabetically and look for Outlook.exe.  If it’s not there, great.  If it is, right click it and select  End Process.  You should get a verification dialog and after you click OK on that, you shouldn’t see Outlook.exe in the process list any more.

  Then navigate to C:Documents and Settings[userid]Local SettingsApplication DataMicrosoftOutlook and delete any files with the ost extension that you find.  After the files are deleted, start Outlook and it will build a new ost file.  Then keep an eye out and see if you still get the hang.

• We are testing another solution to this problem:

  We noticed the following error in the Application Event Viewer any time a machine would hang at shutdown:

  Event Type:        Warning

  Event Source:    Userenv

  Event Category:                None

  Event ID:              1517

  Date:                     1/15/2008

  Time:                     8:21:30 AM

  User:                     NT AUTHORITYSYSTEM

  Computer:          CN99999

  Description:

  Windows saved user [username] registry while an application or service was still using the registry during log off. The memory used by the user’s registry has not been freed. The registry will be unloaded when it is no longer in use.

   This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

  For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

  So we searched on the error and found the following article:

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

  Which points users in the direction of this UPHClean utility:

  http://www.microsoft.com/downloads/details.aspx?FamilyId=1B286E6D-8912-4E18-B570-42470E2F3582

  Overview

  The User Profile Hive Cleanup service helps to ensure user sessions are completely terminated when a user logs off. System processes and applications occasionally maintain connections to registry keys in the user profile after a user logs off. In those cases the user session is prevented from completely ending. This can result in problems when using Roaming User Profiles in a server environment or when using locked profiles as implemented through the Shared Computer Toolkit for Windows XP.

  We are now testing whether this UPHClean service will prevent Communicator from hanging on shutdown.

• I’ve seen the same problem. The problem occurs regardless of whether the UPHClean has been installed or not.

  Thanks

• We are having this issue as well. Has anyone found a reliable solution to this? We’ve determined that communicator doesn’t begin hanging until the user has built an outlook profile. If they haven’t run outlook previously, there don’t appear to be any problems.

• We too have this problem.  With identical systems, 95% of the users do not have an issue.  For some reason,there are a few that do.  We have patched Office with the latest update, which did resolve it for the majority of users, but there is still a remaining 5% who experience this issue. 

  I can confirm that I have witnessed this behaviour starting AFTER outlook was run for the first time.

  I also noticed that the issue was resolved for one user when an OUTLOOK update was installed.

  A bit more information as well, I have noticed the problem occurs more often when a laptop user is using a wireless connection.

• We were never able to figure out exactly what the issue was. The workaround I’m currently using is setting AutoEndTasks to 1 instead of 0 in HKCUControl PanelDesktop. This will at least kill the app and log off the user rather than leave their computer sitting at a prompt to end the task. Hope this helps.

  Code Snippet

  Windows Registry Editor Version 5.00

  [HKEY_CURRENT_USERControl PanelDesktop]
  «AutoEndTasks»=»1»

• We also have a lot of these problems!

  I think this might be related to Outlook 2007’s useless and buggy handling of PST-files, thus making the cache «dirty» (as stated above). Maybe you Communicator folks could try detect a shutdown and make Communicator shut down before outlook tries it, instead of blaming another team?

  This happen at almost ALL our client installs. I sometimes wonder if Microsoft test their products at all.

  Can you please fix it?

• I’m currently trying to do the same. However I want to deploy it using the same GPO I used to deploy MOC. I tried to create an ADM file to modify the registry key, but I haven’t succeeded so far. Here is the content of my file:
  CLASS USER

  CATEGORY «KillCat»

  KEYNAME «Control PanelDesktop»

  POLICY «KillPol»
  EXPLAIN «KillExp»
  VALUENAME AutoEndTasks
  VALUEON NUMERIC 1
  VALUEOFF NUMERIC 0
  END POLICY
  END CATEGORY

  
  Does anyone has any idea on how to make it work?

• We to have several users experiencing the Office Communicator 2007 client hanging at shutdown.  However; we also experience this on a Windows 2003 R2 Terminal Server where the Outlook Cache and PST files are blocked from being used in Outlook 2007.  It does appear to be related as to whether they open Outlook, but it looks at this point if the user waits ~ 30 seconds after closing Outlook 2007, then attempts to logoff, Communicator closes correctly.  Even though the Outlook Executable does not appear as a running process, you still need to wait at a few more seconds before attempting to logoff.  I think this points to something else going on in the background with Outlook and Communicator.

  We are running the latest version of Office Communicator 2007 — 2.0.6362.111 on all systems and still have reports of the problem.  Hope this helps fix this bug.

  Lyle

•  same here.  Office 2007 with SP1, Communicator 2007 x.111 (december 2008) and still have Communicaor hanging on log off.  I imagine the reg setting is a work around, but it does cause the Outlook .ost rebuild on next logon.

  I can confirm it doesn’t happen for our Vista users, and UPH Clean doesn’t fix it for XP.

• I am running Windows Vista Business x86 with MOC 2007 R2 (build 3.5.6907.0). No issue with hang on shutdown or reboot. Though we are experincing this issue with our Widnows XP with SP3 users. Even with a fresh build of the OS. All users including my self are running Outlook 2003 (build 11.8217.8221) SP3.

  I do not think that the PST or OST has anything to do with it as our fresh Widnows XP with SP3 builds have the same issue where no user profiles have been created.

  Thanks,
  Niles 

• We have the same issue on all of our XP machines.  We are running MOC 2007 R2 and Office 2003.  Communicator fails to close and end task is pressed on restart.  This keeps outlook’s ost file open and causes a lengthy rebuild upon restart.  This is a long outstanding issue and is a major BUG with MOC.  Auto closing the application does not resolve the outlook ost rebuild.

  On a Vista machine, communicator does not give me the error that it can’t close, however outlook 2007 does require a rebuild.

  Does Microsoft read these posts?  If you find a fix, please post the solution.

• I was at microsoft when this issue first surfaced ( I had the first case). The customer was a fortune 500 company but the issue only occurred with certain Outlook versions (W2K3 if i remember correctly). I worked closely with the UC debug engineer collecting and analyzing the MOC dump files in different configurations.  the end result of this was the hotfix…but the workaround to disable the beforementioned Outlook add-in came from that case also.

  But part of this is user education also. Understand that Communicator has open handles to Outlook for a reason (outlook integration is «turned on» by default (it can be disabled in the registry)) and (unfortunately!) and it will not always exit gracefully unless Outlook is closed first. Think of the nice presence status icons in your e-mail messages. If MOC is logged out then Outlook cannot grab this presence information and make it available to you.

  Think of it as a service dependency if you like. I would be very surprised to see this issue occurr if Outlook is properly closed first.

  <turn on rant>
  And for the situation where someone is logging out of their account with Outlook, Sharepoint, and MOC running, that’s just a bad idea all around. Users need to understand (and accept) the consequences of data corruption when they pull stunts like that, especially with network connected applications!
  <turn off rant>

  For those that have applied the hotfix and are still seeing the issue and don’t want to or feel like they should have to <(;-)> educate their users then install userdump.exe and configure it to capture communicator.exe. Grab the dump file and open a case with microsoft. If enough people open cases and submit dumps files then something will be done…conversely if one customer with enough effected seats opens a <premier> case chances are things will get done also. Microsoft is its own closed little world and many of the guys there have never been «out in the trenches»….so sometimes you have to shake the tree a little and get their attention.

  hth

  Vic

  ---

  Vic Rozumny mcse
  AT&T

• lol too funny. scott sat two seats down from me at microsoft charlotte. he is the one I worked with on this issue. Super funny guy. Does stand-up comedy on the side.

  ---

  Vic Rozumny mcse
  AT&T

• Think of it as a service dependency if you like. I would be very surprised to see this issue occurr if Outlook is properly closed first.

  <turn on rant>
  And for the situation where someone is logging out of their account with Outlook, Sharepoint, and MOC running, that’s just a bad idea all around. Users need to understand (and accept) the consequences of data corruption when they pull stunts like that, especially with network connected applications!
  <turn off rant>

  Heck, I agree with you. I actually DO TRY close out Outlook consistently before logging out (some of my co-workers think I’m a little odd because I do this.) Despite this, I still get the issue. It’s frustrating, since I’m frequently working remotely, and this often results in my being unable to access my box at work.

  Just occurred to me. I had shut down Outlook, THEN logged off the computer. When I tried to TS in again from home, Communicator.exe was hung.

  <rant>
  GRRRR.

  Even better, it feels like my employer won’t open a ticket with unless something is actually happening to the system administrators. Since I’m only a lowly analyst/developer, I’m on my own.
  </rant> <!— you’re not the only one who does that!!!! —>

• Hello all,

  For what it’s worth, here is my collection of my testing thus far — tested with Microsoft XP, office/outlook 2007, Communicator 2007 R2 3.5.6907

  
  * The following results in this error/issue only — otherwise it is fine:
       — if outlook is not configured to a user account
       — if outlook account is not configured in the communicator
       — if AutoEndTasks»=»0″ (Disabled) — see below for details

  * Workarounds for now are:
       — manually click on the communicator in the system tray and select exit or
       — end process tree on communicator.exe — manaully or via script or

       — Enable AutoEndTasks=»1″ (do this before installing outlook and/or communicator as a reboot is needed for it to take effect)

  Windows Registry Editor Version 5.00

  [HKEY_CURRENT_USERControl PanelDesktop]

  «AutoEndTasks»=»1»

  
  The legacy version did not do this before — so what has changed — is there an initial launching method configuration that can be adjusted — i know that this can be done by temporarily setting the outlook connection option, but unfortunately im not allowed to alter the configuration from the standard — but adding extra ones without impact standard config and use is ok — does anyone else know of any other tips and/or tricks?
  

  • Edited by
    derrick.j.m.anderson
    Wednesday, June 10, 2009 10:12 PM

• I’ve also seen that if you exit Outlook, and then Re-Open Outlook, you are no longer able to view Personal Folders (PST-files) if they are loaded from an UNC share.

  The solution to this is to first exit and then re-open communicator before opening outlook, because communicator seem to lock these pst-files.

• A Quick update…

  Communicator r2 has resolved the remaining shutdown issues in our office.

  I have also noticed that this issue occurs more frequently if you install communicator BEFORE joining the domain.
  It also seems to be an issue if the account used to install doesnt have domain admin rights.  Installing from just the local admin account seems to increase the chances of a later shutdown issue for other users.

• Nori, instead of just typing, «Answered in another thread.», how about being more helpful and directing us to that thread?

  I mean, either give us a link to the thread, or the title to the other thread.

  Thanks,

  P.S.  I did search for this other elusive thread and I couldn’t find it.

• We are still facing this issue. We have Office Communication Server 2007 R2 installed with Office Communicator 2007 R2. We have mix of Outlook 2003 and Outlook 2007.

  On Outlook 2003 Machine the communicator hangs on shutdown and finally starts the end program window killing the communicator process.
  OS is Windows XP SP2
  Outlook version is Outlook 2003 (11.8206.8202) SP3
  and Communicator is 2007 R2 Version 3.5.6907.0

  OnOutlook 2007 machine, it takes more than 2-3 minutes to shutdown.
  OS is Windows XP Professional Service Pack 3
  Outlook version is Outlook 2007 (12.0.6504.5000) SP2 MSO (12.0.6425.1000)

  Please let us know if any resolution has been found for this issue.

  Thanks,
  Laxmi.

• We are in the midst of a Pilot deployment and we are seeing this problem.  We are running OCS 2007 R2 in a Consolidated Enterprise deployment.  The front-end servers are load balanced with an F5.  The clients are a mix of Windows XP SP3 and Windows 7 workstations.  I just started troubleshooting this problem.  I intend to use the post from this forum, a few workstations known to have this problem and a call to Microsoft to attempt resolution.  I will reply to this thread if/as I make progress.

• A solution that actually works — upgrade to this version of Outlook 2007.

  support.microsoft.com/kb/978401

  Not documented as a fix to this problem, but it does fix the communicator issue.

  Accepting hugs and high-fives if not vast sums of money…

• Answered in another thread.

  What is the other thread? How could anyone possibly mark this as a correct answer when there is no actual solution given? I have searched the forums and cannot find another thread mentioning this issue.

• • Edited by
    RoboTekniX
    Wednesday, September 21, 2011 6:36 AM

• Anyone have a fix for this from Microsoft that specifically addresses the «End Now» hang at log off in
  Lync 2010?  We’re using Lync 2010 and I don’t want to have some sort of failure / mix-up with versions of communicator.exe between Office Communicator 2007 and Lync 2010.  If there is a solid fix for
  Lync 2010 please let me know — unless of course Office Comm and Lync are they exact same product… and in that case — excuse my confusion and thanks in advance!  I’ve read the messages here and as far as I can tell
  — our situation is the same — we use Outlook integration and somehow the communicator.exe hang is related to outlook.  I don’t want to run around updating registy settings if I can help it.

  System:Windows XP SP3 | Office 2007 SP2 | Lync 2010

  Issue: Communicator.exe hang at log off — restart — shutdown

Answers

• Answered in another thread.

All replies

• I saw this before when using older beta versions of MOC 2007.

  Can you verify what version of MOC you are using? It should match your server version. The public beta version is 6090.

• Yes. 6090 is the build I’m using.

• Hi Nori,

  I have been trying to get some more help on this, but have not been able to yet. Can you give a status of your situation? Have you tried reinstalling communicator? What version of Outlook are you using?

• We’re using Outlook 2007. This is happening on newly built laptops so I doubt a reinstall will make any difference.

• Are you able to upgrade to RTM?

• Answered in another thread.

• Same situation here.

  Have a mixed deployment of Outlook 2003 / 2007, all OSes are Windows XP SP2 on a domain.

  It’s somewhat annoying since Communicator doesn’t auto exit properly all the time; and that stops the logoff process. That leaves user’s account wide open with no password-protected screensaver, and blocks updating of roaming profiles.

  It’s pretty easy to repeat the scenario. Just have the following opened: Outlook, a Sharepoint site, and Communicator 2007. All should have been signed in with same credential. Then try logging off your Windows account and you’ll see Communicator 2007 cannot quit itself. It will sign off, but cannot end the process. Somehow it’s locked with Outlook/Sharepoint site until Outlook and Sharepoint are exited.

  That «minor» issue and lack of support for Mac Messenger 6.0.3 are factors of why we are still on an evaluation phase for this product. Searching for archived messages on the OCS 2007 isn’t convenient too.

• We are experiencing this problem as well.  We have Office 2007 and Office Communicator 2007 deployed to about 900 users and most users get the Communicator.exe hanging on the shutdown problem.  This is not only an application issue but also a security issue since some users walk away not noticing the hang problem and leave their pc’s vulnerable.

  We get this problem without a Sharepoint site being involved at all.

  We consider this a «major» issue as well as a security threat.

  We’ve applied this OCS 2007 hotfix and still have the problem: http://www.microsoft.com/downloads/details.aspx?familyid=1ad57f8f-78f7-45f6-a8c0-805936f46645&displaylang=en

• I have the same problem and also notice that i cannot exit the communicator if the outlook is open. Sometime when I logout of my pc communicator logs out automatically but most often it hangs.

  Nori said this was answered on another thread, can we get the link of that tread?

•   We recently upgraded over 900 users from Office Communicator 2005 to 2007.  After the upgrade to the new version of Communicator 2007, some users began experiencing the following problem:  When shutting down their PC at night (either Shutdown or Restart) the Communicator.exe program hangs.  So if the user walks away after shutting down…the machine will just hang there.  This can leave the machine unprotected since the screen saver never kicks in.  We are attempting to resolve this issue but at this point, no resolution has been found. 

  We give users the following two options as a workaround:

  1. When you attempt to shut down your machine and then get the message that communicator.exe is still running, just click the End Now button.  Your machine should shut down correctly after that.
  2. Before you shut down your machine, right click on the Communicator Icon (in the system tray in the lower right corner of your machine) and choose Exit.  Then shut down your machine.

  We’ve discovered that an Office Communicator Hotfix was released on 12/17/2007.  The hotfix alone doesn’t solve the Hang problem.  Next, we tried this one other setting* but the problem persists.

  *In connection with the hotfix, we tested that if this checkbox (Microsoft Office SharePoint Server Colleague Import Add-in) is unchecked in the COM Add-Ins section of the Outlook Trust Center, the Communicator Hang problem might go away.  We found that this did not solve the problem. 

  Question:

  Are you aware of this issue or any possible solution?  Can you direct this issue to someone who can help?

  This comment on the blog represents our problem well:

  It’s somewhat annoying since Communicator doesn’t auto exit properly all the time; and that stops the logoff process. That leaves user’s account wide open with no password-protected screensaver.

  Thanks for your time.  -KDOT R

• We’re still seeing this even with the December hotfix. People get really annoyed when they have to check their OST file as a result of ending communicator.exe abnormally. Checking 2-4GB mailboxes can take a while

  Although it seems our Vista users aren’t experiencing this. But I’ll have to investigate further.

  Regards,

  Nóri

• The MS Outlook team states that the ost file (your Exchange cache) can get the “dirty flag” set to where it will never clear and that can cause the shutdown hang.  The solution they want us to try first is to clear the ost file and let Outlook build a new one.  First step is to shutdown Outlook.  Just to be sure, hit Ctrl-Alt-Del and click on Task Manager, then on the Processes tab, click on image name to sort alphabetically and look for Outlook.exe.  If it’s not there, great.  If it is, right click it and select  End Process.  You should get a verification dialog and after you click OK on that, you shouldn’t see Outlook.exe in the process list any more.

  Then navigate to C:Documents and Settings[userid]Local SettingsApplication DataMicrosoftOutlook and delete any files with the ost extension that you find.  After the files are deleted, start Outlook and it will build a new ost file.  Then keep an eye out and see if you still get the hang.

• We are testing another solution to this problem:

  We noticed the following error in the Application Event Viewer any time a machine would hang at shutdown:

  Event Type:        Warning

  Event Source:    Userenv

  Event Category:                None

  Event ID:              1517

  Date:                     1/15/2008

  Time:                     8:21:30 AM

  User:                     NT AUTHORITYSYSTEM

  Computer:          CN99999

  Description:

  Windows saved user [username] registry while an application or service was still using the registry during log off. The memory used by the user’s registry has not been freed. The registry will be unloaded when it is no longer in use.

   This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

  For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

  So we searched on the error and found the following article:

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

  Which points users in the direction of this UPHClean utility:

  http://www.microsoft.com/downloads/details.aspx?FamilyId=1B286E6D-8912-4E18-B570-42470E2F3582

  Overview

  The User Profile Hive Cleanup service helps to ensure user sessions are completely terminated when a user logs off. System processes and applications occasionally maintain connections to registry keys in the user profile after a user logs off. In those cases the user session is prevented from completely ending. This can result in problems when using Roaming User Profiles in a server environment or when using locked profiles as implemented through the Shared Computer Toolkit for Windows XP.

  We are now testing whether this UPHClean service will prevent Communicator from hanging on shutdown.

• I’ve seen the same problem. The problem occurs regardless of whether the UPHClean has been installed or not.

  Thanks

• We are having this issue as well. Has anyone found a reliable solution to this? We’ve determined that communicator doesn’t begin hanging until the user has built an outlook profile. If they haven’t run outlook previously, there don’t appear to be any problems.

• We too have this problem.  With identical systems, 95% of the users do not have an issue.  For some reason,there are a few that do.  We have patched Office with the latest update, which did resolve it for the majority of users, but there is still a remaining 5% who experience this issue. 

  I can confirm that I have witnessed this behaviour starting AFTER outlook was run for the first time.

  I also noticed that the issue was resolved for one user when an OUTLOOK update was installed.

  A bit more information as well, I have noticed the problem occurs more often when a laptop user is using a wireless connection.

• We were never able to figure out exactly what the issue was. The workaround I’m currently using is setting AutoEndTasks to 1 instead of 0 in HKCUControl PanelDesktop. This will at least kill the app and log off the user rather than leave their computer sitting at a prompt to end the task. Hope this helps.

  Code Snippet

  Windows Registry Editor Version 5.00

  [HKEY_CURRENT_USERControl PanelDesktop]
  «AutoEndTasks»=»1»

• We also have a lot of these problems!

  I think this might be related to Outlook 2007’s useless and buggy handling of PST-files, thus making the cache «dirty» (as stated above). Maybe you Communicator folks could try detect a shutdown and make Communicator shut down before outlook tries it, instead of blaming another team?

  This happen at almost ALL our client installs. I sometimes wonder if Microsoft test their products at all.

  Can you please fix it?

• I’m currently trying to do the same. However I want to deploy it using the same GPO I used to deploy MOC. I tried to create an ADM file to modify the registry key, but I haven’t succeeded so far. Here is the content of my file:
  CLASS USER

  CATEGORY «KillCat»

  KEYNAME «Control PanelDesktop»

  POLICY «KillPol»
  EXPLAIN «KillExp»
  VALUENAME AutoEndTasks
  VALUEON NUMERIC 1
  VALUEOFF NUMERIC 0
  END POLICY
  END CATEGORY

  
  Does anyone has any idea on how to make it work?

• We to have several users experiencing the Office Communicator 2007 client hanging at shutdown.  However; we also experience this on a Windows 2003 R2 Terminal Server where the Outlook Cache and PST files are blocked from being used in Outlook 2007.  It does appear to be related as to whether they open Outlook, but it looks at this point if the user waits ~ 30 seconds after closing Outlook 2007, then attempts to logoff, Communicator closes correctly.  Even though the Outlook Executable does not appear as a running process, you still need to wait at a few more seconds before attempting to logoff.  I think this points to something else going on in the background with Outlook and Communicator.

  We are running the latest version of Office Communicator 2007 — 2.0.6362.111 on all systems and still have reports of the problem.  Hope this helps fix this bug.

  Lyle

•  same here.  Office 2007 with SP1, Communicator 2007 x.111 (december 2008) and still have Communicaor hanging on log off.  I imagine the reg setting is a work around, but it does cause the Outlook .ost rebuild on next logon.

  I can confirm it doesn’t happen for our Vista users, and UPH Clean doesn’t fix it for XP.

• I am running Windows Vista Business x86 with MOC 2007 R2 (build 3.5.6907.0). No issue with hang on shutdown or reboot. Though we are experincing this issue with our Widnows XP with SP3 users. Even with a fresh build of the OS. All users including my self are running Outlook 2003 (build 11.8217.8221) SP3.

  I do not think that the PST or OST has anything to do with it as our fresh Widnows XP with SP3 builds have the same issue where no user profiles have been created.

  Thanks,
  Niles 

• We have the same issue on all of our XP machines.  We are running MOC 2007 R2 and Office 2003.  Communicator fails to close and end task is pressed on restart.  This keeps outlook’s ost file open and causes a lengthy rebuild upon restart.  This is a long outstanding issue and is a major BUG with MOC.  Auto closing the application does not resolve the outlook ost rebuild.

  On a Vista machine, communicator does not give me the error that it can’t close, however outlook 2007 does require a rebuild.

  Does Microsoft read these posts?  If you find a fix, please post the solution.

• I was at microsoft when this issue first surfaced ( I had the first case). The customer was a fortune 500 company but the issue only occurred with certain Outlook versions (W2K3 if i remember correctly). I worked closely with the UC debug engineer collecting and analyzing the MOC dump files in different configurations.  the end result of this was the hotfix…but the workaround to disable the beforementioned Outlook add-in came from that case also.

  But part of this is user education also. Understand that Communicator has open handles to Outlook for a reason (outlook integration is «turned on» by default (it can be disabled in the registry)) and (unfortunately!) and it will not always exit gracefully unless Outlook is closed first. Think of the nice presence status icons in your e-mail messages. If MOC is logged out then Outlook cannot grab this presence information and make it available to you.

  Think of it as a service dependency if you like. I would be very surprised to see this issue occurr if Outlook is properly closed first.

  <turn on rant>
  And for the situation where someone is logging out of their account with Outlook, Sharepoint, and MOC running, that’s just a bad idea all around. Users need to understand (and accept) the consequences of data corruption when they pull stunts like that, especially with network connected applications!
  <turn off rant>

  For those that have applied the hotfix and are still seeing the issue and don’t want to or feel like they should have to <(;-)> educate their users then install userdump.exe and configure it to capture communicator.exe. Grab the dump file and open a case with microsoft. If enough people open cases and submit dumps files then something will be done…conversely if one customer with enough effected seats opens a <premier> case chances are things will get done also. Microsoft is its own closed little world and many of the guys there have never been «out in the trenches»….so sometimes you have to shake the tree a little and get their attention.

  hth

  Vic

  ---

  Vic Rozumny mcse
  AT&T

• lol too funny. scott sat two seats down from me at microsoft charlotte. he is the one I worked with on this issue. Super funny guy. Does stand-up comedy on the side.

  ---

  Vic Rozumny mcse
  AT&T

• Think of it as a service dependency if you like. I would be very surprised to see this issue occurr if Outlook is properly closed first.

  <turn on rant>
  And for the situation where someone is logging out of their account with Outlook, Sharepoint, and MOC running, that’s just a bad idea all around. Users need to understand (and accept) the consequences of data corruption when they pull stunts like that, especially with network connected applications!
  <turn off rant>

  Heck, I agree with you. I actually DO TRY close out Outlook consistently before logging out (some of my co-workers think I’m a little odd because I do this.) Despite this, I still get the issue. It’s frustrating, since I’m frequently working remotely, and this often results in my being unable to access my box at work.

  Just occurred to me. I had shut down Outlook, THEN logged off the computer. When I tried to TS in again from home, Communicator.exe was hung.

  <rant>
  GRRRR.

  Even better, it feels like my employer won’t open a ticket with unless something is actually happening to the system administrators. Since I’m only a lowly analyst/developer, I’m on my own.
  </rant> <!— you’re not the only one who does that!!!! —>

• Hello all,

  For what it’s worth, here is my collection of my testing thus far — tested with Microsoft XP, office/outlook 2007, Communicator 2007 R2 3.5.6907

  
  * The following results in this error/issue only — otherwise it is fine:
       — if outlook is not configured to a user account
       — if outlook account is not configured in the communicator
       — if AutoEndTasks»=»0″ (Disabled) — see below for details

  * Workarounds for now are:
       — manually click on the communicator in the system tray and select exit or
       — end process tree on communicator.exe — manaully or via script or

       — Enable AutoEndTasks=»1″ (do this before installing outlook and/or communicator as a reboot is needed for it to take effect)

  Windows Registry Editor Version 5.00

  [HKEY_CURRENT_USERControl PanelDesktop]

  «AutoEndTasks»=»1»

  
  The legacy version did not do this before — so what has changed — is there an initial launching method configuration that can be adjusted — i know that this can be done by temporarily setting the outlook connection option, but unfortunately im not allowed to alter the configuration from the standard — but adding extra ones without impact standard config and use is ok — does anyone else know of any other tips and/or tricks?
  

  • Edited by
    derrick.j.m.anderson
    Wednesday, June 10, 2009 10:12 PM

• I’ve also seen that if you exit Outlook, and then Re-Open Outlook, you are no longer able to view Personal Folders (PST-files) if they are loaded from an UNC share.

  The solution to this is to first exit and then re-open communicator before opening outlook, because communicator seem to lock these pst-files.

• A Quick update…

  Communicator r2 has resolved the remaining shutdown issues in our office.

  I have also noticed that this issue occurs more frequently if you install communicator BEFORE joining the domain.
  It also seems to be an issue if the account used to install doesnt have domain admin rights.  Installing from just the local admin account seems to increase the chances of a later shutdown issue for other users.

• Nori, instead of just typing, «Answered in another thread.», how about being more helpful and directing us to that thread?

  I mean, either give us a link to the thread, or the title to the other thread.

  Thanks,

  P.S.  I did search for this other elusive thread and I couldn’t find it.

• We are still facing this issue. We have Office Communication Server 2007 R2 installed with Office Communicator 2007 R2. We have mix of Outlook 2003 and Outlook 2007.

  On Outlook 2003 Machine the communicator hangs on shutdown and finally starts the end program window killing the communicator process.
  OS is Windows XP SP2
  Outlook version is Outlook 2003 (11.8206.8202) SP3
  and Communicator is 2007 R2 Version 3.5.6907.0

  OnOutlook 2007 machine, it takes more than 2-3 minutes to shutdown.
  OS is Windows XP Professional Service Pack 3
  Outlook version is Outlook 2007 (12.0.6504.5000) SP2 MSO (12.0.6425.1000)

  Please let us know if any resolution has been found for this issue.

  Thanks,
  Laxmi.

• We are in the midst of a Pilot deployment and we are seeing this problem.  We are running OCS 2007 R2 in a Consolidated Enterprise deployment.  The front-end servers are load balanced with an F5.  The clients are a mix of Windows XP SP3 and Windows 7 workstations.  I just started troubleshooting this problem.  I intend to use the post from this forum, a few workstations known to have this problem and a call to Microsoft to attempt resolution.  I will reply to this thread if/as I make progress.

• A solution that actually works — upgrade to this version of Outlook 2007.

  support.microsoft.com/kb/978401

  Not documented as a fix to this problem, but it does fix the communicator issue.

  Accepting hugs and high-fives if not vast sums of money…

• Answered in another thread.

  What is the other thread? How could anyone possibly mark this as a correct answer when there is no actual solution given? I have searched the forums and cannot find another thread mentioning this issue.

• • Edited by
    RoboTekniX
    Wednesday, September 21, 2011 6:36 AM

• Anyone have a fix for this from Microsoft that specifically addresses the «End Now» hang at log off in
  Lync 2010?  We’re using Lync 2010 and I don’t want to have some sort of failure / mix-up with versions of communicator.exe between Office Communicator 2007 and Lync 2010.  If there is a solid fix for
  Lync 2010 please let me know — unless of course Office Comm and Lync are they exact same product… and in that case — excuse my confusion and thanks in advance!  I’ve read the messages here and as far as I can tell
  — our situation is the same — we use Outlook integration and somehow the communicator.exe hang is related to outlook.  I don’t want to run around updating registy settings if I can help it.

  System:Windows XP SP3 | Office 2007 SP2 | Lync 2010

  Issue: Communicator.exe hang at log off — restart — shutdown

Проблемы Netscape Communicator.exe обычно наблюдаются во время запуска программы Network Tools 2003 и обычно возникают в результате повреждения исполняемого файла или, в некоторых случаях, случайного или намеренного удаления вредоносным ПО. Большую часть проблем, связанных с данными файлами, можно решить посредством скачивания и установки последней версии файла EXE. Запуск сканирования реестра после замены файла, из-за которого возникает проблема, позволит очистить все недействительные файлы Netscape Communicator.exe, расширения файлов или другие ссылки на файлы, которые могли быть повреждены в результате заражения вредоносным ПО.

Исполнимые файлы с расширением файла EXE, также известны в качестве формата Windows Executable File. Ниже представлена наша база версий файлов Netscape Communicator.exe для большинства выпусков операционной системы Windows (включая %%os%%), где вы также можете их скачать. К сожалению, в настоящее время в нашей базе могут отсутствовать некоторые версии файлов Netscape Communicator.exe, но их можно запросить, нажав на кнопку Request (Запрос). Если вы не нашли необходимую вам версию файла в нашей базе, представленной ниже, мы рекомендуем обратиться непосредственно к Next Step Publishing.

Поместите новый файл Netscape Communicator.exe на место предыдущего (перезаписав предыдущий). Проблема больше не должна возникать, однако, чтобы убедиться в этом окончательно, следует выполнить проверку. Чтобы убедиться в том, что удалось решить проблему, попробуйте запустить Network Tools 2003, и посмотреть выведется ли ошибка.

Продукт Solvusoft

Загрузка
WinThruster 2023 — Сканировать ваш компьютер на наличие ошибок реестра в Netscape Communicator.exe

Windows
11/10/8/7/Vista/XP

Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление