Ошибка 1307 при установке программ

Перейти к контенту

  • Remove From My Forums
  • Question

  • Experts ,

    I have a situation where we need to uninstall SQL Server 2005 instance from a 2 node cluster .It fails because during the uninstall it creates RBF (Rollback file) files on G drive . Now G drive has a few mount points and only 500MB for itself .Out of 500MB
    483 MB is empty .

    I was looking for a way to tell the setup to not create these files on G drive and instead on some other drive .

    Is there a way to Do that ..I know that when we install the hotfix through command prompt we give /x <path> and it creates the temp folder there .But here /x option is for uninstall .

    Many thanks

    Regards


    Abhay Chaudhary OCP 9i, MCTS/MCITP (SQL Server 2005, 2008, 2005 BI) ms-abhay.blogspot.com/

Answers

  • Usually these files are located on the root directory of the system drive. Is the operating system installed on G drive?

    Please try extracting the MSI to a different location using the below command

    msiexec /a [msipath] /qb TARGETDIR=[newlocation]

    Then run the .msi from the newly extracted folder. Check if this helps.


    Pradeep Adiga
    Blog: sqldbadiaries.com

    Twitter: @PradeepAdiga

    • Marked as answer by

      Monday, February 14, 2011 10:19 AM

  • Remove From My Forums
  • Вопрос

  • Имеется файловый сервер(он же контроллер домена) —
    Server 2003 R2 Std SP2

    Хочу перенести каталог на другой диск, с сохранением ACL и владельцев.
    Работаю под админом домена.
    На каталоге админам и системе полный доступ.

    ACL переностится нормально, а вот владелец не хочет переноситься, т.к. не хватает прав доступа.

    Robocopy выводит такую ошибку
    ERROR 1307 (0x0000051B) Copying NTFS Security to Destination Directory D:Archive

    This security ID may not be assigned as the owner of this object.

    проводник:
    You do not have the Restore privilege required to set this user/group as owner

    В локальных политиках сервера для права «Restore files and directories» стоят дефолтные: administrators, backup operators, server operators

    Не пойму, где дальше копать…
    Подскажите пожалуйста…

    Спасибо.

Ответы

  • проблему решил

    оказывается на сервере, где назначение владельца работает применяется локальная политика сервера, в которой права прописаны, а на остальных применялись только доменные политики, где права не были прописаны. Прописал права в доменных политиках и сразу все
    заработало.

    спасибо за участие.

    • Помечено в качестве ответа

      13 июля 2012 г. 7:38

Обычно вы можете приобрести NTFS только право собственности на объекты файловой системы для себя. Вы не можете установить право собственности на третье лицо. (Это препятствует тому, чтобы пользователи, например, хранили компрометирующие или инкриминирующие данные под собственностью другого ничего не подозревающего человека.)

В политике безопасности есть привилегия «восстановить файлы и каталоги». Microsoft заявляет:

Этот параметр безопасности […] определяет, какие пользователи могут установить действительные участники безопасности в качестве владельца объекта.

Видимо, вам нужна эта привилегия для копирования права собственности. Robocopy должен работать в контексте безопасности, который позволяет устанавливать владение произвольным принципалам.

По умолчанию локальные администраторы имеют эту привилегию:

По умолчанию это право предоставляется группам «Администраторы», «Операторы архива» и «Операторы сервера» на контроллерах домена, а также группам «Администраторы» и «Операторы архива» на автономных серверах.

(Привилегия «восстановить файлы и каталоги» является частью политики. Возможно, вам придется выйти и снова войти, чтобы она вступила в силу.)

Click Here to follow to fix error 1307 and related errors.

The “1307” error is commonly caused by incorrectly configured system settings or irregular entries in the Windows registry. This error can be fixed with special software that repairs the registry and tunes up system settings to restore stability.

If you got Error 1307 then We strongly recommend that you  >> Download (MyPC Utilities) Repair Tool <<

Note: This article was previously published under WIKI_E2122545

Causes of Error “1307”

