1 Reply Latest reply on Jan 15, 2015 3:24 PM by Greg Rupp

    File That is Exclusively Opened by Another Application

    Steve Zema

      Hello All,

       

      I have ran across an error that I have not seen yet.  I have done a search from Google and SW Forums about this and was not successful in solving the issue, so I am posting this today.

       

      A user in our sales department wants to create a new engineering change request.  When he follows the instructions and click 'OK', he receives the following message;

       

      "Could not copy the file '00711.xlsx' from 'C:\EPDM\Admin\Templates\33-124-19008.xlsx'.

      Cause: An attempt was made to access a file that is exclusively opened by another application".

       

      I have the template properties copy the template (33-124-19008.xlsx) from the Admin foler and rename the file to sequential serial number name (00711.xlsx) and place in the proper folder.

       

      The sales department was able to create engineering change requests before, but for some reason, they cannot today.  Below is how they access EPDM.

      1. Sales uses Macbooks and have all rights access to the Remote Server (I know what you all are thinking. Why does one department use Macbooks while the rest of the company uses Windows?).

      2. All permissions are set for them to copy the templates when creating a new form.

      3. The proper workflow, states and transitions are also set for them to perform the task.

       

      I have tried having the user log out of EPDM, then I checked the task manager to ensure that nothing related to SolidWorks are still running in the background, and had him restart EPDM.  This issue is still present.

       

      If any of you have ran across this issue before and have found a solution, I'd appreciate any assistance you can provide.

       

      Thanks,

      Steve Zema

        • Re: File That is Exclusively Opened by Another Application
          Greg Rupp

          Hi Steve, The full solution to your problem can be found in the kb under s-017137

           

          If the logged in Windows® user profiles lacks sufficient local access permissions to the cached files (i.e. the template source file) in a file vault view then the Windows API may return a file access error such as this when trying to create a new file via a template:

           

          ----

          Could not copy the file 'source.doc' from 'c:\vault\templates\source.doc'.

          Cause: An attempt was made to access a file that is exclusively opened by another application.

          ----

           

          Ensure that the logged in Windows profile has FULL folder and file permissions to the file vault view folder (cache folder).

           

          This is described in the installation guide under chapter "Using shared PDMWorks Enterprise view with multiple user profiles". The instructions follows below:

           

          ---

          Using shared PDMWorks Enterprise view with multiple user profiles

          ----------------------------------------------------------------------------------

          A shared file vault view is created by a user with local administrative Windows permissions. The local administrator group will, by default, get full file permissions to any files created (or cached) in that view.

           

          On many systems, the local user or power user groups have only limited file permissions to folders in Windows. This means that if a user with local administrative permissions caches a file in the shared vault view, other Windows user profiles with only user or power user access permissions might not have sufficient permissions to fully access that file or change the read-only state when checking out that file. 

           

          If you plan on using a shared file vault view with Windows user or power user profiles, it is recommended that you define the following folder access permissions for those groups.

           

          To change Windows access permissions on a shared view using the property dialog:

          1. Log in as a user with local administrative permissions, right-click the vault view, and select Properties.

          2. Select the Security tab.

          3. Select the Windows profile groups to use the shared file vault view and make sure that they have all access permissions checked (i.e., Full Control).

          4. Click OK to close and update the permissions.

           

          To change Windows access permissions on a shared view using the command prompt:

          1. Log into the system as a user with local administrative permissions.

          2. Open a command prompt and open the parent folder containing the file vault view (usually C:\).

          3. Use the cacls command to assign sufficient access control to the user and power user groups.

          CACLS “vault_view_name” /E /G “group/username”:F

           

          For example, to grant local users group sufficient access control, type:

          CACLS “c:\PDMWE File Vault” /E /G “users”:F

           

          Read more about the cacls command at http://support.microsoft.com/kb/162786/EN-US/.