• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1445
  • Last Modified:

Unable to run TcpView.exe "You don't have appropriate permissions to access"

Got TcpView.exe on our Exchange server, Windows 2003.
When trying to run I'm getting error message "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access them".

I've tried taking ownership of the folder and file but hasn't helped.
The account I'm logged in with is a Domain Admin so should have access to all the local resources.

The file is held on C:

Tried rebooting the server to refresh server on domain etc, which didn't help either.
I'm a bit stuck!

Any ideas?
0
jonhagger
Asked:
jonhagger
1 Solution
 
pinkisthenewblueCommented:
When you took ownership did you also change the permission to "full access"? (Although being a domain admin I would have thought it would be inherited from the c:\).

Also have you succesfully taken ownership? Try adding your name specifically to the perms rather than any group you are in. What about moving tcpview to your desktop and trying it from there? Bit weird tho :S
0
 
zc2Commented:
I think, the file access rights is not the issue.
Some windows' subsystem blocks you from collection information about TCP and processes.
Say, can procexp.exe work on that machine?
Does tcpvcon.exe (console version of Tcpview.exe) work?
Try to disable every antivirus/firewall monitoring software if you have any.
Check the event log, does it have any record, connected with your attempt to run Tcpview.exe ?
0
 
jonhaggerAuthor Commented:
procexp.exe wouldn't run either. Disabled AV and ran OK...

Thanks zc2
0

Featured Post

[Webinar] Improve your customer journey

A positive customer journey is important in attracting and retaining business. To improve this experience, you can use Google Maps APIs to increase checkout conversions, boost user engagement, and optimize order fulfillment. Learn how in this webinar presented by Dito.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now