4.5.0d Can Create Lead assigned to others

[kirkland]

Since upgrading to 4.5.0d from 4.2.1a, I can no longer create a new lead and assign it to another person.

If I create the lead and assign it to myself, it works fine. If I then try to assign it someone else, I just get a blank response page and no errors in the sugarcrm.log.

If I create a new lead and immediately assign it to another person, it also gives me a blank page.

Note that when the blank page error occurs, the lead is also not created/saved.

This is not turning out to be a very happy upgrade since we're now experiencing:

1) Sugar theme does not layout correctly, forcing us to use Sugar Classic for now.
2) Documents cannot be downloaded via IE, but can via Firefox.
3) New leads cannot be created and assigned to others. I fear for what else is wrong....

Thanks for any help as there's nothing like angry sales people to keep you tense!

[kpit]

Are you using the pecl json extension? If so you must use version 1.1.1 as the latest does not work with SugarCRM. I was getting this blank page problem with that plugin.

Another possability is PHP is running out of memory. Check your setting in your php.ini file.

[kirkland]

I'm not even sure what "pecl json extension" means. Was that a typo for "perl"? Either way, I didn't do anything besides upgrade from 4.2.1a to 4.5.0d and this problem arose.

It seems unlikely assigning a lead to another person would be memory intensive. The site continues to run and does lots of queries. It's only when assigning the lead to another person. I don't see anything in the sugarcrm logs either. If I assign it to myself, the lead is created fine.

[kpit]

pecl is customized extensions for php. json extention is written in c/c++ and is an extension of php. this is not required for sugar to work but if you have a busy server this extension enhances performance.

PHP when it hits its memory limit just stops and the web server returns a blank page. you may be able to use some areas but if another requires more memory you may find that you get a blank page.

Other considerations is the max packet size for mysql. With version 4.5 this is espeially a problem because of the multi-byte character support. Data can expand up to 3 times the size before using multi-byte characters.

[kirkland]

There's no way an error that occurs repeatedly is a memory error. Why would it take more memory to save a lead assigned to someone else than it is to save it to yourself? Why can I save the lead assigned to myself, but then try to change it and have this error -- every single time? Yet I can do lots of far more intense queries that have to produce real results.

This is not a memory issue.

There's some other bug associated with assigning the lead to someone else, perhaps related to the email notification that goes out when a lead is assigned to someone else.

[kirkland]

Here's a debug trace when I change only the "Assigned to" field of a Lead and then click Save:

