Unable to resolve storage 'sequelize' [on Win7 64-bit]

[jagged3dge]

Hi,

I am using sequelize-cli to migrate new changes to my running solution. Basically, creating a workflow for pushing updates to my MySQL server hosting my test db. I have one migration file named 20141218140725-create-cafe-owner.js created using the CLI's migration:create command. I used the db:migrate command and it borked giving me this error:

D:\WampDeveloper\Websites\www.example.com\webroot\api_dev>sequelize db:migrate

Sequelize [Node: 0.10.21, CLI: 1.0.0, ORM: 2.0.0-dev9]

Loaded configuration file 'config\config.json'.
[17:24:19] Using sequelizefile ~\AppData\Roaming\npm\node_modules\sequelize-cli\lib\sequelizefile.js
[17:24:19] Starting 'db:migrate'...
[17:24:19] 'db:migrate' errored after 51 ms Unable to resolve the storage: sequelize

D:\WampDeveloper\Websites\www.example.com\webroot\api_dev>

Here's my migration file migrations/20141218140725-create-cafe-owner.js :

"use strict";
module.exports = {
  up: function(migration, DataTypes, done) {
    migration.createTable("CafeOwners", {
      id: {
        allowNull: false,
        autoIncrement: true,
        primaryKey: true,
        type: DataTypes.INTEGER
      },
      email: {
        type: DataTypes.STRING(100)
      },
      password: {
        type: DataTypes.STRING(255)
      },
      lastLogin: {
        allowNull: true,
        type: DataTypes.DATE,
      },
      createdAt: {
        allowNull: false,
        type: DataTypes.DATE
      },
      updatedAt: {
        allowNull: false,
        type: DataTypes.DATE
      },
      deletedAt: {
        allowNull: true,
        type: DataTypes.DATE
      },
    }).done(done);
  },
  down: function(migration, DataTypes, done) {
    migration.dropTable("CafeOwners").done(done);
  }
};

For the sake of completeness, here's my config/config.json file as well:

{
  "development": {
    "username": "dbuser",
    "password": "test123",
    "database": "sequelize_test",
    "host": "127.0.0.1",
    "dialect": "mysql"
  },
  "test": {
    "username": "eratest",
    "password": "eratest",
    "database": "sequelize_test",
    "host": "127.0.0.1",
    "dialect": "mysql"
  },
  "production": {
    "username": "ha61gc4e",
    "password": "317e7da87327b3f149b8da90fc1d5746",
    "database": "erasmus",
    "host": "127.0.0.1",
    "dialect": "mysql"
  }
}

I tried to dig through the source, but I am still learning production JS and it seems quite complicated to follow where it's going wrong. After trying to look up this error on Google, I found something about the Sequelize_meta table, but could not find such a table in my database.

Can anyone guide me in the right direction to alleviate this problem?

[sdepold]

which version of umzug are you using? This issue should be fixed

[jagged3dge]

I just installed the cli earlier in the morning today. Going through the internal node_modules folder for this module, I notice that umzug is showing as v1.2.2. Checking the umzug repo, it seems this is the latest build published to npm.

Is there a command-line arg or flag to see stacktrace of an error while running the CLI?

[sdepold]

Can you tell me what the result of the following commands are looking like?

mkdir tmp
cd tmp
npm install sequelize-cli sequelize mysql
node_modules/.bin/sequelize init
# please edit the config/config.json accordingly
node_modules/.bin/sequelize db:migrate

[jagged3dge]

I created a tmp folder, installed all 3 modules like you suggested. Also created a fresh database on MySQL with a dedicated user with password. Updated the config.json file under config/config.json.

Instead of creating a new migration from scratch, i just copied the file from my other project folder. I then ran the command:
node_modules\.bin\sequelize db:migrate

Here's the output:

E:\tmp>node_modules\.bin\sequelize db:migrate

Sequelize [Node: 0.10.21, CLI: 1.0.0, ORM: 2.0.0-rc3]

Loaded configuration file 'config\config.json'.
EventEmitter#success|ok is deprecated, please use promise-style instead.
[15:31:49] Using sequelizefile E:\tmp\node_modules\sequelize-cli\lib\sequelizefile.js
EventEmitter#failure|fail|error is deprecated, please use promise-style instead.

[15:31:49] Starting 'db:migrate'...
Unable to connect to database: Error: Error: ER_ACCESS_DENIED_ERROR: Access denied for user ''@'localhost' (using password: NO)

E:\tmp>

Can't seem to wrap my head around this. Here's my config.json file:

{
  "development": {
    "username": "test",
    "password": "test123",
    "database": "sequelizeclitest",
    "host": "127.0.0.1",
    "dialect": "mysql"
  },
  "test": {
    "username": "test",
    "password": "test123",
    "database": "sequelizeclitest",
    "host": "127.0.0.1",
    "dialect": "mysql"
  },
  "production": {
    "username": "test",
    "password": "test123",
    "database": "sequelizeclitest",
    "host": "127.0.0.1",
    "dialect": "mysql"
  }
}

