Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Error 1044 – Trying To Do Backup Table As Sql Dump

forums forums SQLyog Using SQLyog Error 1044 – Trying To Do Backup Table As Sql Dump

  • This topic is empty.
Viewing 1 reply thread
  • Author
    Posts
    • #11601
      a_edwall
      Member

      I am suddenly experiencing Error 1044 when I try to Backup Table As SQL Dump. It gets about halfway through the dump, according to the progress bar, then stops. I have no idea why or what to do about it. Can anyone help? Thank you.

      Error message: Error No. 1044. Access denied for user 'allen'@localhost' to database 'socnet'.

      This used to work and I have no idea what changed. I have not changed any users since it used to work

      I have Enterprise version v8.1 – registered user.

    • #29357
      peterlaursen
      Participant

      I think you created a ticket too. Actually the ticket had one more question (about 'access denied' to mysql.user table). I have replied in the ticket this:

      Quote:
      1)

      When you execute Backup Table As SQL Dump' it seems that you are 'allen'@localhost' user.

      However when you execute 'select user, host from mysql.user' it seems that you are 'timemapu_shemp'@'localhost' user and when managing privileges.

      Can you explain why two users are involved?

      2)

      “It gets about halfway through the dump, according to the progress bar, then stops.”

      Is anything written to the file at all except for initial SET statements? Just open it in an editor and see what it reads like.

      3)

      If it worked before with same user(s) then something has changed server-side.

      One possibility is that some mistake happened during a server upgrade or that the `mysql` database on the server has simply corrupted.

      Is this server a server managed by somebody in your your organisation or is it a hosted server? I am afraid you will need to ask the appropriate server admin to look into this. Only a person with full admin privilege can sort it out. What you experience with SQLyog would happen with any client. Problem is server-side, not client-side.

      Please decide if you want to communciate in the ticket or here. It gets confusing if the same discussion goes in parallel two different places.

Viewing 1 reply thread
  • You must be logged in to reply to this topic.