Archives of the TeradataForum

Message Posted: Tue, 12 Jun 2007 @ 10:54:57 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

One possibility (and please tread carefully) is some remnants in the Windows\System32 directory. Obviously there could be other changes which might not be immediately visible to you (e.g. someone updated the DNS or hosts files at around the same time).

I don't know how your web server and the interactive execution sets up your PATH variables, but I (and some others) have experienced this problem when upgrading TTU.

The issue is that when you upgrade you are supposed to remove the old TTU. In some cases, some DLL's in the Windows\System32 directory are not removed.

The new TTU may pick up these old DLL's. If it does, the CLI application (in this case bteq) will hang.

Check your windows\system32 directory for the following files:

     * tdusr32.dll
     * terasso.dll
     * wincli32.dll

MOVE (don't delete) them to another directory (e.g. c:\temp) and see if this helps (you might need to restart). If this solves your problems (and doesn't create any new ones) then you can delete the files when you feel comfortable.

As I said, I don't know if this will help, but it solved a problem of bteq (and other applications) hanging for me...

Good Luck

Glenn Mc

	<Prev	Next>		<<First	<Prev	Next>	Last>>