remote desktop initial program cannot be started

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I want to create a desktop shortcut that will launch a Microsoft Access
database on the terminal server. (The server is Windows 2000 Server with
Terminal Services and the TS installation of Office; the client is Windows XP
or Windows 2000 running the XP version of Remote Desktop Connection.)
I create the shortcut, including (under the "Programs" tab) the full path
and filename for the database. After launching the shortcut and logging into
the server, I get a dialog box including: "The initial program cannot be
started. Please check the initial program in the client configuration."
I have checked, and tried all kinds of variations (prefixing the filename
with "msaccess", including a "start in the following folder" value, using
quotes, not using quotes, etc.) The specific error message text varies:
"The process cannot access the file because it is being used by another
process" or "The system cannot find the file specified." But the end result
is always a blank screen and no database.
If I leave out the "program" entry I can get to the desktop and launch the
application just fine. But I would really like to eliminate that extra step.
I'd even settle for getting it to launch Access, and I'll select the
database myself.
Any ideas? Is there perhaps a special syntax for filling in the "Program"
tab? Maybe something special about running Office applications?
 
Use the UNC, i.e.

\\Server\Program File\MSOffice\MsAccess.exe

Or where ever your program is.

This should work just fine.
 
I had certainly tried using that format in the "Program to start" tab. But
the shortcut on the Start menu didn't say anything about MSACCESS.EXE or
where it was -- it just showed a greyed out "Microsoft Office 2000"
application, rather than pointing to a file somewhere.
Once I searched for MSACCESS and found it buried on an obscure folder, I was
able to share that folder, refer to it with a UNC, and start the program.
Put all that in quotes, add a space and the full path to the database, and
the database opens automatically when the session starts. Success!

Interestingly, when I exited from the Access database, it would not
automatically close down the remote session, but would hang with an entirely
blank (remote) desktop. I would have to force the session to close. Another
puzzle.

But we've definitely resolved the main problem, so thanks!

David H.
 
Glad I could help

David H. said:
I had certainly tried using that format in the "Program to start" tab. But
the shortcut on the Start menu didn't say anything about MSACCESS.EXE or
where it was -- it just showed a greyed out "Microsoft Office 2000"
application, rather than pointing to a file somewhere.
Once I searched for MSACCESS and found it buried on an obscure folder, I was
able to share that folder, refer to it with a UNC, and start the program.
Put all that in quotes, add a space and the full path to the database, and
the database opens automatically when the session starts. Success!

Interestingly, when I exited from the Access database, it would not
automatically close down the remote session, but would hang with an entirely
blank (remote) desktop. I would have to force the session to close. Another
puzzle.

But we've definitely resolved the main problem, so thanks!

David H.
Click to expand...
 
Back
Top