Toad World® Forums

Why does the login screen take at least 30 mins to display on TOAD 10.6?


#1

I’ve recently upgraded to 10.6 and have a new laptop. When working from home, on several occassions, it takes 30 mins or more after the “ribbit” for the login screen to show, to be able to log in. In addition, once connected, if I try to start a new session, the same condition occurs. I have also noticed that when trying to connect to another session, I’m not able to see the “login screen” with previously utilized user names and environments.

I have used TOAD for several years, but have never had this condition on my earlier versions of TOAD (9.7). Any ideas?

I would greatly appreciate any insights.

Thanks.


#2

One of the things you can check:

What is the name of your virusscanner? If it is McAfee, then configure it in
such a way that it does not scan the Toad directories.

Groetjes,
Wim

On Fri, Apr 1, 2011 at 06:59, andre.l.cheese_781
wrote:

Message from: andre.l.cheese_781

I’ve recently upgraded to 10.6 and have a new laptop. When working
from home, on several occassions, it takes 30 mins or more after the
“ribbit” for the login screen to show, to be able to log
in. In addition, once connected, if I try to start a new session, the
same condition occurs. I have also noticed that when trying to connect to
another session, I’m not able to see the “login screen”
with previously utilized user names and environments.

I have used TOAD for several years, but have never had this condition on
my earlier versions of TOAD (9.7).  Any ideas?  

I would greatly appreciate any insights.

Thanks. 

_______________________________________

Historical Messages

Author: andre.l.cheese_781
Date: Thu Mar 31 21:59:54 PDT 2011
I’ve recently upgraded to 10.6 and have a new laptop. When working
from home, on several occassions, it takes 30 mins or more after the
“ribbit” for the login screen to show, to be able to log
in. In addition, once connected, if I try to start a new session, the
same condition occurs. I have also noticed that when trying to connect to
another session, I’m not able to see the “login screen”
with previously utilized user names and environments.

I have used TOAD for several years, but have never had this condition on
my earlier versions of TOAD (9.7).  Any ideas?  

I would greatly appreciate any insights.

Thanks. 
__
_______________________________________

#3

Morning Andre,

are you by any chance running a virus scanner? There have been problems
with MacAfee (If I remember correctly) always scanning the Toad Exe
which can seriously delay startup times. They have been asked by Quest
to white list the file, but as yet, I’m not sure that it has been done.

There’s a small thread here:
http://toadfororacle.com/thread.jspa?threadID=24825&tstart=650

Also, is it possible that your database has lost it’s system stats?
Check out Bert’s blog here:
http://toadworld.com/BLOGS/tabid/67/EntryId/624/Go-Toad-Go.aspx

Cheers,
Norm. [TeamT]

Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else.

We have checked this email and its attachments for viruses. But you should still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes.

If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk


#4

Both are excellent replies (and exactly what I would have said – so thanks
for beating me to it J ). In addition, on the main menu under help you can also
run the toad advisor to see if it turns up anything. But my money is on the
first two already pointed out J


#5

There was later information on the McAfee issue:

http://tech.groups.yahoo.com/group/toad/message/54305

and I’m seeking still later info today.

They were able to reproduce the problem and fix it, and released a .dat file
which resolved it according to tests which we did. The .dat version which
resolved it was 6222. I see they are up to 6302:

http://www.mcafee.com/apps/downloads/security-updates/security-updates.aspx


#6

To close the loop on this for historical reasons, they resurrected the
KnowledgeBase article:

https://kc.mcafee.com/corporate/index?page=content&id=KB70932

however it’s really no longer necessary except for documentation purposes,
because all their newer .dat files since then are reported to have fixed the
issue.