Asked By
xycastillo
10 points
N/A
Posted on - 02/25/2012
Hello guys,
While trying to delete a repository from the Component Database Manager, I received an error dialog box saying, "There is a problem accessing the file(path/access error). You may not have access to the file".
When I clicked on OK on the dialog box, the repository no longer existed as shown in the "Available repositories" listing. However, the repository folder is on the C:Windows Embedded DataRepositories{………..} with all the driver files in it. I have to delete this folder manually before re-importing the SLD file that I created in Component Designer. The problem is that every time I make a change in my component, I have to first follow the above steps before I can re-import my component in the Component Database Manager successfully.
So what is this problem? Can anyone help me? Thanks.
Component Database Manager error when deleting a repository
Hi,
Actually for every repository it has inspection or deletion, and there are some other things that we do using repositories. Try this once as follows for your query.
-
Change the properties of the Repositories folder to get Full Control of the folder. As the folder is setup as read-only when installing the database. It discusses the process: https://www.addictivetips.com/windows-tips/take-ownership-of-files-folder-and-change-permissions-in-windows-8/
-
You can also alter the location of repositories and it acts upon the highlighted repository, and lets you move the repository manually.
-
This accepts to do some simple load by balancing through movement of repositories to different locations for improvement of their performance of network.
-
Movement of repository to the local folder (C:box) refers to that others may be using your's database will not be able to build.
Thank you.
Component Database Manager error when deleting a repository
Hello Castillo,
To resolve that issue, you will need to check the compatibility mode of the database manager:
-
Just right click on it and then select Properties.
-
After that choose the Compatibility tab.
-
And the ensure that the box for Compatibility mode is not checked, and if so, clear the check for Run this program in compatibility mode for.
Regards,
Nicke
