User’s Guide — LinkFixer Advanced

Chapter 18 — New Features and Fixes

New Features and Fixes

5.7.1 (22 July 2021)

Who needs this update?

This is a recommended update for all users of LinkFixer Advanced 5.6.3 and earlier released versions.

Beta Version Users: If you rely on a pre-release (“beta”) version of LinkFixer Advanced, please contact LinkTek Support before upgrading. This is very important. Your beta version may include a feature or fix which is critical to your migration. That feature or fix may not be present in this released version.

You can also check below to see if your critical features or fixes are included in this release.

Already migrating or preparing to migrate?

In general, “don’t upgrade software without cause during a migration” is good advice.

Here are some specific suggestions.

5.7.1 is a substantial upgrade to the excellent 5.6 family of releases. This is not a minor upgrade.

If you are mid-migration with 5.6.3 and don’t require any of the improvements in 5.7.1, you should probably consider finishing your migration with 5.6.3.

If you are still in the early testing phase of a migration with any released version prior to 5.7.1, you should probably upgrade to 5.7.1 and perform your testing with it. But it depends on your needs and your schedule.

If you were planning to upgrade to 5.6.3 and are not currently in the middle of a migration, upgrade to 5.7.1 instead.

Please contact LinkTek Support if you have any questions about when you should upgrade.

New — LinkTek Labs

We added the “LinkTek Labs” settings category. This is a place for users to explore early-access features and provide us with feedback. LinkTek Labs includes:

A new performance setting to only check whether a link is working or broken if we are modifying that link. Default: Check all links, the legacy behavior.
A new performance setting to only add a file ID to files we know are a parent file or a child file. Default: Add file ID to all files, the legacy behavior.
The ability to enable/disable processing of Microsoft Office macros. Previously, macro processing was not optional. Default: Do not process links in macros.
Limited support for Office Data Connection links to .odc files in Excel 2007 parent files. Default: Do not process these links.

New

We now support links to Excel charts in PowerPoint (.pptx and .ppt) parent files.

Fixed

Some PDF files generated by DocuSign could not be opened after being inoculated. This bug is fixed in 5.7.1. This resulted in no known data loss whatsoever. We are working on a version of LinkFixer Advanced which makes these PDFs openable again.
After modification by LinkFixer Advanced, some PowerPoint .pptx files could no longer be opened. This results in no known data loss whatsoever. Workaround: Use PowerPoint’s “Recover” feature when opening one of these files. Cause: A bug in a third-party library used for PowerPoint files, which has now been fixed.
Users of 5.6.3 who had not yet activated their LinkFixer Advanced license (which includes trial version users) would get an error on launch due to a benign (but annoying) check for updates bug. Fixed. The workaround was to activate the license.
Fixed the ability to restore file modification timestamps and “modified by” usernames in SharePoint On-Premises 2010.
Fixed a case where certain Excel spreadsheets could not be opened.
Fixed a case where we were matching links which were the result of a formula in an Excel cell. These should have been ignored.
Fixed a bug in how Cure reports non-curable UNC links. We were always reporting them as not curable link types (similar to how we report mailto links — not supported by Cure), but in reality the child file was either not found, or the link was unprotected. UNC links are curable if they are inoculated and the child file can be found.
Fixed an extremely rare case (only seen once and we could not reproduce it so we had to simulate it) where our controller would fail to kill a stuck agent and the controller would get into an infinite loop. Symptom was a stalled Cure.
Strange window coordinates could get stored in our settings file, causing LinkFixer Advanced to fail to launch. We now check for this strange case.
Various minor bug fixes.

Improved

Improved the speed of processing modern Excel (2007 format) spreadsheets.
Made significant improvements to our handling of links in Microsoft Office macros.
We now actively warn users that “Office 365” authentication does not support restoring file modification timestamps and “modified by” usernames. Our message encourages the user to use an authentication method which does support the restoration of those modification values. Previously, this information was only in a tooltip.
We found a way to send one SharePoint request per folder link, instead of two. This should reduce throttling.
Improved our logging of SharePoint throttling.
Improved how wrapped text in bullets looks in tooltips.
Network Locations: We now export passwords in an encrypted form, rather than in the clear. This applies to SharePoint site list CSV files and SharePoint user list CSV files.
When processing files in SharePoint, OneDrive and OpenText, we would only remove temporary files after the job was complete. Now we remove temporary files as we go, which uses less disk space.
Improved our PowerPoint (.pptx and .ppt) support by upgrading the third-party PowerPoint library we use.
Select Folders: Improved how we sort lists of SharePoint sites, sub-sites and folders. Folders and sites/sub-sites are no longer commingled.
Select Folders: Improved how the “Jump to location” field behaves.
Minor user interface improvements.

5.6.3.76 (14 May 2021)

Who needs this update?

This is a recommended update for all users of LinkFixer Advanced 5.6.2 and earlier released versions.

You can also check below to see if your critical features or fixes are included in this release.

Already migrating or preparing to migrate?

In general, “don’t upgrade software without cause during a migration” is good advice. So here are some specific suggestions.

This release (since it includes all of the 5.6.1 and 5.6.2 releases’ improvements) is a substantial update to the excellent 5.5.27 release. If you are mid-migration with 5.5.27 and don’t require any of the things we’ve improved in 5.6.1, 5.6.2, and 5.6.3, you should probably consider finishing your migration with 5.5.27.

If you are still in the early testing phase of a migration with 5.6.2 or any earlier released version, you should probably upgrade to this new version (5.6.3). But it depends on your needs and your schedule.

If you were planning to upgrade to 5.6.1 or 5.6.2, upgrade to 5.6.3 instead. It is basically the same except for behind-the-scenes improvements which we consider very safe.†

This release is a minor upgrade to the excellent 5.6.1 and 5.6.2 releases. If you are mid-migration with 5.6.1 or 5.6.2, it is probably very safe to upgrade to 5.6.3 at any time.†

Please contact LinkTek Support if you have any questions about when you should upgrade.

Just budget a little time to upgrade your site list CSV files, if you use any. See details in the next section.

New

We added a great new feature for users migrating to or from multiple SharePoint Online or OneDrive sites:

Network Locations | {Import…} now lets you import multiple SharePoint/OneDrive username/password pairs for each site listed in your site list CSV file.

Previously, you had to first import your site list CSV file and then import your user list CSV file into each site individually — even if it was the same user list for every site. The more sites you needed to set up, the more time this would take.

Now your site list CSV file can have any number of username/password pairs (not just one) defined in it, so you can import everything (site list and user list) in one go. To create a multi-user site list CSV file:

Manually create two SharePoint Online (or OneDrive) site entries in the Network Locations box of LinkFixer Advanced 5.6.3 or later. No need to create more than two at this point.
Manually enter username/password credentials in each of those sites. Two credentials per site is sufficient and they can be the same two credentials for both sites.
Use Network Locations | {Export…} to create a site list CSV file.
Open and edit that site list CSV file in Microsoft Excel. (Be sure to keep it as a CSV file — don’t upgrade it to Excel format.)
Follow the format already defined in the site list CSV file. Add entries for your other sites and add your set of username/password pairs under each site definition.
When you’re done, use Network Locations | {Import…} to load your multi-user site list CSV file into LinkFixer Advanced 5.6.3.

If you need any help, please contact us at Support@LinkTek.com.

Fixed

A handful of fixes:

Cure: Fixed a stall reported by one user. Cause: A third-party library used for filetype detection was failing on an Excel spreadsheet containing a very specific kind of corruption.
Fixed a narrow case where we would fail to upgrade our database to add two new-in-5.6.2 columns.
Network Locations | Configure | SharePoint: Fixed a case where the {OK} button would be disabled when importing a CSV file containing a list of SharePoint Online credentials.
Preview: Fixed a couple of display-only bugs.
View Results: Fixed some cases where we would present incorrect or confusing counts.

Improved

Some little improvements:

Minor user interface improvements.
Added day name to the date at the top of our PDF-format summary reports.
Network Locations: The default CSV filename for exported site lists and exported user account lists now includes the date and time.

5.6.2.19 (13 April 2021)

Who needs this update?

This is a recommended update for all users of LinkFixer Advanced 5.6.1 and earlier released versions.

You can also check below to see if your critical features or fixes are included in this release.

Already migrating or preparing to migrate?

In general, “don’t upgrade software without cause during a migration” is good advice. So here are some specific suggestions.

This release (since it includes all of the 5.6.1 release’s improvements) is a substantial update to the excellent 5.5.27 release. If you are mid-migration with 5.5.27 and don’t require any of the things we’ve improved in 5.6.1 and 5.6.2, you should probably consider finishing your migration with 5.5.27.

If you are still in the early testing phase of a migration with 5.6.1, 5.5.27, or any earlier released version, you should probably upgrade to this new version (5.6.2). But it depends on your needs and your schedule.

If you were planning to upgrade to 5.6.1, upgrade to 5.6.2 instead. It is basically the same except for behind-the-scenes improvements which we consider very safe.

This release is a minor upgrade to the excellent 5.6.1 release. If you are mid-migration with 5.6.1, it is probably very safe to upgrade to 5.6.2 at any time.

Please contact LinkTek Support if you have any questions about when you should upgrade.

New

New features:

Update agent’s processing timestamp during SharePoint throttling so controller knows not to restart the agent. This way still-healthy agents will be allowed to continue processing their files during times of sustained (greater than ten minutes) SharePoint throttling.
Immediately after an agent has to be restarted, query SharePoint to see if that agent’s last-requested parent file is still checked out. SharePoint throttling during an agent restart could possibly prevent such files from being logged in our database as being checked out by us, so we could possibly leave them checked out in very rare cases.

Fixed

We fixed a lot of small stuff and one (Loch Ness) monster:

A stall which would happen unpredictably and only during large (generally multi-day) jobs. This bug would pop up every once in a while and then submerge for a very long time, making it difficult to locate. If you are not mid-migration, this fix is probably enough reason to upgrade from any earlier released version to 5.6.2.
Email notifications would sometimes falsely report “process terminated” when the process completed successfully.
A SharePoint authentication problem involving special characters in passwords.
An error encountered when adding a SharePoint On-Premises 2016 site in Network Locations.
A rare case where logging would stop, but processing would continue.
A 5.6.1 bug where Preview would say some SharePoint links could not be cured, but they actually could be cured.
Very minor: LinkFixer Advanced would sometimes fail to recycle its agent ID numbers.

Changed

Updated the LinkTek End-User License Agreement (EULA).

5.6.1 (5 March 2021)

This is a major release of LinkFixer Advanced.

Who needs this update?

This is a recommended update for all users of LinkFixer Advanced 5.5.27 and earlier released versions.

You can also check below to see if your critical features or fixes are included in this release.

Already migrating or preparing to migrate?

In general, “don’t upgrade software without cause during a migration” is good advice.

This release is a substantial upgrade to the excellent 5.5.27 release. If you are mid-migration with 5.5.27 and don’t require any of the things we’ve improved in this new version, you may want to consider finishing your migration with 5.5.27.

If you are still in the early testing phase of a migration with 5.5.27, you should probably upgrade to this version. But it depends on your needs and your schedule.

Please contact LinkTek Support if you have any questions about when you should upgrade.

Increased Stability

We identified and handled a number of cases where jobs would temporarily stall or permanently halt.

Preview Panel — Major User Interface Overhaul

We did a complete visual overhaul of the Preview panel. Behind the scenes, Preview has not changed much, but it should be considerably easier to understand now.

Here is what the Preview panel previously looked like (example from 5.3.0):

Here is what the Preview panel looks like now:

User Interface Improvements

We made improvements to the user interface, including:

Total visual overhaul of Previews, as described above
Added a {Next Step…} button to help you navigate through each step of setting up a job.
Major improvements to the “Jump to location:” field in the Select Folders panel
Added column header sorting to the folder browser pane in Select Folders.
Various tooltip improvements
Clarified wording of some pie chart “slices”.
Minor improvements to what goes into certain pie chart “slices”
You can now display release notes from the ☰ menu. Previously, this was handled via a shortcut in the installation folder.
Email notifications now include the name of the machine running LinkFixer Advanced.
Minor reorganization of Settings categories and entries
When the main window is maximized, you can now (finally) restore (un-maximize) it by dragging its title bar.
Renamed “Process Files” page to “Run Report” in the Reports process.
Numerous additional user interface improvements

Bug Fixes

We made numerous bug fixes, including:

Some cases where agents (the sub-processes that processes parent files and child files) would go idle
Fixed a number of performance bottlenecks.
Fixed some hard-to-isolate memory leaks.
File exclusion lists were being used even when the setting was disabled.
LinkFixer Advanced would sometimes be unable to start a new process if user canceled the previous process before completion.

Code Signing (Digital Signatures)

We now apply a digital signature to LinkTek-created executable files delivered with LinkFixer Advanced. Previously, we only digitally signed the setup programs, not the executables installed by those setup programs. Signing all of our executable files should reduce the (already very rare) incidence of false-positive malware detection alerts during LinkFixer Advanced processing.
We renewed our digital code-signing certificate, which happens every three years. While the new certificate gains a reputation of trust through use, you may get a Windows SmartScreen warning at some or all of the following times:

When you start the installation
During installation
When you start LinkFixer Advanced
During a LinkFixer Advanced processing job

Restore Sample Files

| Settings | General | {Refresh Sample Files} has been completely re-written and renamed to {Restore Sample Files}. Previously, it simply ran a self-extracting archive. Replacing that self-extracting archive with a software feature decreased our surface area for false-positive anti-malware alerts, though these were very rare. More importantly, doing this allowed us to provide users with better error handling.

Filetype-Specific Improvements

Visio .vsd files:

Added support for links containing Unicode characters in Visio .vsd parent files.
Visio .vsd files will now be inoculated using the new data format introduced in 5.5.8. This means they cannot be Cured by a pre-5.6.1 version if they are inoculated by 5.6.1 or later.

Improved stability of Access .mdb and .accdb file handling.

Fixed a problem handling Power Query links in .xlsx files. (If you don’t already use Power Query, we don’t recommend clicking on that hyperlink. Definitely not required reading for most users.)

Removals

We removed some things from LinkFixer Advanced in this release:

Removed Settings | Performance:. We plan to create the next generation of this feature before restoring this setting. We may even be able to accomplish a level of dynamic performance optimization that makes a setting unnecessary.

If you have the need to increase or decrease LinkFixer Advanced’s overall performance, please contact LinkTek Support. We will be happy to make a recommendation based upon your exact situation.

The Modify and Move/Rename processes had “Before Preview” and “After Preview” panels. Now these processes have just one Preview panel and it contains “Before” and “After” columns.
Removed three Visio file extensions which crept into Select Files | File Extensions:

.vdw, .vss, and .vst. We don’t support these particular Visio files.

5.5.27 (18 December 2020)

Who needs this update?

This is a recommended update for all users of LinkFixer Advanced 5.5.8 and earlier released versions.

You can also check below to see if your critical features or fixes are included in this release.

New in 5.5.27 — Text-Format File Character Encoding Detection

The following includes all supported text-format files, regardless of their file extension (.html, and so on). LinkFixer Advanced only supports text-format files containing certain specific, structured content (such as HTML and XML files). And LinkFixer Advanced does not support unstructured text-format files.

All previous versions of LinkFixer Advanced save text-format files in the character encoding defined in Windows on the computer running LinkFixer Advanced.

Now LinkFixer Advanced attempts to identify the following character encodings when processing text-format files:

ASCII
UTF-8 (With Byte Order Mark)
UTF-8 (Without Byte Order Mark)
UTF-32 (Big-Endian)
UTF-32 (Little-Endian)

If LinkFixer Advanced does not determine that a text-format file’s encoding is one of those above, it will save that file using the encoding defined in Windows on the computer running LinkFixer Advanced.

Note: Text character encoding determination is not a foolproof process. We plan to continue to improve our character encoding detection over time. If you encounter any character encoding problems, however minor, please report them to Support@LinkTek.com or call LinkTek Support at 727-442-1822.

Fixed in 5.5.27

5.5.8 introduced occasional stalling during large jobs. This update (5.5.27) fixes all known cases of stalling introduced by 5.5.8. (We are also working on a follow-up release that fixes some other causes of stalling — these are more rare and they were not introduced in 5.5.8.)

OpenText only: While adding support in 5.5.8 for password-protected Excel and Word files, we introduced a narrow-scope filetype identification bug which is limited to OpenText:

.xlsm and .docm files have their MIME types changed to non-macro-enabled versions of their formats.
These two types of files get checked out of OpenText with their extensions modified to match those incorrect MIME types — .xlsx and .docx, instead of .xlxm and .docm.

5.5.8 (9 October 2020)

This is a major release of LinkFixer Advanced.

Who needs this update?

This is a recommended update for all users of LinkFixer Advanced 5.4.53 and earlier released versions.

Beta Version Users: If you rely on a pre-release (“beta”) version of LinkFixer Advanced, please contact LinkTek Support before upgrading. This is very important.

Your beta version may include a feature or fix which is critical to your migration. That feature or fix may not be present in this released version.

You can also check below to see if your critical features or fixes are included in this release.

New in 5.5.8 — Password-Protected Files Support!

Added support for processing password-protected Excel spreadsheets!
Added support for processing password-protected Word documents!

New in 5.5.8 — Excel .xls Unicode Support

Added support for links containing Unicode characters in Excel .xls parent files.

Changed in 5.5.8 — New Inoculation Data Format

Upgraded the format of the inoculation data LinkFixer Advanced stores in the majority of its supported file types. This new inoculation data format is compressed, encrypted, and also modularized. This makes it fast to process, very secure, and more resilient than earlier formats.

Important: LinkFixer Advanced versions prior to 5.5.8 will not recognize and will not support this new inoculation data format. LinkFixer Advanced 5.5.8 does recognize and fully retains support for inoculation data stored in your files by earlier LinkFixer Advanced versions.

For example, you can inoculate your files with 5.5.8 and then cure those files with some future version of LinkFixer Advanced. But you cannot inoculate your files with 5.5.8 and then cure them with an earlier version of LinkFixer Advanced.

Inoculation Data — Technical Details and Reasoning

Our inoculation data includes link information from inside inoculated parent files. Now that 5.5.8 adds support for password-protected Excel and Word files, we did not want to expose anything about the content of your password-protected files by storing our inoculation data in the clear. The privacy of your data is as important to us as the integrity of your data.

So the inoculation data had to be encrypted. And that made the inoculation data longer (larger). So, to keep it high-performance, we had to compress it. And, since it was longer than it used to be, it also sometimes needed to be broken up into smaller “chunks” to make it survive (whenever possible) users editing their files after inoculating them. This last point varies by file type and should only matter if you are editing your inoculated files before curing them.

Rather than only encrypt the inoculation data for password-protected files, we decided to encrypt the data by default for all file types that use this new inoculation data format.

This upgrade of our inoculation data format was necessary because we take seriously our responsibility to maintain the privacy of your links.

Removed

This release retires the “Classic” user interface version of LinkFixer Advanced. It had been made available via the ☰ menu since the release of 5.0 in order to help users gradually transition to the new, modernized user interface.

Fixed in 5.5.8

Numerous minor user interface improvements.

Numerous minor bugfixes.

5.4.53 (10 July 2020)

Who needs this update?

This is a recommended update for all users of LinkFixer Advanced 5.4.40 and earlier released versions.

You can also check below to see if your critical features or fixes are included in this release.

Fixed

Major stability improvement to our Adobe InDesign file handling.

Plus signs (‘+’) in links were omitted from output links during Cure in SharePoint. Re-running Cure with version 5.4.53 (or certain earlier beta versions) will repair this link harm.

Move/Rename would skip certain links containing plus signs (‘+’) in SharePoint Online.

Could not cure certain links containing a percent sign (‘%’).

Failed to detect a particular malformed link produced by a user-created Modify Links rule.

The Select Folders | [Files] node could not be processed individually. You had to include the folder containing those files.

A case where LinkFixer Advanced would count files in a folder above the selected folder in SharePoint Online. It would still process the correct files.

A SharePoint site collection authentication problem.

A case where Move/Rename fails to copy from SharePoint On-Premises to SharePoint Online.

A case where Move/Rename copies files instead of moving them while migrating from a local folder or network share to SharePoint Online, even when the option to “Copy files instead of moving them” is OFF.

Improved

Added additional automatic corrections for user-provided site collection URLs.

Installer

We now deliver the Visual C++ 2013 redistributable package. This is used by our .xls file handler. We still deliver the Visual C++ 2010 redistributable package, which is used by various other file handlers.

We stopped delivering legacy .doc (Word) and .ppt (PowerPoint) file handler DLLs. These were retired in an earlier release and kept in the distribution until now as part of their gradual deprecation.

5.4.40 (1 June 2020)

Added a popup box to alert SQLite database users that they will achieve higher performance by using SQL Server.

Added an Information Security FAQ chapter to this guide.

5.4.38 (15 April 2020)

This is a major release of LinkFixer Advanced.

Who needs this update?

This is a recommended update for all users of LinkFixer Advanced 5.3.0 and previous released versions.

You can also check below to see if your critical features or fixes are included in this release.

New in 5.4.38

We are delighted to announce:

Our SharePoint Online anti-throttling technology is now available to Office 365 authentication users! Numerous large-scale migrations have proven this to be extremely effective at reducing or avoiding throttling imposed by SharePoint Online.

Until now, this technology was only available with “User name/password” authentication — meaning no support for multi-factor authentication (“MFA”) and other modern authentication features.

Now you can accomplish top-speed SharePoint Online migrations without having to temporarily give up multi-factor authentication or create legacy user accounts.

Network Locations: We added a second Office 365 authentication option. This new option, “Office 365” authentication, removes the {Admin Consent} requirement. This gives the vast majority of users everything they need and nothing they don’t.

Both of LinkFixer Advanced 5.4’s Office 365 authentication options (including our new option) support our SharePoint Online anti-throttling technology.

Technical Note: If your migration involves SharePoint document IDs, please contact LinkTek Technical Support and ask whether you should use “Office 365 with admin consent” authentication. There are still some (fairly uncommon) cases where you should use that authentication option if you’re dealing with SharePoint document

IDs. It’s fast and easy for us to figure this out with you via phone or email — we just need to know a little bit about your particular migration.

We added support for SharePoint On-Premises 2019.

Improved in 5.4.38

Network Locations: Major overhaul of how we establish imported SharePoint network connections and re-establish all types of network locations whenever LinkFixer Advanced is started. This “just works” and vastly improves the experience when working with large amounts of network connections and with overloaded SharePoint servers.

Various minor user interface improvements.

Fixed in 5.4.38

Various stability fixes.

5.3.0 (13 December 2019)

New in 5.3

SharePoint Improvements

Added the ability to define a pool of SharePoint Online user accounts for LinkFixer Advanced to use during processing. This feature distributes SharePoint Online operation requests across those accounts and considerably reduces the chance of a request being throttled. This feature works exclusively with “User name/password authentication”. A future version of LinkFixer Advanced will add support for this feature to the “Office 365 authentication” option.

Added setting to enable/disable SharePoint email alerts during LinkFixer Advanced processing.

Processing Speed

Made a major improvement to the speed of LinkFixer Advanced’s Cure process. If a migrated file is already in the database (because it has already been scanned) and its modification timestamp has not changed, Cure will no longer re-scan that file. This is a huge speed optimization for many common migration scenarios.

OneDrive Support

Added support for Microsoft OneDrive in Network Locations.

Reporting

Added a setting to let users choose to combine LinkFixer Advanced’s three detailed reports into a single report file.

OpenText

Added support for OpenText Content Server “nicknames.” These are a special shorthand way of referring to links in OpenText Content Server.

Settings

Added the ability to sort the Network Locations list by any of its columns. Previously, there was no sorting ability in this list.

Fixed in 5.3

Made numerous stability improvements based on feedback from clients.

Improved our handling of Excel .xlsx files.

Certain filetypes would have their creation date changed during processing. We now restore their creation dates.

Fixed a case where we would sometimes save a file that we did not modify any links in.

This was an unnecessary change. This fix will slightly improve processing speed.

Fixed a rare bug where LinkFixer Advanced would display a “No Files Found” message during Scan.

5.2.0 (22 June 2019)

New in 5.2

New Authentication Method

Added Office 365 authentication as a new way of authenticating to SharePoint Online. Office 365 authentication supports Microsoft’s modern authentication features, including multi-factor authentication (“MFA”) and SAML-based third-party identity providers like Okta.

If you require other authentication options, please contact us at 727-442-1822 or Support@LinkTek.com.

More Speed

Version 5.2 features major performance improvements that should be noticeable by every user of LinkFixer Advanced working with files stored on local drives or on shared network drives.

Long Filenames

Processing files with long filenames (paths longer than 260 characters) is now enabled by default.

Tip: LinkFixer Advanced 5.2 processes long filenames faster than earlier versions could process short filenames. If you never have long filenames, you can still squeeze a small additional performance increase out of LinkFixer Advanced by disabling “Long filename support” in the settings.

Huge SharePoint Folders

Added support for SharePoint folders containing more than 5,000 items.

Technical Details: This is even better than it sounds, but it’s a little bit technical.

LinkFixer Advanced 5.2 actually overcomes the SharePoint “List View Threshold” (“LVT”) limitation entirely — even if a user had their LVT limit set to more than the common value of 5,000.

When using LinkFixer Advanced 5.2, your LVT limit is just not a concern when fixing your links anymore!

