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

  • Outlook 2007 + Call Manager

    Whenever I attempt to install the Outlook integration for voice mail notifications inside of Outlook 2007 I receive the following error.
    An error occurred while install ShoreWare voicemail for Microsoft Outlook.
    Please make sure the Outlook is in the Corporate Workgroup mode, and have been fully configured.
    Also, please insure that Outlook is the default client for mail on this machine.

    Just wondering if anyone has seen this and has a resolution.

  • #2
    What build are you running?

    Comment


    • #3
      Originally posted by jlear View Post
      What build are you running?
      Running Build 12.12.6116.0.

      Comment


      • #4
        I'm going from memory here but I think that you are probably affected by the issue that this work around fixes:

        When installing Call Manager, during the Outlook integration, receive the error message "Please make sure Outlook is running in Corporate Workgroup mode".
        Outlook is running in Corporate Mode.
        In somes cases:
        The issue is a typo in the VMailfrm.cfg file. To correct the issue Open File Manager and go to C:\Program Files\Shoreline Communications\ShoreWare Client, or the drive your PCM is installed in.
        1) Open the following file with Notepad: VMailfrm.cfg
        2) Look for the following:
        [Platform.NTx86]
        CPU=ix86
        OSVersion=WinNT3.5
        file1=VMailForm.dll
        registry1=InprocServer32 = VMailForm.dll
        2) Remove the o from the following lines
        file1=VMailForm.dll
        registry1=InprocServer32 = VMailForm.dll
        3) It should now look like this
        CPU=ix86
        OSVersion=WinNT3.5
        file1=VMailFrm.dll
        registry1=InprocServer32 = VMailFrm.dll
        4) Restart your PC and then run the Outlook Integration

        This was corrected in newer builds but I can't remember the number.

        Comment


        • #5
          Mmmm Interesting..

          Here's the cfg file section as referenced. This is undmodified doesn't have the 'o'.

          [Platform.NTx86]
          CPU=ix86
          OSVersion=WinNT3.5
          file1=VMailFrm.dll
          registry1=InprocServer32 = VMailFrm.dll

          Comment


          • #6
            Very interesting indeed...

            How are you installing Call Manager? From the weblink, local setup file (from CD or something) or silent install through AD?

            If you are installing interactively then you need to have local admin rights on the machine.

            You might also try this one although I didn't think you needed the CDO if you weren't doing calendar integration:

            Cannot see the Collaboration Data Object option in Outlook 2007
            In earlier Outlook 2007, the CDO portion was not included. If you do not see CDO, then download it from the Microsoft website
            Website: Download the Collaboration Data Object Version 1.2.1 from http://www.microsoft.com/downloads/details.aspx?FamilyID=2714320d-c997-4de1-986f-24f081725d36&displaylang=en

            Comment


            • #7
              Yes installing from LAN Share. Have deployed via AD GPO, and also via a silent MSIEXEC.EXE command, using Kaseya. (CD's.. you mean ShoreTel software comes on CD's?)

              The machine in question is mine running Vista Business SP1, Office 2007, and I have the CDO objects installed. (Found out about the CDO requirements early on the piece.)

              I do have local admin rights, and have UAC off.

              Cheers.
              Last edited by francismcphail; 05-18-2008, 09:06 PM.

              Comment


              • #8
                Perhaps give it a go from the weblink (http://<ShoreTel Server>/shorewaredirector/clientinstall

                and see what happens. What about the other machines in your office? Are they running the same config? It is important that the Outlook profile is created before PCM is installed. If PCM was pushed out to the machine by AD before you created an Outlook profile it could cause issues.

                You could also try installing from a local drive, you might need to right click and run as administrator. Maybe not with UAC off.

                Comment


                • #9
                  Hi, I have same problem, How has been resolved?, please let me know if it was resolved, I'm new ShoreTel Administrator.

                  I'm using 7.5 Call Manager, Win XP SP3

                  Comment


                  • #10
                    Originally posted by icmadmin View Post
                    Hi, I have same problem, How has been resolved?, please let me know if it was resolved, I'm new ShoreTel Administrator.

                    I'm using 7.5 Call Manager, Win XP SP3

                    You may want to check on the service Pack three.

                    I don't know if the call manager has had any issues with Sp3, but it very may well could be.

                    Comment


                    • #11
                      I have seen that problem, and I've been able to fix it by reinstalling call manager

                      Comment


                      • #12
                        Originally posted by francismcphail View Post
                        Whenever I attempt to install the Outlook integration for voice mail notifications inside of Outlook 2007 I receive the following error.
                        An error occurred while install ShoreWare voicemail for Microsoft Outlook.
                        Please make sure the Outlook is in the Corporate Workgroup mode, and have been fully configured.
                        Also, please insure that Outlook is the default client for mail on this machine.

                        Just wondering if anyone has seen this and has a resolution.
                        This is a known bug, I am not sure if it is fixed in the Current GA, Open a SR with TAC and Have it tracked. Last I was aware they were looking into this with Keen Interest

                        PLus SP3 Is not supported at this time

                        Comment


                        • #13
                          There's one computer in our building that has this issue: Mine. It's been there since 6.0 (now at 7.5), and no matter how I install it I've never gotten it to work. I assume it has something to do with having had many different profiles on this machine (though no more than two at a time), as I used to routinely log into email accounts of new hires as we were getting their accounts and equipment ready. I always deleted these profiles once they were no longer needed, but I think that maybe there are some remnants left and it freaks out Call Manager.

                          Comment


                          • #14
                            Try this, it works for me.....

                            1. Quit all open programs.

                            2. Rename the Mapi32.dll file in C:\Windows\System32 to Mapi32.old.

                            3. Locate the Fixmapi.exe file in C:\Windows\System32, and then double-click Fixmapi.exe to run the program.

                            4. Restart your computer.

                            5. Attempt install of Outlook Integration

                            Comment


                            • #15
                              The above fix works

                              The above fix worked for me.

                              Comment

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