Version 1.4.9 - November 5, 2007

Recognizes Shipper Service for StoreFront 7.0

Version 1.4.8 - October 18, 2007

This version is compatible with UPS WorldShip 9 for Vista. Several bugs were identified and fixed.

Release Notes

If you install Shipper 1.4.8, you must also install Shipper Service 1.4.8 on your web site.

Version 1.4.7 - May 15, 2007

This version is compatible with compatible with Endicia Galaxy Ship version 5.1 which in turn is compatible with the new USPS mail classes and rates that started on May 14, 2007.

Version 1.4.6 - May 8, 2007

This version includes minor updates from 1.4.1.

Version 1.4.1 - January 17, 2007

Shipper now supports UPS WorldShip 9.0. See the Version 1.4 release notes below if you are updating from Shipper 1.3.

Version 1.4 - November 25, 2006

New Carrier Support

Shipper now supports UPS WorldShip 9.0 beta 1 in addition to UPS WorldShip 8.0.

Shipper now supports Galaxy Ship 4.5. Shipper 1.4 will not integrate completely with previous versions of Galaxy Ship. You can download the latest version of Galaxy Ship from http://www.endicia.com/endicia-usa/hot/galaxyusersguide.cfm.

Shipper now imports the shipment Order Number to the DHL Reference field in DHL EasyShip Connect.

New Online Store Support

Shipper now supports BV Commerce 5 in addition to BV Commerce 2004 and StoreFront 6.0.

Two new fields are now included in the shipment data: OrderID and UserData. Using the OrderID, you can build a link to the order edit page of your site. Using the UserData field and an advanced filter, you can add your own custom field(s) to the shipment information which you can then export to your carrier software. See the new userdata.xslt sample in the Shipper Service xslts folder.

User Interface Enhancements

Two new print formats will help you prepare shipments: Pull Sheet and Pull Sheet Details. Pull Sheet lists the total number of each unique item in the selected shipments. Pull Sheet Details adds the individual quantities for each order including the quantity for each variation.

A new Display Count feature lets you decide how many shipments to include in the Print Preview. Previous versions of Shipper fixed this limit at 100 to ensure fast response time. You can now choose a value between 25 and all shipments. A new tool bar is displayed above the Print Preview Pane to make adjustments to Print Format and Display Count even easier.

Two new features now let you easily move shipments between folders:

Drag and drop shipments from the Shipments Pane to a folder in the Views Pane. For example you can drag a shipment from the UPS WorldShip folder to the Endicia Galaxy folder.
Select one or more shipments and then select Edit > Move to Folder from the Shipper menu or the shipments context menu.

Directly access Store Settings from the store's context menu or by selecting a store and then choosing Edit > Store Settings from the Shipper menu.

Send/Receive shipments from a single store by choosing Send/Receive Only from the store's context menu.

Previous versions of Shipper did not reflect changes made to a shipment in the store if the shipment was already prepared for carrier processing. Now a conflict will be generated with the changes identified so that you can decide if the changes affect how you want to process the shipment.

Release Notes

If you install Shipper 1.4 on your computer, you must also install Shipper Service 1.4 on your web site(s). Similarly, if you install Shipper Service 1.4 on your web site, then you must install Shipper 1.4 on your computer.
Shipper 1.4 will attempt to copy any custom print formats from previous versions of Shipper. However, this only works if Shipper can find them. If your custom print formats are not displayed in the File > Print Formats menu you will need to manually copy them to the new installation directory.
The new shipment fields (e.g. OrderID and UserData) will not appear in shipments that you have already prepared for processing. To force the new fields to appear select Tools > Options from the Shipper menu, then select the Application Data tab and click on the Delete Offline Data button. The new fields will be included the next time you run Send/Receive.
In Shipper 1.3.6, the IEmailHelper.SendMail method took an integer value as the first parameter. In Shipper 1.4, the first parameter is now a string.

Version 1.3.6.0 - July 26, 2006

Support for DHL EasyShip Connect

Follow these steps to configure Shipper to use DHL EasyShip Connect:

Install EasyShip Connect and complete the configuration steps described in EasyShip Connect Installation Guide.
Install DB Connect from the EasyShip Connect installation CD (find the DBConnect directory and run DBConnectSetup.msi).
Select Tools > Options from the Shipper menu.
Select the Carriers tab, select DHL EasyShip and then check Turn on integration with DHL EasyShip.
Enter the Shipper ID that you created when you installed EasyShip Connect.
Click on the OK button to save your changes.

