Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

WHD upgrade 12.5.2 to 12.6 failedusing mysql

mst

Experts,

Looks like using mysql 5.6 on Centos WHD failed:

Next exception:SQL State:42S02 -- error code: 1146 -- msg: Table 'webhelpdesk.api_key' doesn't exist

any thoughts?

Find more posts tagged with

Accepted answers

All comments

pabely

Not sure if this your exact issue but are you aware of the following: Upgrading to Web Help Desk 12.6 for MySQL users - SolarWinds Worldwide, LLC. Help and Support

mst

1st part of that link totally broke my mysql db and schema so dont use it at all.

But 2nd part of that link using the update script upgrade went well.

How can I replace starting posgress with mysql? I dont even have postgress. Is there a way to replace that in whd? thank you

pabely

The workaround has nothing to do with PostgreSQL based database systems, it only applies to MySQL. Any PostgreSQL based WHD will not have this upgrade issue.

typhoon87

At this point since they are doing the upgrade they have maintenance should probably just open a support ticket.

adamc

well that's not quite true- I have migrated my database from mysql to postgres and I am getting that exact error.

I'm going to look into it further and will reply if I get it fixed

adamc

ok found the problem- I have been building and discarding a bunch of VMs to help with this and apparently I had built this one with

jdbc v8 which is not compatible.

Support sent me this-

https://dev.mysql.com/get/Downloads/Connector-J/mysql-connector-java-5.1.47.zip

which worked- so while the error is specific to MySQL setups, it did affect me on Postgres. You could also argue that I didn't know what I was doing, which is also fair.

adamc

that's not 100% correct,