OL2003 under Vista Home Premiun SP1.
(See my original post on this problem in microsoft.public.outlook.general -
4/2/09 4:32 pm)
I've cross-posted to ...windows.vista.general in a desperate reach for
additional assistance.
I originally asked for help on a known OL2003 problem, and found many fixes
by Googling mapi32.dll. None of them seemed to work. I think they all
tried to rename \windows\system32 mapi32.dll to something invalid, in the
belief that when OL2003 couldn't find the file it would generate what it
needed.)
One Outlook MVP told me how to rename the file, but I wasn't authorized to
do it, and $30 later, Geek Squad did it for me.
IT DIDN'T HELP!
What do I do next?
OL2003/Vista/mapi32.dll fix didn't work!
Moderators: DllAdmin, DLLADMIN ONLY
-
- Posts: 5
- Joined: 07 Mar 2009, 00:00
Re: OL2003/Vista/mapi32.dll fix didn't work!
"BudV" <BudVitoff@(NO)att.(SPAM)net> wrote:
>OL2003 under Vista Home Premiun SP1.
>
>(See my original post on this problem in microsoft.public.outlook.general -
>4/2/09 4:32 pm)
[snip]
>What do I do next?
If you want the folks in vista.general to help, then you're going to
have to copy your original post to that group (here) rather than hope
vista.general users will go find it in outlook.general.
>OL2003 under Vista Home Premiun SP1.
>
>(See my original post on this problem in microsoft.public.outlook.general -
>4/2/09 4:32 pm)
[snip]
>What do I do next?
If you want the folks in vista.general to help, then you're going to
have to copy your original post to that group (here) rather than hope
vista.general users will go find it in outlook.general.
Re: OL2003/Vista/mapi32.dll fix didn't work!
"BudV" <BudVitoff@(NO)att.(SPAM)net> wrote in message
news:eWz6w2WtJHA.1492@TK2MSFTNGP03.phx.gbl...
> OL2003 under Vista Home Premiun SP1.
The following (between the lines) was the original thread about the problem
I have:
Can I get a little more help on this mapi32 fix/denied access problem?
-------------------------------------------------------------------------------------
"BudV" <BudVitoff@(NO)att.(SPAM)net> wrote in message
news:uru$KH%23sJHA.2532@TK2MSFTNGP05.phx.gbl...
> It felt good to get into DOS again, but the feeling was short-lived.
> Access was denied. Yes, the title bar shows Administrator:Command Prompt
>
> "neo [mvp outlook]" <neo@discussions.microsoft.com> wrote in message
> news:u%23f3n79sJHA.4876@TK2MSFTNGP02.phx.gbl...
>> Start a command prompt with elevated permission. (e.g. Pearl button >
>> All Programs > Accessories > Right click on command prompt and pick run
>> as administrator > CD \windows\system32 > rename mapi32.dll
>> mapi32.dll.original
>> > exit command prompt)
>>
>> "BudV" <BudVitoff@(NO)att.(SPAM)net> wrote in message
>> news:e92%23Gq9sJHA.2532@TK2MSFTNGP05.phx.gbl...
>>> I'm trying to install Outlook2003 from a CD intoVista. Problems with
>>> mapi32.dll is a well-known item, and the fixes call for renaming it in
>>> Windows/system32. When I try to rename it, it spits up with "You need
>>> permission to perform this action." I'm logged on as an
>>> administrator -- don't I have permission? And what do I do to get it?
--------------------------------------------------------------------------------
> I've cross-posted to ...windows.vista.general in a desperate reach for
> additional assistance.
>
> I originally asked for help on a known OL2003 problem, and found many
> fixes by Googling mapi32.dll. None of them seemed to work. I think they
> all tried to rename \windows\system32 mapi32.dll to something invalid, in
> the belief that when OL2003 couldn't find the file it would generate what
> it needed.)
>
> One Outlook MVP told me how to rename the file, but I wasn't authorized to
> do it, and $30 later, Geek Squad did it for me.
>
> IT DIDN'T HELP!
>
> What do I do next?
news:eWz6w2WtJHA.1492@TK2MSFTNGP03.phx.gbl...
> OL2003 under Vista Home Premiun SP1.
The following (between the lines) was the original thread about the problem
I have:
Can I get a little more help on this mapi32 fix/denied access problem?
-------------------------------------------------------------------------------------
"BudV" <BudVitoff@(NO)att.(SPAM)net> wrote in message
news:uru$KH%23sJHA.2532@TK2MSFTNGP05.phx.gbl...
> It felt good to get into DOS again, but the feeling was short-lived.
> Access was denied. Yes, the title bar shows Administrator:Command Prompt
>
> "neo [mvp outlook]" <neo@discussions.microsoft.com> wrote in message
> news:u%23f3n79sJHA.4876@TK2MSFTNGP02.phx.gbl...
>> Start a command prompt with elevated permission. (e.g. Pearl button >
>> All Programs > Accessories > Right click on command prompt and pick run
>> as administrator > CD \windows\system32 > rename mapi32.dll
>> mapi32.dll.original
>> > exit command prompt)
>>
>> "BudV" <BudVitoff@(NO)att.(SPAM)net> wrote in message
>> news:e92%23Gq9sJHA.2532@TK2MSFTNGP05.phx.gbl...
>>> I'm trying to install Outlook2003 from a CD intoVista. Problems with
>>> mapi32.dll is a well-known item, and the fixes call for renaming it in
>>> Windows/system32. When I try to rename it, it spits up with "You need
>>> permission to perform this action." I'm logged on as an
>>> administrator -- don't I have permission? And what do I do to get it?
--------------------------------------------------------------------------------
> I've cross-posted to ...windows.vista.general in a desperate reach for
> additional assistance.
>
> I originally asked for help on a known OL2003 problem, and found many
> fixes by Googling mapi32.dll. None of them seemed to work. I think they
> all tried to rename \windows\system32 mapi32.dll to something invalid, in
> the belief that when OL2003 couldn't find the file it would generate what
> it needed.)
>
> One Outlook MVP told me how to rename the file, but I wasn't authorized to
> do it, and $30 later, Geek Squad did it for me.
>
> IT DIDN'T HELP!
>
> What do I do next?
-
- Posts: 1
- Joined: 23 May 2009, 23:00
Re: OL2003/Vista/mapi32.dll fix didn't work!
Being a little impatient, I carried on digging. The trick to deleting
mapi32.dll (so that I could replace it with a working mapi32.dll from
another Vista+Office2003 installation) is to *change specific file
permissions*.
(If you're taking my route, copy mapi32.dll from a working
Vista+Office2003 system and put it on a flash drive / network drive /
whatever you like)
- Right-click on *mapi32.dll*
- Select *Properties *and then the *Security *tab
- Click *Edit *button
- Click *Add *button
- Enter a username in the box "*Enter the object names to select*" -
i.e. your own
- Click on *Check names* to be sure you got it right and then OK
- With the newly added user selected in the 'Group or user names'
list, check *Allow *for *Full Control*
- Click *Apply *and then *OK *(probably OK will do, but I was so
annoyed by now I didn't want to take any chances!)
- Reboot (again, probably not needed, but I did it just to be sure)
- Find mapi32.dll and rename to MAPI32.CORRUPT (again, me being
pedantic; you could probably just delete it)
- Copy to the same location the mapi32.dll that you prepared
earlier.
I rebooted again and started Outlook and EUREKA! It works just fine
now.
The replacement file has the proper level of protection (i.e. noone but
TrustedInstaller has full control), so I haven't left a gaping security
problem on the file I'm using.
b.
--
thingummijig
mapi32.dll (so that I could replace it with a working mapi32.dll from
another Vista+Office2003 installation) is to *change specific file
permissions*.
(If you're taking my route, copy mapi32.dll from a working
Vista+Office2003 system and put it on a flash drive / network drive /
whatever you like)
- Right-click on *mapi32.dll*
- Select *Properties *and then the *Security *tab
- Click *Edit *button
- Click *Add *button
- Enter a username in the box "*Enter the object names to select*" -
i.e. your own
- Click on *Check names* to be sure you got it right and then OK
- With the newly added user selected in the 'Group or user names'
list, check *Allow *for *Full Control*
- Click *Apply *and then *OK *(probably OK will do, but I was so
annoyed by now I didn't want to take any chances!)
- Reboot (again, probably not needed, but I did it just to be sure)
- Find mapi32.dll and rename to MAPI32.CORRUPT (again, me being
pedantic; you could probably just delete it)
- Copy to the same location the mapi32.dll that you prepared
earlier.
I rebooted again and started Outlook and EUREKA! It works just fine
now.
The replacement file has the proper level of protection (i.e. noone but
TrustedInstaller has full control), so I haven't left a gaping security
problem on the file I'm using.
b.
--
thingummijig
Re: OL2003/Vista/mapi32.dll fix didn't work!
My son tried installing Office 2007 on my new computer. The new
computer is running Vista. But Office 2007 did not actually install.
And none of the Office programs were working. So I reinstalled Office
2003. All the 2003 programs worked EXCEPT for Outlook. I also was
receiving the error message...
*_Cannot_start_Microsoft_Office_Outlook._MAPI32.DLL_is_corrupt_or_the_wrong_version._This_could_have_been_caused_by_installing_other_messaging_software._Please_reinstall_Outlook._*
**
I uninstalled Office 2003 and reinstalled it - still received the error
message. I searched for hours and tried renaming the MAPI32.DLL etc but
it did not work.
**
The fix that I found that worked for me was so easy!
I opened Microsoft Word - then clicked on Help in the Menu Bar. From
there I clicked on Detect and Repair. I left the box checked beside of
Restore my shortcuts while repairing. Then I clicked the Start button.
Voila! Microsoft Outlook 2003 is now back up and running! :party:
--
snave613
computer is running Vista. But Office 2007 did not actually install.
And none of the Office programs were working. So I reinstalled Office
2003. All the 2003 programs worked EXCEPT for Outlook. I also was
receiving the error message...
*_Cannot_start_Microsoft_Office_Outlook._MAPI32.DLL_is_corrupt_or_the_wrong_version._This_could_have_been_caused_by_installing_other_messaging_software._Please_reinstall_Outlook._*
**
I uninstalled Office 2003 and reinstalled it - still received the error
message. I searched for hours and tried renaming the MAPI32.DLL etc but
it did not work.
**
The fix that I found that worked for me was so easy!
I opened Microsoft Word - then clicked on Help in the Menu Bar. From
there I clicked on Detect and Repair. I left the box checked beside of
Restore my shortcuts while repairing. Then I clicked the Start button.
Voila! Microsoft Outlook 2003 is now back up and running! :party:
--
snave613