Archives of the TeradataForum

Message Posted: Thu, 25 Mar 2004 @ 23:07:03 GMT

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

Teradata Manager 6.x client will not connect to a TM server or RDBMS (nor allow you to do anything else but grind your teeth) if the username you specified when you first bring up Teradata Manager (formerly called the Executive) has no profiles for which it is authorized on the system you specified in the Logon Information dialog box. You may have specified the wrong username or systemname ... or your workmates in the office may have de-authorized your userid! Just joking. (You did say you were doing this from home though. You haven't been fired, have you? :-))

Verify that the "xxx" username you specified is indeed authorized to run a profile and that the profile is enabled by querying DBCMNGR.TMGRProfileUser & DBCMNGR.TMGRProfile on the database you want to manage. If not authorized, that is your problem, and Teradata Manager is running by design as documented in Chapter 4 Step 4 (Restricting User Access with Profiles) of the Teradata Manager User Guide.

Once you enter Teradata Manager (Executive), the DBSName, ServerName, Username and other information are saved on the client PC in registry entries under "My Computer\HKEY_CURRENT_USER\Software\NCR\TeradataManager\06.00.00.00\Preferences\tdclient" and "...TMSystems". Future starts of TM Executive will automatically use these saved values for attempted logons/connections. (You can regedit these directories to see/modify these values.)

This type of problem situation is likely one reason that NCR defaults the DEFAULT profile as being accessible to all users, but it sounds like you have already removed that authorization. (So have we.)

Best wishes.

Steve Maynard
EDS - BellSouth Account
Midrange Database Support

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