in reply to win32::ole and MS Office 2010 over cgi

Usually, Apache runs as service, and services are not allowed to interact with any desktop, neither console nor remote. So, the Word executable may start, but it won't be able to open a window, Windows actively prevents this. No window, no communication, no OLE. That are Windows' rules.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
  • Comment on Re: win32::ole and MS Office 2010 over cgi

Replies are listed 'Best First'.
Re^2: win32::ole and MS Office 2010 over cgi
by wal77 (Novice) on Feb 04, 2012 at 21:06 UTC
    But it works with Windows Server 2003 and Office 2003
[reply]
      I'm not familiar with Server 2008 OR Office 2010...buuut...you might check a couple of things. First, if you installed Office with VBA, check the docs for changes. Running Office from VBA should be almost identical from running it via Perl and OLE, but for some syntax changes. You probably know that a quickstart to automating a task in Office is creating a VBA macro, and then translating it to Perl. Anyway, another possibility is that it's not Word.Application anymore. It's only a shot in the dark, but I hope it helps.

      --marmot

[reply]

        But it works using the command line or Perl editor, even I tested the script sceduled under the same privileged user as Apache service runnung. All is OK. CGI is the problem.

[reply]

      But it works with Windows Server 2003 and Office 2003

      Microsoft actively improves windows and office, check the changes files on msdn

[reply]

In Section Seekers of Perl Wisdom