Hello everyone,
we want to install App Volumes on a fresh Windows Server 2016 Standard (latest patch level).
Remote database is a Windows SQL Server 2012 Standard (SP4, latest patch level), SQL authentication is active (user has db_creator rights).
The installation aborts at this state everytime:
create_db_config_file.log:
I checked this forum and other sites, with no luck.
Can anyone help with this issue?
Alright, I found the solution ... guess what?
The database credentials didn't work for App Volumes.
Maybe there were too complex or some special characters are not allowed (which is not documented or reported by the installer).
We changed the credentials to a simple style and it worked.
VMware should document or report this during the GUI installer!
svmanager_setup.log
Running as test.INTERNAL on Server
#### Rails environment set to production for action production
#### Ruby version:
The command "ruby" is either misspelled or
could not be found.
Excluding Oracle
Excluding development_postgres
BUNDLE_WITHOUT is now development_postgres oracle development test
Creating link
Connection created for C:\ProgramData\CloudVolumes\ruby <<===>> C:\Program Files (x86)\CloudVolumes\Manager\ruby
HOME is required for rb-readline and be ASCII or UTF-8
HOME was
HOME now C:\ProgramData\CloudVolumes\ruby
PATH C:\ProgramData\CloudVolumes\ruby\bin;C:\Program Files (x86)\CloudVolumes\Manager\ruby\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\
#### Copy any dependencies from dependencies\windows
The system can not find the stated file.
File not found 0 file (s) copied
#### Create log folders
ERROR: While executing gem ... (Gem::InstallError)
gem "bundler" is not installed
#### Ruby version:
ruby 2.3.7p456 (2018-03-28 revision 63024) [x64-mingw32]
#### GEM version:
2.5.2.3
#### GEM environment:
RubyGems Environment:
- RUBYGEMS VERSION: 2.5.2.3
- RUBY VERSION: 2.3.7 (2018-03-28 patchlevel 456) [x64-mingw32]
- INSTALLATION DIRECTORY: C:/ProgramData/CloudVolumes/ruby/lib/ruby/gems/2.3.0
- USER INSTALLATION DIRECTORY: C:/ProgramData/CloudVolumes/ruby/.gem/ruby/2.3.0
- RUBY EXECUTABLE: C:/ProgramData/CloudVolumes/ruby/bin/ruby.exe
- EXECUTABLE DIRECTORY: C:/ProgramData/CloudVolumes/ruby/bin
- SPEC CACHE DIRECTORY: C:/ProgramData/CloudVolumes/ruby/.gem/specs
- SYSTEM CONFIGURATION DIRECTORY: C:/ProgramData
- RUBYGEMS PLATFORMS:
- ruby
- x64-mingw32
- GEM PATHS:
- C:/ProgramData/CloudVolumes/ruby/lib/ruby/gems/2.3.0
- C:/ProgramData/CloudVolumes/ruby/.gem/ruby/2.3.0
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :backtrace => false
- :bulk_threshold => 1000
- REMOTE SOURCES:
- SHELL PATH:
- C:\Program Files\Git\bin
- C:\ProgramData\CloudVolumes\ruby\bin
- C:\Program Files (x86)\CloudVolumes\Manager\ruby\bin
- C:\Windows\system32
- C:\Windows
- C:\Windows\System32\Wbem
- C:\Windows\System32\WindowsPowerShell\v1.0\
#### Bundle version:
Bundler version 1.16.1
#### Bundle config:
Settings are listed in order of priority. The top value will be used.
frozen
Set for your local app (C:/Program Files (x86)/CloudVolumes/Manager/.bundle/config): true
path
Set for your local app (C:/Program Files (x86)/CloudVolumes/Manager/.bundle/config): "vendor/bundle"
clean
Set for your local app (C:/Program Files (x86)/CloudVolumes/Manager/.bundle/config): "true"
without
Set for your local app (C:/Program Files (x86)/CloudVolumes/Manager/.bundle/config): [:development_postgres, :oracle, :development, :development_sqlite, :development_threading, :development_mysql, :test, :test_mysql, :test_sqlite, :test_postgres, :development_postgres, :oracle, :development, :development_sqlite, :development_threading, :development_mysql, :test, :test_mysql, :test_sqlite, :test_postgres]
Set via BUNDLE_WITHOUT: [:"development_postgres oracle development test"]
#### Bundle platform:
Your platform is: x64-mingw32
Your app has gems that work on these platforms:
* x64-mingw32
Your Gemfile specifies a Ruby version requirement:
* ruby 2.3.7p456
Your current platform satisfies the Ruby version requirement.
#### Using prebuilt environment
Running enable_hyperv.bat
#### Installing PowerShell Remoting Service HTTPS cert and port bindings.
The URL reservation could not be deleted. Error: 2
The system can not find the stated file.
Administrators: Account name and security identifier mappings were not made.
0 files successfully processed, 1 file has encountered a processing error.
#### Setting up database
Creating new database
create 1
rake aborted!
Errno::ENOENT: No such file or directory @ rb_sysopen - C:/Program Files (x86)/CloudVolumes/Manager/config/database.yml
C:/Program Files (x86)/CloudVolumes/Manager/lib/database_yaml.rb:68:in `read'
C:/Program Files (x86)/CloudVolumes/Manager/lib/database_yaml.rb:68:in `load_yaml'
C:/Program Files (x86)/CloudVolumes/Manager/lib/database_yaml.rb:55:in `rewrite_file'
C:/Program Files (x86)/CloudVolumes/Manager/lib/database_yaml.rb:18:in `initialize'
C:/Program Files (x86)/CloudVolumes/Manager/config/application.rb:91:in `new'
C:/Program Files (x86)/CloudVolumes/Manager/config/application.rb:91:in `database_configuration'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/activerecord-4.1.16/lib/active_record/railtie.rb:126:in `block (2 levels) in <class:Railtie>'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/activesupport-4.1.16/lib/active_support/lazy_load_hooks.rb:38:in `instance_eval'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/activesupport-4.1.16/lib/active_support/lazy_load_hooks.rb:38:in `execute_hook'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/activesupport-4.1.16/lib/active_support/lazy_load_hooks.rb:28:in `block in on_load'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/activesupport-4.1.16/lib/active_support/lazy_load_hooks.rb:27:in `each'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/activesupport-4.1.16/lib/active_support/lazy_load_hooks.rb:27:in `on_load'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/activerecord-4.1.16/lib/active_record/railtie.rb:116:in `block in <class:Railtie>'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/railties-4.1.16/lib/rails/initializable.rb:30:in `instance_exec'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/railties-4.1.16/lib/rails/initializable.rb:30:in `run'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/railties-4.1.16/lib/rails/initializable.rb:55:in `block in run_initializers'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/railties-4.1.16/lib/rails/initializable.rb:54:in `run_initializers'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/railties-4.1.16/lib/rails/application.rb:300:in `initialize!'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/railties-4.1.16/lib/rails/railtie.rb:194:in `public_send'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/railties-4.1.16/lib/rails/railtie.rb:194:in `method_missing'
C:/Program Files (x86)/CloudVolumes/Manager/config/environment.rb:4:in `<encoded>'
C:/Program Files (x86)/CloudVolumes/Manager/config/environment.rb:2:in `RGLoader_load'
C:/Program Files (x86)/CloudVolumes/Manager/config/environment.rb:2:in `<top (required)>'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:247:in `require'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:247:in `block in require'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:232:in `load_dependency'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/activesupport-4.1.16/lib/active_support/dependencies.rb:247:in `require'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/railties-4.1.16/lib/rails/application.rb:276:in `require_environment!'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/railties-4.1.16/lib/rails/application.rb:405:in `block in run_tasks_blocks'
Tasks: TOP => db:reset => environment
(See full trace by running task with --trace)
reset 1
database creation failed
Launching grant_sqlserver_access
console_handle_fault: Exception Errno::ENOENT: No such file or directory @ rb_sysopen - C:/Program Files (x86)/CloudVolumes/Manager/config/database.yml
console_handle_fault: Exception ActiveRecord::ConnectionNotEstablished: ActiveRecord::ConnectionNotEstablished
*** script/grant_sqlserver_access: start 2018-11-19 15:29:12 UTC
E, [2018-11-19T16:29:15.471686 #4616] ERROR -- : ActiveRecord::ConnectionNotEstablished (ActiveRecord::ConnectionNotEstablished)
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/activerecord-4.1.16/lib/active_record/connection_handling.rb:109:in `connection_pool'
C:/Program Files (x86)/CloudVolumes/Manager/vendor/bundle/ruby/2.3.0/gems/activerecord-4.1.16/lib/active_record/connection_handling.rb:105:in `connection_config'
script/grant_sqlserver_access:8:in `<encoded>'
script/grant_sqlserver_access:3:in `RGLoader_load'
script/grant_sqlserver_access:3:in `<main>'
Seems as if permissions are not correct. I assume you did install using "Run as administrator" command?
the database.yml is a file that is being created on the Appvolumes manager itself, has got nothing to do with the actual access to the database.
What I tried:
The setup aborts with the same error everytime.
Maybe the installation file is corrupt?
Update:
I tried the 2.14.0 installation ISO, same error...
Does that log file say that is being specified in the screenshot? Thing is I have never seen this error and have installed Appvolumes managers multiple times...
We have the same setup and the exact same problem. I've tried to run the setup in every possible way, it always fails at the create_db_config_file.
After the setup I ran the generate_db_config.cmd from the program files folder as admin to create the Database.yml. The file is created without any problem and it looks like its got the correct settings configured, but unfortunately the manager is still unable to connect to the sql database.
When I looked on the SQL server I saw something that looked strange to me. On the security -> users tab of the database my SQL_App_Volumes SA account is not listed, but is named "dbo". Normaly I would expect my SA account here with both user name and login name. Because of this I'm also not able to add the SA account manually to the database.
I'm curios, which database version do you use?
We use Windows SQL Server 2012 Standard (SP4) and it's listed on the compatibility page, but not on the docs page (SP3 is listed).
We are using the same version so no, this cannot be the issue.
One thing to keep in mind though (but my guess is this won't be an issue because you did have correct permissions), when creating the database this is being done by the machine that is being used to install the Appvolumes manager so you need to give the computer account enough permissions on the database.
I would suggest creating a database before starting to install and give the computer account DBOwner permission on that table..Might be worth a shot.
Alright, I found the solution ... guess what?
The database credentials didn't work for App Volumes.
Maybe there were too complex or some special characters are not allowed (which is not documented or reported by the installer).
We changed the credentials to a simple style and it worked.
VMware should document or report this during the GUI installer!
We had a random generated password, using a "simple" one did the trick. Thanks!
I was getting the same "app volumes error in creating database.yml file" error when trying to install version 2.15. I would even get the error when trying to install with local SQL Express. My sa account on my SQL server did have special characters in the password, but that did not seem to be the issue. I solved the issue by running the the installer msi as administrator.
Click Start > type cmd > right click and select "run as administrator". Then from the command window navigate to the installer .msi and launch it through the command window.
They expect you to run the installer thats in the root of the installation cd, that elevates your permissions successfully. The manager installer doesn't check and just runs with it, at least it causes problems now, it used to finish and give errors on startup. I'm hoping in future they figure out people are going to go directly to the manager installer and skip the one asking if your installing the agent or manager