Ошибка 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!

Возможно, вам также будет интересно:

  • Ошибка 1306 другое приложение имеет монопольный доступ
  • Ошибка 1306 microsoft windows terminal
  • Ошибка 13056 при подключении к роботу пылесосу
  • Ошибка 1305 при подключении зала
  • Ошибка 1305 на зале как устранить

  • Понравилась статья? Поделить с друзьями:
    0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии