8197 ошибка srmsvc приложение

  • Remove From My Forums
  • Question

  • For the past month we have been receiving the following error on a 2012 r2 file server:

    File Server Resource Manager Service error: Unexpected error. 
       Error: RtlCreateSystemVolumeInformationFolder on volume C:?Volume returned 0x5, 0x8000ffff, Catastrophic failure

    We have tried the standard reboots, etc… to no avail.

    Is this something anyone can shed any light on? Anyone found a resolution?

Answers

  • Hi jrosen1987,

    Regarding to the error message that you provide, please check if miss
    System Volume Information folder from any partition. The System Volume Information folder is a hidden system folder. Please refer to the following operations and gain access to the System Volume Information folder.

    1. In Search option, type
      Folder Options and then click to open.
    2. In Folder Options, please select View tab. In Advanced settings, click
      Show hidden files, folders and drivers. Meanwhile, please uncheck
      Hide protected operating system files (Recommended). Then click
      Yes
      when you are prompted to confirm the change. Click OK.
    3. Then you will be able to find the System Volume Information folder in the root folder.

    Please check if any System Volume Information folder missed.

    Regarding to Event ID 8197, please refer to the following article.

    Event ID 8197 — FSRM Basic Functionality

    By the way, please also right click the System Volume Information folder and select
    Properties. In Properties, please select
    Security
    tab and check if SYSTEM group is added with full control permission.

    In addition, use
    chkdsk command to check disk state. Please monitor the result.

    There is a similar thread. Please refer to and check if can help you.

    Missing «System Volume Information» from a Drive

    http://social.technet.microsoft.com/Forums/en-US/d492a1c7-f811-48f4-a0a0-8d1e68f912c3/missing-system-volume-information-from-a-drive?forum=winserver8gen

    Hope this helps.

    Best regards,

    Justin Gu

    • Edited by

      Tuesday, March 18, 2014 2:35 AM

    • Marked as answer by
      Justin Gu
      Tuesday, March 25, 2014 7:12 AM

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

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

  • На сервере Windows Server 2012 в журнале событий встречаю периодически ошибку:

    Источник: SRMSVC

    ID: 8197

    Ошибка службы диспетчера ресурсов файлового сервера: непредвиденная ошибка.

    Подробные сведения об ошибке:
       Ошибка: GetNodeClusterState(NULL, &dwClusterState), 0x80070002, Не удается найти указанный файл.

    Что это за ошибка?

