o you have appropriate Python version on your computer? Is it in your PATH?
The installer takes care of this but these could have been altered.
Close all instances of Excel, kill the pfeControlShell process from Windows
Task Manager, kill all orphaned Excel processes and run the installer again.
If the problem persists then contact me at kaslanidi@yahoo.com. I will help
you free of charge. I would need the ErrorLog files described in the next
paragraph.
The Python For Excel creates a PythonForExcel folder in your user's directory.
On Windows Vista such directory is located in c:\Users\<User Name>. On
Windows XP such directory is located in c:\Documents and Settings\<User
Name>. After an attempt to start the ControlShell such PythonForExcel
folder will be filled with files. See the picture below.
Some of these files may be non-empty and contain a helpful error message.
Under some scenarios there may be a need to check that the COM components are
properly registered. This could be done with MS COM Object Browser or MS
OLE/COM Object Viewer.
Right click on every one of the Ots_pfe* objects and see if you can "Create
Instance" without generating an error message. Such test would also verify
that the immediate binary dependencies are all present and accessible via the
PATH.
|
