1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Outlook 2003

Discussion in 'Windows Home Server' started by Denis, Sep 5, 2009.

  1. Denis

    Denis Guest

    Windows server 2003 with Exchange.

    Outlook 2003 has been installed onto this server. I have tried to remove it
    but get the msi file is not available even with the correct disk in the CD. I
    have checked the msi file and it is there, if I try and run it I get an
    incorrect patch error!

    Question; Can I use the mirosoft uninstall tool (msicuu2.exe) safely on a
    2003 server?
     
  2. "Denis" <Denis@discussions.microsoft.com> wrote in message
    news:CAC8600F-9EC4-41FE-8EB7-0BEFC6E1127D@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Windows server 2003 with Exchange.
    >
    > Outlook 2003 has been installed onto this server. I have tried to remove
    > it
    > but get the msi file is not available even with the correct disk in the
    > CD. I
    > have checked the msi file and it is there, if I try and run it I get an
    > incorrect patch error!
    >
    > Question; Can I use the mirosoft uninstall tool (msicuu2.exe) safely on a
    > 2003 server?<!--colorc--><!--/colorc-->


    Just to state up front, Outlook shouldn't be installed on an Exchange server
    due to the MAPI differences.

    As for uninistalling OUtlook, did you get incorrect patch or path error?
    I've never used msicuu2.exe, but it may remove necessary files. Have you
    tried re-installing it, then uninstalling it? You may have to make sure the
    correct MAPI.dll file is in place after the installation for Exchange to
    use.

    More info on the msicuu2.exe file. Read the cautions in the links.

    Description of the Windows Installer CleanUp Utility


    You receive the "This patch package could not be opened" error message in an
    Office program



    --
    Ace

    This posting is provided "AS-IS" with no warranties or guarantees and
    confers no rights.

    Please reply back to the newsgroup or forum for collaboration benefit among
    responding engineers, and to help others benefit from your resolution.

    Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
    Microsoft Certified Trainer

    For urgent issues, please contact Microsoft PSS directly. Please check
    for regional support phone numbers.
     
  3. Denis

    Denis Guest

    I was getting Outlook off the server due to the possible problems with
    Exchange on the same machine.

    I took a flier, after trying all the normal approaches, and ran msicuu.exe
    on the server then removed all the office11 files (only outlook was installed
    no other Office apps). It appears to work fine. The server appears OK.

    Phew!

    "Ace Fekay [MCT]" wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > "Denis" <Denis@discussions.microsoft.com> wrote in message
    > news:CAC8600F-9EC4-41FE-8EB7-0BEFC6E1127D@microsoft.com...<!--coloro:green--><span style="color:green <!--/coloro-->
    > > Windows server 2003 with Exchange.
    > >
    > > Outlook 2003 has been installed onto this server. I have tried to remove
    > > it
    > > but get the msi file is not available even with the correct disk in the
    > > CD. I
    > > have checked the msi file and it is there, if I try and run it I get an
    > > incorrect patch error!
    > >
    > > Question; Can I use the mirosoft uninstall tool (msicuu2.exe) safely on a
    > > 2003 server?<!--colorc--><!--/colorc-->
    >
    >
    > Just to state up front, Outlook shouldn't be installed on an Exchange server
    > due to the MAPI differences.
    >
    > As for uninistalling OUtlook, did you get incorrect patch or path error?
    > I've never used msicuu2.exe, but it may remove necessary files. Have you
    > tried re-installing it, then uninstalling it? You may have to make sure the
    > correct MAPI.dll file is in place after the installation for Exchange to
    > use.
    >
    > More info on the msicuu2.exe file. Read the cautions in the links.
    >
    > Description of the Windows Installer CleanUp Utility
    >
    >
    > You receive the "This patch package could not be opened" error message in an
    > Office program
    >

    >
    >
    > --
    > Ace
    >
    > This posting is provided "AS-IS" with no warranties or guarantees and
    > confers no rights.
    >
    > Please reply back to the newsgroup or forum for collaboration benefit among
    > responding engineers, and to help others benefit from your resolution.
    >
    > Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
    > Microsoft Certified Trainer
    >
    > For urgent issues, please contact Microsoft PSS directly. Please check
    >
    for regional support phone numbers.
    >
    > <!--colorc--><!--/colorc-->
     
  4. "Denis" <Denis@discussions.microsoft.com> wrote in message
    news:34E64388-0AB5-43DE-B074-007E4B6E9F9F@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    >I was getting Outlook off the server due to the possible problems with
    > Exchange on the same machine.
    >
    > I took a flier, after trying all the normal approaches, and ran msicuu.exe
    > on the server then removed all the office11 files (only outlook was
    > installed
    > no other Office apps). It appears to work fine. The server appears OK.
    >
    > Phew!
    ><!--colorc--><!--/colorc-->


    I would heed Anthony's warnings regarding what it does. Therefore, keep in
    mind the MAPI differences. Outlook uses Simple MAPI, and Exchange 2003 uses
    Extended MAPI. The don't show up with those identifiers (simple or
    extended), but you can tell from the file sizes, versions and dates on the
    dll. The Extended version is 10 times the size of the simple version.

    Check your mapi32.dll versions left behind, in \program files\exchsvr\bin,
    windows\system32 and in \program files\Common Files\System\Mapi\1033\NT.
    They should read as (SP2 version). Exchange has its copy in the bin folder,
    but copies it to system32, and registers that version during setup.

    The latest should be:
    mapi32.dll, 11/25/08, ver 6.5.7654.12, 623KB

    If any different, you may have to reinstall Exchange using the reinstall
    option. However you can try another way by stopping the info store,
    unregister mapi32.dll, copy the files from an Exchange SP2 source into the
    system32 folder, and re-register it.

    Cmd prompt, navigate to windows\system32, then run:

    regsvr32 /u mapi32.dll
    copy the correct version
    regsvr32.dll mapi32.dll

    Mapi32.dll is the wrong version


    Microsoft does not support installing Exchange Server components and Outlook
    on the same computer


    Installing Microsoft Outlook on Exchange Server 2003 (says you may have to
    re-install Exchange using the reinstall option):


    Ace
     

Share This Page