To process shipments in DHL EasyShip Connect see Processing Shipments in DHL EasyShip Connect. Note that EasyShip Connect does not support batch processing.

If you created a custom print format, you may need to add some XSL to recognize the DHL carrier code. Open your custom print format file and search for this XSL:

<xsl:when test="$guid='D8C14CF8-DC37-401f-A770-A0C6A80E1AE7'">UPS</xsl:when>

If you find it, then you will need to add the equivalent XSL for DHL shown here:

<xsl:when test="$guid='B70850E4-26DA-466C-896A-BFA393547DEE'">DHL</xsl:when>

Support for Customized Confirmation Email

Customized Confirmation Email support is a feature of Shipper Service 1.3.6 and above. See Customizing the Confirmation Email for more information.

Version 1.3.4.0 - April 21, 2006

Galaxy Ship was recently updated to include printed address in the post-back data. This version of Shipper reads that address information and sends it back to your store. This means that if you edit or correct the address in Galaxy Ship, the new address will be sent to your store and recorded.

Version 1.3.3.1 - March 1, 2006

Time zone information removed from OrderDate and ShipmentShipDate to prevent date changes if Shipper and Shipper Service are run in different time zones.

No configuration change is required. Just install the new version of Shipper. Note that if you install Shipper 1.3.3.1, you should also install Shipper Service 1.3.3.1. If you don't, Shipper will report that every shipment changed every time you run send/receive. This is because the time zone information is included going one way (the send or receive) but not the other.

Version 1.3.3 - February 6, 2006

Resolves miscellaneous bugs that affect specific installations.

Version 1.3.2 - December 15, 2005

1437: Add Recipient ID to the FedEx Ship Manager import map

New Feature: Added Recipient ID as a field that is exported from Shipper to FedEx Ship Manager. This will let you store the recipient address (also called the Ship To address in Shipper) in the FedEx Ship Manager address book if you want. To select a value for the Recipient ID select Tools > Options from the menu. Then select the Carriers tab. Finally, select FedEx from the list of carriers and choose either Ship To Attention or Ship To Company for the value to be exported as the Recipient ID.

1409: Shipper 1.3.1.0: MergeInboxShipments: Input array is longer than the number of columns in this table.

Problem: Extra fields used to transfer carrier specific settings to FedEx Ship Manager and Endicia Galaxy Ship were causing an error to occur during refresh if shipments were waiting to be processed.

Fix: The extra fields are ignored during refresh.

1416: Shipper 1.3.1.0: AddShipmentToOutbox: This row has been removed from a table and does not have any data. BeginEdit() will allow

Problem: Using Quick Ship! to process multiple shipments in a carrier folder resulted in an error.

Fix: Changed the way multiple shipments are handled to remove timing issue.

1428: Shipper 1.3.1.0: GetOutboxShipments: Failed to enable constraints. One or more rows contain values violating non-null, unique, o

Problem: An error occurred during refresh if the same shipment was processed twice or more in FedEx Ship Manager without deleting the prior shipments.

Fix: Added code to detect and remove duplicate records. If a shipment is processed more than once in FedEx Ship Manager, Shipper will use the most recent information that Ship Manager recorded.

1439: FedEx service assigned in Ship Manager is not correct in Outbox

Problem: Shipper ignored the service that was actually used to process a shipment in FedEx Ship Manager, using the service that was assigned in Shipper instead.

Fix: The service that was actually used in FedEx Ship Manager is now correctly imported back into Shipper and sent to the underlying store.

Version 1.3.1 - December 1, 2005

NEW: Added support for Galaxy Ship 4.4.8 which has the ability to import Mail Class. You can now assign a mail class in Shipper and it will be imported to Galaxy Ship.
FIXED: The name of the cart remained blank in the tool tip that is displayed when you let the cursor hover over the name of a store in the Tools > Options window.
FIXED: Occasional errors were displayed when deleting a shipment from the Outbox.
FIXED: An "InvalidCastException" error was displayed when shipments without a tracking number were read from the Endicia Galaxy export table.
FIXED: Shipments without a tracking number were not removed from the Endicia Galaxy export table (the Outbox in Shipper).
FIXED: If a shipment was edited while in a carrier folder (such as changing the weight) and then processed, it did not appear in the Outbox after pressing Refresh. After the second Refresh the shipment moved to the Inbox. Both were symptoms of a single bug which has been fixed.

