On Tue, Mar 18, 2008 at 4:32 PM, Kurt Buff [EMAIL PROTECTED] wrote:
Problem is, there is a definite limit on file/path specifications with
the Win32 API - after 254 characters, things get really wonky ...
Yah, I'll second that. I realized after my last post in this thread
that the limit is
://TheEssentialExchange.com
-Original Message-
From: Ben Scott [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 3:59 PM
To: NT System Admin Issues
Subject: Re: NTFS take ownership question
On Tue, Mar 18, 2008 at 4:32 PM, Kurt Buff [EMAIL PROTECTED] wrote:
Problem is, there is a definite limit on file
Admin Issues
Subject: Re: NTFS take ownership question
On Tue, Mar 18, 2008 at 4:32 PM, Kurt Buff [EMAIL PROTECTED] wrote:
Problem is, there is a definite limit on file/path specifications with
the Win32 API - after 254 characters, things get really wonky ...
Yah, I'll second that. I
Have you tried taking ownership with subinacl.exe? Sometimes I find it is a bit
more effective than the GUI way - especially if run locally.
-Original Message-
From: Juned Shaikh [mailto:[EMAIL PROTECTED]
Sent: 17 March 2008 18:45
To: NT System Admin Issues
Subject: NTFS take ownership
Kurt, have you ever had to deal with teachers and writers? They seem to
love very long folder and file names, at least mine do.
Jon
On Mon, Mar 17, 2008 at 6:01 PM, Kurt Buff [EMAIL PROTECTED] wrote:
Two things that I've run across that cause this:
1) Corrupt file/directory
2) Incredibly
Harris [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2008 3:55 AM
To: NT System Admin Issues
Subject: Re: NTFS take ownership question
Kurt, have you ever had to deal with teachers and writers? They seem to love
very long folder and file names, at least mine do.
Jon
On Mon, Mar 17, 2008 at 6
On Tue, Mar 18, 2008 at 6:54 AM, Jon Harris [EMAIL PROTECTED] wrote:
Kurt, have you ever had to deal with teachers and writers? They seem to
love very long folder and file names, at least mine do.
A common cause of that here is the Internet Explorer Favorites
system. Since every bookmark is
-Original Message-
From: Ben Scott [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2008 9:12 AM
To: NT System Admin Issues
Subject: Re: NTFS take ownership question
Windows Explorer also fell apart trying to manage the files, but I
was able to work around that by moving
,
Michael B. Smith
MCSE/Exchange MVP
http://TheEssentialExchange.com
-Original Message-
From: Ben Scott [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2008 9:12 AM
To: NT System Admin Issues
Subject: Re: NTFS take ownership question
On Tue, Mar 18, 2008 at 6:54 AM, Jon Harris [EMAIL
I'd say you should run a checkdisk real quick then run admnalow on that drive!
~ Upgrade to Next Generation Antispam/Antivirus with Ninja!~
~ http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm ~
I'll match that against salesgeeks and technical writers.
Problem is, there is a definite limit on file/path specifications with
the Win32 API - after 254 characters, things get really wonky - as in,
can't open files, can't delete them, security starts getting funky,
etc.
The native Windows API
Hi,
Need help in resolving this issue on our Common/Public drive. A directory is
showing as NO permission even for Administrator. the NTFS permission security
tab is absolutely blank.
Current owner of this shows Unable to display current owner.
If I tried to take ownership - it displays
Are you connecting remotely to view security or locally. Do you have a
backup?
Regards,
Dave
-Original Message-
From: Juned Shaikh [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2008 1:45 PM
To: NT System Admin Issues
Subject: NTFS take ownership question
Hi,
Need help
Two things that I've run across that cause this:
1) Corrupt file/directory
2) Incredibly long (way longer than the usual 254 characters limit)
path specification for the file/directory
In the first case, a 'chkdsk /f' is needed, and probably a restore of
the file after that, because it might be
14 matches
Mail list logo
