Here is the code I am using:

using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Runtime.InteropServices;
using System.Drawing;
using Microsoft.Office.Interop.Word;
using System.ComponentModel;
using System.Windows.Forms;

public partial class WordTest : System.Web.UI.Page
{
   protected void Page_Load(object sender, EventArgs e)
   {
       try
       {
           object missing = Type.Missing;

           Microsoft.Office.Interop.Word.ApplicationClass oWordApp =
new Microsoft.Office.Interop.Word.ApplicationClass();
           oWordApp.Visible = true;

           Microsoft.Office.Interop.Word.Document oWordDoc = new
Microsoft.Office.Interop.Word.Document();
           object oTemplate = "C:\\BOL.dot";
           oWordDoc = oWordApp.Documents.Add(ref oTemplate, ref
missing, ref missing, ref missing);

           oWordDoc.Activate();
           object oBookMark = "shipperBOL";
           oWordDoc.Bookmarks.get_Item(ref oBookMark).Range.Text =
"Some Text Here";

       }
       catch (Exception exc)
       {
           errorLabel.Text += exc.Message;
       }

   }
}

-Ryan

Nope - it has nothing to do with that... It's simply that server-side Office
automation doesn't work because Office just wasn't designed to run in that
environment - Microsoft won't support any solution which even tries to use
it:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q257757#kb2

See the "MORE INFORMATION" section, particularly the bold paragraph...

If you need to manipulate Word documents server-side, you need this:
http://www.aspose.com/Products/Aspose.Words/Default.aspx

The COM object (in this case, Word) needs to be installed on the
server.  You can do this by installing Word/Office on the server.

This will work but I think they're encouraging people to use the
PIAs...

I'm showing off my noob newsgroup skills.  I just posted reply to the wrong
thread. This one is for Ryan.

This is kind of a random suggestion, but since the Office Interop works
better in a Windows environment, you might try setting up a Windows Service
that watches a database table for information about "jobs" to pickup. Make
it synchronous (only one job at a time because running Word COM is just like
using it manually; you can only edit one document at a time per Word
application). Let the service pickup jobs and generate the word docs for you
with the information submitted from the website. You can tag the job records
with some kind of status so you can see the status on the website. Then when
it's done, make the end result word doc available to the site via its
status.

Just an idea.  You also might check out using a third party utility like
Aspose (aspose.com) or TXTextControl Server (textcontrol.com) which will
give you an API to manipulate word docs without using Office COM to do it.
Then you could do it directly in the site or in a windows service easily.
But it comes with a cost.

Good luck!
-Nathan