Hi!
> Carl Evans wrote:
I am running 32bit Python 2.7 on 64bit excel
Warning! 64 bits Excel have not the same CLSID than 32 bits Excel.
If it run in tests/dev. with 32 bits Excel, try to install a 32 bits
Office on the production computer.
MS himself advises to prefer the 32-bit version.
@-
Carl Evans wrote:
> Yea I know. It worked fine when testing, I had it set up on task scheduler
> when it stopped working u expectedly.
Aha! I should have asked that earlier. I can explain this.
By default, processes running under Task Scheduler run as the
LocalSystem user, not as the logged in
Carl E. Evans wrote:
> I can open excel fine with no issues. Its a full 64bit edition, so no
> trial or anything. Also, when I run the script, this error occurs in
> about 2 seconds, so not waiting for any sort of time out.
Very odd. Has this EVER worked for you? You aren't trying to run this
fr
You might consider double-checking your message subjects before
responding. That's especially important when you read the digest.
Blair Hall wrote:
>
> Can you show us your manifest?
>
>
> Thanks for taking a look.
>
> I have put the contents of the manifest file at the bottom of this post:
>
Carl Evans wrote:
>
> I am trying to dipatch excel using the win32com library but for some
> reason am running into an issue. I have the following code:
The obvious question is, do you have Excel installed?
That error (80080005) means that the COM server app (Excel, in this
case) did not start up
