# Dashboard Not Available, possible fix?

**URL:** <https://community.localwp.com/t/dashboard-not-available-possible-fix/41228>\
**Category:** Bugs\
**Tags:** windows, wp-admin\
**Created:** [February 7, 2024, 9:18am UTC](https://community.localwp.com/t/dashboard-not-available-possible-fix/41228 "2024-02-07T09:18:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AndyT](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@AndyT](https://community.localwp.com/u/AndyT)\
**Post date:** [February 7, 2024, 9:18am UTC](https://community.localwp.com/t/dashboard-not-available-possible-fix/41228/1 "2024-02-07T09:18:48Z")

</div>

WHAT?  
After new migration  
Log into admin page  
It should have gone straight to the dashboard.  
Instead, website home page shows with wordpress menu bar across the top with no dashboard option to select.

HOW?  
In Adminer (database tab in Localwp dashboard)  
I checked out xx\_usermeta and xx\_users (xx= table prefix) as I had read on the net a possible fix to this issue is to add a new admin user via the database.  
However I noticed that in xx\_usermeta for the proper admin that some of the meta\_key values that reference other tables had the the table prefix capitalised. Sure enough SQL is case sensitive.

FIX  
I went through and edited all the appropriate meta\_key values returning the table prefix to lower case, saved, and the normal admin now works as it should going straight through to the dashboard.

BUGFIX  
add a crosscheck routine after import?

---

<div class="post-metadata">

**Author:** ![ben.turner](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/ben.turner/32/5366_2.png) [@ben.turner](https://community.localwp.com/u/ben.turner)\
**Post date:** [February 8, 2024, 10:22pm UTC](https://community.localwp.com/t/dashboard-not-available-possible-fix/41228/3 "2024-02-08T22:22:04Z")

</div>

Hey @AndyT – yeah, it doesn’t happen often, but I’ve been bitten by case sensitivity related to MySQL table and column names.

This reply has more info and a link to documentation:

> [@Database tables case issue](https://community.localwp.com/t/database-tables-case-issue/19349/6):
>
> I’ve been taking a closer look at things and I think I have more information to help out with this issue. Thanks for you patience with this, and sorry for the delay – it’s been a tricky thing to zero in on. It looks like the general issue has to do with the fact that Windows’ file system is case-insensitive, while the remote, UNIX-y file system is case sensitive. Because Windows is case-insensitive, this can cause problems with MySQL when changing environments. The MySQL documentation goes int…

As I understand it, Windows is case insensitive, but issues can arise when changing to a different, unix-y environment and back.

As a general rule of thumb to allow maximum portability, I’d recommend having all the table names for your WordPress sites default to lowercase letters.

Hope that gives you some more context around this wacky issue!

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/system/32/1_2.png) [@system](https://community.localwp.com/u/system)\
**Post date:** [February 6, 2026, 9:19am UTC](https://community.localwp.com/t/dashboard-not-available-possible-fix/41228/4 "2026-02-06T09:19:42Z")

</div>

This topic was automatically closed after 729 days. New replies are no longer allowed.