Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Word / Programming / May 2004

Tip: Looking for answers? Try searching our database.

Microsoft Word Development on Web Server

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jon Ebersole - 31 May 2004 18:11 GMT
I am creating an application that creates Microsoft Word Documents on the fly for the user.  I have developed this as a web page, and tested it on my machine.  It works fine, but when I publish the page to the server, it won't work.  I have Microsoft Office 2003 installed on my machine, but no Office products installed on the server.  My assumption was that the deployment package I created would package all the necessary dependencies to allow the project to run on the server.  It doesn't seem to be the case.  I am getting errors that certain classid's aren't registered.  Usually this means that the Office isn't installed (which is true in this case of course).  My question is; Is it necessary to install Microsoft Office 2003 on the server, or can I just package the necessary DLL's

Thank you in advance for your assistance

Jon Ebersole
Peter Hewett - 31 May 2004 23:02 GMT
Hi Jon Ebersole

I'm not sure you can do what you want, I've never tried it.  But if you can you'll
obviously need Office installed.  Just packaging the DLLs wont do it as they wont be
correctly registered, plus you need a license for Office for the Server.

Office requires a user context (account).  The first time you use Office you need to start
it manually so that it is initialised correctly.

HTH + Cheers - Peter


Jon Ebersole <jon@compdevsys.com>, said:

>I am creating an application that creates Microsoft Word Documents on the fly for the user.  I have developed this as a web page, and tested it on my machine.  It works fine, but when I publish the page to the server, it won't work.  I have Microsoft Office 2003 installed on my machine, but no Office products installed on the server.  My assumption was that the deployment package I created would package all the necessary dependencies to allow the project to run on the server.  It doesn't seem to be the case.  I am getting errors that certain classid's aren't registered.  Usually this means that the Office isn't installed (which is true in this case of course).  My question is; Is it necessary to install Microsoft Office 2003 on the server, or can I just package the necessary DLL's?
>
>Thank you in advance for your assistance.
>
>Jon Ebersole
Jay Freedman - 31 May 2004 23:08 GMT
Hi Jon

I think you need to read http://support.microsoft.com/?id=257757,
which strongly discourages using Word in a server role.

>I am creating an application that creates Microsoft Word Documents on the fly for the user.  I have developed this as a web page, and tested it on my machine.  It works fine, but when I publish the page to the server, it won't work.  I have Microsoft Office 2003 installed on my machine, but no Office products installed on the server.  My assumption was that the deployment package I created would package all the necessary dependencies to allow the project to run on the server.  It doesn't seem to be the case.  I am getting errors that certain classid's aren't registered.  Usually this means that the Office isn't installed (which is true in this case of course).  My question is; Is it necessary to install Microsoft Office 2003 on the server, or can I just package the necessary DLL's?
>
>Thank you in advance for your assistance.
>
>Jon Ebersole

--
Regards,
Jay Freedman
Microsoft Word MVP        FAQ: http://www.mvps.org/word
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.