none
Рабочие процессы не выходят из паузы RRS feed

  • Вопрос

  • Добрый день. Рабочие процессы не выходят из паузы – не срабатывает корректно Sharepoint Timer
    Service. Иногда срабатывает перезагрузка этой службы на сервере (редко), иногда
    – перезапуск в целом Портала на сервере (через IIS)(тоже не всегда). Более менее
    продолжительный эффект при перезагрузке сервера Портала  –
    точнее, сервера Портала и сервера базы данных. Может кто знает как решить эту проблему на постоянной основе?
    3 августа 2017 г. 9:24

Ответы

  • Здравствуйте

    Попробуйте следующий вариант:

    Clearing the cache is the best resolving part for this.

    To resolve this issue, clear the file system cache on all servers in the server farm on which the Windows SharePoint Services Timer service is running. To do this, follow these steps:

    1. Stop the Timer service. To do this, follow these steps:
      1. Click Start, point to Administrative Tools, and then click Services.
      2. Right-click SharePoint 2010 Timer services, and then clicks Stop.
      3. Close the Services console.
      4. Navigate to the directory:C:\ProgramData\Microsoft\SharePoint\Config
      5. \GUID.
      1. Backup the GUID folder
      2. Back up the Cache.ini file. (Make a copy of it. DO NOT DELETE THIS FILE, Only the XML files in the next step)
      1. Delete all the XML configuration files in the GUID folder (DO NOTE DELETE THE FOLDER). Do this so that you can verify that the GUID folders content is replaced by new XML configuration files when the cache is rebuilt.  Note when you empty the configuration cache in the GUID folder; make sure that you do NOT delete the GUID folder and the Cache.ini file that is located in the GUID folder.
      2. Double-click the Cache.ini file.
      3. On the Edit menu, click Select All.
      4. On the Edit menu, click Delete.
      5. Type 1, and then click Save on the File menu. (Basically when you are done, the only text in the config.ini file should be the number 1)
      6. On the File menu, click Exit.
      7. Start the Timer service. To do this, follow these steps:
        1. Click Start, point to Administrative Tools, and then click Services.
        2. Right-click SharePoint 2010 Timer, and then click Start.
        3. Close the Services console.
      8. Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
      9. Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.
      10. Check in the GUID folder to make sure that the xml files are repopulating. This may take a bit of time.

     


    Мнения, высказанные здесь, являются отражением моих личных взглядов, а не позиции корпорации Microsoft. Вся информация предоставляется "как есть" без каких-либо гарантий.

    3 августа 2017 г. 10:06
    Модератор
  • Добрый день

    то что предложил Иван Проданов

    можно сделать через готовый скрипт 

    SharePoint 2010 / 2013: Clearing the Configuration Cache

    мой блог не много о SharePoint

    3 августа 2017 г. 10:21

Все ответы

  • Здравствуйте

    Попробуйте следующий вариант:

    Clearing the cache is the best resolving part for this.

    To resolve this issue, clear the file system cache on all servers in the server farm on which the Windows SharePoint Services Timer service is running. To do this, follow these steps:

    1. Stop the Timer service. To do this, follow these steps:
      1. Click Start, point to Administrative Tools, and then click Services.
      2. Right-click SharePoint 2010 Timer services, and then clicks Stop.
      3. Close the Services console.
      4. Navigate to the directory:C:\ProgramData\Microsoft\SharePoint\Config
      5. \GUID.
      1. Backup the GUID folder
      2. Back up the Cache.ini file. (Make a copy of it. DO NOT DELETE THIS FILE, Only the XML files in the next step)
      1. Delete all the XML configuration files in the GUID folder (DO NOTE DELETE THE FOLDER). Do this so that you can verify that the GUID folders content is replaced by new XML configuration files when the cache is rebuilt.  Note when you empty the configuration cache in the GUID folder; make sure that you do NOT delete the GUID folder and the Cache.ini file that is located in the GUID folder.
      2. Double-click the Cache.ini file.
      3. On the Edit menu, click Select All.
      4. On the Edit menu, click Delete.
      5. Type 1, and then click Save on the File menu. (Basically when you are done, the only text in the config.ini file should be the number 1)
      6. On the File menu, click Exit.
      7. Start the Timer service. To do this, follow these steps:
        1. Click Start, point to Administrative Tools, and then click Services.
        2. Right-click SharePoint 2010 Timer, and then click Start.
        3. Close the Services console.
      8. Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
      9. Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.
      10. Check in the GUID folder to make sure that the xml files are repopulating. This may take a bit of time.

     


    Мнения, высказанные здесь, являются отражением моих личных взглядов, а не позиции корпорации Microsoft. Вся информация предоставляется "как есть" без каких-либо гарантий.

    3 августа 2017 г. 10:06
    Модератор
  • Добрый день

    то что предложил Иван Проданов

    можно сделать через готовый скрипт 

    SharePoint 2010 / 2013: Clearing the Configuration Cache

    мой блог не много о SharePoint

    3 августа 2017 г. 10:21