The 1307 error may be caused by windows system files damage. The corrupted system files entries can be a real threat to the well being of your computer. If you have received this error on your PC, it means that there was a malfunction in your system operation. Common reasons include incorrect or failed installation or uninstallation of software that may have left invalid entries in your Windows registry, consequences of a virus or malware attack, improper system shutdown due to a power failure or another factor, someone with little technical knowledge accidentally deleting a necessary system file or registry entry, as well as a number of other causes.


How to easily fix 1307 error?

There are two (2) ways to fix 1307 Error:


Advanced Computer User Solution (Manual Fix):

1. Start your computer and log on as an administrator.

2. Click the Start button then select All Programs, Accessories, System Tools, and then click System Restore.

3. Select the most recent system restore point from the “On this list, click a restore point” list, and then click Next.

4. Click Next on the confirmation window.

5. Restarts the computer when the restoration is finished.


Beginner Computer User Solution (Automatic fix):

1. Download (MyPC Utilities) Repair Tool.

2. Install program and click Scan button.

3. Click the Fix Errors button when scan is completed. And restart your computer.


How does it work?

This tool will scan and diagnose, then repairs, your system registry errors, with both manually and automatic tools.
Basic features: (registry cleaner, junk cleaner, evidence cleaner, startup manager and uninstall manager).


  • Remove From My Forums
  • Question

  • Hi,

    We are getting the Error 1307: This security ID may not be assigned as the owner of this object.

    When we tried to open services.msc on Administrator account on windows server 2003.

    Please help use to fix ASAP.

    Thanks.

All replies

  • You posted this in Server Preview forum, is this really on a 2003 Server? ‘Windows Server 2003 extended support ended on July 14, 2015’

    Have you tried creating a shortcut to services.msc on the desktop then right clicking that and Run As then the administrator account?

  • Hi,

    This is windows server 2003. It was working fine till Feb-2018.

    We have tried to open CMD with run as Administrator. Even we are getting same issue.

    Services.msc opened with blank page only. There are no services on services.msc.

    Please let me know any other procedure to fix this issue.

    Please treat it as higher priority.

    Thank you

  • This is a commiunity based forum, there is no priority. ‘Windows Server 2003 extended support ended on July 14, 2015’ you will not be able to get support for Server 2003 from MS afaik.

    As a work-around you could manage the services from command line

    Essential Tools for Windows Services: The NET Command

  • Hi,

    We have tried with Command prompt. We are getting below same error.

    system error 1307 has occurred. This security ID may not be assigned as the owner of this object.

    We are requesting you to help us to resolve the issue.

    Please share me any other troubleshooting steps for the same.

    We are awaiting for your favor reply.

    Thank you.

  • Remove From My Forums
  • Question

  • Hi,

    We are getting the Error 1307: This security ID may not be assigned as the owner of this object.

    When we tried to open services.msc on Administrator account on windows server 2003.

    Please help use to fix ASAP.

    Thanks.

All replies

  • You posted this in Server Preview forum, is this really on a 2003 Server? ‘Windows Server 2003 extended support ended on July 14, 2015’

    Have you tried creating a shortcut to services.msc on the desktop then right clicking that and Run As then the administrator account?

  • Hi,

    This is windows server 2003. It was working fine till Feb-2018.

    We have tried to open CMD with run as Administrator. Even we are getting same issue.

    Services.msc opened with blank page only. There are no services on services.msc.

    Please let me know any other procedure to fix this issue.

    Please treat it as higher priority.

    Thank you

  • This is a commiunity based forum, there is no priority. ‘Windows Server 2003 extended support ended on July 14, 2015’ you will not be able to get support for Server 2003 from MS afaik.

    As a work-around you could manage the services from command line

    Essential Tools for Windows Services: The NET Command

  • Hi,

    We have tried with Command prompt. We are getting below same error.

    system error 1307 has occurred. This security ID may not be assigned as the owner of this object.

    We are requesting you to help us to resolve the issue.

    Please share me any other troubleshooting steps for the same.

    We are awaiting for your favor reply.

    Thank you.

  • Remove From My Forums
  • Вопрос

  • Имеется файловый сервер(он же контроллер домена) —
    Server 2003 R2 Std SP2

    Хочу перенести каталог на другой диск, с сохранением ACL и владельцев.
    Работаю под админом домена.
    На каталоге админам и системе полный доступ.

    ACL переностится нормально, а вот владелец не хочет переноситься, т.к. не хватает прав доступа.

    Robocopy выводит такую ошибку
    ERROR 1307 (0x0000051B) Copying NTFS Security to Destination Directory D:Archive

    This security ID may not be assigned as the owner of this object.

    проводник:
    You do not have the Restore privilege required to set this user/group as owner

    В локальных политиках сервера для права «Restore files and directories» стоят дефолтные: administrators, backup operators, server operators

    Не пойму, где дальше копать…
    Подскажите пожалуйста…

    Спасибо.

