RE: Can't install Outlook 2003 upgrade on client

Hi Michael,

Thank you for your update.

1. Considering the current condition, this issue may occurs due to some
corrupt .dll files or registry keys related to Office XP. In this
situation, I suggest that we completely uninstall Outlook XP from
Add/Remove Programs (if you have installed entire Office XP, please
uninstall Office XP including Outlook XP and other Office applications),
and delete the following registry keys:

HKEY_CURRENT_USER\Software\Microsoft\Office
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
Messaging Subsystem\Profiles
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange

Then, install Office 2003 on the problematic workstation.

2. If the issue persists, please kindly perform the following steps:

To uninstall Outlook XP
======================
1). Select the Microsoft Office XP Professional with FrontPage, and click
OK.

2). In the Microsoft Office XP Setup dialog box, click "Add or Remove
Features"
option, and click Next.

3). Click "Microsoft Outlook for Windows", click X Not Available, and then
click
Update.

4). Click OK.

NOTE: This process does not remove all of the Outlook 2002 program files
from you
hard disk. The registry entries and the icons for Outlook are either
disabled or
removed.

Remove or rename mapi32.dll (and/or mapisp32.exe) in the
C:\Windows\System32
folder.

To remove or rename mapi32.dll
======================
1). Open Windows Explorer and navigate C:\Windows\System32.

2). Right click mapi32.dll, click Rename, type a different name for it
(such as
mapi32.old), and press Enter to confirm.

3). If mapisp32.exe is found in this folder, rename it also.

3. If you cannot completely remove Outlook XP, please use the following
tools to check what file or registry key cannot be deleted.

Filemon
http://www.sysinternals.com/Utilities/Filemon.html

Regmon
http://www.sysinternals.com/Utilities/Regmon.html

NOTE: This response contains a reference to a third party World Wide Web
site. Microsoft is providing this information as a convenience to you.
Microsoft does not control these sites and has not tested any software or
information found on these sites; therefore, Microsoft cannot make any
representations regarding the quality, safety, or suitability of any
software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make
sure that you completely understand the risk before retrieving any software
from the Internet.

4. If the issue still persists, please help me collect the following
information for further analysis:

SBSMSI-Clientsetup.log
%programfiles%\Microsoft Integration\Windows Small Business Server
2003\Logs\SBSMSI-Clientsetup.log

More information:

How To Restore a User Profile in Windows Server 2003
http://support.microsoft.com/kb/324734/

How to copy data from a corrupted user profile to a new profile
http://support.microsoft.com/?id=811151

I appreciate your time and cooperation. If anything is unclear, please feel
free to let me know. I am looking forward to hearing from you.

Best regards,

