I am trying to open a word document via PHP but the script always stops here $this->handle = new COM("word.application") or die("Unable to instanciate Word"); <-- the object fails to initializeThe program fails to initialize the object. I am guessing tha tit is a permission issue with the COM object. My question is how do I change the permission of the win2::ole object. It works on my windowxp machine because of little or no security restrictions but not on a dedicated server with windows 2003. Fatal error: Uncaught exception 'com_exception' with message 'Unable to lookup `Documents': Call was rejected by callee. ' in C:\Inetpub\vhostshttpdocs\word\clsWord.php:34 Stack trace: #0 C:\Inetpub\vhostshttpdocs\word\clsWord.php(34): clsMSWord::Open() #1 C:\Inetpub\vhosts\gethttpdocs\word\index.php(8): clsMSWord->Open('C:\1.doc') #2 {main} thrown in C:\Inetpub\vhosts\gethttpdocs\word\clsWord.php on line 34

Hello, This seems a known issue relating to Automation of Office on server-side components. I just quote the following information. Please take a look at this to see if it applies to your situation: "Developers can use Automation in Microsoft Office to build custom solutions that use the capabilities and the features that are built into the Office product. Although such programmatic development can be implemented on a client system with relative ease, a number of complications can occur if Automation takes place from server-side code such as Microsoft Active Server Pages (ASP), ASP.NET, DCOM, or a Windows NT service. " "All current versions of Microsoft Office were designed, tested, and configured to run as end-user products on a client workstation. They assume an interactive desktop and user profile. They do not provide the level of reentrancy or security that is necessary to meet the needs of server-side components that are designed to run unattended." The detailed information are documented in the following article: Considerations for server-side Automation of Office: http://support.microsoft.com/kb/257757/ You can change the default behavior to allow Automation Office applications to run under the interactive user account. Note that, Office was not designed, and is not safe, for unattended execution on a server. Developers who use Office in this manner do so at their own risk. The detailed steps about how to do it is listed in the following article: How to configure Office applications to run under the interactive user account: http://support.microsoft.com/kb/q288366/ Hope this can be of help. Best regards,Chang Yin