Все ответы

  • Привет,

    Проделайте cluster validation report, все проходит на ура?


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

  • С учетом того, что это — одноузловой кластер (мы собирается в ближайшее время сделать его двухузловым), тест прошел успешно. Тесты, требующие наличия нескольких узлов естественно не выполнялись.

    Единственное, что меня озадачило. По разделяемым файловым ресурсам выдано предупреждение:

    Этот ресурс настроен на использование нестандартного для данного типа ресурса
    интервала значения параметра «Время ожидания». В параметре «Время ожидания»
    указывается время, в течение которого ресурс должен переключиться между режимом
    работы вне сети и интерактивным режимом, прежде чем служба кластера переведет
    ресурс в состояние «Сбой». Обычно рекомендуется использовать значения по
    умолчанию, однако в некоторых случаях лучше выбрать другие значения. Эти
    параметры настраиваются в диспетчере отказоустойчивости кластеров на вкладке
    «Политики» окна «Свойства».

    В свойствах файлового разделения я не нашел вкладки Политика. Поэтому не знаю, что можно сделать. Может быть эта ошибка — тоже результат одноузлового кластера?

  • Еще одна ошибка подобного типа.

    Источник: SRMSVC

    ID: 8197

    Ошибка службы диспетчера ресурсов файлового сервера: непредвиденная ошибка.

    Операция:
       Идет запуск службы диспетчера ресурсов файлового сервера.

    Подробные сведения об ошибке:
       Ошибка: ClusterRegCreateKey(), 0x80070046, Сервер сети был остановлен или находится в процессе запуска.

  • читали статью для ошибки
    ClusterRegCreateKey(), 0x80070046

    http://support2.microsoft.com/kb/822050


    C уважением к Вам, Я

  • Данная ошибка возникает при включении сервера? 

    Попробуйте сервис «службы диспетчера ресурсов файлового сервера» поставить как отложенный
    запуск.


    C уважением к Вам, Я

  • Remove From My Forums
  • Question

  • My client’s file server is logging this error message every 20 minutes and I am baffled at what it could be.  I’ve ran CHKDSK successfully, but this error keeps coming up.  Any suggestions would be greatly appreciated. The Event is posted below:

    Log Name:      Application
    Source:        SRMSVC
    Date:          9/3/2018 4:51:05 PM
    Event ID:      8197
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      FileServer1.ClientDomain.local
    Description:
    File Server Resource Manager Service error: Unexpected error.

    Error-specific details:
       Error: GetVolumeNameForVolumeMountPoint, 0x80071126, The file or directory is not a reparse point.

    Event Xml:
    <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
      <System>
        <Provider Name=»SRMSVC» />
        <EventID Qualifiers=»32772″>8197</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime=»2018-09-03T23:51:05.000000000Z» />
        <EventRecordID>514768</EventRecordID>
        <Channel>Application</Channel>
        <Computer>FileServer1.ClientDomain.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>

    Error-specific details:
       Error: GetVolumeNameForVolumeMountPoint, 0x80071126, The file or directory is not a reparse point.
    </Data>
        <Binary>2D20436F64653A2053524D564F4C4D4330303030303133312D2043616C6C3A2053524D564F4C4D4330303030303037352D205049443A202030303030313336302D205449443A202030303030313639362D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B2073726D737663732020202020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
      </EventData>
    </Event>

  • Remove From My Forums
  • Question

  • My client’s file server is logging this error message every 20 minutes and I am baffled at what it could be.  I’ve ran CHKDSK successfully, but this error keeps coming up.  Any suggestions would be greatly appreciated. The Event is posted below:

    Log Name:      Application
    Source:        SRMSVC
    Date:          9/3/2018 4:51:05 PM
    Event ID:      8197
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      FileServer1.ClientDomain.local
    Description:
    File Server Resource Manager Service error: Unexpected error.

    Error-specific details:
       Error: GetVolumeNameForVolumeMountPoint, 0x80071126, The file or directory is not a reparse point.

    Event Xml:
    <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
      <System>
        <Provider Name=»SRMSVC» />
        <EventID Qualifiers=»32772″>8197</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime=»2018-09-03T23:51:05.000000000Z» />
        <EventRecordID>514768</EventRecordID>
        <Channel>Application</Channel>
        <Computer>FileServer1.ClientDomain.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>

    Error-specific details:
       Error: GetVolumeNameForVolumeMountPoint, 0x80071126, The file or directory is not a reparse point.
    </Data>
        <Binary>2D20436F64653A2053524D564F4C4D4330303030303133312D2043616C6C3A2053524D564F4C4D4330303030303037352D205049443A202030303030313336302D205449443A202030303030313639362D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B2073726D737663732020202020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
      </EventData>
    </Event>

I found next to no information about this error with respect to Server 2012. There is a good deal of information out about this error with Server 2003 with a update package fix from Microsoft as well as notes about how the error has been resolved for Server 2008 and 2008 R2 but nothing for 2012.

On both Server 2012 and Server 2012 R2 (edition doesn’t matter) after installing the File System Resource Manager (FSRM) role an error occurs:

Event ID 8197
Source: SRMSVC
File Server Resource Manger Service error: Unexpected error. 
Error-specific details:
Error: GetVolumeNameForVolumeMountPoint, 0x800700001, incorrect function

This error also occurs on every restart as well as after the service has been restarted (specifically 30 seconds after it has been started). This error was happening on two Dell servers: PowerEdge R720 and PowerEdge R620.

The first thing I discovered was that this only occurs while using UEFI. There is no error when the server is using standard BIOS. I could have stopped there and just stuck with BIOS but I didn’t want to lose out on any of the new features of UEFI and server 2012.