Version 1.3.0 - November 27, 2005

NEW: Support for Endicia Galaxy. Galaxy works with Endicia Dazzle to create and print postage and mailing labels for USPS mail. One click integration with Shipper uploads address and tracking information to your store, downloads pending shipments, and prepares them for processing with Galaxy and Dazzle. For more information about Endicia, please visit http://www.endicia.com.

The are two limitations in the integration with Galaxy Ship versus FedEx Ship Manager and UPS WorldShip.
- Galaxy Ship does not import the Mail Class (a.k.a. ShipmentService) so this must be selected in Galaxy Ship after importing the shipment.
- Galaxy Ship does not perform batch imports.
NEW: Shipper will automatically run refresh its view of the offline data (as if you pressed F5) every 30 seconds. The effect of this change is that the Outbox will always show the shipments you have processed with the carrier software. This will make it easier to print packing slips that include tracking information.
CHANGE: Shipper was changed so that you can choose the field you would like to use as the import key when processing shipments in the carrier software. The two choices are Order Number and Shipment ID. You can choose a different field for each carrier. The default (if no choice is made) is Order Number.

The selected field value is displayed in the Shipments pane where Shipment ID was displayed in previous versions. That means that if you choose to import using the Shipment ID field, the Shipments pane will not look any different. If you choose to import using the Order Number, then you will see the order number instead of the Shipment ID.

The UPS WorldShip import maps called "From Shipper by Key" and "From Shipper by Order" have been replaced by a single import map called "From Shipper" that uses the import key you choose in Shipper.

The FedEx Ship Manager profiles called "FromShipperByKey" and "FromShipperByOrder" have been replaced by a single profile called "FromShipper" that uses the reference field you choose in Shipper.
CHANGE: BillToName, ShipFromName, and ShipToName have been renamed to BillToCompany, ShipFromCompany, and ShipToCompany. If you created a custom print format in a previous release, you will need to change any references to the old names to use the new names.

Furthermore, in previous releases, ShipToName and ShipFromName were always non-blank. They were set equal to the company name if it existed, otherwise they were set equal to the full contact name. Now they are always set equal to the company name, which may be blank. This can be a breaking change for custom print formats and/or advanced filters that relied on ShipToName and ShipFromName always having a non-blank value. Please see Invoices.xsl and Packing Slips.xsl for examples of have to deal with the new treatment.

Version 1.2.3 - November 11, 2005

FIXED: Null reference exception when the list of shipping methods is displayed after all shipping methods have been assigned to carrier services. Now a message is displayed confirming that all shipping methods have been assigned.
FIXED: Application exception when launching the Shipper Service Configuration page by clicking on the Shipping Service URL link in Tools > Options. This error only occurs on computers running Windows 2000 Pro.
FIXED: Only one shipment is displayed in the Preview pane in some circumstances.
CHANGE: Additional web site errors are recognized so that an interpretive message can be displayed.

Version 1.2.2 - October 31, 2005

FIXED: Null reference exceptions when Shipper is closed by alerts are displayed.
FIXED: FedEx Ship Manager integration is disabled if export table contains non-Shipper data.
CHANGE: Integration with UPS WorldShip now checks that UPS WorldShip version 7 or higher is installed.

Version 1.2.1 - October 19, 2005

CHANGE: Removed OrderNumber field from UPS WorldShip export table. The Package::Reference 1 field in UPS WorldShip is filled with the shipment order number as a convenience. Reference 1 normally appears on the label. This change means that the reference field can be changed or even erased in UPS WorldShip.
CHANGE: FedEx Ship Manager requires Contact (ShipToAttention) but not Company. This is the reverse of UPS WorldShip. FedEx support changed to reverse ShipToAttention and ShipToName if only one is not blank. A future version of Shipper will rename ShipToName to ShipToCompany.
FIXED: ConfigureCarriers: Could not load type StructuredSolutions.Shipper.CarrierAccess.Wrapper.
FIXED: OnSendReceiveError: Cannot call Invoke or InvokeAsync on a control until the window handle has been created.
FIXED: TestStore_Click: NullReferenceException if the Test Store button is clicked when no store is defined. Now the button is disabled until a store is defined.

