One of my coleagues has recently been working on a module that uses the easyPDF .Net component to convert Word 2000 documents to PDF format. He had evaluated many third party components and easyPDF seemed to offer the best performance, was straightforward to implement and not too expensive.
Everything was going well, the module deployed successfully to a windows 2000 server and processed several thousand documents in our test enviroment.
The next step was to ship the server to our colocation facility, we were already running the server on the same domain via VPN so we were confident that this would be straightforward.
When we fired up the server at the colo the module which ran as an NT service started up it then started to produce a document and then it promptly froze and after 50 seconds a timeout error was written to the log. We were puzzled as to what could be causing this and spent the next few days trying to figure it out. To cut a long story short at the colocation facility we did not attach keyboard or a mouse to the server, when these were attached and the server was restarted our application started working!
MS do warn against using Word Automation but in this case we didn't have any choice, we are looking forward to the release Office 12 and the native PDF output capability of Word.
UPDATE: Still not working after a reboot the dreaded freezing has come back! Will update if we figure it out.
Another Update: We have had no problems getting this working on desktop OS's like W2K Pro and XP Pro but on servers it is just hanging.