Re: Trouble Launching Apps

The other environments where this app works fine, are they also using the MS client rather than Client 32? Also, does this happen for any app that resides on the Novell server? Does this app have specific local requirements, such as installation that should be performed when the server is in 'install mode'?

You can use Process Monitor (a tool from MS) to provide information on access failures due to permissions on the TS.

--
Guy Yardeni



"azevon" <azevon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:C012A121-7786-4219-A650-AFBB86652600@xxxxxxxxxxxxxxxx
Oh yes - this apps have been used for years, even currently, and even
currently on an older Win2000TS with Citrix. Seems there is something on
this new server that I have misconfigured. I only mentioned Netware because
that's what I was working with - and the *.exe's reside on the netware
server. I have installed Office and GroupWise to the TS server and this user
can access them - perhaps because they are installed locally?

"guyyardeni" wrote:

Are you sure the users have permissions on the Novell side? If they don't,
adding them to Windows Administrators group would not solve the problem.

--
Guy Yardeni



"azevon" <azevon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5CF49DEF-A184-44C8-B48C-416C1737CAA4@xxxxxxxxxxxxxxxx
> Perhaps a little more information could help find an answer...
>
> If I log onto the server (via Citrix client, MSRDP, or at the console
> itself) as admin, I get into the apps without the permissions error. > If I
> add the ordinary user into the Administrator group I still can not get
> into
> the apps. So the administrator group itslef doesn't seem to have > access
> while the Admin user itself does.
>
> "azevon" wrote:
>
>> Greetings All,
>>
>> After setting up Windows2003TS server with Citrix Metaframe 3.0, I can
>> successfully have my users connect to the server via DR or the citrix
>> client.
>> However, when they attempt to launch an app that resides on a netware
>> server
>> (I'm using the MS client for Netware, not Novell's), I get the >> following
>> error:
>>
>> "Windows cannot access the specified device, path, or file. You may >> not
>> have
>> the appropriate permissions to access the item"
>>
>> The user has rights to Remote Desktop Users. Do they need to be in >> aby
>> other groups? Does the ICA or RDP connections needs to have specific
>> permissions set? Also, if I try to publish an application, when I >> click
>> Browse to locate the *.exe file, I get no drive letters past D (when I
>> clearly have F, G, O, etc...)
>>
>> I'm getting there...
>>
>> Thanks in advance,
>>
>> -andy-



.

Relevant Pages

  • RE: Using kerberosSecurity Throws Security Exception
    ... I am experiencing this error while trying to use a Windows XP client ... application to access a web service located on a W2k3 server. ... client app on the server, ... > Account with a Custom Principal Name using SetSPN.exe utility. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Questions about Remoting, objects, threading. lease lifetime and object cleanup, and a couple of
    ... so long as the Client app is ... always refering to the same server object. ... it sets its ClassOne object to nothing and goes away. ... >>The client app at some point is going to become an ASP.Net app also. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Remoting or windows service
    ... Thanks for writing up such a decent overview of the remoting dev process ... the client and the server. ... > 2) Implement this class in the server app and say that it can be accessed ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Schannel and Session Renegotiation
    ... Schannel does not support the server sending app ... We are discussing the option of providing support for the client blowing off ...
    (microsoft.public.platformsdk.security)
  • Re: Getting Events, for Windows Service
    ... else tries to run my client app he gets an timeout error. ... The server application has a public object called logger, ... So it seems that the logger is properly instantiated and works. ...
    (microsoft.public.dotnet.framework.remoting)
Loading