I am having a problem with TOAD in which about 30 seconds, the application becomes unresponsive. Other applications that I am using work fine, but TOAD just hangs. I tried to “Reset to a clean set of user files from the base installation”, but it complained about files being read only.
I then went to my TOAD User Files folder and I deleted all of the INI files. (Created a backup just in case). I was able to start TOAD, but I don’t see that my settings have been removed nor has the hanging problem gone away. Please understand, it can hang without running any SQL, I can be just looking at the screen and when I attempt to scroll through a script it won’t allow me to grab the scroll bar.
I also have an issue in which all of the Code Snippets are gone. I am not sure if this related or not.
I have been living with the problem for several upgrades and am just to the point now where the hanging is seriously impacting my work. Is there some process in TOAD which polls? I know session browser does and I do not have than up.
Is there something else I can do return TOAD back to stop the hanging? Maybe re-install?
***** This email is from an external sender outside of the CenterPoint Energy network. Be cautious about clicking links or opening attachments from unknown sources. *****
There are background threads which update Toad’s settings periodically; however, those shouldn’t hang the main Toad thread. Your error message above is interesting. Usually, Windows identifies users by username, not IDs. Are you, perhaps, connected via a terminal service (like Microsoft, Citrix, etc) or is this your own local machine and you log in as “00911877”? If you open up Task Manager, are there any other Toad processes running in the background? Perhaps another Toad process is locking the files needed by the one you’re working with.
Seems, You have some problems with directory/file permissions on those location.
I think you're definitely right, Damir. It's just a matter of what might be causing those permissions issues. It's also possible, David, that your network administrators may have set certain group policies that could restrict permissions to some of these folders. If neither of our suggestions work, it may be a good idea to check with your networking group to see if any restrictions were placed on those folders.