Version 1.2.0 - October 7, 2005

NEW: Support for FedEx Ship Manager.
- FedEx Ship Manager does not import the "Ship From" address (UPS WorldShip requires importing the "Ship From" address for batch processing). This means that the shipper address you set using Edit > Edit Shipper Addresses is ignored by FedEx Ship Manager.
- FedEx Ship Manager does not create an export record when a shipment is deleted (voided). This means that if you process a shipment in FedEx Ship Manager, run Shipper Send/Receive, and then delete the shipment in FedEx Ship Manager; the shipment will *not* be voided in the store by Shipper. You will have to manually void the shipment in your store.
NEW: Carrier service assignments (mappings) are based on the carrier and shipping method selected in the store rather than just the shipping method. This allows mapping UPS Ground to a different carrier than FedEx Ground for example.
NEW: You can now edit the shipment weight while the shipment is in the carrier's inbox and before importing to the carrier's shipment processor. This allows you to quickly edit all the shipment weight estimates and then process all the shipments in one batch.
NEW: The version of Shipper Service installed on your web site is recorded and displayed in Shipper > Tools > Options.
NEW: There is a new CSV print format (csv.xsl) that will create a list of comma separated values which you can save to a CSV file or copy and paste into another application. Most of the shipment information from each selected shipment is included in the CSV output. You can easily create custom CSV files by making your own print format based on csv.xsl with the fields that you want to include.
NEW: Export directly to Excel. Select Edit > Export to Excel from the menu. This will export all shipment information to an Excel workbook.
NEW: Quick Ship! now has two update options: 1) immediate, or 2) deferred to the next send/receive. Previously, Quick Ship! updates were always deferred to the next send/receive.
NEW: EXSLT namespace added to print format processing. This adds literally hundreds of well-defined functions to increase the power and flexibility of the print format templates. Packing Slips.xsl, Emails.xsl, and Invoices.xsl were rewritten to use the new data-time functions. One side benefit is that order dates are now automatically corrected for the time zone shift.
NEW: The Packing Slips.xsl and Invoices.xsl print formats now display HTML embedded in product name and code fields, as well as in the attribute and gift wrap text fields.
NEW: BillToAddress, ShipmentHandlingCharge, ShipmentTaxCharge, and ShipmentTotalCharge added to data so that a complete invoice can be printed. There is also a new Invoices.xsl print format that includes the new invoice fields.
NEW: Support for pen-based interaction such as with a Tablet PC.
CHANGE: Both Tools > Options and Tools > Options > Store Options were significantly rewritten to clarity and to allow for multiple carriers.
CHANGE: "Remove shipment from Inbox" command removed and "Delete shipment" command semantics changed. The delete command now removes the shipment from the corresponding folder.
CHANGE: ShipmentShipDate is now a date-time field. This will affect print templates that treat the ship date as a string.
CHANGE: The Print Preview pane will only display the first 100 selected shipments from the Shipments pane. This is meant to improve the responsiveness of the user interface when there are 100's of shipments.

Version 1.1.5 - September 28, 2005

FIXED: Can't access SelectionStart unless the Editor is in edit mode.
FIXED: Column 'StoreShipmentID, StoreName, ShipmentIsBackorder" is constrained to be unique.
FIXED: Column 'UPSShipmentTrackingNumber' does not belong to table Shipments.
FIXED: Object reference not set to an instance of an object in SaveShipperData.

Version 1.1.4 - September 6, 2005

FIXED: ConstraintException error occurs when new shipments are merged into local data.

Version 1.1.3 - July 28, 2005

FIXED: Shipper error displayed when web server has an internal processing error.
FIXED: PENDX SF-Static / Best-Way Ground does not show up in the list of methods that can be mapped to a carrier service.
FIXED: System.Data.RowNotInTableException after selecting a shipment in the Shipments pane.
FIXED: System.InvalidOperationException if required fields are renamed or removed from the import/export database. The database is now checked during startup and a message is displayed if one or more of the required fields are missing.
FIXED: Array index out of bounds error when quickly clicking on the scroll bar for the list of stores in the Options form (if there are 8 or more stores).
FIXED: Options form does not appear in UltraVNC client.
FIXED: Processed shipments are not removed from the Pending folder if multiple stores are defined and more than one store has processed shipments.

