Windows Server 2003 R2 - Caught Exception

[Antarias]

C:\OpenEMM>setup.bat
Starting up .. home is C:\OpenEMM .. found codebase .. CAUGHT EXCEPTION:
Traceback (most recent call last):
File "C:\OpenEMM\bin\openemm.py", line 61, in <module>
addpath (agn.pythonpath)
AttributeError: 'module' object has no attribute 'pythonpath'

Any Ideas?

Server 2003 R2 SP2
Python 2.5 - isntalled
MySQL-python-1.2.2.win32-py2.5.exe - installed
jdk1.6.0_02 - installed

Enviroment Variables
PATH C:\Sun\SDK\bin;%PythonPath%
PythonPath C:\Python25

[Antarias]

http://www.activestate.com/Products/activepython/

I uninstalled Python and installed the prepackaged version of Python from ActiveState. The installation was smooth as butter.

[ud]

Antanias, looks like OpenEMM does not recognize your system as a Windows. Can you prove this by starting an interactive python shell and type these commands:

Code: Select all

import platform
print platform.system ()

and copy the answer? Perhaps Python behaves different on Windows Server 2003 (I have no access to all possible windows derivates here).

-- ud

[Antarias]

The result of the executed code is:

Windows

However my previous post should have been clearer. After installing Activestate Active Python, instead of Python from the official Python website, the installation of OpenEMM went great. The Windows installation is fresh. The system is working great and VERY, VERY fast. I suspect I didn't have the environment variables set correctly, as Activestate does that automatically. When I get a chance I will try and reproduce the problem and find out what went wrong. Ill keep this thread updated for others.

FYI Hardware Specs:

Dell PowerEdge 2400
Dual Xeon 2.6Ghz. @ 400Mhz FSB
4GB RAM DDR ECC
RAID 1 - 2 - 15K Hitachi Drives

I run an application development company and have never considered using Python, much less MySQL. We are a MicroCough company and use MSSQL/VB.NET for projects. However since the installation of this software and with my review of the Python language combined with Java, I am very interested in experimenting.

Thanks for your reply.

Antarias

[Antarias]

When Python 2.5 is installed (not the activestate version) the

Code: Select all

print platform.system()

command produces the following output:

Microsoft

I am sure the enviroment variables are set correctly. I get the same error as before:

C:\OpenEMM>setup.bat
Starting up .. home is C:\OpenEMM .. found codebase .. CAUGHT EXCEPTION:
Traceback (most recent call last):
File "C:\OpenEMM\bin\openemm.py", line 61, in <module>
addpath (agn.pythonpath)
AttributeError: 'module' object has no attribute 'pythonpath'

when I run setup.

So the question is why does the OpenEMM setup work flawlessly when ActiveState Python is installed but not when normal Python is installed?

[Antarias]

Reinstalled ActiveState Python and boom. OpenEMM works great.

FYI: For any Windows users out there, REBOOT constantly.

[the182guy]

Thanks for the info. Had the same problem with my windows 2003 server. Getting the active python package fixed it!