Код ошибки 2147750687

узелок на память.

Столкнулся недавно с ошибкой 2147750687 в логах при попытке автоматического запуска запланированного задания в Windows Server 2008. Дело в том, что в данном задании установлен параметр «Не запускать второй экземпляр задания» («Do not start a new instance» условия «If the task is already running, then the following rule applies:» на вкладке Settings), а так как у меня выполнялись несколько однотипных vbs-скриптов в разное время и время выполнения предыдущего скрипта превысило интервал между запуском этих заданий то текущий экземпляр программы wscript уже не смог запуститься. Ошибка описана в Winerror.h:

# as an HRESULT: Severity: FAILURE (1), FACILITY_WIN32 (0x7), Code 0x4dd
# for decimal 1245 / hex 0x4dd
ERROR_NOT_LOGGED_ON
# The operation being requested was not performed because the
# user has not logged on to the network.
# The specified service does not exist.

Также советую проверить параметр выполнения задания при не выполненном входе в систему пользователя, от имени которого запускается задание («Run whether user is logged or not») и снята ли галка «Do not store password. The task will only have access to local computer resources».

Rating: 5.0/5 (1 vote cast)

узелок на память.

Столкнулся недавно с ошибкой 2147750687 в логах при попытке автоматического запуска запланированного задания в Windows Server 2008. Дело в том, что в данном задании установлен параметр «Не запускать второй экземпляр задания» («Do not start a new instance» условия «If the task is already running, then the following rule applies:» на вкладке Settings), а так как у меня выполнялись несколько однотипных vbs-скриптов в разное время и время выполнения предыдущего скрипта превысило интервал между запуском этих заданий то текущий экземпляр программы wscript уже не смог запуститься. Ошибка описана в Winerror.h:

# as an HRESULT: Severity: FAILURE (1), FACILITY_WIN32 (0x7), Code 0x4dd
# for decimal 1245 / hex 0x4dd
ERROR_NOT_LOGGED_ON
# The operation being requested was not performed because the
# user has not logged on to the network.
# The specified service does not exist.

Также советую проверить параметр выполнения задания при не выполненном входе в систему пользователя, от имени которого запускается задание («Run whether user is logged or not») и снята ли галка «Do not store password. The task will only have access to local computer resources».

Rating: 5.0/5 (1 vote cast)

If you often use the tool you’ll encounter some error codes and one of such error code is task scheduler error 2147750687. Windows task scheduler helps a lot when it comes to managing and monitoring your machines, you can automate tasks and let servers run on autopilot.

Users receive this error message when they’re running vantage on:

  • windows 7
  • windows vista
  • windows server 2008 R2
  • windows server 2008

When you receive such error code it means the task isn’t running and hence you’ll receive the error code ‘2147750687’ in windows task scheduler.

Fix Task Scheduler Error 2147750687

What Does Task Scheduler Error 2147750687 Mean?

When this error is shown it means task scheduler tried to run the task twice. In other words, it means duplicate schedules want to run at the same time.

What Causes Error 2147750687?

Windows task scheduler is designed to schedule tasks that will be run over the next hour using a scheduled window. When the start time of any given task clash with current schedule window and with the starting time of next scheduled window, it will result in scheduling the task twice. Which means the task will be scheduled at the end of current scheduled window and then again at the start of the next schedule window.

task scheduler 2147750687

task scheduler 2147750687

How To Fix Error 2147750687

There are three effective methods that can solve this problem, we’ll take a look at them one by one, when try one option and it doesn’t work you should move on to the next method. Let’s take at the three options you have:

First Method – Reduce The Frequency Of The Task

Reducing the frequency of the task can solve the problem because as we’ve mentioned earlier the error arise when the same task is schedule twice at the given time, and reducing the frequency minimize the risk of running duplicate schedule.

Second Method – Change Task Behavior

This is another method that has worked for most users. You should open task settings, at the bottom which is the last option, you’ll notice the message “if the task is already running, then the following rule applies