Version 1.1.1 - June 6, 2005

CHANGE: Added support for UPS WorldShip Batch Export function. Most recent shipment record (shipped or voided) is always used during send/receive.
CHANGE: Add new version of GetDateTime function to print formats that accepts an offset in minutes. The offset is added to the date/time before the date/time is formatted. This can be used to compensate for time zone differences between Shipper and Shipper Service. The new format is GetDateTime(date, offset, format). For example GetDateTime($date, 120, 'd').
FIXED: Conflict prompt is confusing when a processing error occurs on the server.
FIXED: Slow redraw during resize and paint
FIXED: Shipment carrier and method are not updated during conflict resolution in favor of local copy.
FIXED: Error when using Quick Ship!
FIXED: Unexpected error while activating license file.

Version 1.1.0.6 - May 1, 2005

CHANGE: Quick Ship! added to Edit menu.
FIXED: Multiple packages in one UPS WorldShip® shipment are incorrectly treated as duplicates.

Version 1.1.0.5 - April 15, 2005

NEW: Add View Source to Preview Pane menu to facilitate customizing print format templates.
CHANGE: Switched to a more efficient compression algorithm for another 2% gain.
FIXED: Wrong field selected in Packing Slips template.
FIXED: Error if synchronization finished exactly while Shipper is closing.
FIXED: Restricted data type attribute exception when using Quick Ship!.
FIXED: Quick Ship! can process a shipment that has already been processed by UPS WorldShip.
FIXED: Shipments that are processed multiple times in UPS WorldShip and then voided are not reconciled correctly.

Requires Shipper Service 1.1 final release or higher on each store.

Version 1.1.0.4 (RC5) March 29, 2005

