[spambayes-bugs] [ spambayes-Bugs-983539 ] Install error on Outlook 2002

[SourceForge.net]

Bugs item #983539, was opened at 2004-07-02 05:04
Message generated for change (Comment added) made by anadelonbrin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=983539&group_id=61702

Category: Outlook
Group: Binary 1.0rc2
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Taed Wynnell (taed)
Assigned to: Mark Hammond (mhammond)
Summary: Install error on Outlook 2002

Initial Comment:
When I installed 1.0 RC 2, I got an installation error.  
When I then loaded Outlook, SpamBayes seemed to load 
and displayed the buttons, but the SpamBayes menu 
was non-functional (ignored click).

I'm running Outlook 2002 (with all updates) on my 
Windows NT 4.0 Server (with all updates).  I've tried 
installing it multiple times (and rebooting and so on), but 
no luck.  Re-installing 1.0 RC 1 will then work fine.

Here's the outlook_addin_register.exe.log file contents:

Traceback (most recent call last):
  File "addin.py", line 40, in ?
  File "win32gui.pyc", line 9, in ?
  File "win32gui.pyc", line 7, in __load
ImportError: DLL load failed: The specified procedure 
could not be found.
Traceback (most recent call last):
  File "addin.py", line 40, in ?
  File "win32gui.pyc", line 9, in ?
  File "win32gui.pyc", line 7, in __load
ImportError: DLL load failed: The specified procedure 
could not be found.



----------------------------------------------------------------------

>Comment By: Tony Meyer (anadelonbrin)
Date: 2004-12-16 12:29

Message:
Logged In: YES 
user_id=552329

Fantastic :)  The poster today probably has 1.0, then.  I'll
close this as fixed, then.

Thanks for the update!

----------------------------------------------------------------------

Comment By: Taed Wynnell (taed)
Date: 2004-12-16 12:15

Message:
Logged In: YES 
user_id=1025617

I'm the original submitter, and 1.0.1 did fix this problem for me 
on Windows NT, so as far as I'm concerned, this has been 
fixed.  (Thanks!)


----------------------------------------------------------------------

Comment By: Tony Meyer (anadelonbrin)
Date: 2004-12-16 12:12

Message:
Logged In: YES 
user_id=552329

I'm 99.9% sure that I used build 203 to create 1.0.1, so if
that was all it took, it ought to be fixed.  However, a
message to spambayes at python.org today indicated that maybe
it is not.  Possibly something else needs to be done?

----------------------------------------------------------------------

Comment By: Kenny Pitt (kpitt)
Date: 2004-10-13 04:21

Message:
Logged In: YES 
user_id=859086

It appears that build 203 of pywin32/win32all has split out
the XP-specific functions into a separate extension to
restore NT compatibility.  We will upgrade to build 203 for
the next SpamBayes build (probably either 1.1a1 alpha
release or 1.0.1 maintenance release), so hopefully that
will fix this problem.

Here are a couple bullets snipped from Mark's release
announcement:

* The win32gui, win32security, and win32service modules all
again work
  on Windows NT.
* New 'winxpgui' module - almost identical to win32gui, but
has a
  Windows XP manifest included, and a couple of extra
functions not
  supported by Windows NT (AnimateWindow, FlashWindowEx, etc)


----------------------------------------------------------------------

Comment By: Kenny Pitt (kpitt)
Date: 2004-09-29 09:18

Message:
Logged In: YES 
user_id=859086

Noting dupe in [ 1036551 ]

----------------------------------------------------------------------

Comment By: Kenny Pitt (kpitt)
Date: 2004-07-16 08:24

Message:
Logged In: YES 
user_id=859086

It seems that the problem is not a *call* to FlashWindowEx, 
but rather simply that FlashWindowEx appears in the import 
table of the win32gui.pyd DLL file and the import cannot be 
resolved on NT4.

This is an issue in the pywin32 extensions, and appears to 
have been introduced in build 202. Revision 1.42 of win32gui.i 
added the PyFlashWindowEx function that generates the 
offending import.

I'm assigning this to Mark to see if he can find a way to 
implement the FlashWindow function without generating a 
static import reference to the FlashWindowEx function 
(maybe LoadLibrary/GetProcAddress after an OS version 
check?).

----------------------------------------------------------------------

Comment By: pbarbour (pbarbour)
Date: 2004-07-10 08:11

Message:
Logged In: YES 
user_id=1080518

likely due a call to the FlashWindowEx() function which is not 
supported in NT4.  This error occured on my NT4 workstation 
also.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=983539&group_id=61702