We finally got this resolved with the help of PSS. They had to make a registry change per this KB: http://technet.microsoft.com/en-us/library/ff633453%28v=ws.10%29.aspx.
From what the tech said, the problem may exhibit itself when more 300,000 files have been placed. Although, for us, I don't understand why it took so long since there are over 1M files there. Oh well, vendor has verified files are transferring so this project may actually get done. -----Original Message----- From: Kurt Buff [mailto:[email protected]] Sent: Thursday, February 14, 2013 5:01 PM To: NT System Admin Issues Subject: Re: File limitation error:updated On Thu, Feb 14, 2013 at 1:41 PM, Chinnery, Paul <[email protected]> wrote: > I had a conference call with our vendor this afternoon. Here is where > the error occurs: > > I open up a command prompt and go to this folder on the server: > > z:\00000000\0000\0000\00000 > > I then type in : > > MD 111111111111 (that's twelve digits) , it works. > > If I type in: > > MD 001111111111 > it fails with that file limitation error. > > Right now there are approximately 4.5 million files. This is one > Server > 2008 r2 sp1 server. That's awesome! Same number of digits, but it doesn't like the name. And, it's nowhere near the path length limitations we've discussed. MFT fragmentation perhaps? Is that Z: drive local to the machine, or is it mapped to a share on another machine? Just curious - it shouldn't make a difference... I am now officially consumed with curiousity - do keep posting updates. Kurt ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
