Ошибка getvolumenameforvolumemountpoint 0x80071126

  • Remove From My Forums
  • Question

  • Hi All,

    Apologies if I am posting on the wrong forum.

    I am getting the above error occasionally on my server running Win Server 2012 R2 and it only seems to happen most frequently between 3am to 7am. There are times the error does appear in the afternoon but maybe once or twice in a week.

    What is this error ? Does it affect anything and how do i resolve it ?

Answers

  • placing this on hold as it seems to be an OEM error.

    • Marked as answer by

      Friday, September 28, 2018 3:46 AM

When processing a set from
component’s file
, the requester may need to recursively traverse a
directory tree
. This can necessitate the handling of
mounted folders
and
reparse points
(like links) that refer to data not located on the current volume.

To ensure proper backup and restore operations, requesters must adhere to VSS guidelines for navigating a directory tree, including following
mounted folder
s and
Reparse Points
.

To exemplify these principles, take into account the subsequent instance:

  • The drive letter C:\ is assigned to volume \\?\Volume{GUID_1}.
  • The path of the file set is located at C:\WriterData.
  • The file set utilizes a *.dat file that has the
    file specification
    extension.
  • The recursion of the file set is enabled by setting it to TRUE.
  • The volume with the GUID_1 contains the directory named C:\WriterData.
  • The mounted folder can be found in the directory C:\WriterData\Archive.
  • The mounted folder C:\WriterData\Archive is linked with the volume \\?\Volume{GUID_2}.

Handling Mounted Folders and Reparse Points during Backup

When conducting a recursive backup under VSS, the handling of mounted folders and reparse points can be simplified to the following fundamental guidelines.

  • Traversing occurs through mounted directories and reparse points.
  • When a mounted folder or a reparse point is directed towards a volume, it is recommended to create a shadow copy of the respective volume.
  • Mounted folders and reparse points within a volume will be visible in its corresponding shadow copy.
  • The shadow copy of the volume which the mounted folder or reparse point refers to, captures the data located under it.

Taking the mentioned example into account, the requester needs to explore all the data located under C:\WriterData\Archive and its subdirectories since the recursive flag is enabled.

To include them in the shadow copy set, the requester should use IVssBackupComponents::AddToSnapshotSet to add both the volume with drive letter C:\ (\\?\Volume{GUID_1}) and the volume linked to the mounted folder C:\WriterData\Archive (\\?\Volume{GUID_2}).

The deviceObject1 is associated with the shadow copy of volume \\?\Volume{GUID_1}, where the C:\WriterData\Archive folder is mounted.

Nonetheless, the shadow copy referenced by deviceObject1 will not capture any information located in the mounted folder (data on \\?\Volume{GUID_2}). Conversely, the shadow copy of \\?\Volume{GUID_2} with a device object named deviceObject2 will contain that data.

To search for files matching C:\WriterData\*.dat, a requester who is backing up shadow copied files under C:\WriterData would utilize the path deviceObject1\WriterData.

The requester will search for files matching the pattern C:\WriterData\Archive\*.dat in deviceObject2 path, which is associated with the mounted folder C:\Writer\Archive. This is done to backup shadow copied files located under C:\WriterData\Archive, as the root directory of \\?\Volume{GUID_2} is linked with C:\Writer\Archive.

It’s important to keep in mind that a reparse point is treated similarly to a mounted folder. While the reparse point is visible in the shadow copy of the initial volume, the data located underneath it is visible in the shadow copy of the second volume.

While backing up, it is important for requesters to save details regarding the mounted folders and their associated volumes, as well as the targets and reparse points, in order to guarantee the accurate backup and restoration of all data.

Handling Mount and Reparse Points during Restore

While restoring files, the requester needs to adhere to guidelines that are not identical to the ones followed during backup, disregarding factors like alternative location mapping and the destination of the new target.

  • Recursive paths are traced across mounted folders and reparse points, if necessary, as previously done.
  • The restoration process involves bringing back the folders that have been mounted.
  • The original paths of mounted folders and reparse points dictate their respective restoration locations.

Assuming the volume names remain unchanged during the backup and restore process, the restored reparse points and mounted folders will accurately reference the correct volumes without requiring volume re-creation.

In the previously mentioned scenario, restoring the mounted folder C:\WriterData\Archive to (\\?\Volume{GUID_1}) and the associated volume to (\\?\Volume{GUID_2}) would ensure that both the restored files and
file structure
are accurate and coherent.

Data restoration to a system with changed volume names can occur following disk crashes, which may necessitate manual system recovery and re-
create volumes
. Unfortunately, mounted folders and reparse points become invalid after restoration in such cases. To restore files and file structure on the
restored volume
, you must delete the restored mounted folders and reparse points and create new ones on the disk. Whether or not this is appropriate is at the discretion of the backup application.

Keep in mind that the mounted folder’s restore destination can potentially be occupied already, such as C:\WriterData\Archive, which may have existing files. The course of action for this scenario is left to the discretion of the backup application.

Windows 10 What is the meaning for a reparse point?, Replied on July 20, 2017. Hello, A file or directory can contain a reparse point, which is a collection of user-defined data. For more information about reparse points in Windows 10, please refer to this article from our MSDN website. To resolve the issue, we recommend running the Disk cleanup app and …

