locked
Resource Manager Service Error 8197 - "StringCchCopy, 0x8007007a, The data area passed to a system call is too small" RRS feed

  • Question

  • I'm getting the following error in my event viewer on a 2008 STD Server (running DFS):

    Event ID: 8197
    Source: SRMSVC
    ----------------------------------------------------------------------------------------------------------------
    File Server Resource Manager Service error: Unexpected error.

    Operation:
       Getting file screen on folder 'C:\Windows\SYSVOL\sysvol\<My Domain Info>'.

    Error-specific details:
       Error: StringCchCopy, 0x8007007a, The data area passed to a system call is too small.
    ----------------------------------------------------------------------------------------------------------------

    Microsoft does not provide any further on-line information.
    Tuesday, September 30, 2008 2:57 PM

Answers

  • I think I found the root cause, but no fix.  If I click on DFS Management and then Replication and look at the "Domain System Volume", it shows an unknown server volume which points to an old non-production server.  I am unable to remove or update this record.

    If this is the problem, is there a way to resolve without removing the DFS roll and re-installing?  Apparently if you attempt to remove DFS as a roll you are prompted that you must remove AD first.... um, no thanks.

    BTW: It appears DFS is not replicating bewteen two of my production servers.
    • Proposed as answer by David Shen Thursday, October 2, 2008 7:06 AM
    • Marked as answer by David Shen Monday, October 6, 2008 2:46 AM
    Tuesday, September 30, 2008 8:02 PM
  • Hi Rollinz,

     

    1. What is the domain functional level of the current domain in the environment? Windows Server 2003 or Windows Server 2008?

     

    2. Are there any Windows Server 2003 based domain controller in the domain? Or did you upgrade the domain from Windows Server 2003 to Windows Server 2008? Can you check if the old non-production server information has been removed in Active Directory?

     

    3. Can you find the "Domain System volume" entry in the ADSIedit.msc?

     

    a. Open AdsiEdit.msc on domain controller.

     

    b. Connect to Default naming context.

     

    CN=Domain System Volume, CN=DFSR-GlobalSettings, CN= System, DC= <domain>, DC= <com>

     

    c. If you verify it really point to the old server, you may try to remove this entry in the ADSIedit.msc

     

    Hope it helps.


    David Shen - MSFT
    • Marked as answer by David Shen Monday, October 6, 2008 2:46 AM
    Friday, October 3, 2008 8:04 AM

All replies

  • I think I found the root cause, but no fix.  If I click on DFS Management and then Replication and look at the "Domain System Volume", it shows an unknown server volume which points to an old non-production server.  I am unable to remove or update this record.

    If this is the problem, is there a way to resolve without removing the DFS roll and re-installing?  Apparently if you attempt to remove DFS as a roll you are prompted that you must remove AD first.... um, no thanks.

    BTW: It appears DFS is not replicating bewteen two of my production servers.
    • Proposed as answer by David Shen Thursday, October 2, 2008 7:06 AM
    • Marked as answer by David Shen Monday, October 6, 2008 2:46 AM
    Tuesday, September 30, 2008 8:02 PM
  • Hi Rollinz,

     

    1. What is the domain functional level of the current domain in the environment? Windows Server 2003 or Windows Server 2008?

     

    2. Are there any Windows Server 2003 based domain controller in the domain? Or did you upgrade the domain from Windows Server 2003 to Windows Server 2008? Can you check if the old non-production server information has been removed in Active Directory?

     

    3. Can you find the "Domain System volume" entry in the ADSIedit.msc?

     

    a. Open AdsiEdit.msc on domain controller.

     

    b. Connect to Default naming context.

     

    CN=Domain System Volume, CN=DFSR-GlobalSettings, CN= System, DC= <domain>, DC= <com>

     

    c. If you verify it really point to the old server, you may try to remove this entry in the ADSIedit.msc

     

    Hope it helps.


    David Shen - MSFT
    • Marked as answer by David Shen Monday, October 6, 2008 2:46 AM
    Friday, October 3, 2008 8:04 AM
  • Thank you for your response, I think we are close!  To answer your questions:

    1. Functional level is 2008.

    2. We've never had any other type of server other than 2008 in our environment.  It looks like the old non-production server has not been removed in AD in the domain controller list.  Hmmmm, Interestingly enough the new domain controller I built to replace it is NOT in AD.  ???  I know it's a member of the domain how is this possible?

    3.   I found the "Domain System volume" for the old non-production server in ADSIedit.  Should I just delete the domain controller and everything under it since it's no longer around?  And why is my new domain controller not in my list?

    The old non-production server is actually the same physical server as the new domain controller, but it was completely wiped and rebuilt and given a totally different system name.  Does server 2008 have some sort of intelligence that checks hardware components to make it think it's the old server some how?

    Tuesday, October 7, 2008 1:29 PM
  • Whoa!  Weird! ????  Read the above first before reading this.

    Ok this is craziness......  I swear when I opened ADSIedit before the old server name was listed in "Domain Controllers" and NOT the new server.  Before I even exited the ADSIedit tool the server name changed to the new server name.  Looks like there is some sort of intelligence built into the OS that could be causing this issue.

    Any recommendations?
    Tuesday, October 7, 2008 1:37 PM
  • It looks like the AD took care of itself just by simply opening ADSIedit.msc and updating the schema.

    Dfs is again working and everything is normal except one small issue, the bogus sysvol is still listed in DFS Replication groups.  I have a total of three volumes showing when there should only be two.  The boggus one still has a red error mark on it. 

    Is there anyway to get rid of that?
    Tuesday, October 7, 2008 4:41 PM
  • I'm getting basically the same error but I'm not running DFS - 

    Log Name:      Application
    Source:        SRMSVC
    Date:          3/5/2009 7:42:56 PM
    Event ID:      8197
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      anth-fsexn.anthem.lan
    Description:
    File Server Resource Manager Service error: Unexpected error.

    Operation:
       Getting file screen on folder 'C:\Windows\SYSVOL\sysvol\anthem.lan'.

    Error-specific details:
       Error: StringCchCopy, 0x8007007a, The data area passed to a system call is too small.

    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="2009-03-06T03:42:56.000Z" />
        <EventRecordID>26570</EventRecordID>
        <Channel>Application</Channel>
        <Computer>anth-fsexn.anthem.lan</Computer>
        <Security />
      </System>
      <EventData>
        <Data>

    Operation:
       Getting file screen on folder 'C:\Windows\SYSVOL\sysvol\anthemvp.lan'.

    Error-specific details:
       Error: StringCchCopy, 0x8007007a, The data area passed to a system call is too small.
    </Data>
        <Binary>2D20436F64653A2053524D504154484330303030303633352D2043616C6C3A2053524D504154484330303030303536392D205049443A202030303030313436342D205449443A202030303030323432382D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F7374202D6B2073726D7376637320202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
      </EventData>
    </Event>

    Friday, March 6, 2009 2:41 PM