# Admin: Application error (Apache) **URL:** \ **Category:** Radiant CMS\ **Created:** [October 17, 2007, 9:17pm UTC](https://www.ruby-forum.com/t/admin-application-error-apache/117537 "2007-10-17T21:17:50Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![thechak](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/aeb1de/32.png) [@thechak](https://www.ruby-forum.com/u/thechak)\ **Post date:** [October 17, 2007, 9:17pm UTC](https://www.ruby-forum.com/t/admin-application-error-apache/117537/1 "2007-10-17T21:17:50Z")
The main part of the site works, the admin section throws this error: Application error (Apache) Change this error message for exceptions thrown outside of an action (like in Dispatcher setups or broken Ruby code) in public/500.html Here’s my dispatch.rb, cgi, fcgi: * * * ## Status: 400 Bad Request /opt/ruby/lib/ruby/gems/1.8/gems/radiant-0.6.3/vendor/rails/activerecord/lib/…/…/activesupport/lib/active\_support/dependencies.rb:404:in `to_constant_name': Anonymous modules have no name to be referenced by (ArgumentError) from /opt/ruby/lib/ruby/gems/1.8/gems/radiant-0.6.3/vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:214:in`qualified\_name\_for’ from /opt/ruby/lib/ruby/gems/1.8/gems/radiant-0.6.3/vendor/rails/activerecord/lib/…/…/activesupport/lib/active\_support/dependencies.rb:476:in `const_missing' from /opt/ruby/lib/ruby/gems/1.8/gems/rails-1.2.5/lib/dispatcher.rb:116:in`reset\_after\_dispatch’ from /opt/ruby/lib/ruby/gems/1.8/gems/rails-1.2.5/lib/dispatcher.rb:50:in `dispatch’ from ./dispatch.cgi:11 The error logs are clean. Running on Apache2 with fcgi. I checked the permissions on the tmp, but they should be right. thanks! ---
**Author:** ![thechak](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/aeb1de/32.png) [@thechak](https://www.ruby-forum.com/u/thechak)\ **Post date:** [October 19, 2007, 9:38pm UTC](https://www.ruby-forum.com/t/admin-application-error-apache/117537/2 "2007-10-19T21:38:00Z")
Turns out that I ddin’t run `rake db:migrate` immediately after installation, and tried to plug it directly into a database that was created in an earlier version. I was able to get it working after recreating my projects correctly. ---
**Author:** ![thechak](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/aeb1de/32.png) [@thechak](https://www.ruby-forum.com/u/thechak)\ **Post date:** [October 22, 2007, 1:06am UTC](https://www.ruby-forum.com/t/admin-application-error-apache/117537/3 "2007-10-22T01:06:06Z")
Dan Carey wrote: > Turns out that I ddin’t run `rake db:migrate` immediately after > installation, and tried to plug it directly into a database that was > created in an earlier version. I was able to get it working after > recreating my projects correctly. I have had the same problem… I don’t understand… You solved this issue running “rake db:migrate” on the old db or you restarded from a blank DB? I’m updating from 0.6.2 to 0.6.3 but I’d like to use the same db… ---
**Author:** ![thechak](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/aeb1de/32.png) [@thechak](https://www.ruby-forum.com/u/thechak)\ **Post date:** [October 22, 2007, 11:06am UTC](https://www.ruby-forum.com/t/admin-application-error-apache/117537/4 "2007-10-22T11:06:28Z")
Sean C. wrote: > Andrea, > > There were no database changes between 0.6.2 and 0.6.3. You should not > need to migrate. Dan was upgrading from 0.5.x. > > Sean Umh… ok… but I have the same problem… and this error occur only in /admin/pages page. I can login and navigate in all admin pages (with direct link), but everytime I click on “pages” tab I get that error… Could it be caused by an extension incompatibility? thanks Andrea ---
**Author:** ![thechak](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/aeb1de/32.png) [@thechak](https://www.ruby-forum.com/u/thechak)\ **Post date:** [October 22, 2007, 2:33am UTC](https://www.ruby-forum.com/t/admin-application-error-apache/117537/5 "2007-10-22T02:33:28Z")
Andrea O. wrote: > blank DB? I’m updating from 0.6.2 to 0.6.3 but I’d like to use the same > db… Andrea, There were no database changes between 0.6.2 and 0.6.3. You should not need to migrate. Dan was upgrading from 0.5.x. Sean ---
**Author:** ![thechak](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/aeb1de/32.png) [@thechak](https://www.ruby-forum.com/u/thechak)\ **Post date:** [October 22, 2007, 3:26pm UTC](https://www.ruby-forum.com/t/admin-application-error-apache/117537/6 "2007-10-22T15:26:34Z")
On Oct 21, 2007, at 8:32 PM, Sean C. wrote: > > issue running “rake db:migrate” on the old db or you restarded from a > > Sean > > Actually, the sessions table was added, so a migration is necessary. I haven’t followed this thread so hopefully I’m answering the question properly, but you should migrate the existing database, Andrea. ---
**Author:** ![thechak](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/aeb1de/32.png) [@thechak](https://www.ruby-forum.com/u/thechak)\ **Post date:** [October 22, 2007, 7:02pm UTC](https://www.ruby-forum.com/t/admin-application-error-apache/117537/7 "2007-10-22T19:02:31Z")
Jim G. wrote: > On Oct 21, 2007, at 8:32 PM, Sean C. wrote: > > > > issue running “rake db:migrate” on the old db or you restarded from a > > > Sean > > > Actually, the sessions table was added, so a migration is necessary. > > I haven’t followed this thread so hopefully I’m answering the > question properly, but you should migrate the existing database, Andrea. Yes, Jim is right. This is exactly what happened to me. I was upgrading from 6.2 and when I switched servers I didn’t notice that the gem had been updated. I did notice something about a sessions table in a log file somewhere but I thought it was associated with an extension. Turns out that 6.3 added the requirement of a sessions table which my previous database did not have. Definitely migrate if you have a newer version of the gem. I would try just creating a simple project using a blank database with no customizations. Then slowly add your customizations to see when it breaks. dan