Tue 17 Oct 2006 08:34:16 AM PDT,276 [4553] INFO SugarCRM - Connect:Resource id #155
Tue 17 Oct 2006 08:34:16 AM PDT,276 [4553] INFO SugarCRM - Query:SELECT id, name, symbol, conversion_rate FROM currencies WHERE status = 'Active' and deleted = 0
Tue 17 Oct 2006 08:34:16 AM PDT,277 [4553] INFO SugarCRM - Query Execution Time:0.00020600000000004
Tue 17 Oct 2006 08:34:16 AM PDT,280 [4553] INFO SugarCRM - Query:SELECT category, name, value FROM config
Tue 17 Oct 2006 08:34:16 AM PDT,280 [4553] INFO SugarCRM - Query Execution Time:0.000365
Tue 17 Oct 2006 08:34:16 AM PDT,288 [4553] DEBUG SugarCRM - ****Starting Application for session 6358cf328ea1a6d7695965438a9b6d3c
Tue 17 Oct 2006 08:34:16 AM PDT,288 [4553] DEBUG SugarCRM - We have an authenticated user id: ae566eec-28df-52a7-0aae-4235ff2d5d5f
Tue 17 Oct 2006 08:34:16 AM PDT,288 [4553] DEBUG SugarCRM - We have an authenticated user id: ae566eec-28df-52a7-0aae-4235ff2d5d5f
Tue 17 Oct 2006 08:34:16 AM PDT,289 [4553] DEBUG SugarCRM - Retrieve User : SELECT users.* FROM users WHERE users.id = 'ae566eec-28df-52a7-0aae-4235ff2d5d5f'
Tue 17 Oct 2006 08:34:16 AM PDT,289 [4553] DEBUG SugarCRM - Limit Query:SELECT users.* FROM users WHERE users.id = 'ae566eec-28df-52a7-0aae-4235ff2d5d5f' Start: 0 count: 1
Tue 17 Oct 2006 08:34:16 AM PDT,289 [4553] INFO SugarCRM - Query:SELECT users.* FROM users WHERE users.id = 'ae566eec-28df-52a7-0aae-4235ff2d5d5f' LIMIT 0,1
Tue 17 Oct 2006 08:34:16 AM PDT,290 [4553] INFO SugarCRM - Query Execution Time:0.00037300000000001
Tue 17 Oct 2006 08:34:16 AM PDT,294 [4553] INFO SugarCRM - Query:SELECT u1.first_name, u1.last_name from users u1, users u2 where u1.id = u2.reports_to_id AND u2.id = 'ae566eec-28df-52a7-0aae-4235ff2d5d5f' and u1.deleted=0
Tue 17 Oct 2006 08:34:16 AM PDT,294 [4553] INFO SugarCRM - Query Execution Time:0.00019200000000003
Tue 17 Oct 2006 08:34:16 AM PDT,294 [4553] DEBUG SugarCRM - additional detail query results:
Tue 17 Oct 2006 08:34:16 AM PDT,295 [4553] DEBUG SugarCRM - Current user is: first.person
Tue 17 Oct 2006 08:34:16 AM PDT,295 [4553] DEBUG SugarCRM - Current user is: first.person
Tue 17 Oct 2006 08:34:16 AM PDT,296 [4553] DEBUG SugarCRM - array (
'module' => 'Leads',
'record' => 'bd3f0c7f-a482-904a-e87c-4533c3d303fe',
'action' => 'Save',
'contact_role' => '',
'inbound_email_id' => '',
'email_id' => '',
'start' => '',
'type' => '',
'return_module' => 'Leads',
'return_id' => 'bd3f0c7f-a482-904a-e87c-4533c3d303fe',
'return_action' => 'DetailView',
'prospect_id' => '',
'account_id' => '',
'contact_id' => '',
'opportunity_id' => '',
'button' => ' Save ',
'lead_source' => 'Phone In',
'status' => 'New',
'lead_source_description' => '',
'status_description' => '',
'refered_by' => '',
'salutation' => '',
'first_name' => 'Test',
'phone_work' => '',
'last_name' => 'Test3',
'phone_mobile' => '',
'phone_home' => '',
'account_name' => 'Test',
'phone_other' => '',
'phone_fax' => '',
'title' => '',
'email1' => '',
'department' => '',
'email2' => '',
'assigned_user_name' => 'someone.else',
'assigned_user_id' => '75aa26a8-f369-b8d2-e684-4236000e9e8f',
'invalid_email' => '0',
'primary_address_street' => '',
'alt_address_street' => '',
'primary_address_city' => '',
'alt_address_city' => '',
'primary_address_state' => '',
'alt_address_state' => '',
'primary_address_postalcode' => '',
'alt_address_postalcode' => '',
'primary_address_country' => '',
'alt_address_country' => '',
'description' => 'here's so quick info',
'showLeftCol' => 'true',
'e' => 'first.person@host.com',
'ck_login_language_20' => 'en_us',
'ck_login_theme_20' => 'SugarClassic',
'ck_login_id_20' => 'ae566eec-28df-52a7-0aae-4235ff2d5d5f',
'Accounts_divs' => 'history_v=inline#',
'Sugar_color_style' => 'sugar',
'Calls_divs' => 'users_v=inline#',
'ck_record' => 'true',
'ck_shortcuts' => 'true',
'ck_lastview' => 'true',
'PHPSESSID' => '6358cf328ea1a6d7695965438a9b6d3c',
'Leads_divs' => 'activities_v=#',
'Accounts_sp_tab' => 'All',
)
Tue 17 Oct 2006 08:34:16 AM PDT,296 [4553] INFO SugarCRM - In module: Leads -- About to take action Save
Tue 17 Oct 2006 08:34:16 AM PDT,296 [4553] DEBUG SugarCRM - in module Leads -- in Save
Tue 17 Oct 2006 08:34:16 AM PDT,297 [4553] DEBUG SugarCRM -
(more next)

[kirkland]

I have tracked it down to failing on the call:

$notify_mail->prepForOutbound();

inside the code data/SugarBean.php function create_notification_email($notify_user)

The debug statement before it works, but the debug statement after (I added these debug statements) doesn't come out, so that's where it's likely dying.

[kirkland]

By essentially not doing the code in include/SugarPHPMailer.php, function prepForOutbound(), I can assign leads like before.

What does that code do that's necessary for this to work. Right now, I'm not doing it at all because it traps. Is there something in that code that implies a configuration error or the like? It appears to be a bunch of code for UTF8 charset conversions, something that's not really even needed in our world (right now) because we're all simple English needs here.

I found that it's dying on the line:

$this->From = $locale->translateCharsetMIME($this->From, 'UTF-8', $locale->getPrecedentPreference('default_email_charset') );

The conversions translateCharset work okay on Body, AltBody and Subject, but then fails with the translateCharsetMIME call when it tries to do the From. By the way, my debug showed that the From is set to "root@localhost" before it dies. Note that we are set so that notifications are supposed to appear to be from the original party per the setup in Admin "Send notification from assigning user's e-mail address?" being checked.

[dsga1]

Hello -- we are seeing exact same problem but in assigning TASK to other sugar user from ACCOUNT view. The next sugar page is blank.

After we have upgraded to 4.50c (and applied 4.5.0d), we are seeing this frequently -- example: assigning TASK to different user from CASE.

Bad stuff -- very frustrating. You don't realize how much to use something until you lose it. Unfortunately, my users have become frustrated beyond belief with this problem and are now not using sugar.

--GA

Since upgrading to 4.5.0d from 4.2.1a, I can no longer create a new lead and assign it to another person.

If I create the lead and assign it to myself, it works fine. If I then try to assign it someone else, I just get a blank response page and no errors in the sugarcrm.log.

If I create a new lead and immediately assign it to another person, it also gives me a blank page.

Note that when the blank page error occurs, the lead is also not created/saved.

....

[kirkland]

Did you try what I posted above?

You might want to just comment out this line (put two slashes in front: //)

$notify_mail->prepForOutbound();

This is in the code data/SugarBean.php function create_notification_email($notify_user).

Of course, if you need the UTF normalization (or whatever it is that takes place therein), you might still be out of luck, but if you don't, it seemed to resolve things here. Good luck.