Initially, I assumed this was an issue with Dell’s UEFI implementation since it occurred on both of my new servers as well as in a VM running on a DELL PowerEdge ESX host. However, I was able to reproduce this error with another VM running on non-Dell hardware. This means the problem is with Microsoft. Installing FSRM on Server 2008 R2 on UEFI does not produce the error, only 2012 & 2012 R2 do, narrowing this down to a Server 2012 problem with UEFI.

I have not seen anything negative come of this error aside from the glaring red x in event viewer. I fully tested FSRM functionality and found everything seemed to work without a hitch. Unfortunately, I’m not the type to just ignore an unknown persistent error so I spent a whooole lot of time trying to get to the bottom of this. I was highly motivated to get this figured out because the one hit I had on google with this error and Server 2012 mentioned vanishing volumes on restarts (something I didn’t want popping up on me down the road).

FAQ: File Server Resource Manager(FSRM) server does not – Microsoft Partners Forum:
http://partnersupport.microsoft.com/en-us/mpndataplat/forum/mpncatwinsvr-mpnwssmbus/faq-file-server-resource-managerfsrm-server-does/9e9cecf8-fefb-47dc-b7e8-783da48391b0

Symptoms:

FSRM cannot start with the event id: 8197.

Cause:

This issue not only occurs when the system account does not have permission to the quota.xml file, but also related with the srmglobalsettings.xml which is the settings file of File Server Resource Manager global configuration store.

Solution

Step1. Download Psexec tool from the link below and extract  to the C: drive

PsExec v1.98

http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx

Step2. Start  a CMD with using System account by running the psexec command

================================

a. Open Command Prompt and navigate to the folder or the psexec tool

b. Run the command: psexec -i -d -s cmd.exe to start a new Command Prompt which is running under the System Account

c. In the new opened Command Prompt, run the commands below one by one to take ownership of the took the ownership of hidden folder SRM, quota.xml, reportsettings.xml and srmglobalsettings.xml and give the full rights to system account on the files and folders.

detailed commands:

————————————

cd

cd “System Volume Information”

takeown /r /F srm

# Do you want to replace the directory permissions with permissions granting you full control (“Y” for YES, “N” for NO or “C” to CANCEL)? Y

icacls srm /grant system:(F)

cd srm

takeown /f quota.xml

icacls quota.xml /grant System:(F)

takeown /f settings

icacls settings /grant system:(F)

cd settings

takeown /f reportsettings.xml

takeown /f srmglobalsettings.xml

icacls reportsettings.xml /grant System:(F)

icacls srmglobalsettings.xml /grant System:(F)

Best regards,


April Zhao

Microsoft Partner Support Community

—————————————————————————————–

We hope you get value from our new forums platform! Tell us what you think:

http://partnersupport.microsoft.com/en-US/mpnfeedback/forum

——————————————————————————————

This posting is provided “AS IS” with no warranties, and confers no rights. PSC support provides service from Monday to Friday (your local business hours). Thanks!

I found next to no information about this error with respect to Server 2012. There is a good deal of information out about this error with Server 2003 with a update package fix from Microsoft as well as notes about how the error has been resolved for Server 2008 and 2008 R2 but nothing for 2012.

On both Server 2012 and Server 2012 R2 (edition doesn’t matter) after installing the File System Resource Manager (FSRM) role an error occurs:

Event ID 8197
Source: SRMSVC
File Server Resource Manger Service error: Unexpected error. 
Error-specific details:
Error: GetVolumeNameForVolumeMountPoint, 0x800700001, incorrect function

This error also occurs on every restart as well as after the service has been restarted (specifically 30 seconds after it has been started). This error was happening on two Dell servers: PowerEdge R720 and PowerEdge R620.

The first thing I discovered was that this only occurs while using UEFI. There is no error when the server is using standard BIOS. I could have stopped there and just stuck with BIOS but I didn’t want to lose out on any of the new features of UEFI and server 2012.

Initially, I assumed this was an issue with Dell’s UEFI implementation since it occurred on both of my new servers as well as in a VM running on a DELL PowerEdge ESX host. However, I was able to reproduce this error with another VM running on non-Dell hardware. This means the problem is with Microsoft. Installing FSRM on Server 2008 R2 on UEFI does not produce the error, only 2012 & 2012 R2 do, narrowing this down to a Server 2012 problem with UEFI.