Here's the MySQL commandline output detailing the test database sequelizeclitest and the user test:

E:\tmp>mysql -u test -p    <~ Username is 'test', as in the config.json file
Enter password: *******    <~ This is 'test123', exactly as it is in the config.json file
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 10928
Server version: 5.6.16-log MySQL Community Server (GPL)

Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| sequelizeclitest   |    <~ SHOW DATABASES lists the database as in the config.json file
+--------------------+
2 rows in set (0.00 sec)

mysql>

[sdepold]

Hmm it doesn't seem to use the password, right? I wonder if this problem is related to windows :-/

[jagged3dge]

I just tried repeating the same steps on my production server (Amazon EC2 instance with an RHEL AMI). That worked just fine. Here's the output:

[jaggz@xxxzzz temp]# node_modules/.bin/sequelize db:migrate

Sequelize [Node: 0.10.26, CLI: 1.0.0, ORM: 2.0.0-rc3]

Loaded configuration file 'config/config.json'.
Using environment 'development'.
[03:45:25] Using sequelizefile /home/git/temp/node_modules/sequelize-cli/lib/sequelizefile.js
[03:45:25] Starting 'db:migrate'...
EventEmitter#success|ok is deprecated, please use promise-style instead.
EventEmitter#failure|fail|error is deprecated, please use promise-style instead.
[03:45:25] Finished 'db:migrate' after 302 ms
[jaggz@xxxzzz temp]#

You might be right about this problem being related to Windows.

Updating the title of this issue to reflect my windows version. Just for future clarity's sake.

[sdepold]

Alright will give this a try on windows :)

[sdepold]

Thanks for the test on a Linux machine!

[jagged3dge]

Thanks for the test on a Linux machine!

Oh, don't mention it. It's the least I can do since I am not equipped to suggest a fix for this myself >.<
I really really appreciate the work you and the team are putting into developing and maintaining sequelize and its tools.Thank you so much for making the work of people like me easier!

[sdepold]

Hmm so this is interesting. I was just running the following stuff on my Win 8.1 machine which uses the github application and its shipped powershell extension (i think its actually just the normal powershell but with some additional paths). I'm running node 0.10.29, cli 1.0.0 and sequelize 2.0.0-rc3. Can you please run the following commands and let me know if you run into any issues?

mkdir tmp
cd tmp
npm install sequelize-cli sequelize mysql
.\node_modules\.bin\sequelize init
# now i changed the config/config.json accordingly
.\node_modules\.bin\sequelize model:create --name foo --attributes name:string
.\node_modules\.bin\sequelize db:migrate

all these commands ran without any issues for me and correctly created two new tables called foos and sequelizemeta.

[mariuszdev]

I have the same problem on OSX Yosemite and Mavericks.

sequelize db:migrate --coffee
Sequelize [Node: 0.10.32, CLI: 1.0.0, ORM: 2.0.0-rc3, pg: ^4.1.1]

Loaded configuration file 'config/config.json'.
Using environment 'development'.
[22:08:56] Using sequelizefile /usr/local/lib/node_modules/sequelize-cli/lib/sequelizefile.js
[22:08:56] Starting 'db:migrate'...
[22:08:56] 'db:migrate' errored after 155 ms Unable to resolve the storage: sequelize

But... ./node_modules/.bin/sequelize db:migrate --coffee works.

[jagged3dge]

This surely is getting interesting now. So it works fine on Linux (RHEL tested) & Windows 8.1, but fails on Windows7 & OSX Yosemite.

The plot thickens...

[jagged3dge]

Just tried creating a model+migration from the CLI before running db:migrate. This time, there's no error message.

E:\tmp>.\node_modules\.bin\sequelize model:create --name foo --attributes name:string

Sequelize [Node: 0.10.21, CLI: 1.0.0, ORM: 2.0.0-rc3]

Loaded configuration file 'config\config.json'.
[04:05:29] Using sequelizefile E:\tmp\node_modules\sequelize-cli\lib\sequelizefile.js
[04:05:29] Starting 'model:create'...
[04:05:29] Finished 'model:create' after 19 ms

E:\tmp>.\node_modules\.bin\sequelize db:migrate

Sequelize [Node: 0.10.21, CLI: 1.0.0, ORM: 2.0.0-rc3]

Loaded configuration file 'config\config.json'.
EventEmitter#success|ok is deprecated, please use promise-style instead.
[04:06:51] Using sequelizefile E:\tmp\node_modules\sequelize-cli\lib\sequelizefile.js
EventEmitter#failure|fail|error is deprecated, please use promise-style instead.

[04:06:51] Starting 'db:migrate'...

E:\tmp>

But there's no success message either. No tables were created.

However, the bright side is that this time it seems to have read the config.json authentication data like it always should, unlike what happened earlier with me and the copied migration file.

[sdepold]

@Pilaas you installed it globally right? Will give that setup a try