TariffShark Software Update Fixes Error

TariffShark Software Update Fixes Error

A new TariffShark release is available primarily as a fix for the “This method or property is not available because the document is locked for editing” error.

Background and Details

When TariffShark on your desktop is working with Tariff Record Version content files in Microsoft Word, the following error appears: This method or property is not available because the document is locked for editing. The following TariffShark activities may result in this error:

  • The Shark is swimming to perform TRV Content Processing
  • You selected Option 3 (Import Microsoft Word document) in the Build Content wizard and you used the “Optional Document Compare” option

The underlying cause of the error is that Microsoft is rolling out an update to Microsoft Word, one that altered Word’s behavior when documents are open for “read only”. In a few places in TariffShark, the new Word behavior triggers the “This method or property is not available because the document is locked for editing” error.

Resolution

  • If you’re running release 5.1.5, release 5.1.6 is available for download. The update merely requires that you install an updated TariffShark desktop client.
  • If you’re running an earlier 5.1.x release, we recommend updating to release 5.1.6, but a hotfix may be available (see below).
  • If you’re running one of various earlier releases and your desktop version is one of the following, a hotfix is available.
Your TariffShark Desktop Client VersionHotfix Version
3.1.2047.03.1.2047.2
3.0.1486.13.0.1486.3
3.0.1312.03.0.1312.2

Please visit the TariffShark website for detailed instructions or contact TariffShark Support.

If you’re not yet using TariffShark to meet your FERC eTariff obligations, we invite you to contact sales and ask for a demo of TariffShark Tiger today.

TariffShark Software Update Available

TariffShark Software Update Available

A TariffShark software update (release 5.1.5) is available NOW, primarily for minor FERC compliance reasons. Chief among the changes is the following.

  • Updated Tariff Record Version Versions to store values as high as 9999.9999.9999 (previously 9999.99.99) so long as the total number of digits doesn’t exceed 8
  • Removed the feature that submits XML to the FERC eTariff Sandbox (it’s no longer supported by FERC) and replaced it with instructions for manual Sandbox submission
  • Changed validation rule R011 from Warning to Fail in accordance with FERC’s November 17, 2022 notice in docket RM01-5-000

This update affects all TariffShark software components: database, application server, and desktop client. If you want to learn about the upgrade process and your quickest path to running the new software, please contact TariffShark Support.

If you’re not yet using TariffShark to meet your FERC eTariff obligations, we invite you to contact sales and ask for a demo of TariffShark Tiger today.

TariffShark Software Update Available Now

TariffShark Software Update Available Now

On April 17, 2020, FERC issued a notice that introduced a new eTariff validation rule to become effective May 18, 2020. The new validation verifies that “Normal” and “Amendment” type filings contain at least one (1) “actual” (non-Pro Forma) tariff record.

A TariffShark software update (release 5.1.3) is available now that introduces a parallel validation. The new validation rule in TariffShark is “F065” and its message reads as follows:

When making a Normal or Amendment filing, the Filing cannot contain exclusively FTRVs of Record Change Type “Pro Forma”.

If you’re running TariffShark release 5.1.2, the only component affected is the Application Server (unaffected are the TariffShark desktop client and the TariffShark database). Consult the TariffShark Releases page to assess the impact to your installation.

For customers who utilize hosted TariffShark servers and are running a current software release, there is nothing for you to do. We will update your hosted server prior to May 18.

Please contact TariffShark Support at 847-252-1611 or at support@tariffshark.com if you have any questions or concerns.

If you’re not yet using TariffShark to meet your FERC eTariff obligations, we invite you to contact sales and ask for a demo of TariffShark Tiger today.

FERC Reorganizes OGC to Speed Landowner Rehearing Process

FERC Reorganizes OGC to Speed Landowner Rehearing Process

The Federal Energy Regulatory Commission (FERC) announced that the Office of General Counsel (OGC) will be reorganizing the “process requests for rehearing of Natural Gas Act (NGA) section 7 certificate orders filed by affected landowners” to make it more expeditious.

In September, FERC Chairman Neil Chatterjee said he would work to “refine the FERC process to prioritize rehearing requests involving landowner issues, with a target of issuing rehearing orders within 30 days and reducing the use of tolling orders. At that time, Chatterjee designated attorneys in the rehearings group of the Solicitor’s Office to focus on rehearing requests involving landowner issues.”

“Our objective today is to reinforce the Commission’s commitment to ensure landowners are afforded a judicially appealable rehearing order as quickly as possible,” Chatterjee said. He says that he is “confident that this action will help substantially reduce the amount of time we take to issue rehearing orders in these critical cases.”

Chatterjee has directed OGC to create a new section specifically for rehearings, which “will have two separate groups, a Landowner Rehearings group and a General Rehearings group. The Landowner Rehearings group will give first priority to landowner rehearing requests, and would work on other rehearing items only when time permits.”

Chatterjee said he anticipates that this will allow them to move faster on any landowner requests for rehearings.

“We are hopeful that these actions will help alleviate the very real landowner concerns about timing and fairness in infrastructure cases implicating landowner rights,” Chatterjee said. “I remain committed to doing all we can to improve our FERC processes on this front.”