I have not seen anything negative come of this error aside from the glaring red x in event viewer. I fully tested FSRM functionality and found everything seemed to work without a hitch. Unfortunately, I’m not the type to just ignore an unknown persistent error so I spent a whooole lot of time trying to get to the bottom of this. I was highly motivated to get this figured out because the one hit I had on google with this error and Server 2012 mentioned vanishing volumes on restarts (something I didn’t want popping up on me down the road).

  • Remove From My Forums
  • Question

  • Getting the following error from SRMSVC when a quote threshold is exceeded.

    File Server Resource Manager Service error: Unexpected error. 

    Operation:

       Running command line action.

       Quota threshold reached.

       Processing File Server Resource Manager event

    Context:

       Action type: Command Action

       Account: NT AUTHORITYLocalSystem

       Executable path: %windir%system32dirquota.exe

       Arguments: quota modify /path:[Quota Path] /sourcetemplate:»3GB Home Share Extension»

       Working directory: [Quota Path]

       Quota path: G:HomeDirbob

       Threshold percent: 98

    Error-specific details:

       Error: AuthzInitializeContextFromSid, 0x80070005, Access is denied.

    The command is set to run as the Local System, and the SYSTEM account has full access to the G: drive and beyond.

    Let me know if there is anymore information I can provide to maybe help fix this. Thanks!

Answers

  • Have a try on following steps:

    Download psexec from

    http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx

    Used following command to open command prompt with system account :

    psexec -i -d -s cmd.exe

    took the ownership of hidden folder SRM, quota.xml, reportsettings.xml and srmglobalsettings.xml.

    Gave the full rights to system account on the the above mentioned files & folders.

    Detailed steps:

    cd

    cd «System Volume Information»

    takeown /r /F srm

    Do you want to replace the directory permissions with permissions granting you full control («Y» for YES, «N» for NO or «C» to CANCEL)? y

    icacls srm /grant system:(F)

    cd srm

    takeown /f quota.xml

    icacls quota.xml /grant System:(F)

    takeown /f settings

    icacls settings /grant system:(F)

    cd settings

    takeown /f reportsettings.xml

    takeown /f srmglobalsettings.xml

    icacls reportsettings.xml /grant System:(F)

    icacls srmglobalsettings.xml /grant System:(F)


    Shaon Shan |TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tngfb@microsoft.com

    • Marked as answer by

      Friday, April 8, 2011 2:30 AM

У нас есть та же проблема. Были находятся на RHEL 5.3, 2.6.18-128.el5, у Нас была проблема с нашим маршрутом к нашей частной сети. Это продолжало отбрасывать. Мы нашли работу вокруг. Мы помещаем это в наш crontab, и это устраняет проблему. * * * * */sbin/arp-d IP к устройству хранения данных

задан
15 February 2011 в 17:39

Ссылка

2 ответа

Поскольку Windows все еще не имеет собственного ISO, монтируют способность, я использовал Виртуальный Драйвер CD-ROM от Microsoft. Это описано здесь: http://jamesewelch.wordpress.com/2007/08/13/mounting-an-iso-image-using-microsofts-virtual-cdrom-driver/

Я использовал это для монтирования файлов ISO, которые в свою очередь были совместно использованы по сети для развертывания. Поскольку мы больше не развертываем приложения таким образом, я удалил этот инструмент и разрешенные журналы ошибок. Больше никакой ошибки когда-либо час и несколько минут.

Очевидно, этот драйвер не поддерживается, но эта фиксация была бы немедленно очевидна, если ошибка точки монтирования сообщила, что она пыталась смонтировать более применимым способом.

ответ дан Godeke
4 December 2019 в 01:44

Ссылка

Теги

Похожие вопросы

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

  • 81401 ларгус код ошибки
  • 8139 ошибка ниссан эльгранд
  • 813 ошибка pppoe win 10
  • 81110007 war thunder ошибка чтения файла
  • 81 20 ошибка honda accord 2013

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

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