There are four options in the drop-down list and you need to select “Do not start a new instance”. This option ensures that a new instance is not run and the current instance that’s running will not be stopped.

Third Methods – Install Hotfix

If you’re still not able to fix the problem you need to install Hotfix update from Microsoft. It’s available in all the operating systems that experience this problem, they’re windows vista, windows 7, windows server 2008 R2 and windows server 2008.

Head over to Microsoft and search for Hotfix, on the page you’ll notice a download button and if it’s not available you can still make a request from their support center where you’ll be provided with a download link.

Some Prerequisites Before Installing Hotfix

Before you begin to install Hotfix on windows server 2008 R2 and windows 7, you should install 2305420 updates or service pack 1 update on your pc. These update packs are also available for download for free from Microsoft website.

Operating Systems That Can Use Hotfix

Hotfix update is available on the following operating systems;                                                                                                                            

  • Windows 7
  • Windows 7 (SP1)
  • Windows vista (SP1)
  • Windows vista (SP2)
  • Windows server 2008 (SP1)
  • Windows server 2008 (SP2)
  • Windows server 2008 R2
  • Windows server 2008 R2 (SP1)

Once you install Hotfix, windows scheduler error 2147750687 will be solved. If you need more support regarding installing Hotfix, you can always contact Microsoft support for assistance.

Conclusion:

So far these are the top three ways you can follow to fix Task Scheduler Error 2147750687 and we hope you find them useful. If you also have another method that works for you, please do share in the comment box.

If you often use the tool you’ll encounter some error codes and one of such error code is task scheduler error 2147750687. Windows task scheduler helps a lot when it comes to managing and monitoring your machines, you can automate tasks and let servers run on autopilot.

Users receive this error message when they’re running vantage on:

  • windows 7
  • windows vista
  • windows server 2008 R2
  • windows server 2008

When you receive such error code it means the task isn’t running and hence you’ll receive the error code ‘2147750687’ in windows task scheduler.

Fix Task Scheduler Error 2147750687

What Does Task Scheduler Error 2147750687 Mean?

When this error is shown it means task scheduler tried to run the task twice. In other words, it means duplicate schedules want to run at the same time.

What Causes Error 2147750687?

Windows task scheduler is designed to schedule tasks that will be run over the next hour using a scheduled window. When the start time of any given task clash with current schedule window and with the starting time of next scheduled window, it will result in scheduling the task twice. Which means the task will be scheduled at the end of current scheduled window and then again at the start of the next schedule window.

task scheduler 2147750687

task scheduler 2147750687

How To Fix Error 2147750687

There are three effective methods that can solve this problem, we’ll take a look at them one by one, when try one option and it doesn’t work you should move on to the next method. Let’s take at the three options you have:

First Method – Reduce The Frequency Of The Task

Reducing the frequency of the task can solve the problem because as we’ve mentioned earlier the error arise when the same task is schedule twice at the given time, and reducing the frequency minimize the risk of running duplicate schedule.

Second Method – Change Task Behavior

This is another method that has worked for most users. You should open task settings, at the bottom which is the last option, you’ll notice the message “if the task is already running, then the following rule applies

There are four options in the drop-down list and you need to select “Do not start a new instance”. This option ensures that a new instance is not run and the current instance that’s running will not be stopped.

Third Methods – Install Hotfix

If you’re still not able to fix the problem you need to install Hotfix update from Microsoft. It’s available in all the operating systems that experience this problem, they’re windows vista, windows 7, windows server 2008 R2 and windows server 2008.

Head over to Microsoft and search for Hotfix, on the page you’ll notice a download button and if it’s not available you can still make a request from their support center where you’ll be provided with a download link.

Some Prerequisites Before Installing Hotfix

Before you begin to install Hotfix on windows server 2008 R2 and windows 7, you should install 2305420 updates or service pack 1 update on your pc. These update packs are also available for download for free from Microsoft website.

Operating Systems That Can Use Hotfix