File Exclusion Lists

Added a new feature called “File Exclusion Lists”. This feature allows you to create a list of files to exclude from processing. Use this when you need to exclude certain files from processing and it is impossible (or impractical) to exclude them any other way.

This can massively reduce total processing time because files you don’t need processed are completely skipped — they’re not adding processing time to your LinkFixer Advanced job. (If you don’t think you need this feature for your migration, you’re almost certainly right. If you do need this feature for your migration, you probably already stopped reading this so you could start building your first file exclusion list!)

Upgraded Microsoft Project File Handler

Upgraded our file handler for the Microsoft Project (.MPP) filetype from version 18.12 to 19.4.

Fixed in 5.2

Fixed a bug where processing results were shown incorrectly for a canceled job.

If a file from SharePoint or OpenText could not be processed, LinkFixer Advanced will now undo the file’s checkout. Previously, such a file would have been left checked out.

Fixed an obscure bug saving a particular DWG file.

Fixed a bug in “Don’t spend time making multiple attempts to access files on inaccessible folders, drives or servers”.

5.1.0 (4 April 2019)

Made considerable clarifications to LinkFixer Advanced’s tooltips, labels and PDF-format summary reports. All of these improvements are designed to make LinkFixer Advanced easier to use for new users and experienced users.

An initial connection to SharePoint is now done in advance (automatically, in the background) to prevent brief delays for users. Previously, this connection to SharePoint was done upon request, often resulting in a brief delay for users if SharePoint took a long time to respond.

Turned “Long filename support” off by default.

Fixed a problem handling some DWG 2018 files.

Fixed a problem preventing the processing of some SQL Server database files which was introduced in 5.0.0.

Fixed a very rare problem that would intermittently prevent Inoculate from starting.

5.0.0 (15 February 2019)

LinkFixer Advanced 5.0 features the biggest facelift in its history. LinkFixer Advanced’s user interface has been completely redesigned based on numerous usability labs and customer feedback from IT professionals like yourself. LinkFixer Advanced 5.0 is a whole new experience — friendlier than ever but with the same power to handle thousands of links in minutes.

New in 5.0

