Latest update: March 11, 2021
ID: 15351
The «Error 1306. Another application has exclusive access to file [file path]» error may appear during installation of a Kaspersky application.
Solution
What to do if the issue persists
If the issue persists, submit a request to Kaspersky technical support by choosing the topic and filling out the form.
Did you find what you were searching for?
Website feedback
What information, in your opinion, should we add to this page? Write your comment in the form below. If you want to contact technical support, close this pop-up and click Contact support.
Статья обновлена: 16 августа 2022
ID: 15351
При установке программы «Лаборатории Касперского» может появиться сообщение «Ошибка 1306. Другая программа имеет монопольный доступ к файлу [путь к файлу]».
Решение
Что делать, если решение не помогло
Если ошибка повторяется, свяжитесь с технической поддержкой «Лаборатории Касперского», выбрав тему для своего запроса.
Вам помогла эта страница?
Содержание
- Error 1306 another application has exclusive access to the file
- Question
- Answers
- Error 1306 another application has exclusive access to the file
- Вопрос
- Ответы
- Error 1306 another application has exclusive access to the file
- Asked by:
- Question
- All replies
- Error 1306 another application has exclusive access to the file
- Question
- Answers
- Error 1306 another application has exclusive access to the file
- Asked by:
- Question
- All replies
Error 1306 another application has exclusive access to the file
Question
I’ve recently installed SCCM 2007, and pushed clients out to PCs.
I apologise if this is the wrong forum, but the error seems to indicate this is related to SCCM, and I have never seen this error prior to installing the SCCM Clients.
An issue I have found (which only seems to be happening on our Windows XP machines) is when we physically go to AddRemove Programs and try to uninstall a piece of software, it cannot complete the process.
It starts uninstalling (and even removes the desktop icons), but then it gives the below error, and I have to cancel the uninstall. It then rolls back the uninstall (and puts the icons back on the desktop)
Product: Program Name — Error 1306.Another application has exclusive access to the file C:WINDOWSsystem32CCMLogsPolicyAgentProvider.log. Please shut down all other applications, then click Retry.
I apologise if this is not an SCCM thing, but the file mentioned in the error seems to be related to SCCM.
Would the agent being installed on a machine prevent a program being uninstalled?
The Program being uninstalled was not installed by SCCM. In fact, there have been no packages pushed to these PCs. The only thing installed by SCCM was the client itself.
Answers
Here’s my guess (and it is the same as Todd Miller’s response above) but I’ll just try to restate it differently. here’s my guess of what happened.
1. At some point in the past, a software packager at your company ‘repackaged’ that application (or every application) using something like Wise or Installshield to repackage. And, that Software packager used as it’s computer to create that repackage; a system which had the ConfigMgr client installed.
2. That software repackager, when they went through the post-repackaging process, either did not know or did not realize that you simply cannot accept at face value what ANY repackager does on your behalf. That person SHOULD have, prior to completing the repackage, carefully examined all the files included in the repackage attempt, and delete the ones clearly NOT related to whatever it was they were packaging—like files in system32ccm*
3. You happily accepted the repackage, and installed it successfully on computers all over the company.
4. Now. the fun begins. Those same computers now get the ConfigMgr Client. So the CM client now ‘owns’ the folder and files in system32ccm. So. now that the bad repackage wants to uninstall—and take files with it that it should NEVER have owned in the first place, it fails.
Conclusion: um. you’re messed up. Your re-packaging practices have got you into deep do-do.
What I STRONGLY suggest if you get those repackaging people to a training class immediately, so they stop their bad repackaging practices. It may be that what will be required is a custom uninstall script, to stop the CM client, then do the uninstall of whatever, then trigger a repair of the CM client (because the uninstall of whatever likely mucked up the cm client)
Источник
Error 1306 another application has exclusive access to the file
Вопрос
I’ve recently installed SCCM 2007, and pushed clients out to PCs.
I apologise if this is the wrong forum, but the error seems to indicate this is related to SCCM, and I have never seen this error prior to installing the SCCM Clients.
An issue I have found (which only seems to be happening on our Windows XP machines) is when we physically go to AddRemove Programs and try to uninstall a piece of software, it cannot complete the process.
It starts uninstalling (and even removes the desktop icons), but then it gives the below error, and I have to cancel the uninstall. It then rolls back the uninstall (and puts the icons back on the desktop)
Product: Program Name — Error 1306.Another application has exclusive access to the file C:WINDOWSsystem32CCMLogsPolicyAgentProvider.log. Please shut down all other applications, then click Retry.
I apologise if this is not an SCCM thing, but the file mentioned in the error seems to be related to SCCM.
Would the agent being installed on a machine prevent a program being uninstalled?
The Program being uninstalled was not installed by SCCM. In fact, there have been no packages pushed to these PCs. The only thing installed by SCCM was the client itself.
Ответы
Here’s my guess (and it is the same as Todd Miller’s response above) but I’ll just try to restate it differently. here’s my guess of what happened.
1. At some point in the past, a software packager at your company ‘repackaged’ that application (or every application) using something like Wise or Installshield to repackage. And, that Software packager used as it’s computer to create that repackage; a system which had the ConfigMgr client installed.
2. That software repackager, when they went through the post-repackaging process, either did not know or did not realize that you simply cannot accept at face value what ANY repackager does on your behalf. That person SHOULD have, prior to completing the repackage, carefully examined all the files included in the repackage attempt, and delete the ones clearly NOT related to whatever it was they were packaging—like files in system32ccm*
3. You happily accepted the repackage, and installed it successfully on computers all over the company.
4. Now. the fun begins. Those same computers now get the ConfigMgr Client. So the CM client now ‘owns’ the folder and files in system32ccm. So. now that the bad repackage wants to uninstall—and take files with it that it should NEVER have owned in the first place, it fails.
Conclusion: um. you’re messed up. Your re-packaging practices have got you into deep do-do.
What I STRONGLY suggest if you get those repackaging people to a training class immediately, so they stop their bad repackaging practices. It may be that what will be required is a custom uninstall script, to stop the CM client, then do the uninstall of whatever, then trigger a repair of the CM client (because the uninstall of whatever likely mucked up the cm client)
Источник
Error 1306 another application has exclusive access to the file
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
I have downloaded adventure works, i installed but it was empty so i tried to unsintall to install it again but i am unable to Uninstall. Am keep gettting the Error as: «Error 1306: Another Application has exclusive access to the file AdventureWorks_Log.ldf. Please shutdown all other applications and then click retry»
I have not used it anywhere i could not find the reference where the log file is used pls help me to uninstall Adventure Works.
This error you got because somewhere your database is in use.
right click the database adventurework
go to task and then detach option
see if there are any message in message column if there is then some connection are still there with database.
kill all the connection and then you will be able to do your task.
Please click the Mark as Answer button if a post solves your problem!
If the SQL Server services are running, the sql server process access the database files and you can not copy, delete, rename, etc on those database files.
But removing a database or deleting or uninstalling is easy.
You can execute the following DROP command to delete a database.
As Mayur suggested detaching a database is also an other option.
Drop will delete the database files and also backups on the other hand detach will leave the database data and log files on their current locations but they are not registered on the SQL Server.
Источник
Error 1306 another application has exclusive access to the file
Question
I’ve recently installed SCCM 2007, and pushed clients out to PCs.
I apologise if this is the wrong forum, but the error seems to indicate this is related to SCCM, and I have never seen this error prior to installing the SCCM Clients.
An issue I have found (which only seems to be happening on our Windows XP machines) is when we physically go to AddRemove Programs and try to uninstall a piece of software, it cannot complete the process.
It starts uninstalling (and even removes the desktop icons), but then it gives the below error, and I have to cancel the uninstall. It then rolls back the uninstall (and puts the icons back on the desktop)
Product: Program Name — Error 1306.Another application has exclusive access to the file C:WINDOWSsystem32CCMLogsPolicyAgentProvider.log. Please shut down all other applications, then click Retry.
I apologise if this is not an SCCM thing, but the file mentioned in the error seems to be related to SCCM.
Would the agent being installed on a machine prevent a program being uninstalled?
The Program being uninstalled was not installed by SCCM. In fact, there have been no packages pushed to these PCs. The only thing installed by SCCM was the client itself.
Answers
Here’s my guess (and it is the same as Todd Miller’s response above) but I’ll just try to restate it differently. here’s my guess of what happened.
1. At some point in the past, a software packager at your company ‘repackaged’ that application (or every application) using something like Wise or Installshield to repackage. And, that Software packager used as it’s computer to create that repackage; a system which had the ConfigMgr client installed.
2. That software repackager, when they went through the post-repackaging process, either did not know or did not realize that you simply cannot accept at face value what ANY repackager does on your behalf. That person SHOULD have, prior to completing the repackage, carefully examined all the files included in the repackage attempt, and delete the ones clearly NOT related to whatever it was they were packaging—like files in system32ccm*
3. You happily accepted the repackage, and installed it successfully on computers all over the company.
4. Now. the fun begins. Those same computers now get the ConfigMgr Client. So the CM client now ‘owns’ the folder and files in system32ccm. So. now that the bad repackage wants to uninstall—and take files with it that it should NEVER have owned in the first place, it fails.
Conclusion: um. you’re messed up. Your re-packaging practices have got you into deep do-do.
What I STRONGLY suggest if you get those repackaging people to a training class immediately, so they stop their bad repackaging practices. It may be that what will be required is a custom uninstall script, to stop the CM client, then do the uninstall of whatever, then trigger a repair of the CM client (because the uninstall of whatever likely mucked up the cm client)
Источник
Error 1306 another application has exclusive access to the file
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
I have downloaded adventure works, i installed but it was empty so i tried to unsintall to install it again but i am unable to Uninstall. Am keep gettting the Error as: «Error 1306: Another Application has exclusive access to the file AdventureWorks_Log.ldf. Please shutdown all other applications and then click retry»
I have not used it anywhere i could not find the reference where the log file is used pls help me to uninstall Adventure Works.
This error you got because somewhere your database is in use.
right click the database adventurework
go to task and then detach option
see if there are any message in message column if there is then some connection are still there with database.
kill all the connection and then you will be able to do your task.
Please click the Mark as Answer button if a post solves your problem!
If the SQL Server services are running, the sql server process access the database files and you can not copy, delete, rename, etc on those database files.
But removing a database or deleting or uninstalling is easy.
You can execute the following DROP command to delete a database.
As Mayur suggested detaching a database is also an other option.
Drop will delete the database files and also backups on the other hand detach will leave the database data and log files on their current locations but they are not registered on the SQL Server.
Источник
- Remove From My Forums
-
Question
-
Hi all,
I’ve recently installed SCCM 2007, and pushed clients out to PCs.
I apologise if this is the wrong forum, but the error seems to indicate this is related to SCCM, and I have never seen this error prior to installing the SCCM Clients.
An issue I have found (which only seems to be happening on our Windows XP machines) is when we physically go to AddRemove Programs and try to uninstall a piece of software, it cannot complete the process.
It starts uninstalling (and even removes the desktop icons), but then it gives the below error, and I have to cancel the uninstall. It then rolls back the uninstall (and puts the icons back on the desktop)
The error is:
Product: Program Name — Error 1306.Another application has exclusive access to the file C:WINDOWSsystem32CCMLogsPolicyAgentProvider.log. Please shut down all other applications, then click Retry.
I apologise if this is not an SCCM thing, but the file mentioned in the error seems to be related to SCCM.
Would the agent being installed on a machine prevent a program being uninstalled?
The Program being uninstalled was not installed by SCCM. In fact, there have been no packages pushed to these PCs. The only thing installed by SCCM was the client itself.
Answers
-
Here’s my guess (and it is the same as Todd Miller’s response above) but I’ll just try to restate it differently. here’s my guess of what happened.
1. At some point in the past, a software packager at your company ‘repackaged’ that application (or every application) using something like Wise or Installshield to repackage. And, that Software packager used as it’s computer to create that repackage;
a system which had the ConfigMgr client installed.2. That software repackager, when they went through the post-repackaging process, either did not know or did not realize that you simply cannot accept at face value what ANY repackager does on your behalf. That person SHOULD have, prior to completing
the repackage, carefully examined all the files included in the repackage attempt, and delete the ones clearly NOT related to whatever it was they were packaging—like files in system32ccm*3. You happily accepted the repackage, and installed it successfully on computers all over the company.
4. Now… the fun begins. Those same computers now get the ConfigMgr Client. So the CM client now ‘owns’ the folder and files in system32ccm. So… now that the bad repackage wants to uninstall—and take files with it that it should NEVER
have owned in the first place, it fails.Conclusion: um… you’re messed up. Your re-packaging practices have got you into deep do-do.
What I STRONGLY suggest if you get those repackaging people to a training class immediately, so they stop their bad repackaging practices. It may be that what will be required is a custom uninstall script, to stop the CM client, then do the uninstall
of whatever, then trigger a repair of the CM client (because the uninstall of whatever likely mucked up the cm client)fyi, the class I went to for repackaging was www.windowsinstallertraining.com.
Standardize. Simplify. Automate.
-
Marked as answer by
Thursday, March 7, 2013 12:47 AM
-
Marked as answer by
-
There’s not much information to work on here, but I’ll take a guess.
If you made the software installer yourself using a before and after snapshot to «capture» the installation on a machine that the SCCM client was installed on, it could be that that log changed between when you did the before and after snapshots. This
would add that log file to your snapshot based MSI installer. That is a total guess. Now when you are removing the software package you built it is trying to remove the log and failing. I can’t think of another reason why an unrelated software
package would try to remove an SCCM log file.Let us know if this is a vendor provided installer package or something you built in-house.
-
Marked as answer by
RCPAQAPIT
Thursday, March 7, 2013 12:47 AM
-
Marked as answer by
No prizes for guessing why the Sage accounting software is extremely popular among businesses and accounting professionals across the world. With its amazing features and improved tools, it has indeed made their lives easier. Accounting tasks can now be completed with minimal effort by businesses and professionals.
However, as with any other accounting software, Sage 50 has its share of bugs and issues. One common issue faced by the users is the Sage company won’t Open issue as another application has exclusive access to the file. If you’ve recently encountered this problem and are looking for simple solutions, we can help. All you have to do is read this blog all the way through. We will discuss the primary causes of this problem and demonstrate simple solutions. So, follow these simple steps to resolve this issue permanently.
First things first! Let’s have a look at why this error occurs…
User Navigation
1
Causes of the Sage Error 1306: Another application has Exclusive Access to the File’ issue?
This problem could be caused by a variety of technical issues. Here are some prominent examples:
- The Windows Management Instrumentation service is preventing the installation from continuing, by holding onto the avapicfg.mdb file.
- The Sage 50 EFT Direct program was installed using a different Windows administrator user account than that used by the current Windows user.
- A corruption in the installation folder (C:program files(x86) )
Steps to resolve the Sage Error 1306: Another application has Exclusive Access to the File’ issue
Here we are providing simple and multiple methods to resolve this issue –
Total Time: 35 minutes
Method 1: End the MySQL Process
🔹 Close the Sage 50 Accounting application on all the workstations
🔹 Log in to the computer that stores the company data
🔹 Press the Ctrl + Alt + Del keys together
🔹 Choose Start Task Manager
🔹 Click on the Processes tab
🔹 Please make sure to enable the button/checkbox that states Show processes from all users
🔹 Locate the mysqld.exe process
🔹 Click on End Process.
Please Note: The process will be called mysqld-nt.exe if you are using Sage 50 Accounting 2013 or older versions.
🔹 Open the SAJ company file folder.
🔹 Manually delete the process.pid file
🔹 If you are still having this issue, reboot the computer / server
Method 2: The Data File is Located on the Server
🔹 Open Windows Explorer
🔹 Copy the SAJ & SAI files from the server to your desktop temporarily
🔹 Open the company file on the desktop
🔹 If you are unable to open the file, restore the latest backup to the server
🔹 If the file refuses to open, close the company file
🔹 Wait till you can have access to the server
🔹 Restart the server
🔹 From the desktop copy, overwrite the SAJ & SAI files onto the server o
🔹 Delete the SAJ & SAI files from the desktop
Method 3: Restart the Computer
🔹 Reboot the computer.
🔹 If multiple computers are accessing the Sage 50 EFT Direct data, then reboot these computers as well.
🔹 Check if you are still having this issue
Method4: If Rebooting does not Resolve the issue
🔹 Take a proper backup of the Sage 50 EFT Direct data.
🔹 Uninstall Sage 50 EFT Direct.
🔹 Now create a new folder on the C drive of the computer where Sage 50 EFT Direct will be reinstalled.
🔹 Reinstall Sage 50 EFT Direct.
🔹 Browse to the location of the executable file (e.g. SA_20XXEFTCP1.EXE. Here, XX is the year of the version)
🔹 Double-click on the SA_20XXEFTCP1.EXE file to begin the installation.
🔹 When prompted, select the new folder created on C:.
🔹 Finish the Sage 50 EFT Direct installation.
🔹 Restore the Sage 50 EFT Direct data.
We hope the above mentioned methods would be of great help for you to resolve the sage Error 1306: Another application has exclusive access to the file’ issue. If the issue persists even after attempting these methods, or if you have any further questions, you should consult with one of the authorized Sage experts.
Accounting Professionals & Specialized Experts
Want quick help from accounting software experts? Get in touch with our team members who can install, configure and configure your software for you. Proficient in fixing technical issues, they can help you quickly get back to work whenever you encounter an error in Sage software. Our team is available 24/7 365 days to assist you. To get in touch.
FAQs
What Causes the ‘Sage 50 not opening in full screen’ issue?
This problem could be caused by a variety of technical issues. Here are some prominent examples:
🔹 Data corruption
🔹 The Windows Theme is conflicting with the screens
🔹 The Window position may have got saved out from the viewable area
🔹 The positions registry key may have been damaged
🔹 In case you are using Windows 10, it remembers the Windows size and position in a Particular program and recreates the same when you open Sage 50
🔹 Cluttered data folder
What is the Procedure to resolve the ‘Sage Won’t Open issue when the Sage 50 application is running in the background’?
Here are the steps to follow-
🔹 Press ctrl, alt and del together on your keyboard
🔹 Now click on the Start Task Manager tab
🔹 If you are using the OS Windows 7, Server or Vista, Click Process
🔹 If you are using the Windows 8 or 10 OS, click More Details >> Details
🔹 Next, click on the peachw.exe file
🔹 Click End Task
🔹 Close the task manager
🔹 Open the Sage application again and check if the issue is still there.
How can I change the Font Size in Windows 10, to fix the ‘Sage 50 not Opening in Full Screen’ issue?
To solve this issue, it is sufficient to modify the font size in the Windows settings, instead of making changes in Sage settings. To change the font size in Windows 10, follow the steps below-
🔹 Click Start
🔹 Click on Settings
🔹 Now click on System
🔹 Then click on the Display tab
🔹 Choose the size of the text, apps and other items
🔹 Next , choose 125%
🔹 Click on Apply.
🔹 Click Sign out now
🔹 Restart the computer and verify if the issue is solved by now