HEY!  That solved the problem!  Thanks so much Jun  :-)

It's interesting that this section of the stock config file refers correctly to 
the stock Users table, except for including references to this column that 
isn't part of the table.
--
Kendric Beachey



-----Original Message-----
From: Zhang,Jun [mailto:jhzh...@mdanderson.org] 
Sent: Friday, March 02, 2012 11:49 AM
To: Beachey, Kendric; rt-users@lists.bestpractical.com
Subject: RE: Transitory error on login (LDAP against AD)

I got the same error and I understand this must be minors, since my AD user is 
authenticated. The Users table in my rt4 database doesn't have a column called 
'disable'. Removing the d_field line in RT_SiteConfig.pm and the error no 
longer show up. Looks like a bug.

Jun

-----Original Message-----
From: rt-users-boun...@lists.bestpractical.com 
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Beachey, Kendric
Sent: Friday, March 02, 2012 10:59 AM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Transitory error on login (LDAP against AD)

Hi all,

We're running RT 3.6.5, authenticating against AD.  When people login, they get 
this error...

-------------------------------------------
error:          DBD::mysql::db selectall_hashref failed: Unknown column 
'disabled' in 'field list' at 
/usr/local/share/request-tracker3.6/lib/RT/Authen/ExternalAuth/DBI.pm line 279.
context:
...
275:    # DBI->trace(1,'/tmp/dbi.log');
276:
277:    # Get DBI Object, do the query, disconnect
278:    my $dbh = _GetBoundDBIObj($config);
279:    my $results_hashref = 
$dbh->selectall_hashref($query,$u_field,{},@bind_params);
280:    $dbh->disconnect();
281:
282:    my $num_of_results = scalar keys %$results_hashref;
283:
...
code stack:     
/usr/local/share/request-tracker3.6/lib/RT/Authen/ExternalAuth/DBI.pm:279
/usr/local/share/request-tracker3.6/lib/RT/Authen/ExternalAuth.pm:403
/usr/local/share/request-tracker3.6/lib/RT/Authen/ExternalAuth.pm:244
/usr/local/share/request-tracker3.6/lib/RT/Authen/ExternalAuth.pm:200
/usr/share/request-tracker3.6/html/Callbacks/ExternalAuth/autohandler/Auth:25
/usr/share/request-tracker3.6/html/Elements/Callback:85
/usr/share/request-tracker3.6/html/autohandler:240
-------------------------------------------

...but the fun part is, if you just hit "refresh" on your browser, everything 
is fine.  You're logged in and ready to go.

Is this a bug in part of the system that got solved in a later version, or do I 
have something configured in a slightly wrong way?  To this point I've just 
told people to refresh the page and move on with life, but if it is something I 
can fix easily I'd like to do so.

If more info is needed to be able to tell what's happening, I can provide it, 
just let me know.  Thanks for any help you can give!
--
Kendric Beachey



This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient. If you are not the intended recipient, please be 
aware that any disclosure, copying, distribution or use of this e-mail or any 
attachment is prohibited. If you have received this e-mail in error, please 
contact the sender and delete all copies.

Thank you for your cooperation.

--------
RT Training Sessions (http://bestpractical.com/services/training.html)
* Boston  March 5 & 6, 2012


--------
RT Training Sessions (http://bestpractical.com/services/training.html)
* Boston  March 5 & 6, 2012

Reply via email to