Announcement

Collapse

Welcome to ShoreTelForums.com

Welcome to ShoreTelForums.com!

This site was created as a place to share stories, tips, and troubleshooting help with ShoreTel/Mitel systems. ShoreTel/Mitel is obviously the MOST exciting VoiP platform on the market right now, and we realized there was no centralized place to discuss this platform, but now there is. Please feel free to join and share your experiences.

Please Note: This site IS NOT owned, funded, or managed by ShoreTel/Mitel, Inc. although you may find ShoreTel/Mitel employees sharing there experiences and expertise. If you would like more information on ShoreTel/Mitel systems, contact BTX at [email protected]

As always please support the advertisers that help support our site.

Thank You,
BTX
See more
See less
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ShoreTel Director Error Messages (Services Restarting)

    Every 2-3 minutes we are having a service restart:
    ServicesMgr main processing loop is stuck. Killing ServicesMgr
    [2009/06/19 13:16:17.581 PDT 10.10.25.3]

    The service then starts up normally for a minute or two and then the same error occurs.

    Anyone seen this before? Any ideas on resolving?

  • #2
    Happened yesterday to me

    Turn off DEP for other than MS.

    Comment


    • #3
      I am currently getting this on a machine with DEP on for essential windows progams and services only. Server 2003 R2 ShoreTel 9 Build 14.5.7805.0.

      Any other suggestions?

      Comment


      • #4
        Services

        I assume you have already tried a reboot?

        This tuesdays microsoft patches caused many of our shoretel services to go crazy. Reboot was necessary for us.

        Comment


        • #5
          Edit the boot.ini change noexecute=optin to noexecute=AlwaysOff (case sensitive) and reboot this disables DEP completely.

          Comment


          • #6
            Was this related to a "V" model switch? I just had the same issue that required a burn flash procedure on my 50V switch.

            Comment


            • #7
              Just to chime in, I just noticed this in my logs on a v-switch. Not sure how long it has been going on for. I'll try to bounce the switch this evening when it is not in use.

              Comment


              • #8
                This issue is caused by a V switch timing out when trying to connect to it's NTP Server. In earlier builds, the maximum latency was 1 second, and there was no way to force an update. This issue is corrected in 13.25.9102 in 8.1 and 14.22.1402 in 9.x. This does not cause any issues other than filling up your NT logs.

                Comment


                • #9
                  We're running 14.22.2904.0 with a 90V switch and we had a bunch of these errors in the log. I restarted the Shoreware Director server, but that didn't help. Rebooting the 90V cleared the error. The error doesn't seem to cause a problem, but I'd rather have it not showing up.

                  Comment


                  • #10
                    Originally posted by jmarthaler View Post
                    We're running 14.22.2904.0 with a 90V switch and we had a bunch of these errors in the log. I restarted the Shoreware Director server, but that didn't help. Rebooting the 90V cleared the error. The error doesn't seem to cause a problem, but I'd rather have it not showing up.
                    We had this happen as well, a reboot only cleared it for about a week or two until it started showing up again.

                    Upgraded to 9.2 and it hasn't shown since.

                    Comment


                    • #11
                      How has the 9.2 code performed for you? We would like to upgrade for some of the voicemail features, but we're a bit concerned about some of the known issues in the release notes -- notably the one about the voicemail system being randomly unavailable (Defect 1-34037044).

                      Comment


                      • #12
                        We've got it on a pretty busy customer (they receive upwards of 2k inbound calls a day) and it seems to be holding up pretty well - although the only issue we had was the personal greetings and name prompts for users mailboxes disappeared and we couldn't restore them. All the workgroups / AA menus were unaffected.

                        Comment

                        Working...
                        X
                        😀
                        🥰
                        🤢
                        😎
                        😡
                        👍
                        👎