Ответы

  • проблему решил

    оказывается на сервере, где назначение владельца работает применяется локальная политика сервера, в которой права прописаны, а на остальных применялись только доменные политики, где права не были прописаны. Прописал права в доменных политиках и сразу все
    заработало.

    спасибо за участие.

    • Помечено в качестве ответа

      13 июля 2012 г. 7:38

  • Remove From My Forums
  • Question

  • This is the full error message:

    Windows Could not start the Workstation service on Local
    Computer

    Error 1307: This security ID may not be assigned as the owner of this 
    object.

    I went to ‘Log on’ and ticked the box ‘This account:’ then put in Local service and erased the passwords and applied it. But now I’m getting this 1307
    error.

    Please help it’s urgent, thanks.

All replies

  • I really need this please! Whoever answers it, leave your email or something and i’ll send you $10 through paypal please I really need help it’s so urgent!

  • Remove From My Forums
  • Question

  • This is the full error message:

    Windows Could not start the Workstation service on Local
    Computer

    Error 1307: This security ID may not be assigned as the owner of this 
    object.

    I went to ‘Log on’ and ticked the box ‘This account:’ then put in Local service and erased the passwords and applied it. But now I’m getting this 1307
    error.

    Please help it’s urgent, thanks.

All replies

  • I really need this please! Whoever answers it, leave your email or something and i’ll send you $10 through paypal please I really need help it’s so urgent!

Click Here to follow to fix error 1307 and related errors.

The “1307” error is commonly caused by incorrectly configured system settings or irregular entries in the Windows registry. This error can be fixed with special software that repairs the registry and tunes up system settings to restore stability.

If you got Error 1307 then We strongly recommend that you  >> Download (MyPC Utilities) Repair Tool <<

Note: This article was previously published under WIKI_E2122545

Causes of Error “1307”

The 1307 error may be caused by windows system files damage. The corrupted system files entries can be a real threat to the well being of your computer. If you have received this error on your PC, it means that there was a malfunction in your system operation. Common reasons include incorrect or failed installation or uninstallation of software that may have left invalid entries in your Windows registry, consequences of a virus or malware attack, improper system shutdown due to a power failure or another factor, someone with little technical knowledge accidentally deleting a necessary system file or registry entry, as well as a number of other causes.


How to easily fix 1307 error?

There are two (2) ways to fix 1307 Error:


Advanced Computer User Solution (Manual Fix):

1. Start your computer and log on as an administrator.

2. Click the Start button then select All Programs, Accessories, System Tools, and then click System Restore.

3. Select the most recent system restore point from the “On this list, click a restore point” list, and then click Next.

4. Click Next on the confirmation window.

5. Restarts the computer when the restoration is finished.


Beginner Computer User Solution (Automatic fix):

1. Download (MyPC Utilities) Repair Tool.

2. Install program and click Scan button.

3. Click the Fix Errors button when scan is completed. And restart your computer.


How does it work?

This tool will scan and diagnose, then repairs, your system registry errors, with both manually and automatic tools.
Basic features: (registry cleaner, junk cleaner, evidence cleaner, startup manager and uninstall manager).


RRS feed

  • Remove From My Forums
  • Question

  • Hi,

    We are getting the Error 1307: This security ID may not be assigned as the owner of this object.

    When we tried to open services.msc on Administrator account on windows server 2003.

    Please help use to fix ASAP.

    Thanks.