Windows SBS 2011 Standard

Quotas are turned off (have never been used).  I verified System account access to the SRM directory in  \System Volumn Information.

Log Name:      Application
Source:        SRMSVC
Date:          12/19/2012 8:06:52 AM
Event ID:      8197
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER1.domain.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=»2012-12-19T16:06:52.000000000Z» />
    <EventRecordID>728815</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER1.domain.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

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

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

  • Hi All,

    Apologies if I am posting on the wrong forum.

    I am getting the above error occasionally on my server running Win Server 2012 R2 and it only seems to happen most frequently between 3am to 7am. There are times the error does appear in the afternoon but maybe once or twice in a week.

    What is this error ? Does it affect anything and how do i resolve it ?

Ответы

  • placing this on hold as it seems to be an OEM error.

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

      28 сентября 2018 г. 3:46

  • Remove From My Forums
  • Question

  • Hi All,

    Apologies if I am posting on the wrong forum.

    I am getting the above error occasionally on my server running Win Server 2012 R2 and it only seems to happen most frequently between 3am to 7am. There are times the error does appear in the afternoon but maybe once or twice in a week.

    What is this error ? Does it affect anything and how do i resolve it ?

Answers

  • placing this on hold as it seems to be an OEM error.

    • Marked as answer by

      Friday, September 28, 2018 3:46 AM

I have recently started getting this error and not sure why as not have made any amendments to the server or installed any new applications. This is 2012 R2 Server with SQL Server 2012. 

Unable to find out which volume it is referring here to and I have also tried giving access rights to the Systme Volume Information based on few Microsoft tech article I found i.e using Pstools.

File Server Resource Manager Service error: Unexpected error.

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

Windows SBS 2011 Standard

Quotas are turned off (have never been used).  I verified System account access to the SRM directory in  System Volumn Information.

Log Name:      Application
Source:        SRMSVC
Date:          12/19/2012 8:06:52 AM
Event ID:      8197
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER1.domain.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=»2012-12-19T16:06:52.000000000Z» />
    <EventRecordID>728815</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER1.domain.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

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

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

  • 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!

File server resource manager 8197 Windows Server 2008 R2

hi have problem after installing frsm on windows server 2008 r2.

file server resource manager service error: unexpected error. 

error-specific details:
   error: getvolumenameforvolumemountpoint, 0x80071126, file or directory not reparse point.

log name: application
source: srmsvc
event id: 8197
level: error

i saw there similar questions there windows server 2003

hi,

have try on following steps:

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

used following command open command prompt system account :

psexec -i -d -s cmd.exe

took ownership of hidden folder srm, quota.xml, reportsettings.xml , srmglobalsettings.xml.

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

detailed steps:

cd \
cd «system volume information»
takeown /r /f srm
want replace directory permissions permissions granting full control («y» yes, «n» no or «c» 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)


technet subscriber support in forum |if have feedback on our support, please contact tnmff@microsoft.com.

Windows Server  >  File Services and Storage

Popular posts from this blog

Add-DnsServerDirectoryPartition replication

Image

hi i have 2 dc have dns role dc1 domain.me dc2 a.domain.me i want test how dns replication manually configured dns partition works. created new partition on dc1 , dc2 using following powershell command: add-dnsserverdirectorypartition -name 2012b on dc1 add-dnsserverdirectorypartition -name 2012d on dc2 when create new forward lookup zone on dc1 not possible replicate data dc2 (see below). the screenshot in german. think pull down menue gives glimpse problem.  when run get-dnsserverdirectorypartition on dc1 following… hi, i assume lookup zone ad integrated zone, have verified replication between 2 dcs? please run following commands have check: repadmin /showrepl dc2 .yourdomain.com  or dcdiag /test:replications if works well, please wait enough time make newly created objects replicate between 2 dcs or take force update: force ad replication using command repadmin /syncall /parameter( repadmin /syncall ) or using ad sites conso

Failed to delete the test record dcdiag-test-record in zone test.com

ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server…    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ……………………. dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes…          ……………………. dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain

Powershell error — Server instance not found on the given port.

i have ad backup opened in tcp port 5432 dsamain -dbpath ntds.dit -ldapport 5432 -allownosadminaccess when use dsquery tool, can select localhost:5432 target using ds tools can information want but when try use powershell commands -server;localhost:5432 got error: server instance not found on given port. using get-adobject ou get-aduser ps c:\users\administrator> get-adobject -server localhost:5432 -filter ‘objectclass -eq «user»‘ get-adobject : server instance not found on given port. @ line:1 char:13 + get-adobject <<<<  -server localhost:5432 -filter ‘objectclass -eq «user»‘     + categoryinfo          : invalidargument: (:) [get-adobject], argumentexception     + fullyqualifiederrorid : server instance not found on given port.,microsoft.activedirectory.management.commands.getadobject powershell cmdlets dont «speak pure ldap», communicate ad web services (and maybe encrypted). service runs on dc

Понравилась статья? Поделить с друзьями:
  • Ошибка f04 на газовом котле viessmann vitopend 100
  • Ошибка ip конфигурации что это такое
  • Ошибка f04 на газовом котле baltgaz
  • Ошибка ip конфигурации при подключении wifi на телевизоре
  • Ошибка error opening file for writing