Error 1315 Unable to write to the specified folder (Windows 10 v2004)

Error 1315 Unable to write to the specified folder (Windows 10 v2004)


This Windows Installer error can occur during a TopView upgrade or uninstall on Windows 10 v2004 indicating that the installation cannot write/edit an installation folder used by the current TopView installation. This may occur if the TopView DataPath from the most recent TopView installation is located on a network share. The installation message shows this error for a folder located in the TopView DataPath even though the installation user has edit/write/read access to the DataPath files/folders.
Note: We first saw this error on Windows 10 machines running version 2004 (Spring/Summer of 2020) and were able to confirm with Microsoft that this error is caused by Windows 10 version 2004. A Microsoft update is planned for mid-July 2020 to fix this issue.  

How to fix

It would appear that this error could be resolved by changing the permissions/security on the TopView DataPath (network share) although our efforts to do this were not successful. The installation is being blocked from updating/editing folders on the share even though it should have permission to do this.
Although we do not recommend this: users can revert to the previous version of Windows (Settings...Updates and Security...Recovery...Go back to the previous version of Windows 10) but this may also remove applications that were installed after the machine was updated to v2004. 

Fix: Rename DataPath folders before upgrade or uninstall

To fix this issue you can rename some of the folders in the DataPath, then perform the uninstall or upgrade. Upgrade users will then restore some of the information in the renamed folders (from your previous TopView installation) to the folders recreated by the upgrade installation

Make a backup of the following folders in the DataPath: 

Rename these DataPath folders:
o API_Configuration to API_Configuration_prev
o Config to Config_prev
o CustomDS to CustomDS_prev
o EventHooks to EventHooks_prev
o RemView to RemView_prev
o Sounds to Sounds_prev
o Voice to Voice_prev

Perform the TopView upgrade or uninstall. This should now be successful.

Upgrade users: Do not run any TopView applications yet. 
The folders that you renamed above will be recreated by the installation. The contents of these folders will be the same as the contents during a new installation of TopView since the folders did not exist during the installation. You should see these recreated folders as well as your renamed folders. For example, you should see RemView and RemView_prev. 
You will need to restore some DataPath files/folders from your previous TopView installation (folder_prev) to the new TopView installation (folder).
Note: most users will only need to restore information from Config_prev, RemView_prev, and Sounds_prev, and Voice_prev.
  1. API_Configuration
    This folder contains the most recent TopView Configuration API. No action required. API_Configuration_prev can be removed.
  2. Config 
    This folder should contain your TopView configuration files that currently exist in Config_prev. You can either
    1. Delete Config and rename Config_prev to Config
    2. Replace the contents of Config with the contents of Config_prev.
      Replace the files and folders
  3. CustomDS
    This folder contains the most recent Custom DataSource assembly. No action required for most users unless you created a custom data source for TopView. CustomDS_prev can be removed.
  4. EventHooks
    This folder contains the TopView EventHook assembly. Most  users will not require any action.
    If you created an EventHook and placed an assembly into the previous EventHook folder you should copy this assembly from EventHook_prev to EventHook.
    EventHook_prev can be removed.
  5. RemView
    This folder contains the Remote Viewer application and the default Remote Viewer configuration xml file if the Remote Viewer was used on the TopView machine.
    If the file TVRemView.xml exists in RemView_prev, copy this file to RemView.
    RemView_prev can be removed.
  6. Sounds
    This folder contains audio WAV files used by TopView Audible Alarms.
    Copy all files from Sounds_prev to Sounds overwriting any existing files in Sounds.
    Sounds_prev can be removed.
  7. Voice
    This folder contains audio WAV files used by TopView Voice Notification.
    Copy all files from Voice_prev to Voice overwriting any existing files in Voice.
    Voice_prev can be removed.
You can now proceed with TopView upgrade instructions available on the TopView download page for your TopView version.

    • Related Articles

    • Allow a Windows user to start/stop a service

      Background On newer Windows OS’s, the current user may not be allowed to install/start/stop services.  This may prevent the user from installing/starting/stopping TopView Engine Services. The solution has been to run the Configurator “as ...
    • Windows patches and TopView

      Windows patches affect TopView operation. To ensure TopView runs successfully after a Windows patch, we recommend the following during the patching process: Shut down TopView Engine services before Windows patches Apply the Windows patch After the ...
    • Unable to connect to iFix: "Requested operation requires elevation" - error 0x800702e4

      The error you are seeing is a Microsoft DCOM error 0x800702e4. OPC uses DCOM. When TopView connects to the OPC server it doesn't have the ability to override a DCOM connection error. This is based on DCOM configuration for the OPC Server (run ...
    • Error 1606 Could not access network location

      Background This Windows Installer error can occur during a TopView upgrade or uninstall if a location/device specified during a previous TopView installation is no longer accessible. How this can occur: The TopView DataPath entered during the most ...
    • Citect OPC Server on Windows 7

      This is a general support posting regarding TopView OPC communicating to Citect OPC Server on Windows 7. The two issues that a TopView user may experience are: TopView can connect to the OPC Server but reports that the server is not in a “running” ...