Windows cannot access the specified file.

July 29, 2011 at 07:18:14
Specs: Windows Server 2003
Hello All,

I have a Windows Server 2003 DC running Terminals Services. Remote users connect via Remote Desktop. I have an application installed in D:\MED\BIN\med1998.exe on the server. D:\MED is shared and the users have the MED share mapped to H: I have also created a shortcut to med1998.exe where the target is H:\BIN\med1998.exe and the starts in is H:\BIN

When a user tries to launch the shortcut, they get an error message "H:\BIN\med1998.exe - Windows cannot access the specified device, path, or file. You may not have the appropriate permission to access the item."

I can see med1998.exe on H: via Windows Explorer, if I try to launch it, I get the same error message.

However, if I start a command prompt and navigate to H:\BIN and type in med1998.exe to invoke it. It launches and runs fine.

Alternatively, if I were to use Windows Explorer and launch med1998.exe from D:\MED\BIN, it also launches fine.

I know I am missing something, but I am not seeing it. Help? I would like med1998.exe to be launched through the networked drive as this would be consistent for local users and remote users.



See More: Windows cannot access the specified file.

Report •

July 29, 2011 at 12:05:11
You don't map a network drive on the same server to a location on the server.
You only use network drive mappings to a different server than the one you rdp to.

In your situation you would use a desktop shortcut for the RDP users.

Folder shared to everyone with full control?

You don't say what program this is. The program must be TS/RDP aware to operate on a RDP session.

What program is this?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's

Report •

July 29, 2011 at 13:10:08
I know I don't have to map a network drive on the same server, but there isn't a technical limitation, is there?

I want to access the application thru the network drive because in that way the users have the same shortcut they click on if they are remote, or they are in the office running they own desktop PC. By having the shortcut point to a network path, I can create the shortcut on the Desktop for Allusers, then the users will always see the same shortcut regardless of whether they are logged in remotely or they are in the office.

Yes the share was created to everyone with full control.

The program is a simple program. It opens up a screen where the users can type in their observations after an event, the data is store on a file on the server. So the code itself does not explicitly open a socket connection or anything like that, the code just does a simple file open.

I have not read anywhere that programs have to be TS/RDP aware. We have other programs that was written without any TS/RDP awareness, just a simple file open, and they work fine. Is that really the case? Have we just been lucky that our non TS/RDP aware programs work?

Anyway, it doesn't explain why the program runs fine if I invoke from a command prompt but not from a shortcut or from Windows Explorer.

Thanks. Any other ideas?

Report •
Related Solutions

Ask Question