All replies

  • You posted this in Server Preview forum, is this really on a 2003 Server? ‘Windows Server 2003 extended support ended on July 14, 2015’

    Have you tried creating a shortcut to services.msc on the desktop then right clicking that and Run As then the administrator account?

  • Hi,

    This is windows server 2003. It was working fine till Feb-2018.

    We have tried to open CMD with run as Administrator. Even we are getting same issue.

    Services.msc opened with blank page only. There are no services on services.msc.

    Please let me know any other procedure to fix this issue.

    Please treat it as higher priority.

    Thank you

  • This is a commiunity based forum, there is no priority. ‘Windows Server 2003 extended support ended on July 14, 2015’ you will not be able to get support for Server 2003 from MS afaik.

    As a work-around you could manage the services from command line

    Essential Tools for Windows Services: The NET Command

  • Hi,

    We have tried with Command prompt. We are getting below same error.

    system error 1307 has occurred. This security ID may not be assigned as the owner of this object.

    We are requesting you to help us to resolve the issue.

    Please share me any other troubleshooting steps for the same.

    We are awaiting for your favor reply.

    Thank you.

RRS feed

  • Remove From My Forums
  • Вопрос

  • Hi,

    We are getting the Error 1307: This security ID may not be assigned as the owner of this object.

    When we tried to open services.msc on Administrator account on windows server 2003.

    Please help use to fix ASAP.

    Thanks.

Все ответы

  • You posted this in Server Preview forum, is this really on a 2003 Server? ‘Windows Server 2003 extended support ended on July 14, 2015’

    Have you tried creating a shortcut to services.msc on the desktop then right clicking that and Run As then the administrator account?

  • Hi,

    This is windows server 2003. It was working fine till Feb-2018.

    We have tried to open CMD with run as Administrator. Even we are getting same issue.

    Services.msc opened with blank page only. There are no services on services.msc.

    Please let me know any other procedure to fix this issue.

    Please treat it as higher priority.

    Thank you

  • This is a commiunity based forum, there is no priority. ‘Windows Server 2003 extended support ended on July 14, 2015’ you will not be able to get support for Server 2003 from MS afaik.

    As a work-around you could manage the services from command line

    Essential Tools for Windows Services: The NET Command

  • Hi,

    We have tried with Command prompt. We are getting below same error.

    system error 1307 has occurred. This security ID may not be assigned as the owner of this object.

    We are requesting you to help us to resolve the issue.

    Please share me any other troubleshooting steps for the same.

    We are awaiting for your favor reply.

    Thank you.

Support for Microsoft OfficeOffice program often shows several errors
due to updates failure, Network issues
installation/removal errors. Get help from
our experts to fix the Error code 1307

  1. Home
  2. Office support
  3. Error code 1307 when installing office 365/2010/2013

Error code 1307 when installing office 365/2010/2013

(Last Updated On: February 26, 2018)

Error Code 1307 of Microsoft Office commonly occurs because of an existing installation of MS Office pack in your computer system. Please note that this error is relevant to all the editions of Microsoft Office 2013, office 2016 and Microsoft Office 365.

This can occur in the below-enlisted versions of the MS Operating System

  • Windows Server Edition of the year 2012/2008
  • Windows 7 /8 /8.1/10

You can also check the event log for more information about office installation errors by selecting the event source VSTO4.0 from windows applications logs. Here providing some example screenshots of how to check log and office licensing event issues.

1307

1307

Symptoms/Indications Error Code 1307 :
It is noteworthy that the detection of the Error Code 1307 in the earlier stages of the installation process can help you save a lot of time and effort. And there is no requirement of being a techno savvy to detect the early warning signs of this kind of error.

The following are certain critical signs of Error Code 1307 :

  • The installation process of Microsoft Office will stop in an abrupt
  • An error message will be displayed on your screen when you open office 365/2010/2013 program every time.
  • The performance of your computer becomes slow and often hangs.

Causes for the Office Error Code 1307 :

