MySQL Error after logging a call on an Opportunity

[acelmanaged]

Afternoon all,

I have today upgraded my 6.0.3 installation to 6.1.0, the upgrade was seamless with no apparent warnings. The upgradeWizard.log can be provided if needed.

Now when I go to an Opportunity into detail view it looks correct up until the point where I "Log a Call" upon adding a call the Opportunity detail view now appears with the summary at the top followed immediately by the following error:

MySQL Error 1054: Unknown column 'notes.assigned_user_id' in 'field list'

Can anyone shed any light on this please, I have tried searching Google but I find nothing on this error message only similar errors and I don't want to start hacking my files to resolve the issue.

Thanks in Advance!

[acelmanaged]

Anyone got any thoughts on this one?

[andopes]

Do you have any customization on Calls module?
Can you provide the zipped custom/modules/Calls/ folder?
Are you using CE or PRO version?

Cheers

[acelmanaged]

Thanks for the reply Andopes, there is no customisation of the Calls module, however there is of the Opportunities.
I am using the CE version.

I've zipped my entire /custom/modules folder and it should be attached.

[acelmanaged]

Hi Andopes have you managed to take a look at the customisations folder?

Is there anything else that you might need to take a look?

[acelmanaged]

Happy New Year guys and girls!

Anyone seen this before?

[IncassoPartners]

Hi there,

We also encountered a similar error message (MySQL error 1054: Unknown column 'notes.assigned_user_id' in 'field list') after upgrading the 6.0 CE to 6.1 CE as a preparation before upgrading to the Pro version. We get the error after clicking on some (not all!) Contacts and some Accounts. Upgrading process went smooth and no indication of a problem, but alas. Hope SugarCRM devs can shed some light on this. I'm contemplating doing a fresh install of 6.1 Pro (where we are upgrading to eventually) in the hope of getting rid fast of this problem.

[IncassoPartners]

Update:

After searching for the cause, I saw a reference to the Admin Repair Tool and ran it. I saw in the script that the Repair Tool generated that a column assigned_user_id would be added to the table notes, hence I suspected and hoped that would do the trick. For us it seems to have worked.

[acelmanaged]

Update:

After searching for the cause, I saw a reference to the Admin Repair Tool and ran it. I saw in the script that the Repair Tool generated that a column assigned_user_id would be added to the table notes, hence I suspected and hoped that would do the trick. For us it seems to have worked.

I re-ran the admin repair tool and this time it worked for me, my oppotunities all appear correct

Thanks IncassoPartners