gapi32.dll .....

[Richard Keirle]

Can anyone tell me what this file is for, and more importantly why it should
have disappeared from my disk. I think it's to do with OE ,and can i just
drop it into the \windows\system32 folder ?

regards, Richard

 

[S.Sengupta]

Hi!Richard!
http://support.microsoft.com/default.aspx?scid=kb;en-us;320550
it can be copied from your office cd.
regards/

 

[Stock]

-----Original Message-----
Can anyone tell me what this file is for, and more importantly why it should
have disappeared from my disk. I think it's to do with OE ,and can i just
drop it into the \windows\system32 folder ?

regards, Richard

YES YOU CAN!
This dll was missing in my machine the other day. I
downloaded it and put it into system32 AND system to make
sure. So far all perfect again!

 

[R. C. White]

Hi, Richard.

It's a well-known Symantec problem. It's been there for years; I'm
surprised and disappointed they haven't bothered to fix it.

Just search Google for gapi32 and you'll find lots of hits, including this
one:
WinDoctor cannot fix the error "'C:\WINNT\System32\MAPISRVR.EXE' cannot
access a necessary file 'Gapi32.dll'"
http://service4.symantec.com/SUPPORT/nunt.nsf/pfdocs/2000122906113009

RC

 

[My Name]

Yes it is a Symantec problem........most of the time you will find that it
is not actually missing, it is just not in the file that symantec wants it
to be in. Try Search to find out for sure that you don't already have the
dll that you can copy past to the needed folder.

 

[Crusty \(-: Old B@stard :-\)]

It is NOT a Symantec problem. When installing Office 2000, a entry is placed
into the registry that says this file has been copied into the System32
folder. Well, it does NOT happen. That is why WinDoctor finds the error. It
is Microsoft's error - not Symantec's!

 

[Bill Drake]

Agreed. And the way to solve the problem is to search for both the
gapi32.dll and mapi32.dll files on your Local Hard Disk. Use the
Search or Find function (depending upon Windows version).

You'll find the gapi32.dll file in the Mapi folder several sublevels down
in the Common Files structure. Copy the file into whatever system
folder contains the mapi32.dll file. (System on W9x and System32
on NTx) Rerun WinDoctor. Problem solved.


Note: The copy of the gapi32.dll file found on your system *may* be
updated by current or future Service Packs from Office Update.

To be sure you're running the proper version of the file, copy
the version found *on your hard disk* to the System or
System32 folder as appropriate.

Do not make the mistake of assuming the files on your product
CDs are immutable -- or the correct versions in all circumstances.
Patches and updates can and do update DLLs without notice.




Best I can do for now. <tm>


Bill




"Crusty (-: Old B@stard "

 

[John E. Carty]

I wonder why Symantec accepts the blame:

Tell WinDoctor to ignore the error
Because this appears to be a problem with WinDoctor, and not with the
Microsoft files mentioned, it is probably safe to simply ignore the problems
so WinDoctor will not keep detecting them.

<Quoted from
http://service4.symantec.com/SUPPORT/nunt.nsf/pfdocs/2000122906113009>