OfficeWriter Documentation
.
OfficeWriter v8 Docs
Page tree
ConfigureSpace tools

Versions Compared

Old Version 8

changes.mady.by.user Alison Bird [softartisans]

Saved on

compared with

New Version Current

changes.mady.by.user Gabe Goodwin [softartisans]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

Jump

...

to:

...

...

Anchor
ssrs
ssrs

Anchor
ssrs_auto
ssrs_auto

Automatic Installation

...

Introduction

The OfficeWriter 8 installer is available in 64-bit (OfficeWriter-Installer-8.#.#-x64.msi) and 32-bit (OfficeWriter-Installer-8.#.#-x86.msi). The bitness refers to the bitness of the operating system, not the version of SQL Server Reporting Services.

There is a single OfficeWriter installer that that handles installing any configuration of OfficeWriter, regardless of which edition (SE or EE) or components (ExcelWriter, WordWriter, SSRS integration) you have purchased.

Running the Installer

  1. Check that your system meets the [System Requirements]. You MUST

    have

     have SQL Server Reporting Services installed on the machine that you are trying to install OfficeWriter for SSRS. If SSRS is not detected, it will not be available as a custom setup option.

    #

  2. The OfficeWriter for SSRS integration requires modifying several SSRS config files and adding DLLs to the bin directory. To ensure a stable installation, STOP

    the

     the SQL Server Reporting process before installing OfficeWriter.

  3. #

    Double click the msi to begin installing OfficeWriter for .NET:

    !welcome_ow.png!

    Image Added

    Note

    If you have a previous version of OfficeWriter installed, you may be prompted to upgrade or remove the existing version of OfficeWriter. We recommend that you follow the steps to remove the previous version of OfficeWriter before continuing with your installation.

    #

  4. Click Next

    to

     to proceed to the End-User License Agreement.

    #

  5. Read the End-User License Agreement and click Next

    when

     when finished.

    !EULA_ow.png!
    # Click Next to

    Image Added 

  6.  Click Next to proceed to the license key entry.

    #

  7. You will be prompted for a license key. Enter a license key into the box and click

    Check Key

    Add Key.

    {
    Note
    :
    title
    =
    Where to find your license key
    }

    If you are evaluating, your 30-day OfficeWriter EE license key was sent in your evaluation e-mail.

    If you have purchased the product, you can find your license keys:
     - In the original order confirmation e-mail
    - On the OfficeWriter site

...

  1. . You will need to log in with the credentials that were used to purchase the product. These credentials are also available in the original order confirmation e-mail.

...

  1. Image Added

  2. The installer will confirm what edition (Standard or Enterprise) and product the license key is.  Multiple license keys can be entered at this step. Click Next to proceed to the custom setup options.
    Image Added 

  3. You will need to select the components to install. To include or exclude any components from your installation, click on the drop-down next to the component. Click *Next* when done.
    Image Added 

  4. The destination folder is where the OfficeWriter assemblies and utilities will be unpacked. By default, the destination folder will be C:\Program Files\SoftArtisans\OfficeWriter. Click Next when done.
    SSRS-specific assemblies will be unpacked to a subfolder called Reporting Services.
    Image Added 

  5. The installer will attempt to locate any instances of SQL Server Reporting Services on the machine. Select the installation to add OfficeWriter to.

  6. You will also be given the option to unpack the original OfficeWriter Designer installer to the destination folder. This is recommended. Click Install when done.
    Image Added 

  7. The OfficeWriter installer requires administrative privileges to write the license key to the registry. On Windows Vista and above, depending on your UAC settings, you may be prompted for UAC elevation during the installation process.
    Image Added

  8. Click Finished to exit the installer.
    Image Added 

  9. START the SQL Server Reporting Services process to complete the installation process.

Anchor
ssrs_manual
ssrs_manual

Manual Installation

Installation Files

The following files are unpacked to the destination folder selected during the automatic installation process and are needed for the manual installation process.

Installation Files

ProductFileDescription
ExcelWriter

SoftArtisans.OfficeWriter.ExcelWriter.dll

  • .NET ExcelTemplate object 
  •  .NET ExcelApplication object (EE only)
WordWriter

SoftAartisans.OfficeWriter.WordWriter.dll

  • .NET WordTemplate object

  • .NET WordApplication object (EE only)

Reporting Services Integration

SoftArtisans.OfficeWriter.SSRS2008.dll or

SoftArtisans.OfficeWriter.SSRS2005.dll

  •  SSRS integration assembly for SSRS 2012/2008 (R2) or SSRS 2005
 License Manager LicenseManager.exe Manage, add, and remove license keys for OfficeWriter.

Installing OfficeWriter for SSRS

Note
titleAbout SSRS 2012 with SharePoint Integration

 There were some significant infrastructure changes made for SSRS 2012 in SharePoint integration mode that require a different manual installation process than from native mode. Please see Installing for SSRS 2012 with SharePoint for more details.

  1. Run the OfficeWriter installer on another machine with SQL Server Reporting Services to unpack the necessary installation files (see above).

    #

  2. Make sure that your system meets the System Requirements.

    #

  3. Installing OfficeWriter for SSRS requires

    mondifying

    modifying several SSRS config files and dropping DLLs in the bin directory. STOP

    SQL

     SQL Server Reporting Services process before installing OfficeWriter.

  4. #

    Copy the following files to <MSSQL Directory>\Reporting Services\ReportServer\bin

    1. SoftArtisans.OfficeWriter.RS2005.

    dll

    1. dll (for Reporting Services 2005) or SoftArtisans.OfficeWriter.RS2008.dll (for Reporting Services 2008 or Reporting Services 2012)

    2. SoftArtisans.OfficeWriter.WordWriter.dll

    3. SoftArtisans.OfficeWriter.ExcelWriter.dll

    .


  5. #

    Run LicenseManager.exe

    to

     to install the OfficeWriterEE or OfficeWriterSE key

    .

    #

  6. Modify the RSReportServer.config

    file

     file in <MSSQL Directory>\Reporting Services\

    ReportServer

    ReportServe*. Copy the following report rendering extension declaration to the file's <Render>

    node

     node:
    For Reporting Services 2005:

    {newcode:language=xml}
    <Configuration>
    <Extensions>
    <Render>
    <Extension
    Code Block
    languagexml
    <Configuration>
  <Extensions>
    <Render>
      <Extension Name="XLTemplate" Type="SoftArtisans.OfficeWriter.ReportingServices.ExcelTemplateRenderer,

    
          SoftArtisans.OfficeWriter.RS2005"/>

    <Extension 
    
      <Extension Name="WordTemplate" Type="SoftArtisans.OfficeWriter.ReportingServices.WordTemplateRenderer,

    
          SoftArtisans.OfficeWriter.RS2005"/>

    
    </Render>

    
  </Extensions>

    
</Configuration>
    Code Block

    For Reporting Services 2008 or 2012:

    {
    Code Block
    :
    languagexml
    }
    <Configuration>

    <Extensions>
    <Render>
    <Extension 
    
  <Extensions>
    <Render>
      <Extension Name="XLTemplate" Type="SoftArtisans.OfficeWriter.ReportingServices.ExcelTemplateRenderer,

    
          SoftArtisans.OfficeWriter.RS2008"/>

    <Extension 
    
      <Extension Name="WordTemplate" Type="SoftArtisans.OfficeWriter.ReportingServices.WordTemplateRenderer,

    
          SoftArtisans.OfficeWriter.RS2008"/>

    
    </Render>

    
  </Extensions>

    
</Configuration>
    code
    Note
    \{note}

    You

    will

    likely

    already

    have

    Extension

    elements

    in

    your

    Render

    node.

    You

    should

    only

    need

    to

    copy

    the

    Extension

    element

    lines

    below

    your

    existing

    Extension

    elements

    in

    the

    Render

    node.

    {note} \# Modify the *

  7. Modify the rssrvpolicy.config

    * file in *<MSSQL

     file in <MSSQL Directory>\Reporting

    Services\ReportServer

    *

    .

    Add

    the

    following

    security

    trust

    codegroup

    to

    the

    file's

    *

    <CodeGroup>

    * node: \{code:xml}

     node:

    Code Block
    languagexml
    <configuration>
  <mscorlib>
    <security>
      <policy>
        <PolicyLevel version="1">
          <CodeGroup class="FirstMatchCodeGroup" version="1" PermissionSetName="Nothing">
            <CodeGroup class="UnionCodeGroup"
              version="*"
              PermissionSetName="FullTrust"
              Name="SoftArtisans_OfficeWriter_Strong_Name"
              Description="This code group grants SoftArtisans OfficeWriter code full trust.">
              <IMembershipCondition
                class="StrongNameMembershipCondition"
                version="*"
                PublicKeyBlob="00240000048000009400000006020000002400005253413100040000010001004779CB207F11
                5E86EF9DD3233F9F130F8891911345176650F72330F84CA3F54C96DEB08439680660F02872EEF5DA3955
                A14C63F96E57DFB71B1535280C37DA2CB5BA37D78A9882414DB11F67FD66DEBC4AD93DD34F4A587D34D
                B4D23D9C6AF83431D88A7EF42BB01082913F3560DCB50129C5BBA7ECA0DE8BC286DA74F58FADE"/>
            </CodeGroup>
          </CodeGroup>
        </PolicyLevel>
      </policy>
    </security>
  </mscorlib>
</configuration>
     {
     Note
    }
    You will likely already have the "FirstMatchCodeGroup" CodeGroup element in your Render node. You should only need to copy the innermost CodeGroup element (Name="SoftArtisans_OfficeWriter_Strong_Name").
     Note
     Warning
    The PublicKeyBlob value should be in one line. When you copy the lines above to *rssrvpolicy.config*, remove the line breaks within the PublicKeyBlob.
  8. To install the samples, upload the RDL files in OfficeWriter\ReportingServices\Samples
     to 
     to the Reporting Server using Report Manager.