[THIN] Re: "You do not have access to logon to this session."
- From: "Jim Kenzig http://thin.net" <jimkenz@xxxxxxxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Mon, 30 Aug 2004 10:30:48 -0400
Is that info stored in the LHC? Would a dsmaint -recreatelhc work?
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Schneider, Chad M
Sent: Monday, August 30, 2004 10:13 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: "You do not have access to logon to this session."
That is what I was thinking as well....
_____
From: Parker, Dennis [mailto:Dennis.Parker@xxxxxxxxxx]
Sent: Monday, August 30, 2004 9:03 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: "You do not have access to logon to this session."
I'm not certain on this, but it sounds like it is attempting to
reconnect to a disconnected session rather than open a new connection.
Is this the expected situation? I don't know why it's not providing a
new session id for each connection, but I would follow down that path, I
think.
Probably not much help, but maybe it will spark something in someone
else...
Dennis Parker, MCSE, CCA
Senior Systems Analyst
Fiserv EFT/CNS
This e-mail is confidential and may well be legally privileged. If you
have received it in error, you are on notice of its status. Please
notify us immediately by reply e-mail and then delete this message from
your system. Please do not copy it or use it for any purposes, or
disclose its contents to any other person. To do so could violate
state and Federal privacy laws.
Thank you for your cooperation. Please contact me if you need
assistance.
_____
From: Schneider, Chad M [mailto:CMSchneider@xxxxxxxxx]
Sent: Monday, August 30, 2004 6:24 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] "You do not have access to logon to this session."
I have 3 servers, which have been in use, as is, for @ 3 years.
They were member servers of a domain, and recently moved to our AD
domain, as part of our ad conversion project. Since they have been
moved, and renamed, the published applications running on them, not all,
but some, give the error "You do not have access to logon to this
session". When this happens, it happens for everyone, users, admins.,
AD domain admins, everyone. I have tried removing app. Rights,
readding, limiting to a single server, deleting the app. And creating a
new of the same name. The last item, seems to work, but only temporary.
I am pulling out my hair, of course, they only notice this at shift
change, which if middle of the night, so I have been woke up every night
for the past week.
Any help is appreciated.
Other related posts:
