show user details: mysql error 1054, unknown column name

[wivaku]

Running SugarPro 4.5.1g

When I go to Admin -> User Management I see all the users.
When I then click on one of the names, I get "empty" screen (just menu at top and on left) and the following error message:

Error retrieving User list: Query Failed:SELECT users.* FROM users where users.deleted=0 ORDER BY name ASC LIMIT 0,1::MySQL error 1054: Unknown column 'name' in 'order clause'

Indeed, there is no column "name" in the users table, only username, first_name and last_name.

Ran the various repair commands from the Repair menu (e.g. Repair Database), but that did not fix it.
Looked in the forum, found several other 1054 / name issues but they were related to other modules or situations.

How to fix? Thanks in advance.

[wivaku]

Follow up to the original post.
Interesting:
if I click on the name I get the error message, however: when I click on the little pencil instead then I see the Edit View just fine.
So it seems to be specific for the Detail View.

And to be sure, I went to Basic View + pressed Clear, so no custom view or something like that.

[Angel]

What happens if you click the "Email" or "Status" column prior to clicking on a user entry?

This might be a bug, but if it is, it must have been introduced in 4.5.1g as I have 4.5.1f and I can't get it to happen on that version. Albeit, I noticed that on my version, sorting by the Name column actually sets the order to lastname, not name, which is where the problem is coming from on your end.

[wivaku]

This indeed "solves" it. After clicking on the Status column, I can click on the name to get the detailed view.
Thanks for coming up with this workaround!

[GameboyRMH]

Whoa, I just had the EXACT SAME PROBLEM in SugarCRM 5 beta 2.

http://www.sugarcrm.com/forums/showthread.php?t=27735

Same thing fixed it too, this thread was a life-saver

[kuske]

It seems to be the problem where in config.php the line

'db_type' => 'mysql',

is missing or incorrect.
Only if this value is set, the filed "name" will be calculated correctly.

[wivaku]

Confirmed:
- this line was not in my config.php
- after adding this line, the issue disappeared

edit: I spoke too soon...

my config.php did have db_type in there:
'dbconfig' => array (
'db_host_name' => 'localhost',
...
'db_type' => 'mysql',
),

However, at the moment I am unable to reproduce the issue. Will look into it later.

[kuske]

ok, fine.

this error occurs often in the last time. how did you install ?
perhaps anyone knows why this unhappy line is empty? I did not find a reason till now.

hk

[wivaku]

the line was in there after all. Sorry about confirming first the line was missing.
My environment: SUSE (LAMP), ssh access to server, SugarPro, started with 4.0, using regular Sugar patch process, now at 4.5.1g.

[Angel]

Chances are that this is a bug. Like I said in my previous post, I can't duplicate it on 4.5.1f, so it seems that it was likely introduced in patch g, especially given the fact it also happens in 5.0.

I wouldn't be surprised if it is a bug, as there are a couple of ways to generate the same error message in other modules and they are the result of bugs.

I haven't had a chance to upgrade my test system to the latest patch yet, but when I do, I'll see if I can dupe the problem and apply the same fix that I applied for other areas, then I'll share the fixed file.

EDIT: I got a few free minutes and managed to upgrade to 4.5.1h. I cannot duplicate the error, which would seem to indicate the problem was either fixed (haven't reviewed release notes yet) or the problem lies elsewhere.

Does your system continue to experience the problem after upgrading to 4.5.1h?