Calendar Error 3.2 Upgrade

shawnmiller77 wrote on Sunday, March 14, 2010:

I installed OpenEMR version 3.2 on a test Windows 2003 Server.  Installation worked great!  OpenEMR functioning properly with no issues.

I restored my data from my OpenEMR 3.1.0 Windows 2003 Server.  I copied over the following files to restore my data.
edi, era, documents, letter_templates, mysql/data

I am able to log into the 3.2 OpenEMR server and view patient data.  When I log in I get the following calendar error.

ERROR: query failed: select distinct id, username, lname, fname, authorized, info, facility from users where username != ‘’ and active = 1 and id like ‘%’ AND authorized = 1 AND calendar = 1 ORDER BY lname, fname

Error: Unknown column ‘calendar’ in ‘where clause’

Is their something I need to do in order restore my 3.1.0 data to a 3.2 version of OpenEMR to get my calendar working again?  I am using Radio Button view.  Also, the calendar worked fine in 3.2 before I restored my data.

Thanks
Shawn

bradymiller wrote on Sunday, March 14, 2010:

hey,

You need to upgrade your sql database:
http://localhost/openemr/sql_upgrade.php

Also good idea to upgrade the acl controls:
http://localhost/openemr/acl_upgrade.php

You upgrade method should work. To be safe, I recommend you turn off your mysql server while copying the mysql/data files. If problems then could go the documented upgrade route (although i see no issues with your current upgrade procedure):
http://www.openmedsoftware.org/wiki/Linux_Upgrade_3.1.0_to_3.2.0

-brady

bradymiller wrote on Sunday, March 14, 2010:

oops,
meant this link above:
http://www.openmedsoftware.org/wiki/Windows_Upgrade_3.1.0_to_3.2.0
-brady

lar8 wrote on Wednesday, July 07, 2010:

Have the same issue but after install the patch. 

ERROR: query failed: select distinct id, username, lname, fname, authorized, info, facility from users where username != ‘’ and active = 1 and id like ‘%’ AND authorized = 1 AND calendar = 1 ORDER BY lname, fname

Error: Unknown column ‘calendar’ in ‘where clause’

Tried the solutions posted here but no luck.  Thanks in advance.

bradymiller wrote on Wednesday, July 07, 2010:

hey,
What version of openemr are your upgrading from?
What operating system are you using?
-brady

lar8 wrote on Wednesday, July 07, 2010:

It’s 3.0.2 running on Windows 7 Ultimate with an HP Notebook 64bit 4GB Ram 320HDD.  This issue happen after the installation of the patch 6 for version 3.0.2.  Thanks for your quick answer.

Luis

bradymiller wrote on Thursday, July 08, 2010:

hey,
I’m confused on your versions. Are you using version  3.2.0? (There is no patch for 3.0.2; in fact 3.0.2 does not exist)
-brady

lar8 wrote on Thursday, July 08, 2010:

I’m running this package OpenEMR-XAMPP-3.2.0 and after further reading, I found a patch on the following website: http://www.openmedsoftware.org/wiki/OpenEMR_Patches  for version 3.2.0 it’s patch 6 of 6/28/2010.  I installed the patch and the calendar stopped working with the error posted.  Sorry the version was wrong.

bradymiller wrote on Thursday, July 08, 2010:

hey,
I’ll do a sanity check of the patch on xampp-3.2.0 this evening, and get back to you.
thanks,
-brady

bradymiller wrote on Thursday, July 08, 2010:

LAr8,
One more quick question. What version do you see in the openemr login screen (top-left)?
-brady

lar8 wrote on Thursday, July 08, 2010:

OpenEMR v3.2.0

lar8 wrote on Friday, July 09, 2010:

Hi Brady!

I did a test on another machine and did a clean install of the OpenEMR XAMPP package v3.2.0.  Did a backup of the MySQL database from the system with the issue and then restore to the new installation using the MySQL backup tool from WebYog GUI.  Did not work, the error still there.  Any thoughts?

Luis

bradymiller wrote on Friday, July 09, 2010:

hey,

Sorry, wasn’t able to do the sanity test last night. In your test, did you use the patch at all on the clean install? From your explanation it sounds like the issue is there even without the patch. I’m guessing that your mysql database wasn’t upgraded correctly; I’m highly suspicious of this because the ‘calendar’ column was added in 3.2 or 3.1, so if your using a previous version with correctly upgrading the database then you’ll be missing this column and will throw the above error.

Is the your openemr mysql database from an earlier OpenEMR version? If so, did you run the sql_upgrade.php script as described above during your upgrade?

-brady

lar8 wrote on Friday, July 09, 2010:

I didnt install the patch on this one, just the package.  The openemr mysql database is from current version.  It was a clean install two months ago. We read about the patch and installed a few days ago, then it broke.   When I found this post I did ran the script just to try something that can fix the issue.  But did work either.  I will try the script again on the new machine and see.  I’ll keep you posted.

lar8 wrote on Friday, July 09, 2010:

Hi Brady!

After running the following script http://localhost/openemr/sql_upgrade.php on my test system leaving everything to default it work.  I have the calendar.  Thanks

Luis