In the past, SharePoint Online didn’t allow number signs (“#”), also known as pound signs or hash signs, in folder names. Now that these are allowed in SharePoint Online and seem to be in broad use, LinkFixer Advanced has been enhanced to also process folders containing these symbols.

Greatly improved the speed of processing Microsoft Access database files. Depending on your machine’s resources, new processing speeds could reach 10X faster when processing your Access database files.

LinkFixer Advanced has been updated to offer Import/Export in the Network Locations window. This allows users with lots of network locations to add all these much faster. For example, if your company has lots of SharePoint site collections, you can list all of these in a spreadsheet, then import your entire list directly into LinkFixer Advanced using a comma-separated values (“CSV”) file.

LinkFixer Advanced 5.0 adds the ability to browse SharePoint sites while creating Move/Rename and Modify Link rules.

LinkFixer Advanced 5.0 adds improved handling of really long paths. Filenames and links containing more than 259 characters will now get processed, by default, without having to turn on additional options.

Version 5.0 features performance improvements in several areas including checking online status of network locations, folder browsing and timeouts in SharePoint.

In our journey of enhancing the LinkFixer Advanced user experience, {Restore Default Settings} was revised to exclude folder selections, filters, rules and network locations. This means you can restore LinkFixer Advanced to its factory defaults without having to re-select folders for processing and without having to reset your filters or rules. Whatever you set before in those areas will remain.

Resolved a LinkFixer Advanced issue that previously had prevented users from removing invalid entries from their list of network locations. Now users can remove these easily.

Handled a LinkFixer file handler problem where an embedded PowerPoint file could not be processed.

Resolved a bug with PowerPoint files where certain Excel links were not being detected consistently.

Resolved a LinkFixer Advanced Excel file handler issue where certain links containing specific Unicode characters were not being processed.

Fixed a browsing issue where the folder browser would sometimes not navigate SharePoint URLs properly.

Fixed an issue where the files in the root folder of a SharePoint document library were not getting processed.

Fixed a problem saving links and link IDs in some PDF files.

Fixed an issue with Unicode links in PPTX files found during internal testing.

Added advanced support for Access database links in XLSX files.

Technical Details: Previously, LinkFixer Advanced had no support for Access database links in XLSX files. This version takes us from “no support” to “advanced support.”

No change was made to Access database link support in XLS files (the old Excel format). For XLS files, basic support for Access database links was already available has not changed in this version. We plan to bring our advanced support to XLS files’ Access database links in the near future.

Fixed an issue where LinkFixer Advanced was not allowing spaces in Move/Rename and Modify Links rules.

Fixed a rare bug where some links to SharePoint site collections were being reported as web URLs.

4.4.0 (14 September 2018)

After months of work, this release introduces enhancements in the SharePoint area that have been requested by customers for years. The biggest area having to do with how LinkFixer Advanced processes files in SharePoint. Previous versions would require users to map network drives to each SharePoint site collection. In occasions, companies would have hundreds or even thousands of them. With new LinkFixer Advanced 4.4, users will be able to add new sites effortlessly by simply entering the site URL. This will completely eliminate the need for “mapped drives”.

Additionally, by much popular demand, LinkFixer Advanced 4.4 features the ability to multi-thread when processing files in SharePoint on-premise and online. This allows multiple files to be processed at the same time helping you complete your migration to SharePoint faster than ever!

LinkFixer Advanced’s AutoCAD support has been extended to offer support for AutoCAD 2018 files.

This recommended release fixes a bug where LinkFixer Advanced was not processing links in VBA code which contained specific keywords. This has been handled. VBA keywords are now identified correctly.

A LinkFixer Advanced issue was fixed where specific report options were not properly getting updated in Global Settings.

Resolved a rare issue where log file paths were not being updated properly in the Windows registry settings.

Fixed an issue with LinkFixer Advanced where file filters were being automatically reset after a process finished.

4.3.0 (5 June 2018)

LinkFixer Advanced 4.3.0 features new Excel 2016 link handling. A new type of link in Excel 2016 was being reported as “$Workbook$”. LinkFixer Advanced has been enhanced to be able to modify, inoculate and cure these new types of Excel links.

LinkFixer Advanced had an issue with SharePoint's major/minor versioning setting being set to major versioning while inoculating files. Additional logging features were added to more easily show various authentication results.

This recommended release fixes a bug that previously crashes when passing a UNC path into the folder browser in LinkFixer Advanced.

Fixed a bug in LinkFixer Advanced where the cure process with OPENTEXT Content Server was not functioning correctly.

Resolved an issue in LinkFixer Advanced where pie charts were not functioning properly.

Page 234 LinkFixer Advanced

A bug was resolved where the “Process non-broken links” option in Modify Links does not appear to take effect until after restarting LinkFixer Advanced.

4.2.0 (1 February 2018)

By much popular demand, LinkFixer Advanced 4.2 features the ability to maintain the last modified timestamp field and modified by field on files moved to, from or within SharePoint online and on-premise. In past versions, LinkFixer Advanced would create custom fields in SharePoint where this information would be stored. This is not necessary anymore. LinkFixer Advanced will just retain this metadata on all files as if they were never touched.

LinkFixer Advanced’s Report features have been revamped! These are now faster (in certain cases up to 10X faster) than ever before.

LinkFixer Advanced has now added support for links in SQL queries in Access files.

Resolved an issue in LinkFixer Advanced where the progress animation would continue to function whenever the controller was busy with another process, such as when it was running very large reports.

LinkFixer Advanced had an issue where switching databases would not update the controller’s database settings.

LinkFixer Advanced had an issue with certain reports where previews were not able to execute properly. This was handled.

LinkFixer Advanced had an issue where rename rules for the database were not being set for previews. This is now fixed.

LinkFixer Advanced had an issue with PPTX and DOCX links causing a persistent error needing repair. This is now fixed.

Addressed an issue with LinkFixer Advanced where licenses that have link limits were aborting their processes once the limit was reached.

A LinkFixer Advanced startup error was fixed for very large databases.

A bug was resolved where the LinkFixer Advanced automatic update feature would not close all agents and controller causing an error message to appear.

4.1.20 (21 November 2017)

LinkFixer Advanced bug was handled where the agent and the controller would fail to close, this caused a failure during updates.

A bug was resolved where LinkFixer Advanced would report inaccurate SQL Server database detail in the log.

Under certain conditions, an error was handled in LinkFixer Advanced during inoculate or modify links where the original file would be overwritten as 0kb file.

Chapter 20 — New Features and Fixes Page 235

4.1.18 (10 November 2017)

LinkFixer Advanced 4.1 introduces “Clean Files”. This new feature will effectively clear out your LinkFixer Advanced link IDs within your files after running Inoculate and Cure.

A LinkFixer Advanced bug where certain files were skipped instead of being processed was fixed. On more technical terms, LinkFixer Advanced agents were failing to properly perform a cure process across network shares on certain occasions.

LinkFixer Advanced had a bug where moving your log file caused a persistent error message. LinkFixer Advanced now prompts you for the location of your log file if the file or mapped drive has become unavailable.

After the initial release of 4.1, some customers experienced issues with connecting

LinkFixer Advanced to their SQL Server database when using non-domain user accounts.

This was handled.

A bug was corrected where LinkFixer Advanced’s file handlers were finding an embedded excel file as the first file type when it should have detected the file as a PowerPoint.

4.1.9 (29 September 2017)

LinkFixer Advanced 4.1 features a new performance setting which provides a very simple way of allowing the user to specify how aggressive LinkFixer Advanced should be with performance. It will monitor your computer's performance while processing files. On a more technical note, the monitor checks CPU and memory resources and will automatically adjust the number of LinkFixer agent processes to ensure the selected performance level is maintained. You will no longer need to determine the correct number of processes to use simplifying your experience with LinkFixer Advanced.

All of LinkFixer Advanced code that could potentially interrupt processing has been moved to a separate controller process. This has been implemented to make LinkFixer Advanced more robust and bulletproof.

LinkFixer Advanced now backs up files by default. Users will be warned at first run that files will be backed up and it will request a location to save backed up files under. This setting and warning can be turned off for subsequent runs.

LinkFixer Advanced’s file handlers have been modified to write changes to a temp file and not the original file. Once modifications are complete, these temp files would then replace the original files. This new functionality prevents rare cases where a file handler may begin to update a file and then fail causing the agent processor to terminate leaving the original file potentially corrupted.

4.0.26 (22 August 2017)

LinkFixer Advanced has been supporting SharePoint Server since 2013. We’re proud to announce that due to popular demand, LinkFixer Advanced now supports SharePoint “Foundation” edition. This is the free edition of SharePoint.

This recommended release fixes a bug that previously caused some folder links in PDF files to not be cured. These folder links are now recognized and cured correctly by LinkFixer Advanced

Page 236 LinkFixer Advanced

In some rare occasions, LinkFixer Advanced displayed an “out-of-memory” exception when several LinkFixer Advanced agents (threads) processed certain files containing large numbers of links at the same time. This has been handled.

A LinkFixer Advanced bug was fixed that had caused the Document IDs in links in Word files, pointing to image files in SharePoint, to be truncated when modified in SharePoint by LinkFixer Advanced

A bug was fixed in LinkFixer Advanced that caused some links pointing to files that had not been inoculated to be cured incorrectly to point to inoculated files with the same name.

A LinkFixer Advanced bug was handled that assigned some invalid link IDs in some rare occasions where Inoculate was ran multiple times on the same parent files.

4.0.0 (28 April 2017)

With the release of LinkFixer Advanced 4.0, the world’s most complete automated link fixing solution is even more capable than before. This release adds support for additional brand new file types and new versions of types we previously supported, including:

LinkFixer Advanced now supports Microsoft OneNote files. This is key as more and more people are using OneNote for collaboration and idea sharing, now included as part of Windows 10, Microsoft Office 365 and available on PCs, tablets, IOS, Android and on the web.

LinkFixer Advanced now supports Microsoft Project files. Project users commonly utilize links to pull information together from multiple files. Having this capability included in LinkFixer Advanced will save significant time for businesses involved in construction, extensive product development and other activities where scheduling is key.

LinkFixer Advanced 4.0 adds support for the latest versions of Microsoft Visio (2013 and newer).

LinkFixer Advanced now supports the Adobe InDesign CC (Creative Cloud) 2017. All Creative Cloud subscription users can update to the latest version. At LinkTek, we make sure to remain up-to-date on what our customers need.

LinkFixer Advanced has now been enhanced to support the new IDML file type for Adobe InDesign.

LinkFixer Advanced is now able to process links to external resources (such as images, applets, Flash animations and so on) contained in MIME Hypertext Markup Language (MHTML or MHT) files.

It is now faster and easier for you to request tech support. LinkFixer Advanced now includes a function that will (with your permission) automatically gather, compress and send to LinkTek Tech Support a package of logs, reports, settings files, sample files and other support information in the event of an exception in the program. You can also manually initiate a support request by clicking {Support Ticket} on the Application (blue) tab of the LinkFixer Advanced user interface.

LinkFixer Advanced logs now take up less space on your disk. LinkFixer Advanced logging functions have been enhanced to provide the developers with necessary information in a smaller, more efficient package. In some circumstances, this will also result in an increase in processing speed.

Chapter 20 — New Features and Fixes Page 237

You can now choose to purge old LinkFixer Advanced logs by the total size of the logs or by the age of the log files. This gives you greater control over how log files are stored by LinkFixer Advanced.

Your Microsoft Access MDB and ACCDB files are now processed more quickly. LinkFixer Advanced’s Microsoft Access plug-in was enhanced to find links in Access files more efficiently.

A LinkFixer Advanced bug was fixed that had previously caused the “Last Modified” date and time to be updated to the current date and time for some files that contained Unicode characters in the file path.

A bug was fixed in the handler for text files that occasionally resulted in an “out-of-memory” condition in LinkFixer Advanced.

A bug in LinkFixer Advanced was fixed that previously caused some broken web links in Microsoft Word (DOCX) files to be reported with an incorrect error code.

A bug was fixed in the Microsoft Word plug-in that previously caused a specific type of link to be truncated by the Modify Links process.

The full “Setup” and “Update” installers for LinkFixer Advanced were merged into a single, unified installer.

A LinkFixer Advanced bug was fixed that had previously caused some links to not be inoculated if “Long File Name” support was enabled.

A bug in LinkFixer Advanced was fixed that had prevented generating a checksum during the Inoculate process for pre-1997 Office child files, child files larger than 2GB and child files with errors.

A bug was fixed in the Adobe Acrobat plug-in that had previously caused PDF files to be corrupted by the Inoculate process in a rare set of circumstances.

A bug was fixed in LinkFixer Advanced that had previously caused some links contained in VBA macros to be incorrectly prefaced with “file:///” during the Inoculate process.

A LinkFixer Advanced bug was fixed that had previously prevented scanning of SQL Server database tables under certain specific conditions.

LinkFixer Advanced’s included SQLite database was updated to version 5.8.862.

3.5.0 (28 December 2016)

LinkFixer Advanced’s Scan function is once again faster than it’s ever been. It now scans files and links at least twice as fast as previous versions. This improvement was accomplished by enhancing LinkFixer Advanced to count files and retrieve file data using multiple processing “threads” at the same time. This process previously used only a single processing thread.

LinkFixer Advanced’s Inoculate process is also faster than ever. Links are now inoculated two to three times faster by using multiple processing threads (“Agents”) at the same time.

LinkFixer Advanced can now fix links in more of your PDF files. LinkFixer Advanced’s Adobe Acrobat plug-in has been enhanced to recognize and process links in PDF version 1.7 files, as well as links contained in dynamic forms. Dynamic forms are a type of PDF forms that are fillable online.

Page 238 LinkFixer Advanced

It is now easier to use rename rules in the Move/Rename and Modify Links processes. The Rename Rules screen in LinkFixer Advanced has been enhanced with the following new features:

If you want to select all of your rename rules, you no longer need to click the selection box beside each box. A “select all” toggle checkbox was added above the rename rules. Clicking the checkbox enables or disables all rename rules.

You no longer need to click the move button multiple times in order to move a rename rule to the top or bottom of the list. “Move top” and “Move bottom” buttons were added to allow a rename rule to be quickly moved to the top or bottom of the list.

You can now preserve and reuse your rename rules. An export button was added to allow rename rules to be saved to a file.

Now you can modify files with a specific file name. A new “Filename” component was added to the “Component to modify” selection, which allows you to specify a combination of the basename and extension components.

You can now be more exact in specifying when LinkFixer Advanced should rename a file path. A new “Exact match” method was added to the “Rename method” selection, which requires the “from” string to exactly match the selected component in order for it to be replaced with the “to” string.

LinkFixer Advanced now more exactly reproduces your folder structure, when running Move/Rename. LinkFixer Advanced’s Move/Rename was enhanced further to create empty folders in the target location, when these empty folders are encountered in the source location. LinkFixer Advanced will also now remove empty folders in the source location, during the Move/Rename process, even if those folders were not emptied by LinkFixer Advanced during the Move/Rename process.

LinkFixer Advanced can now process extremely large quantities of sub-folders (over 20 million) in a single parent folder. A bug was fixed that previously caused an “Out of Memory” exception when tried to process a single parent folder with over 1 million sub-folders and files.

The CSV reports produced by LinkFixer Advanced will now always be manageable in size. The reporting function has been enhanced to automatically split CSV reports into separate files of a size that you select. Previously, these reports could sometimes become so large that Microsoft Excel could not open them.

You no longer need to worry about installing a PDF viewer on your server in order to view LinkFixer Advanced reports. You can now open its reports and the LinkFixer Advanced user’s guide using its own PDF viewer. This is useful when LinkFixer Advanced is installed on a server or other machine that does not already have a PDF viewer installed. LinkFixer Advanced checks for a previously installed PDF viewer before launching its own PDF viewer.

You will now be able to know the level of importance of LinkFixer Advanced updates before you install them. We have enhanced LinkFixer Advanced’s update system to classify updates as “Required”, “Critical”, “Important”, “Recommended” and “Optional”. We also now provide a preview of the features and fixes included in the update.

Your custom SharePoint “Last Modified” fields can now be written only once and are subsequently “read-only”. A LinkFixer Advanced bug was fixed that previously allowed LinkFixer Advanced custom “Last Modified” fields to be overwritten when and if a subsequent LinkFixer Advanced process was run on the same files.

Chapter 20 — New Features and Fixes Page 239

When running multiples instances of LinkFixer Advanced, you can now instruct the scanning portion of Cure to pause to allow all other instances to also complete their Scan step before your cure process begins. This ensures that LinkFixer Advanced has all of the data, about all of your files, from all of your instances, before it begins to Cure your links. A user interface setting has been added to the “Options | General” screen that allows you to instruct LinkFixer Advanced to pause after the cure scan.

A bug was fixed that had previously misidentified some text files as video media files, and mistakenly added a linkID to those files during the Inoculate process. These text files are now correctly identified and a repair utility was added to LinkFixer Advanced that will remove the linkIDs from any affected text files.

A bug was fixed in LinkFixer Advanced that previously caused some types of files to not be able to be previewed in OpenText Enterprise Connect after being inoculated by LinkFixer Advanced.

A LinkFixer Advanced bug was fixed that previously caused the Cure process to stop during the Scan portion of the process if the license link limit was reached during the scan. LinkFixer Advanced now counts links against the license link limit only when a link is cured during the Cure portion of the process.

A bug was fixed in LinkFixer Advanced that previously prevented links in a file from being fixed during the Move/Rename process in cases where LinkFixer Advanced was not able to set the file’s permissions after the file was moved or renamed.

A bug was fixed in LinkFixer Advanced that previously caused Move/Rename statistics to be incorrect if any files were skipped during the Move/Rename process.

A bug was fixed in LinkFixer Advanced that previously left some files in SharePoint after the Move/Rename process was supposed to move them from SharePoint to the user’s local C:\ drive.

All “Tooltips” are back. A bug in LinkFixer Advanced was fixed that previously prevented “tooltips” from displaying on the “Select Files” screens of all processes.

A bug in LinkFixer Advanced was fixed that previously caused Cure to abort in some cases where the license link limitation was reached prematurely. Links now count toward the link limit only when the applicable process has been successfully accomplished.

The architecture of the LinkFixer Advanced error module has been enhanced to enable the creation of error messages containing more details and diagnostic intelligence.

Microsoft .NET version 4.6.1 will no longer attempt to install when version 4.6.2 is present on your computer. This issue made LinkFixer Advanced’s install to be confusing as it seemed to communicate that LinkFixer Advanced had fail to install.

Windows 7 operating system or higher is now required in order to install LinkFixer Advanced.

Additionally, copyright notices have been updated in source files, installers and the LinkFixer Advanced “About” screen.

3.4.0 (29 August 2016)

LinkFixer Advanced now processes files and links significantly faster. In some benchmark tests, the speed increase averaged over 500%, compared with the previous

Page 240 LinkFixer Advanced

most-recent version of LinkFixer Advanced. We did this by upgrading the method of writing links to the SQL Server database. Data storage structures within the database were revised to improve efficiency. And, the logic used when LinkFixer Advanced controls the multiple threads (“Agents”) was also improved significantly to process files more efficiently.

LinkFixer Advanced can fully handle your MicroStation reference files now. In the past, there were some reference files that LinkFixer Advanced didn’t “see”. That is remedied in this new release. For us geek types, here are the details: The MicroStation plug-in was rewritten to recognize and use variables in link (reference) paths. LinkFixer Advanced can also now modify links paths in both of the storage locations within DGN files (instead of only the location that stores the absolute link path).

LinkFixer Advanced’s Microsoft Excel plug-in can now find and process links in more places automatically. Specifically, and nerdy speaking, we’ve enhanced the Microsoft Excel handler to access links that point to files located in Excel startup and library folders. These links were previously shown as “inaccessible”. That is remedied in this new release.

In our continuous efforts of improving performance and user experience, LinkFixer Advanced has been upgraded to use the latest versions of .NET framework, SQLite and DevExpress. All three of these third-party tools are very important to the operation of LinkFixer Advanced. New version numbers:

.Net Framework 4.6.1

SQLite version 5.6.687

DevExpress 16.1.4

Further on our efforts of improving user experience, LinkFixer Advanced has been enhanced to include more warnings. Details follow:

The SQLite database that comes free with LinkFixer Advanced is a fantastic tool when running small sets of files for smaller projects, or when running our sample files when becoming familiar with the tool. However, if you’d like to run it on larger sets of files, specifically, 100,000 files or more, it is recommended that you switch to a full SQL Server to experience LinkFixer Advanced’s true performance! With release 3.4.0 and beyond, if you point LinkFixer Advanced to a dataset that’s 100,000 files or larger and you have not switched to a full SQL Server, upon firing up LinkFixer Advanced, it will now warn you that performance will be much slower if you do not switch to a full SQL Server, and you’ll be given instructions on how to do so.

LinkFixer Advanced will now warn you if you configure SQL Server with a database schema other than the default “dbo” schema.

LinkFixer Advanced now includes a file system and network diagnostic utility. This utility is a separate executable that gets shipped with LinkFixer Advanced to help our developers diagnose the source of any network or storage issues that could be slowing down the operation of LinkFixer Advanced. This utility does not run automatically.

LinkFixer Advanced has been enhanced to render graphics more reliably when it is being run on a virtual or remote machine using a remote desktop connection. To accomplish this, LinkFixer Advanced now uses software graphics rendering by default (instead of hardware rendering).

AutoCAD users, LinkFixer Advanced will now recognize and process your links that point to underlay layer files (PDF, DWG, DWF, and DGN). We have enhanced

Chapter 20 — New Features and Fixes Page 241

LinkFixer Advanced to recognize this type of link and process it like any other link in AutoCAD files.

Relative links now maintain their relative format when the “Convert mapped drives to UNC” rename rule is used. A bug was fixed that had previously incorrectly applied the “Convert mapped drives to UNC” rename rule to relative links in addition to links in the “mapped drive” format.

LinkFixer Advanced’s “Finishing” rules are now only applied to links that have been modified by the main rename rules. A bug was fixed in LinkFixer Advanced that previously applied “finishing” rename rules to all links, regardless of whether or not these links had been modified by the main rename rule or rules. These “finishing” rules instruct LinkFixer Advanced to leave links in a specific format, such as “absolute”, “relative”, “UNC”, etc., after the links have been modified by the main rename rules.

Links are now only modified in the parent file if LinkFixer Advanced has confirmed that the child file was successfully moved or renamed. A LinkFixer Advanced bug in the Move/Rename process was fixed that previously modified links in some parent files, even when the child file, pointed to by a link, was not successfully moved/renamed for any reason.

Legacy LiveLink files without file extensions, contained in OpenText Content Server, can now be inoculated and cured successfully by LinkFixer Advanced. A bug in LinkFixer Advanced was fixed that previously removed the MIME type information from these files during the Inoculate process. This caused the subsequent curing of these files in a new location to fail. The MIME type of files can now optionally be determined and added to the metadata of files when LinkFixer Advanced processes them.

LinkFixer Advanced can now process files with names containing square brackets. A bug was fixed that previously prevented processing files with these characters.

A LinkFixer Advanced bug in the Modify Links preview was handled where in some rare occasions, some links that were supposed to be modified to “mapped drive” link format were converted instead to UNC link format. This bug was fixed in this release.

A LinkFixer Advanced bug was fixed that previously sometimes caused local drives to be presented on the “Network Locations” screen as though they were mapped drives to network locations.

A bug was fixed in the Microsoft Access file handler that previously caused some Access links to not be modified.

3.3.0 (20 May 2016)

You can now accomplish more with a single processing “pass” through your data when using LinkFixer Advanced. We have added “finishing” options to the Inoculate and Cure processes that will now allow you to specify how you want all of your links formatted when the process is complete. For example, you can specify that all links be “finished” by making them all relative, absolute or upper case. In many cases, this new feature will save you time by reducing the number of LinkFixer Advanced processes that need to be run to accomplish your project.

You now have much more information available to you when LinkFixer Advanced is running a process. The “progress box” has been completely redesigned and expanded into a “progress page”. This page now contains real-time alerts about critical issues, disk

Page 242 LinkFixer Advanced

space and database space monitoring, real-time file and link processing statistics and graphs, an elapsed time indicator, calculations of the numbers of files and links being processed per minute by LinkFixer Advanced, and other information.

LinkFixer Advanced will now warn you in advance about several important potential issues before they have a chance to occur. LinkFixer Advanced has been enhanced to automatically check the amount of available RAM, the increment by which the SQL Server database is set to auto-grow, whether you have selected to process files that reside on a Novell volume and whether you have selected to process more than the recommended number of files using the SQLite database. If any of these are outside the required or recommended parameters, LinkFixer Advanced will warn you about the situation when you click the {Run} button for any process. This new functionality will help LinkFixer Advanced apply the old adage that “an ounce of prevention is worth a pound of cure”.

You are now less likely to accidentally clear (or fail to clear) the LinkFixer Advanced database when running a process. Whether the database will be cleared is now controlled by an obvious checkbox on the Options screen of each process. Additionally, when that option is enabled and you click the {Run} button, a popup box asks whether you really intend to clear the database.

You can now access your SharePoint Online server using “Federated” authentication. LinkFixer Advanced has been enhanced to support this form of “claims based” authentication.

You can now access your OpenText server using SSL. LinkFixer Advanced has been enhanced to support connections using HTTPS.

You can now choose to receive email notifications from LinkFixer Advanced when it finishes a process or encounters an error during processing. You can also choose the level of issue severity about which you wish to be notified.

LinkFixer Advanced reports are now more informative. A “Critical Alerts” section has been added to the Summary Report to summarize and communicate the most important issues that occurred during the LinkFixer Advanced process that just ran.

New users should find LinkFixer Advanced easier to understand and use. The “Options” screens for all of the processes have been revised, updated and simplified so as to be clearer and more intuitive.

You will spend far less time inoculating new and changed files in data sets that have previously been inoculated. The LinkFixer Advanced Inoculate process now has the ability to perform an “incremental” inoculation that processes only files and links that are new or changed since the previous inoculation.

Support for running multiple instances of LinkFixer Advanced at the same time has been enhanced with improved coordination between instances. LinkFixer Advanced now logs and tracks each instance connected to the database at startup and when a process is started. Safety features have been added that make it much more difficult for one instance to accidentally erase or corrupt data that was added by another instance.

The Microsoft Excel plug-in was enhanced to recognize and process macro links that are activated by clicking on buttons in XLSM files.

A LinkFixer Advanced bug was fixed that previously caused processing to be aborted when a certain type of “transport-level” disconnection occurred between LinkFixer Advanced and the SQL Server. LinkFixer Advanced will now recover from this type of

Chapter 20 — New Features and Fixes Page 243

error, attempt to reconnect to the SQL Server and continue processing files if the connection can be reestablished.

A bug was fixed that previously caused the Agent Manager in LinkFixer Advanced to occasionally fail to restart an agent process that had been either intentionally or unintentionally stopped due to file corruption or some other critical issue. This bug, which caused LinkFixer Advanced to occasionally “hang”, has now been fixed.

A bug in the Microsoft Excel plug-in was fixed that caused an exception when links containing certain types of macros in XLSM files were processed. The Excel plug-in was also enhanced to recognize and process several new types of expressions containing links within VBA macro code.

The Microsoft Excel plug-in has been enhanced to provide full Unicode support for links in XLS files.

The Microsoft Excel plug-in was enhanced to be able to work around a known Microsoft issue that arises when attempting to modify a relative link to point to a location closer to the root of the file system than the directory of the parent file in which the link is located.

A bug in the Microsoft Excel plug-in was fixed that previously caused the Last Modified time to not be preserved for Excel files containing VBA macros.

A bug was fixed in the Microsoft Access plug-in that had previously caused some MDB and ACCDB files to be processed very slowly. LinkFixer Advanced now scans only user-defined tables and does not scan “linked tables” to external files. This improved the processing speed dramatically.

A bug in LinkFixer Advanced was fixed that had occasionally caused files copied to SharePoint Online to not be cured.

A bug was fixed that previously caused LinkFixer Advanced to report “no links to cure” in some circumstances where broken links were actually available to cure.

A LinkFixer Advanced bug was fixed that had prevented file and link filters from being applied when generating reports from the Reports tab.

A LinkFixer Advanced bug was fixed that had occasionally caused the Inoculate process to hang during processing due to a SQL deadlock.

A bug was fixed in LinkFixer Advanced that previously prevented any links that contained invalid linkIDs from automatically being reassigned valid IDs during a re-inoculation of those files.

A LinkFixer Advanced bug was fixed that caused active LinkFixer Advanced agents to operate using the default settings file, even though the user had specified a different settings file.

A LinkFixer Advanced bug was fixed that caused file filters set by the user to be ignored during the scan portion of the Cure process. As a result, the Cure process was taking longer than necessary to complete.

3.2.0 (22 January 2016)

The LinkFixer Advanced Cure process is now easier to use. It is no longer necessary to select the locations of the parent and child files on separate wizard screens, and you no longer need to specify whether the files were copied versus moved. You can now cure

Page 244 LinkFixer Advanced

your files simply by selecting the parent and child file locations on a single wizard screen. No other settings or switches are necessary.

The Microsoft Access plug-in can also now find and fix links contained in plain text streams located in any column of an Access table. (Previously, links in Access files could only be found and processed if they were located in a column specifically identified as containing links.)

The AutoCAD plug-in can now recognize and handle files in AutoCAD 2015 and 2016 file formats.

The InDesign plug-in can now recognize and handle Adobe InDesign files in the Creative Cloud file formats.

LinkFixer Advanced was enhanced to show the link-type matrix on all Summary reports (instead of only the Scan Summary). The matrix itself is easier to use because it now reports file types (instead of every single file extension). A bug was also fixed that previously had caused the numbers reported in the file-type matrix to occasionally be inaccurate.

A bug in LinkFixer Advanced was fixed that occasionally had caused corruption of some JPG image files during the Inoculate process. This issue occurred only when large numbers of image files were processed concurrently and has now been fixed.

A bug was fixed in LinkFixer Advanced that previously caused database deadlocks while deleting entries from the ErrorLog table under certain circumstances.

A LinkFixer Advanced bug was fixed that previously caused links in SharePoint Online to be reported and handled as ordinary web links in the case where the child files did not exist in the file selection.

A bug in LinkFixer Advanced was fixed that was previously removing milliseconds in the “last modified” timestamp of files, due to database inaccuracy. LinkFixer Advanced now restores the original file time accurately to the millisecond.

A LinkFixer Advanced bug was fixed that cause links to not be fixed by the Move/Rename process in the case where child files were moved or renamed but parent files containing links to those child files remained in the same location.

A bug was fixed in LinkFixer Advanced that previously caused SharePoint to report ASPX system files as corrupt after being inoculated by LinkFixer Advanced. LinkFixer Advanced now skips and does not process any system folders or files in SharePoint by default.

A bug in LinkFixer Advanced was fixed that previously prevented the Modify Links process from changing OLE links in Microsoft Office files to “relative” or “absolute” link formats.

A bug in LinkFixer Advanced was fixed that previously handled incorrectly some file and link paths that contained question marks. These file and link paths are now handled correctly.

A bug was fixed in the Microsoft Excel plug-in that had previously caused “Error! Hyperlink reference not valid.“ to be added to the beginning of “connection” links (containing the data required to connect to, and retrieve data from, a database) in Excel files during the Cure process. (This behavior is correct for most other links in Excel files, but would be incorrect for connection links.) These links are now correctly handled by LinkFixer Advanced.

Chapter 20 — New Features and Fixes Page 245

A LinkFixer Advanced bug was fixed that previously caused link filters, selected by users in the “Select Links” screen of the Inoculate process, to be ignored. Link filters now work correctly.

Three bugs were fixed in the Microsoft Shortcut (LNK) plug-in. “Last Modified” timestamps of shortcut files were previously not being maintained. Shortcuts to locations with long file paths were previously not supported. Previously, inoculated shortcuts were reported as “not inoculated” after a rescan. All three of these bugs have been fixed.

3.1.0 (4 September 2015)

Do you prefer to copy your files when doing a migration (instead of just moving them)? Well now LinkFixer Advanced can cure all the links in files that you copied to the new location, with no extra steps required on your part. Previously, LinkFixer Advanced would not Cure files that were copied to a new location, because copying usually does not break the links in parent files, thereby causing LinkFixer Advanced to see all the links as still “healthy”. With this new release, the LinkFixer Advanced Cure function can, in essence, recognize that your files were copied and fix the links to point to the child files in their new location.

The LinkFixer Advanced LNK, ASPX, CSS, HTML and JS plug-ins have been completely rewritten. The new file handlers will process your files an average of approximately 2.5 times faster, and are more efficient and robust than the previous plug-ins.

LinkFixer Advanced is now completely compatible with SharePoint Online. LinkFixer Advanced’s ability to use your SharePoint Online credentials to log in to SharePoint Online has been enhanced. Previously, only a limited set of LinkFixer Advanced features were available in SharePoint Online. All LinkFixer Advanced features and functions are now available.

The LinkFixer Advanced Inoculate process just got faster. The speed of the LinkFixer Advanced Inoculate process was improved by a new method of processing unrecognized, unsupported and locked files. These files are now inoculated 3.5 times faster than in previous versions, in part because LinkFixer Advanced is no longer required to make a temporary local copies of the files in order to process them.

LinkFixer Advanced scans Visio files about 4 times faster than the previous version. Users will love this scanning speed increase. For our tech nerds (those who love to know how things are done): This speed increase is due to changing the scanning function such that it can determine the file types without having to make a temporary local copy of each file, as was previously required.

You now have better control over versions in SharePoint. LinkFixer Advanced’s compatibility with Microsoft SharePoint has been enhanced with the ability to create either a “major” version or “minor” version when LinkFixer Advanced modifies files in SharePoint. Previously, LinkFixer Advanced was able to create only a “major” version (such as incrementing from version 1.0 of a file to version 2.0). LinkFixer Advanced is now able to detect the user’s version setting in SharePoint, and to create the appropriate type of new version automatically, based on that user setting. So, for example, if the user setting in SharePoint is set to create “major and minor” versions, LinkFixer Advanced will increment the version number from 2.0 to 2.1 (instead of only incrementing from 2.0 to 3.0).

Page 246 LinkFixer Advanced

You are no longer required to turn off “Require Content Approval” before processing files in SharePoint. LinkFixer Advanced’s compatibility with Microsoft SharePoint has been enhanced with the ability to modify files in a SharePoint library when the “Require Content Approval” setting is enabled. LinkFixer Advanced is now able to automatically disable this setting before processing a file, and re-enable the setting when processing is complete.

LinkFixer Advanced is compatible now with SharePoint Web Apps. The links contained in some files that were moved out of SharePoint with Web Apps, and some files moved within SharePoint, would be automatically fixed by Web Apps and SharePoint. These changes to the link paths had previously caused the links to appear to LinkFixer Advanced to no longer be inoculated. This prevented LinkFixer Advanced from being able to Cure the links if they were subsequently moved to a different location. This is fixed. LinkFixer Advanced is now able to track these links (and their linkIDs) even if Web Apps or SharePoint modifies the links.

Processing large SharePoint sites is now faster. LinkFixer Advanced was enhanced to processes Microsoft SharePoint sites more quickly and efficiently by automatically skipping SharePoint system folders and files. Skipping these system folders and files allows LinkFixer Advanced to process your sites faster. By default, LinkFixer Advanced now skips the “Forms”, “_catalogs”, “_cts” and “_private” folders, and all ASPX parent files it finds in SharePoint libraries.

A bug in LinkFixer Advanced was fixed that previously had caused some child files in SharePoint to be incorrectly reported as not containing a fileID, when SharePoint document IDs were in use. This bug was fixed by adding the ability to retrieve a SharePoint child file’s full URL path using its SharePoint document ID, without requiring the file to be rescanned.

A LinkFixer Advanced bug was fixed in the function that preserves the “last modified by” and “last modified date” information about files moved by LinkFixer Advanced into SharePoint. The point of this feature is to preserve the “last-modified” data that the file had before it got moved to SharePoint. Without our custom fields to store that data, SharePoint immediately changes the last-modified data to the current date and user at the instant the file goes into SharePoint. The bug here was that data from within, instead of from outside SharePoint, was previously preserved. This information about the files, prior to their entry into SharePoint, is now correctly saved to the corresponding custom fields in SharePoint.

A bug in LinkFixer Advanced was fixed that previously sometimes caused individual threads (“agents”) of the LinkFixer Advanced multi-threading capability to hang when network locations were found to be unavailable.

A LinkFixer Advanced bug was fixed that sometimes previously caused SharePoint mapped drives to not be detected. SharePoint mapped locations that previously did not appear in the LinkFixer Advanced “Network Locations” tab and folder selections screens are now recognized and displayed.

A bug in LinkFixer Advanced was fixed that previously stored invalid mapped drive information in the LinkFixer Advanced settings file. This bug caused delays in LinkFixer Advanced processing while invalid drives were searched for. These delays have now been eliminated.

A bug in LinkFixer Advanced was fixed that previously did not allow processing of links containing French accented characters. Files that were previously not processed are now processed successfully.

Chapter 20 — New Features and Fixes Page 247

The “Preview Links to be Cured” screen now presents accurate data. A bug in LinkFixer Advanced Cure Preview screen was fixed that had previously provided an incorrect count of files and links available to be Cured. LinkFixer Advanced now presents a preview of every link that exists in each of the parent files it shows on the Preview screen. It also now continues to scan files until it either finds all available files and links to be cured, or until the user-selected number of links has been found.

LinkFixer Advanced now recognizes “+” symbols in file paths. A LinkFixer Advanced bug was fixed that prevented files with “+” symbols in the file path from being processed. Files with this symbol are now processed and reported correctly.

LinkFixer Advanced is now tolerant of multiple file extensions that are part of the same file name. A bug was fixed that had previously caused LinkFixer Advanced to not correctly process files that contained more than one file extension. For example, the file “\folder\sample.xls.xlsx” would not have been processed. Multiple extensions are now correctly handled.

The modified date of SharePoint files that contain no links is now preserved. A LinkFixer Advanced bug was fixed that previously caused files with no links to appear to have been modified, even though the file contained no links to modify. These files now retain their Last Modified date in SharePoint when processed by the LinkFixer Advanced Modify Links process.

A bug in LinkFixer Advanced was fixed that previously caused file filters to be inconsistently applied at different levels of the selected folder structure. This resulted in files being scanned that should have been filtered out of the Scan selection. This File Filter selection now works correctly.

A LinkFixer Advanced bug was fixed that occasionally caused folder browser selections to be cleared when folders were collapsed and expanded. User selections in folder selection screens are now correctly preserved when the user makes changes to the selection screen or moves to other wizard screens.

3.0.0 (19 June 2015)

LinkFixer Advanced will now process your files, and complete your project, up to three times faster. We have added the ability to process multiple parent files at the same time, through the use of multiple “threads” in the Windows operating system. This will allow you to complete large projects faster, while using fewer instances of LinkFixer Advanced. LinkFixer Advanced determines how many files to process at the same time based on the number of processors it detects in the computer on which it is installed. So, you don’t need to calculate or configure anything to benefit from this new capability.

The LinkFixer Advanced Inoculate, Move/Rename and Modify Links processes can now be completed in about half the time they have previously taken. Instead of requiring two separate steps — for example, Scan and Inoculate — Scan can now be done at the same time as the Inoculate, Move/Rename or Modify Links function, in a single step. This will allow you to complete your project faster, with less interruption for your end users.

LinkFixer Advanced reports are now easier for you to understand and use. We have enhanced the layout of the PDF “Summary” reports for each of the functions, to give you additional statistics, summarize warnings and errors, and to be more concise. The Comma Separated Value (CSV) data file has been split into three files — one for files that were skipped (not processed for some reason), one for the files that were processed normally,

Page 248 LinkFixer Advanced

and another for the files that generated a warning or error when processed. So, now you can easily find exactly the type of information you need — Summary, Skipped, Details or Exceptions.

You will find yourself spending much less time waiting for the previews of the LinkFixer Advanced Inoculate and Cure processes to be generated. Previously, all selected files needed to be scanned before a preview could be presented. This procedure has been enhanced so that the preview is now presented after a maximum of 1,000 links have been scanned. Now you will get a preview right away, even if you are processing millions of files.

A LinkFixer Advanced bug was fixed that previously caused an error when a user would click on the Network Locations tab, but no Network Places or drive letters had been previously been mapped in Windows to display.

A bug in the Microsoft Excel plug-in was fixed that occasionally caused an access violation exception while loading a file.

A bug in LinkFixer Advanced was fixed that occasionally caused LinkFixer Advanced to “hang” for ten minutes at the end of a function. This error only occurred when the last file processed during a task was corrupt and causes the LinkFixer Agent process to be restarted. LinkFixer Advanced now recognizes this unusual situation and continues without pausing.

A memory leak (bug) that affected all of the Microsoft Office file-type plug-ins was eliminated.

A bug in the LinkFixer Advanced was fixed that had previously caused the Modify Links process to fail if the “Match slash orientation” setting in the rename rule was enabled.

A LinkFixer Advanced bug was fixed that previously caused Modify Links to report that some links were modified when they were not. This issue occurred when a file that contained Unicode characters was rewritten to a temp location and then could not be copied back to the original location. This caused changes to the file to be lost.

2.4.0 (4 December 2014)

LinkFixer Advanced now processes files about 50% faster. LinkFixer Advanced was enhanced with a faster method of controlling the file-type plug-ins and the files they process. This eliminates the need for a slower subsystem that previously controlled the plug-ins and produces reductions in processing times of approximately one third.

LinkFixer Advanced users will no longer need to compress and upload huge log files when they are requested by LinkTek Support. We have found a way to improve your user experience, while saving you some time. LinkFixer Advanced was enhanced with a new “automatic” log level that logs a minimum of information when files are processed normally. If an exception or error occurs, detailed (“verbose”) log information is written to the log file, to assist the developers in diagnosing the issue. LinkFixer Advanced now produces smaller log files and processes files and links faster than was previously possible with “verbose” logging enabled. “Automatic” is now the default log level for LinkFixer Advanced.

The trial version of LinkFixer Advanced is now more useful than ever. The trial version can now scan and report on up to 100 GB or 100,000 files in a single run. Trial users can also process up to 500 links per day using each of the other LinkFixer Advanced

Chapter 20 — New Features and Fixes Page 249

functions (Inoculate, Cure, Move/Rename and Modify Links), and up to a total of 5,000 links per function during the course of the 21-day free trial.

If you have multiple instances of LinkFixer Advanced connected to a single SQL database, you can now pause each instance after the scan step of Cure, before the Cure process begins. This will allow all of your instances to complete the scan step before any instance begins curing links. LinkFixer Advanced was enhanced with this “pause” option specifically to help users who are processing very large file sets using multiple instances of LinkFixer Advanced at the same time.

Future releases of LinkFixer Advanced can now be released more often, after being tested more thoroughly. A new LinkFixer Advanced testing program has been created for internal use in testing new builds and releases. This program allows for faster and more thorough automatic testing of a large variety of different link types, in and between many different local and network locations.

A bug was fixed in LinkFixer Advanced that had previously caused a subset of Microsoft Office files to present an error message when opened by the Office application after being Inoculated by LinkFixer Advanced. This issue effected only newer (XLM) Office files that were simultaneously a parent file and a child file, and only when the file was processed as a child file prior to being processed as a parent file.

A LinkFixer Advanced bug was fixed that had caused a Windows exception message to be displayed when the “LinkFixer Agent” process was restarted in the course of its normal operation.

A LinkFixer Advanced bug was fixed that had previously prevented files from being moved from OpenText to the local drive using the Move/Rename process.

We can now process links in your DOC and DOCX files that have the # symbol in them. A bug in the Microsoft Word plug-in was fixed that had previously dropped the “#” symbol from links in DOC and DOCX files. LinkFixer Advanced now recognizes and preserves these “bookmark” symbols, and processes these links correctly.

A bug in the Microsoft Word plug-in was fixed that had previously caused some DOCX files to be reported as corrupt by Word after being inoculated by LinkFixer Advanced. This bug effected only files containing multiple links to the same child file, and when those links were stored in more than one format (such as “relative”, “absolute” or UNC) within the same file.

A bug in the Microsoft PowerPoint plug-in was fixed that had previously caused the some PPTX presentations to appear to be corrupted by the Modify Links process. This caused some lines of text that were on separate lines in the “before” file to be contained in a single line in the “after” file.

A bug in LinkFixer Advanced was fixed that had previously caused some files to not be processed because the temp file created and used by LinkFixer Advanced to rewrite files would become locked. LinkFixer Advanced now uses a different method to identify temp files, to prevent this locked-file issue in the future.

Bugs in Microsoft Excel and PowerPoint plug-ins were fixed that had previously caused the link text of links in XLSX and PPTX file to not be modified when the link text matched the link path.

A bug in LinkFixer Advanced was fixed that had caused spaces in HTML files to be encoded (changed to “%20”) twice when the files were processed by the Move/Rename process while moving the files out of SharePoint.

Page 250 LinkFixer Advanced

A bug was fixed in the Microsoft PowerPoint plug-in that previously prevented some PPTM files from being loaded and processed.

A bug was fixed in the Microsoft PowerPoint plug-in that had previously caused links in PPT files that had been processed by the Modify Links process to revert to the previous link path when the link was clicked in PowerPoint “Presentation Mode”.

The Microsoft Excel plug-in was enhanced to be more tolerant of non-standard macros when loading XLS. These non-standard macros had caused LinkFixer Advanced to record an error in the logs, and to stop processing the file. Such files are now successfully processed.

A bug in the Microsoft Word plug-in was fixed so that hyperlinks located within fields in DOC files now load and are processed correctly.

A bug in LinkFixer Advanced was fixed that previously caused relative links to be incorrectly reported as absolute on the Cure Report.

2.3.0 (23 September 2014)

A LinkFixer Advanced bug was fixed that previously caused LinkFixer Advanced to hang when attempting to open certain corrupt files. A time-out was added to cause LinkFixer Advanced to skip any file that takes more than a certain amount of time to open. This time-out period is configurable in the “LinkFixer User Settings” file.

LinkFixer Advanced was enhanced to add support for links pointing to resource types sftp://, ssh://, svn://, and res://. Such links cannot be validated during the Scan process, and cannot be Inoculated or Cured, but can be modified by the Move/Rename process or Modify Links.

Technical: All file-type plug-ins now require that an unlock key be passed to them by the licensing module in order to operate. All plug-ins now return an error if they receive input instructions without first being unlocked.

LinkFixer Advanced was enhanced to update hyperlink text when the underlying link is contained in the hyperlink text. Previously, LinkFixer Advanced required that the hyperlink text exactly match the underlying link. This function has also been enhanced to make it more tolerant of leading and trailing spaces, trailing punctuation, and the trailing slashes that are often added automatically to links by Microsoft Office applications.

A Microsoft Excel plug-in bug was fixed that previously caused XLS files modified by the Modify Links process, using the option “Update hyperlink text when the hyperlink is changed, regardless of whether hyperlink text is the same as the hyperlink path”, to report errors when the files were subsequently opened by the Excel application. Such links are now processed correctly.

A bug in Microsoft PowerPoint plug-in was fixed that prevented the Modify Links process from updating the hyperlink text when it was the same as the link path. A related bug was also fixed that prevented the Modify Links process from updating the link path unless it was the same as the hyperlink text.

A LinkFixer Advanced bug was fixed that previously caused some types of Excel (XLSB) and PowerPoint (PPTX) files to be reported as unsupported zipped (PKZ) files. These file types are now recognized, processed and reported correctly.

Chapter 20 — New Features and Fixes Page 251

A bug in the Microsoft Excel file handler was fixed that previously caused many (non-existent) “invalid links” to be reported for a specific XLSX file. The unusual file structure of this type of file is now correctly recognized and the non-existent links are no longer reported.

A bug in the Microsoft Excel file handler was fixed that prevented links from an XLS file to an MDB file, containing both a connection string and a command string, from being processed. Such files are now recognized, processed and reported correctly.

A bug in LinkFixer Advanced was fixed that caused successive scans to show an inconsistent number of links in a specific XLSX file.

A bug was fixed that caused LinkFixer Advanced to attempt to validate links with the forms \\www.???.com and \\xxx.???.com, even though the user option to “Check external links pointing to Web-based files” was disabled.

LinkFixer Advanced Full Scan and Incremental Scan CSV reports were enhanced to include a count of links that have not changed since the last scan. The associated PDF reports were also enhanced to include the following new statistics: “Files not changed since last scan” and “Links not changed since last scan”.

The statistics section of LinkFixer Advanced Scan reports was enhanced to hide from the report any sub-categories of “skipped links” that contain zero entries. Now, only non-zero sub-categories are shown on the report.

A bug in the statistics section of LinkFixer Advanced Scan reports was fixed that previously showed the value “-1” for the category “Files with no broken links”.

A bug in LinkFixer Advanced was fixed that caused “mailto:” links to be reported with the error “cannot be modified due to an illegal character”, even though the links were correctly modified, and the “after” link on the report showed the correct modified link path.

A bug in LinkFixer Advanced was fixed that caused the Modify Links “Preview Matching Links” and “Preview Links to be Modified” screens to not show any links available for processing when only the “files” node was selected in the “Select Parent Files” screen. This error would not appear if the entire parent folder was selected, or if any sub-folders were selected along with the files in the folder. This has been fixed and the previews now operate correctly.

2.2.4 (5 August 2014)

A bug in LinkFixer Advanced was fixed that previously caused password-protected XLSM files to be incorrectly reported as an unsupported file type “OLECF”. These files are now correctly reported as “password protected”.

The Microsoft Word plug-in was fixed to correctly recognize and process certain types of links contained in VBA macros that were previously not recognized or processed. So, more of the links in your VBA macros will now be processed by LinkFixer Advanced.

A bug in the Microsoft Word plug-in was fixed that caused links in some older DOC files to be re-written with an empty link path when the link was changed to its relative path by the Modify Links process. Such links are now processed correctly. If you had trouble with some links that were forced relative by the Modify Links process in DOC files, this new version fixes that issue.

Page 252 LinkFixer Advanced

A bug was fixed in the Microsoft Word plug-in that caused internal links in DOC files to be reported as links, but with an empty link path. These links are now correctly skipped and reported as skipped. This will get rid of “phantom” links in the scan report of DOC files containing bookmarks.

The Microsoft Word plug-in was fixed so that DOCX files containing multiple instances of the same link no longer present an error when opened after being inoculated. This type of file is now processed correctly. If Word reported some of your DOCX files as corrupt after being inoculated, this update will solve the problem.

Technical: The internal architecture of LinkFixer Advanced has been enhanced to improve processing efficiency and speed. These changes also make it possible to further enhance LinkFixer Advanced in the future to run multiple processing “threads” at the same time, which will result in further improvements in processing efficiency and speed.

2.2.3 (16 July 2014)

LinkFixer Advanced has been enhanced with an option to “Hide Broken Links” in the set-up screen for Regular reports. Some users want to create a report that shows only links that are valid (working). This ability to show only valid links in the report was not previously available but is available now.

LinkFixer Advanced has been enhanced with the ability to automatically refresh and recognize the online status of newly added or removed network locations while LFA is running. Now, if you map a drive in Windows Explorer while LinkFixer Advanced is open, the new mapped drive will be automatically recognized and added to the Network Locations in LinkFixer Advanced. A manual refresh was previously required to accomplish this function.

A LinkFixer Advanced bug was fixed that prevented links containing bookmark data from being converted to relative paths using the Modify Links process.

LinkFixer Advanced was fixed to handle a bug that sometimes prevented file selection data from being correctly updated and used when running a process such as Scan.

A LinkFixer Advanced bug was fixed that caused an exception at startup when the user settings file was missing.

A bug in LinkFixer Advanced Cure process was fixed that had caused an incorrect selection of parent files to be scanned in certain circumstances. This occasionally resulted in the LinkFixer Advanced database containing incorrect or missing records.

A LinkFixer Advanced bug was fixed that had caused the “Process Broken Links” and “Process Non-Broken Links” Expert Options settings for the Modify Links process to revert to their default state (enabled) after being changed by the user. These settings now persist after LinkFixer Advanced is closed. This means you no longer need to change these settings every time you run the Modify Links process (if you need or want to disable these settings).

LinkFixer Advanced was fixed to eliminate an error that occurred when users attempted to use Modify Links to change links pointing to folders. Links in files usually point to other files, but in some cases can point to folder locations. Such links to folder locations were previously not processed correctly. Links to folders are now modified as expected according to the active rename rules.

Chapter 20 — New Features and Fixes Page 253

A LinkFixer Advanced bug was fixed that previously prohibited relative links containing a colon in the file path from being processed.

LinkFixer Advanced was fixed to eliminate a bug that caused Move/Rename process to fail when moving files directly from OpenText to SharePoint.

The JavaScript plug-in was fixed to eliminate a bug that had caused the Inoculate process to run very slowly when processing JavaScript files with a specific internal structure.

Technical: To correct a prior design decision, all of the newly-rewritten LinkFixer Advanced file type handlers have now been modified to operate under the LinkFixer Advanced Service module (crash prevention software). This was done largely as a precaution after it was discovered that some .NET processes can generate “out-of-memory” exceptions, even though they are running under the control of .NET memory management platform. LinkFixer Advanced legacy file type plug-ins have long operated under this LFA Service module to guard against errors resulting from file and memory corruption.

2.2.2 (30 May 2014)

LinkFixer Advanced was enhanced with new plug-in for scanning and modifying links in databases in SQL Servers.

LinkFixer Advanced was enhanced with a new setting that allows users to move files, using the Move/Rename process, without modifying the links in the moved parent files.

The MicroStation plug-in was enhanced with the ability to modify OLE links in DGN parent files pointing to SharePoint locations, and OLE links to locations with UNC paths.

The Microsoft Excel plug-in was fixed to eliminate a bug that was causing a LinkFixer Advanced sub-system (LFPRW) to restart unnecessarily when processing some XLS files.

The bug in the Microsoft Word plug-in was fixed that was causing some links to not be visible to LinkFixer Advanced after applying “Force mapped drive to UNC” to DOC files located on a mapped drive.

The Microsoft Access plug-in was fixed to eliminate a bug that was causing links in MDB files to lose their inoculation (linkID) after links were forced absolute.

Microsoft Access plug-in was fixed to automatically prepend “..” on any Access link paths that begin with only a backslash (“\”). This bug was causing these links in ACCDB files to be reported as broken when they were actually valid.

A LinkFixer Advanced bug was fixed that caused links to not be modified when files were moved to a mapped drive using the Move/Rename process.

A bug was fixed in LinkFixer Advanced that was causing PDF parent files located on mapped drives and containing UNC links to not be inoculated.

LinkFixer Advanced was fixed to eliminate a bug that caused links in XLSX parent files to not be modified to the expected new path when the parent files were moved using the Move/Rename process.

A bug was fixed in LinkFixer Advanced that caused links pointing to folders to not be fixed when using the Modify Links function.

Page 254 LinkFixer Advanced

The LinkFixer Advanced Scan Report was enhanced to split the “(None)” child file extension, in the File Type matrix at the end of the report, into several distinct categories. This improves that clarity of the data in the File Type matrix.

2.2.1 (30 April 2014)

LinkFixer Advanced was enhanced to be able to read files that have been opened by users without an exclusive lock. Note that such files still cannot be inoculated, cured or modified while open.

The LinkFixer Advanced Scan process wizard was enhanced to include a preview of files to be scanned. This allows users who apply file filters to the Scan process to preview the effects of their filters before running the process.

LinkFixer Advanced was enhanced to support additional Microsoft Office XML file types (2007–2013 versions) that have macros that are contained in binary files. New file types added are XLTM, XLAM, XLSB, PPAM, POTM, PPSM. These are in addition to the DOCM, XLSM and PPTM file types that were previously handled.

LinkFixer Advanced was enhanced with the ability to recognize, parse and modify links to ProjectWise files (links prefaced with pw://). Links to ProjectWise child files cannot yet be validated, inoculated or cured, however.

LinkFixer Advanced was enhanced with the ability to show and process hidden files along with other file types. One practical use of this enhancement is the ability to process shortcuts stored in hidden folders.

A bug was fixed in LinkFixer Advanced that caused expert file and link filtering rules to not get saved and subsequently restored.

A bug was fixed in LinkFixer Advanced that had caused the grids in the “Process files [links] matching filters that are different for each folder” to not get updated when folder selections were changed.

2.2.0 (11 April 2014)

LinkFixer Advanced was enhanced to add support for SharePoint 2003.

LinkFixer Advanced was enhanced to add support for OpenText.

LinkFixer Advanced was enhanced with a new faster method of determining the file type of parent and child files during the Scan process. Additionally, over 50 new file types are now recognized.

LinkFixer Advanced was enhanced with the ability to connect to SQL Server databases (including SQL Express). This improves the performance of LinkFixer Advanced when processing large file sets.

LinkFixer Advanced was enhanced with faster, rewritten plug-ins for the DOCX, XLSX, PPTX, JPG, BMP, TIF and GIF file types. This increases dramatically the processing speed for these file types and produces a general improvement in processing speed for file sets containing a mix of these and other file types.

LinkFixer Advanced was enhanced with the ability to comply with existing group policy registry settings that disable browsing of the network by users with restricted

Chapter 20 — New Features and Fixes Page 255

permissions. LinkFixer Advanced previously showed all available network servers and shares, even if the logged-on user did not have permission to access those resources.

LinkFixer Advanced has been enhanced with new file handlers for 15 media file types: MP4, M4V, MOV, AVI, CDA, QCP, RMI, WAV, ASF, WMA, WMV, MKV, FLAC, MP3 and M4A. These new file handlers dramatically increase the speed with which the Inoculate and Cure functions can process these media file types.

LinkFixer Advanced was enhanced with a new plug-in to process PNG graphics files as a supported child file type.

LinkFixer Advanced was enhanced with the ability to Move/Rename or Cure files directly from SharePoint to OpenText while automatically fixing links.

LinkFixer Advanced was enhanced with improved detection of online and offline network locations. LinkFixer Advanced now “remembers” network locations that are not accessible and does not waste time re-checking locations that cannot be reached. This improves processing speed for files that contain links to inaccessible locations.

LinkFixer Advanced was enhanced to allow users to choose to install the software either for a single user or for all users of the computer, during the installation process.

LinkFixer Advanced was fixed to be tolerant of leading and trailing spaces in link paths contained in parent files. Such files previously could not be processed and resulted in an error message.

All Microsoft Office plug-ins were fixed to be tolerant of encoded special characters in link paths. Links containing these characters were previously not modified as expected.

DGN (MicroStation) plug-in was enhanced to recognize and process OLE links to Microsoft Office files. OLE links in MicroStation files were previously not supported.

DGN (MicroStation) plug-in was fixed to add support for files containing internal links to references within the parent DGN file itself. These internal references were previously not detected or handled.

LinkFixer Advanced was enhanced with the ability to write custom fields to SharePoint to retain an item’s “modified” timestamp and “modified by” user name when requested by the user.

LinkFixer Advanced was enhanced to support caching an item’s metadata to improve performance when processing SharePoint sites.

A bug in the LinkFixer Advanced progress indicator screen was fixed to correctly reflect activity while updating the database. This bug cause LinkFixer Advanced to appear to “hang” (stop responding) when a large number of database updates were occurring.

LinkFixer Advanced was fixed so that OpenText links are now categorized as broken and non-broken links in the dashboard. These links were previously not reported in the dashboard statistics.

LinkFixer Advanced was fixed to be able to resolve and modify relative links in files within OpenText. Such relative links previously could not be resolved.

LinkFixer Advanced was enhanced to use multiple simultaneous threads to retrieve DocumentIDs from SharePoint. This reduces the time required to scan files in SharePoint.

A LinkFixer Advanced bug was fixed that was causing some child files in SharePoint to not appear on Scan reports.

Page 256 LinkFixer Advanced

A bug in LinkFixer Advanced was fixed that was causing files and links that were correctly modified in the Move/Rename process to not be shown on the Rename Report.

A bug was fixed in LinkFixer Advanced that was causing external web links, skipped as a result of the user option setting “Skip external links”, to be reported as “broken”, instead of as “skipped”.

LinkFixer Advanced was fixed to be able to backup files to the same folder as the target file. This feature was previously not working.

LinkFixer Advanced was fixed so that SharePoint sites containing child files are automatically mapped during the Inoculate process. This allows users to successfully inoculate files in SharePoint without knowing in advance which SharePoint sites contain child files, and mapping those sites, prior to running the Inoculate process.

Adobe Acrobat plug-in was fixed to be able to handle Acrobat files that contain data at the beginning of the file, prior to the file header. Such files previously could not be processed and were reported as “corrupt”.

A bug in LinkFixer Advanced was fixed that was causing some SharePoint sites to not be recognized and mapped correctly. Files in these locations can now be detected and processed.

LinkFixer Advanced was enhanced to provide a setting for the Modify Links function that allows the user to select whether or not LinkFixer Advanced will check rename rules for characters that would cause illegal paths in Windows. By default, LinkFixer Advanced checks all rename rules for illegal characters, to protect against accidentally modifying links in a manner that would result in invalid links. Users who have parent files containing links with command data (containing illegal characters) appended to the file paths and wish to have those links processed by LinkFixer Advanced, can now disable this feature.

Microsoft Word and Excel plug-ins were fixed to eliminate a bug that caused processing of some Word and Excel files with macros containing the “Dir” command to fail.

LinkFixer Advanced was fixed to eliminate a bug that caused some ASPX files in SharePoint to be reported as corrupt when they were not.

Microsoft PowerPoint plug-in was fixed so that it now returns the correct error message when attempts to modify links fail because no file exists at the destination location.

Microsoft PowerPoint plug-in was enhanced to recognize and correctly handle files that use the “Best speed” method to compress serialized OLE links. These files were previously reported as corrupt.

Microsoft Visio plug-in was fixed so that files containing embedded OLE objects no longer return an OLE error.

A bug was fixed in the MicroStation plug-in that caused a new Windows “handle” to be created, but not terminated, for each file processed. This had caused the number of open handles to steadily increase when DGN files were processed.

A bug was fixed in Microsoft Word and Access plug-ins that caused a new Windows “handle” to be created, but not terminated, for each file processed. This had caused the number of open handles to steadily increase when DOC and MDB files were processed.

Microsoft Excel plug-in was enhanced to recognize and modify links contained within data-acquisition commands. These commands establish data connections to an Access database, but were previously not recognized by the plug-in.

Chapter 20 — New Features and Fixes Page 257

A LinkFixer Advanced bug was fixed that caused sections of the Dashboard to sometimes appear to overlap.

LinkFixer Advanced was enhanced with a setting to enable or disable previews in process wizards. Disabling previews can save users time waiting for these previews, when preparing to process large files sets.

2.1.0 (5 August 2013)

LinkFixer Advanced was enhanced to add support for Microsoft Office 2013 file types.

LinkFixer Advanced was enhanced to add support for Microsoft SharePoint 2013

LinkFixer Advanced was enhanced to add support for Microsoft Visio files.

LinkFixer Advanced was enhanced to be able to recognize and process “mailto:” links and http links containing a “query” section.

LinkFixer Advanced was enhanced with the ability to run from the command line using a saved settings file. This will allow unattended operation of LinkFixer Advanced using a batch file.

LinkFixer Advanced was enhanced with the ability to import rename rules in bulk from an Excel spreadsheet.

LinkFixer Advanced’s module that processes files on WebDAV servers was completely re-written so that your files on SharePoint (and other WebDAV servers) will be processed faster.

LinkFixer Advanced was enhanced with a completely-rewritten, faster, more efficient method of obtaining the SharePoint DocumentID for files, with a rewritten, more efficient ability to obtain DocumentIDs for files located in SharePoint sub-sites, and with a new ability to convert links containing DocumentID addresses back to their full-filespec absolute addresses.

LinkFixer Advanced was enhanced with two new Rename Methods in Modify Links:

“Convert links to SharePoint Document IDs” and “Convert links from Document IDs”. These functions are useful when you are moving files into or out of SharePoint, or when you initially implement DocumentID service for files within SharePoint.

LinkFixer Advance was enhanced so that the user now has the choice to install the program so that it can be used by all users of the computer, or only by the current user. This gives you additional flexibility in using LinkFixer Advanced.

LinkFixer Advanced was enhanced with an address bar in all folder selection screens. This address bar displays folder path addresses as you select them on the screen, and also allows you to paste a folder path into the address bar in order to quickly navigate to a specific folder. This may simplify your selection of folders in situations where the path to a specific folder is long or complicated.

LinkFixer Advanced was fixed so that child files no longer need to be licensed file types in order to receive a linkID instead of a checksumID during the Inoculate process. Using linkIDs to track child files is more accurate and dependable than using a checksumID.

LinkFixer Advanced was enhanced so that all sub-systems now send log entries to the same LFA.log file, instead of to several separate log files. This will help our developers find and fix bugs more quickly for you in the future.

Page 258 LinkFixer Advanced

LinkFixer Advanced logging performance was optimized by adding a separate write thread. This should allow LinkFixer Advanced to process your files slightly faster.

LinkFixer Advanced reports were enhanced to provide additional information in the Summary section about the numbers of password protected files, inaccessible files, hidden or system files, email links, external web links, internal document links, and other/unsupported links encountered during Scan. Reports were fixed to clarify and simplify informational messages in the body section and to clarify some error messages in the Errors section. Messages for “unlicensed”, “unrecognized” and “unsupported” file types were fixed to improve clarity. These improvements and fixes will make the reports more informative and easier to understand.

LinkFixer Advanced was enhanced to add to the user interface a new button to rescan, and report the status of, all network connections. This feature enables LinkFixer Advanced to recognize and access network resources that were mapped or connected after LinkFixer Advanced was started. This will allow you to identify and connect to any network resources that will be needed while running LinkFixer Advanced, but which are not currently connected or authenticated.

LinkFixer Advanced was enhanced by adding file selection (“browse”) buttons to the Rename Rule creation box. This will make it easier for you to create rename rules, and help you eliminate typographical errors in rule paths.

LinkFixer Advanced was enhanced with checkboxes to allow users to enable/disable individual rename rules in Move/Rename and Modify Links. This will allow you to create batches of rules, but only activate individual rules as you need them.

LinkFixer Advanced was enhanced with a “New scan” option that clears from the database the results of previous scans. This means you no longer need to navigate to the “Options | Database” screen in order to clear the database before starting a new scan.

A bug was fixed that caused certain Windows 8 applets to stop working after running LinkFixer Advanced.

LinkFixer Advanced was fixed so that links with relative paths from the root directory are now parsed and resolved correctly.

A bug was fixed so that the user option to “Force Links Absolute” after Move/Rename now works. This function was previously broken.

LinkFixer Advanced was fixed to remove file monikers from Excel links when attempting to resolve links to specific Excel worksheets and cells, so that only the link to the child file (but not the worksheet or cell address specification) is passed into the Excel plug-in. This eliminated an error, experienced by some users, where some links in Excel files were reported as broken when they really were not. These links are now reported correctly.

LinkFixer Advanced was fixed to display a warning message if LinkFixerService (a fail-safe crash-prevention module) doesn’t start properly along with the rest of the application, while allowing LinkFixer Advanced to continue running with LinkFixerService disabled. This allows you to continue to use LinkFixer Advanced while we fix whatever caused LinkFixerService to start improperly.

LinkFixer Advanced now tests at start-up whether it has read/write/delete access to all folders it will use in normal operation. This fixes an exception that occasionally occurred if LinkFixer Advanced did not have complete access to a “Temp” folder.

Chapter 20 — New Features and Fixes Page 259

LinkFixer Advanced was fixed to eliminate an exception that occurred when attempting to get child file “last modified time” and file size on SharePoint files.

Two different LinkFixer Advanced bugs were fixed that produced “null reference” exceptions at start-up and when changing any settings.

LinkFixer Advanced was fixed to recognize and retain brackets in Excel links that were previously getting lost. This bug was causing links with brackets to be modified incorrectly.

LinkFixer Advanced now correctly handles links that point to folders instead of to files.

Such links previously produced an error message and were incorrectly handled.

LinkFixer Advanced was fixed to correctly handle several different types of “file access” errors. These errors previously caused files that were actually present and accessible to be reported as missing or unreachable.

LinkFixer Advanced was fixed so that links with a specific type of link path construction, pointing to Excel files, are now handled correctly in instances where they previously were not.

A bug in LinkFixer Advanced was fixed so that some links to external sites are now being validated in instances where they previously were not. These links were being reported as broken when they were actually valid.

A bug in LinkFixer Advanced handling of file permissions was fixed to correct an issue that caused some links in parent files to not show up on Scan reports.

LinkFixer Advanced now installs two additional Microsoft Visual C libraries to fix an issue where PDF files caused an exception during the “Force Links Absolute” function. Force Links Absolute now works with UNC paths to PDF files.

LinkFixer Advanced was fixed so that the process progress indicator more accurately reflects actual progress. Previously, the total or “target” number for completion was not taking into account the number of child files, discovered during the scanning of parent files, which also needed to be scanned.

LinkFixer Advanced now correctly parses links containing the “#” symbol, and links containing multiple periods in the file base name. These files previously caused errors, and were not correctly processed.

LinkFixer Advanced now correctly processes links formatted as

“file:///\\server\sharename”. Such links were previously not recognized or processed.

LinkFixer Advanced now correctly processes links formatted (incorrectly) as “file://”. Such links were previously ignored, but are now recognized and processed, even though they do not contain the standard three forward slashes.

LinkFixer Advanced was fixed to eliminate an “OutOfMemory” exception encountered while scanning multi-terabyte file sets. LinkFixer Advanced was unnecessarily holding in memory some link path information that eventually, on huge file sets, would accumulate to fill all available RAM.

LinkFixer Advanced now correctly finds child files with filenames containing HTML encoded characters (such as the %20 sequence that represents a “space”). Links to such files were previously reported as broken.

A bug was fixed where the Inoculate process failed on some links with UNC paths.

Page 260 LinkFixer Advanced

LinkFixer Advanced was fixed to eliminate an issue where some files selected by the user to be cured were not being shown in the preview of files to be cured and were not being cured.

LinkFixer Advanced was fixed to correctly show, on Move/Rename and Modify Links reports, all links to files inoculated using the LinkFixer Advanced alternative inoculation method (“checksumID”). Such links were previously missing from the reports.

LinkFixer Advanced was fixed to correctly move and rename files from one SharePoint site to another, while maintaining correct DocumentID paths. Files moved from one site to another are assigned new DocumentIDs by SharePoint, but the links to these files were previously not being updated by LinkFixer Advanced with the new DocumentIDs.

A bug in LinkFixer Advanced was fixed so that file counts in LinkFixer Advanced dashboard and reports match with file counts from Window Explorer. The counts in the dashboard and in the reports previously did not take into account hidden and system files that were counted and reported by Windows Explorer.

LinkFixer Advanced now correctly forces links to lower or upper case when that user option is selected during the Move/Rename process. Selecting these options previously resulted in no changes in the links.

A LinkFixer Advanced bug was fixed that prevented some unknown/unsupported child file types from being cured. Unknown/unsupported file types are now cured correctly.

Microsoft Excel plug-in has been enhanced so that it can now recognize and process links in XLSX files containing the new link prefix “=HYPERLINK”.

Microsoft Excel plug-in was fixed to correctly handle Excel 97-2003 files with relative links containing the “..\” link construction.

Microsoft Excel plug-in was fixed to eliminate an “Invalid C runtime parameter” error that previously occurred while rewriting some XLS files.

Microsoft Excel plug-in was fixed to correct an error where hyperlink text was being incorrectly changed in some Excel files where one hyperlink path was contained in multiple different cells.

Microsoft Excel plug-in bug was fixed that caused Excel files to be opened in Office 2010 “protected mode” after the Move/Rename process modified links contained in drawing objects.

Microsoft PowerPoint plug-in was fixed to eliminate instances where some link text in PPTX files was being incorrectly updated by the Move/Rename process. This error occurred occasionally in cases where the link text was the same as the link path. The link path was being correctly updated, but link text was not.

Microsoft PowerPoint plug-in was fixed to eliminate an “overflow” error that occasionally occurred while renaming very long links in PPT files.

Adobe Acrobat plug-in was fixed to eliminate an “array size” error that occurred while renaming some links in PDF files.

Adobe Acrobat plug-in bug was fixed that incorrectly reported some PDF files as corrupt.

Adobe Acrobat plug-in was fixed to eliminate an error reading data streams in PDF files that was previously causing the LinkFixerPlus Read-Write sub-system to repeatedly restart.

Chapter 20 — New Features and Fixes Page 261

Microsoft Word plug-in bug was fixed that caused some links contained in nested fields in DOCX files to be rewritten incorrectly.

Microsoft Word plug-in bug was fixed that caused some password protected DOCX files to be mishandled because they were not being identified as password protected.

AutoCAD plug-in was fixed so that the switch controlling the option to “Update XReference names...” now works correctly. All Xref aliases were previously being always updated to the Xref file name.

AutoCAD plug-in can now correctly determine the AutoCAD installation directory under Windows 7 and Windows 8 operating systems.

AutoCAD plug-in was fixed to correct an error that previously caused the rewriting of some DWG files to fail with “error 5200”.

InDesign plug-in was fixed to recognize and correctly process links in INDD files that were previously not recognized.

2.0.5 (11 January 2013)

Initial release.

← Chapter 17

User’s Guide — LinkFixer Advanced

Chapter 18 — New Features and Fixes

Data Disasters Await: Protect Your Links or Face Catastrophe!

Ebook Download - Popup

LinkTek Technical Support