Hotfix update is available on the following operating systems;                                                                                                                            

  • Windows 7
  • Windows 7 (SP1)
  • Windows vista (SP1)
  • Windows vista (SP2)
  • Windows server 2008 (SP1)
  • Windows server 2008 (SP2)
  • Windows server 2008 R2
  • Windows server 2008 R2 (SP1)

Once you install Hotfix, windows scheduler error 2147750687 will be solved. If you need more support regarding installing Hotfix, you can always contact Microsoft support for assistance.

Conclusion:

So far these are the top three ways you can follow to fix Task Scheduler Error 2147750687 and we hope you find them useful. If you also have another method that works for you, please do share in the comment box.

  • Remove From My Forums
  • Question

  • Please need help, i have been struggling with for days now. I have two seperate jobs scheduled using the task scheduler 10 minutes apart. The second job however has 2 additional triggers added in total 3.

    The first trigger is to START the services.

    The second trigger is based on the first trigger (kicks off when the event id =102 which is TASK COMPLETED)

    The third trigger is based off the the second trigger ( kicks off when the event id =102 for trigger 3)

    But when the task is scheduled its throwing the following error:  Additional Data: Error Value: 2147750687.

    Please need help.

    When i’m adding the trigger to a task i’m using the custom instead of basic as i wanted to add two event id’s 102 and 314 task completed and task engine idle before the second trigger kicks in, but when i try the custom am getting the following error message:

    An Error occurred for task START HYPERION. Error Message: The following error was reported. The request is not supported. Please advice. When i choose the basic option  it wont let me add two event id’s

    Thanks

    • Edited by

      Monday, July 13, 2015 5:25 PM
      ss

Answers

  • Hi,

    Thanks a lot for your post, would you please check if the KB2617046 as below helped:

    https://support.microsoft.com/en-us/kb/2617046

    Feel free to post back if any issue.

    Best Regards,

    Elaine


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by
      Elaine Jing
      Monday, July 27, 2015 7:35 AM
    • Marked as answer by
      Elaine Jing
      Thursday, July 30, 2015 1:54 AM

I found another thread on this:

http://community.spiceworks.com/topic/203109-task-scheduler-error-value-2147750687

but it didn’t seem to conclude.  I am on SBS 2008.

I have a task that kicks off a batch file that zips a few files and does the domino rename.  Takes about 2 mins and runs every night. I started getting the error:

EventID 101 — Task Scheduler failed to start «\customTasks\DBBackups\SSAS Backup» task for user «DOMAIN\UserName». Additional Data: Error Value: 2147750687.

On looking at the event log, I can see 3 invocations @ 20:20 identical apart from the Correlation ID

Task Scheduler launched «{f05b9f5d-5dbc-494b-ad45-6673e3f88e84}»  instance of task «\customTasks\DBBackups\SSAS Backup» due to a time trigger condition.

So it looks like the task is being launched 3 times and one is succeeding and the other 2 aren’t.  When I look at the «triggers» for this task, there is just one and it is the «On a schedule», with 6 days ticked and running at 20:20.

It started giving me errors a few days ago when I went into the task and viewed it and I may have asked it to run interactively.  Initially I thought it was still running, but when I click on «Display all running tasks» shows nothing, well 3 system ones.  Also it can’t be still running as the server has had a reboot.

Any ideas, I was thinking about it being in the scheduler as a duplicate, but the GUI layer not showing it?

Понравилась статья? Поделить с друзьями:

Интересное по теме:

  • Код ошибки 2147614719 dr web cureit что это
  • Код ошибки 2148073494
  • Код ошибки 2147483648
  • Код ошибки 2147500037 при печати пароля домашней группы
  • Код ошибки 2147012721

  • Добавить комментарий

    ;-) :| :x :twisted: :smile: :shock: :sad: :roll: :razz: :oops: :o :mrgreen: :lol: :idea: :grin: :evil: :cry: :cool: :arrow: :???: :?: :!: