#546 Error after install ActivePython (ActiveState)

[Ingolf Steinhardt]

Hi,
after installing the ActiveState ActivePython Version
ActivePython-2.3.2-232-win32-ix86 start Outlook with
the Error (translate from German):
"Dont find the procedur springpoint ?
PyCom_SentAnCOMErrorFromPyException@@YAJPBDABU_
GUID@@@Z in the DLL pythoncom23.dll"

The Logfile:
Error connecting to Outlook!
Traceback (most recent call last):
File "addin.pyc", line 1191, in OnConnection
File "manager.pyc", line 908, in GetManager
File "manager.pyc", line 344, in __init__
File "manager.pyc", line 492, in LocateDataDirectory
File "win32com\shell\shell.pyc", line 9, in ?
File "win32com\shell\shell.pyc", line 7, in __load
ImportError: DLL load failed: Die angegebene Prozedur
wurde nicht gefunden.
ERROR: 'There was an error initializing the SpamBayes
addin\r\n\r\nPlease re-start Outlook and try again.'
Traceback (most recent call last):
File "addin.pyc", line 1191, in OnConnection
File "manager.pyc", line 908, in GetManager
File "manager.pyc", line 344, in __init__
File "manager.pyc", line 492, in LocateDataDirectory
File "win32com\shell\shell.pyc", line 9, in ?
File "win32com\shell\shell.pyc", line 7, in __load
ImportError: DLL load failed: Die angegebene Prozedur
wurde nicht gefunden.
pythoncom error: Failed to call the universal dispatcher
Traceback (most recent call last):
File "win32com\universal.pyc", line 173, in dispatch
File "win32com\server\policy.pyc", line 322, in
_InvokeEx_
File "win32com\server\policy.pyc", line 608, in
_invokeex_
File "win32com\server\policy.pyc", line 542, in
_invokeex_
File "addin.pyc", line 1227, in OnStartupComplete
exceptions.AttributeError: 'NoneType' object has no
attribute 'never_configured'

My System:
WinXP SP1
Outlook 2000
SpamBayes 1.09a

by x-herbert

[Ingolf Steinhardt]

Screenshot

[Tony Meyer]

Logged In: YES
user_id=552329

This is a known issue with ActivePython and the latest
release of spambayes. Both the next releases of
ActivePython and of SpamBayes should fix this problem.

In good news, the next release (1.0b1) of SpamBayes may
very well make it out today, so you'll be able to grab that and
it should fix the problem. Stay tuned to the spambayes-
announce list (or the website, or whatever).