When it comes to the technical failures, then there can be a multiple number of factors contributing to the occurrence of this kind of installation error code 1307 . They are given below-

  1. Slow speed of the Internet while installing Office program that may pause the background installation process abruptly.
  2. A previous Office installation that failed or corrupt.
  3. Domain Name System conflict issue (DNS).
  4. The security settings of your computer, software or the firewall blocking the installation process.
  5. Proxy Settings that are active on your computer.
  6. The pre-existing versions of the Office Suite.
  7. Failed Repair/Change/Partial/Removal/Incomplete/Installation of Office Suite.

How to fix Error Code 1307 :

  1. Turn off the firewall settings and anti-virus
  2. Remove the temp files
  3. Perform the system file scanning
  4. Repair/remove the installed office software
  5. Update the pending software patches from Microsoft.
  6. Re-install the office package from MS account

1.Turn-off windows firewall:

Firstly, it is advisable to TURN OFF all the security settings, including the Firewall and security software. Then, if you have an antivirus security software installed on your computer, then TURN OFF the same on a temporary basis.

2.Remove the temp files:-

  • Go to path C:\Windows\Temp
  • Select all files and click on delete
  • Type %temp% in start menu search bar,
  • delete all files , you can skip files that are running in the background.

3.Perform the sfc scan:-

  • Click on the Start button
  • Type CMD
  • Right click and run as an ADMINISTRATOR
  • Type the command SFC /SCANNOW in the command window
  • and press <ENTER>
Video tutorial of SFC scan for the error code 1307 :

It will take some time to finish the scanning process , if it shows any errors in the results you need to do proper action suitable to the error.

4.Repair/remove existing office software:-

If the error code 1307 still persists, please do Repair to the existing or half installed Office package on your computer.

Then, proceed with the installation of Office 365 Suite or Office 2013

Windows 7:-

  1. Please click on the button indicating Start menu and subsequently choose the Control Panel
  2. Initiate the Programs and choose for the button ‘Programs and Features’.
  3. Then, scroll and choose the Office product, then click the button indicating ‘Change’ located above the Window.
  4. After that, select the ‘Quick Repair’ button and wait till the repairing process of the Office Program is executed.
  5. In the case, the above mentioned steps unable to fix the error, then you will be requisite to uninstall all the office products and install them again.

Windows 8 / Windows 8.1:-

  1. Click on the Windows Logo Key, then letter in order to open Run
  2. Insert the Command – ‘Control’ then press Enter.
  3. After that, choose ‘Programs and Features’.
  4. Then, scroll and click the Office product, then hit the ‘Change’ button given on the top of Window.
  5. Pick ‘Quick Repair’ option and then click on the ‘Repair’
  6. Once the Repair process is being done, you can expect the Office Suite to work perfectly well.
  7. In case the issue remains unresolved, it is recommended to uninstall by following the directions on the screen and re-install it.

Windows 10 OS:-

  1. Type ‘Programs and Features’ in the search bar beside the windows logo.
  2. Scroll down and click on the office package from the list, and right click on it to find repair option.
  3. Then click on the ‘Repair’
  4. Once the Repair process is being done, you can expect the Office Suite to work perfectly well.
  5. In case the issue remains unresolved, it is recommended to uninstall by following the directions on the screen, and re-install it.

Steps to follow before Re-installation of office software:-

Now remove office files from C:\Program Files (x86)\Common Files\Microsoft Shared (if you found any traces from older version) then re-install the office program from your Microsoft account.

For additional support, chat with our online experts to take remote assistance.

Still need help!

Chat with our Technical Experts for further help and support

1307

Error chat support

Error Codes ISsues:-

Error code 30175-4, office error code 30175-12, office something went wrong 30175-26, office error 30175-19, error code 30175-13, office 2010 error code 30174-4, office wont install error 30174-8, background installation error code 30174-22, office error code 30170-4, office error code 30174-11,background installation ran into a problem

Понравилась статья? Поделить с друзьями:
  • Ошибка 1303 гранта 8 клапанная что делать
  • Ошибка 1306 при удалении касперского
  • Ошибка 1302 приора
  • Ошибка 1306 другая программа имеет монопольный доступ
  • Ошибка 1302 при подключении зала что делать