Nathan Liu (MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
>Thread-Topic: Can't install Outlook 2003 upgrade on client
>thread-index: AcYE9Yg7laGLqnkRTky8LJDgf4E6Ww==
>X-WBNR-Posting-Host: 63.173.214.115
>From: =?Utf-8?B?TWljaGFlbCBDb21taW5z?=
<MichaelCommins@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <7928CDFC-72C4-4748-8985-1C14CC37EDB1@xxxxxxxxxxxxx>
<6RMddl7#FHA.1240@xxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: Can't install Outlook 2003 upgrade on client
>Date: Mon, 19 Dec 2005 15:40:02 -0800
>Lines: 80
>Message-ID: <DE62041F-31FD-4281-882E-CD4E157F3939@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:231254
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Nathan,
>
>> 1. What version of Outlook was running on the previous Windows 2000
>> workstations (Outlook 2000 or Outlook 2002)? Please completely uninstall
>> the previous Outlook client on the specific workstations, and then try
>> again.
>
>Outlook XP.
>>
>> 2. Did you run "Add User Wizard" and "Set Up Client Computer wizard"
to
>> create appropriate user account and computer account, and then join the
>> computer into SBS Domain through http://SBSServerName/connectcomputer
link?
>
> I ran "Add User Wizard" and Set Up Client Computer wizard," but I did not
>join through the browser interface. I joined through "My
>Computer-Properties-Computer Name-Change"
>
>> If not, please try the following steps on the client workstation and see
>> how it goes:
>>
>> a. Log on locally as a local administrator to the client. In Control
Panel,
>> double-click System. On the Computer Name tab, click Change, select
>> Workgroup, type a workgroup name and click OK. Click OK when prompted to
>> restart the computer.
>>
>> b. On the SBS server, delete the user and computer accounts, click Add a
>> User in Server Management\Users. Follow the instructions to create user
and
>> computer accounts, then click "Assign Applications to Client Computers"
to
>> assign Outlook to this computer.
>>
>> c. On the client, open IE, go to http://SBSServerName/connectcomputer
and
>> follow the instructions to join domain, and install the Outlook 2003.
>
>OK, I did this and still no good.
>>
>> 3. If the issue persists, please perform the following steps to check
if
>> the issue can be resolved:
>>
>> Step 1
>> =====
>>
>> Refer to the following article to remove some Windows Installer related
>> registry keys
>> Q290301 OFFXP: Windows Installer CleanUp Utility
>> http://support.microsoft.com/support/kb/articles/q290/3/01.asp
>
>OK, ran Windows Installer CleanUp Utility and went to step 2
>>
>> Step 2
>> =======
>>
>> Delete the keys in the registry
>>
>> From the Start menu, go to Run, type REGEDIT and press Enter.
>>
>> Locate the following keys and delete them. If you cannot find one key,
just
>> skip it and try the next key.
>>
>> HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\<OfficeGUID>
>>
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Installer\Produc
>> ts\<OfficeGUID>
>> HKEY_LOCAL_MACHINE\Software\Classes\Installer\Products\<Office GUID>
>> HKEY_LOCAL_MACHINE\Software\Microsoft\Office
>>
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\<Offi
>> ceGUID>
>
>
>I could find none of these keys in the registry. It appears from your
post
>that <Office GUID> refers to a variable. Is that true? If so, what
should I
>be looking for? I did not go to step 3 because it seemed futile if none
of
>the keys I was looking for existed.
>This is very frustrating because after deleting the user and computer
>account on the server, I lost all of the user's profile information which
I
>had copied from the local profile. Now when I try to copy the local
profile
>to the domain user's profile on the client computer, it does not copy
>completely. I've been forced to have the user log in as the local user
>instead of the domain user.
>For what it's worth, I've had none of these problems joining a new
computer
>to the domain. It is only the older machines that are or were running W2K
>that seem to be having problems.
>

.

Relevant Pages

  • RE: Outlook 2003 server change
    ... If you would like to check the Exchange name in the registry keys, ... It seems that it should be the same location as in Outlook 2002. ... Microsoft Online Support Engineer ... 60Subject: Outlook 2003 server change ...
    (microsoft.public.outlook.installation)
  • Re: Is my OE 5 or 6.
    ... About Outlook Express will give you the version number as well. ... to the internals including the registry keys, ... So the developers haven't bothered to change ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • RE: GPO to redirect Outlook "AutoArchive" location
    ... I understand you would like to use GPO to redirect the Outlook AutoArchive ... As the Path was stored in the Profile's registry keys, ... The CIW is included with the Microsoft Office Resource Kit 2003. ... following steps describe how you can create an Outlook profile by using CIW ...
    (microsoft.public.office.setup)
  • Re: How do I get rid of multiple personal folders in Outlook 2003?
    ... This is the reason why we developed a freeware tool for this problem. ... It seems like there are many keys for me to ... Share Outlook without Exchange: Public ShareFolder ... having two registry keys versus only one for a ghost PST, ...
    (microsoft.public.outlook.installation)
  • Re: How do I get rid of multiple personal folders in Outlook 2003?
    ... The second has two "ab" keys, ... Share Outlook without Exchange: Public ShareFolder ... having two registry keys versus only one for a ghost PST, ... I've tried deleting two of the Personal Folders, ...
    (microsoft.public.outlook.installation)