NEW: PDF version of Shipper Tutorial for printing.
NEW: Send/Receive data compressed up to 90%.
CHANGE: Extended characters, and { and ~ are not allowed in store name.
CHANGE: List of shippers is disabled while retrieving ship-from address to prevent multiple requests from being queued.
CHANGE: Default online/offline mode changed to offline.
CHANGE: Shipper.mdb schema updated to record ShipmentCarrier and OrderNumber in outbox.
CHANGE: Store name is validated as it is entered to prevent invalid characters.
FIXED: Leading or trailing blanks in service username or password cause service access to fail.
FIXED: Leading or trailing blanks in service serial number cause service access to fail.
FIXED: Tutorial not found when Shipper is launched.
FIXED: Voided shipment carrier and order number are blank.
FIXED: Constraint exception on next refresh after a send/receive that includes only shipment voids.
FIXED: Format exception if store name includes a curly brace "{".

Requires Shipper Service 1.1 RC4 on each store.

Version 1.1.0.3 (RC4) March 14, 2005

CHANGE: Updated help to reflect Shipper 1.1 changes
NEW: Check UPS WorldShip import and export configurations during Shipper startup.
FIXED: Online status out of sync with configuration at startup.
FIXED: First send/receive is delayed when started in online mode.
FIXED: Error report is hidden behind Shipper.
FIXED: Auto processing options are confusing.
FIXED: Underlying connection closed if proxy server changed.
FIXED: Missing word on Shipper Store Options form.
FIXED: Toggling Show Unpaid check box on Shipments Pane changes selected store.

Version 1.1.0.2 (RC3) March 3, 2005

FIXED: Stores appear in random order.
FIXED: Shipments Pane loses focus.
CHANGE: Shipment groups expanded by default.
FIXED: Shipments reset after each send/receive.
FIXED: Select store changed when print format changed.
FIXED: Print format change is sometimes lost.
CHANGE: Removed check for update.

Version 1.1.0.1 (RC2) February 16, 2005

NEW: Page header and footer are no longer included in print.
CHANGED: Shipper Service file name is no longer required during setup.
CHANGED: Faster shutdown when there are many pending shipments.
CHANGED: Minor UI changes.
FIXED: Some phone numbers caused an error during print.
FIXED: Occasional invalid "Invoke" during startup.
FIXED: Occasional null reference error during print.
FIXED: Occasional null reference error if shipment information changed between send/receive.

Version 1.1.0.0 (RC1) February 8, 2005

NEW: Supports UPS WorldShip® batch importing.
NEW: Supports BVC2004.
NEW: Optionally include drop shipments.
NEW: Optionally exclude direct shipments.
NEW: Filter by drop shipper.
NEW: Edit ship-from addresses for store and drop-shippers.
NEW: Quick Ship! feature to bypass UPS WorldShip® (for example to use FedEx).
NEW: Shipment pre-processor (XSLT) to filter or modify shipment information on the fly.
NEW: Print formats (without Structured Solutions's logo).
NEW: Print preview function.
NEW: IE page headers and footers are removed.
NEW: Built-in security to prevent hijacking shipment information.
NEW: Exclude stores from Send/Receive All.
NEW: Hide weight from UPS WorldShip if using an electronic scale.
NEW: Configure UPS Billing option.
NEW: Configure UPS Package type.
CHANGE: Faster user interface.
CHANGE: Easier to find and edit print formats.
CHANGE: Separate installers for Shipper and Shipper Service. The integrated installer in Shipper was removed.
FIXED: Errors during startup if run from a different user than installer.

Special Notes for Upgrading from Shipper 1.0 to Shipper 1.1

Shipper 1.0 and Shipper 1.1 can be installed side-by-side. That means that both versions can be installed on the same computer without conflict. They do not interact after installation, so one will not be aware that you are processing shipments in the other.
If Shipper 1.1 finds the Shipper 1.0 configuration file, it will be copied to Shipper 1.1 and converted to the new format automatically. You will need to fill in 2 new settings for each store: the Shipper Service 1.1 Serial Number and the Shipper Service username and password. See Defining a Connection to Your Store or Create a Connection to Your Store in the tutorial for details.
Print formats in Shipper 1.1 are stored in the Print Formats directory of the installation folder. Print formats in Shipper 1.0 were stored in the C:\Documents and Settings\USERNAME\Application Data\Structured Solutions\Shipper for UPS 1.0\Templates directory. Please copy your customized print formats to the new directory.
The shipments data schema was changed in Shipper 1.1 This will affect custom print formats that you copy from Shipper 1.0 to Shipper 1.1. Please review your custom print formats to ensure their compatibility with Shipper 1.1. There is a new print format in Shipper 1.1 named Raw Data that you can use to examine the new schema.
The import/export database (Shipper.mdb) for Shipper 1.1 is stored in the UPS WorldShip shared database directory. The location of this directory is different for each of the 3 ways that UPS WorldShip can be installed. Please consult the UPS WorldShip documentation for details. Shipper.mdb for Shipper 1.0 was stored in the C:\Documents and Settings\USERNAME\ApplicationData\Structured Solutions\Shipper for UPS 1.0 directory, where USERNAME is the current Windows username.The data is not copied from the old database to the new database.
The import/export database (Shipper.mdb) schema was changed from Shipper 1.0 to Shipper 1.1 to accommodate batch importing. If you extended the database schema in Shipper 1.0, you will need to manually merge your changes into the new database.

Shipper 1.1 only works with Shipper Service 1.1. You must install Shipper Service 1.1 on your web site before you can use Shipper 1.1.

Version 1.0.6

Fix allows client and server to run different versions of .NET Framework 1.1 (with and without SP1)

Version 1.0.5

Include 1.0.4 hot fixes in installer.
Fix licensing conflict with StoreFront add-ons.
Fix updater issue.

This update includes a new release of Shipper Service. You will need to install or update the web service files on your web site.

Version 1.0.4

Fix timing issue downloading large number of shipments.
Fix access denied issue when previewing shipments.
Include attribute weights in shipment weight calculations.

This update is available as a hot fix only. See the README file that comes with the hot fix for installation instructions.

Version 1.0.3

Better error handling during web service test and send/receive operations.
Updated license agreement for release.
Resolved all open bugs

This update includes a new release of the web service. You will need to install or re-install the web service files on your web sites after updating Shipper.

Version 1.0.2

Check for updates on demand by selecting Check for Updates on the help menu.
Improved web service installer.
Improved web service check.

This update uses the same web service as RC2, so you do not need to re-install the web service files if you are upgrading from 1.0.1.

Version 1.0.1

Replaced error log with online error reporting.
Moved all send/receive operations to background for better user experience.
Added support for MS Access database in the store.

This version includes a new web service. Please re-install the web service after upgrading to RC2.