Couchbase 2.2 - Cannot Connect to Console After Installation

I installed the 64-bit version of Couchbase 2.2.0 for Windows 7. I installed it using the default settings. The service is installed and I can stop / start or restart it without errors. However, I cannot connect to the management console on port 8091.

I found several posts on how to handle this, but they all refer to older versions of couchbase and link files / options that I cannot find in version 2.2 (for example, this post: Unable to connect to http: // localhost: 8091 / index.html ).

When I try netstat -an -p tcp, I don’t see a single service listening on port 8091, so I suspect something went wrong during startup.

Looking in couchbase log in / var / lib / couchbase / logs, I see some errors, but for me it does not make sense.

    [error_logger:error,2014-02-11T17:13:16.536,babysitter_of_ns_1@127.0.0.1:error_logger<0.6.0>:ale_error_logger_handler:log_msg:76]** Generic server <0.233.0> terminating 
** Last message in was {die,{abnormal,3}}
** When Server state == {state,ns_server,5000,
                               {1392,135189,391066},
                               undefined,infinity}
** Reason for termination == 
** {abnormal,3}

[ns_server:debug,2014-02-11T17:13:16.536,babysitter_of_ns_1@127.0.0.1:<0.235.0>:supervisor_cushion:init:39]starting ns_port_server with delay of 5000
[error_logger:error,2014-02-11T17:13:16.536,babysitter_of_ns_1@127.0.0.1:error_logger<0.6.0>:ale_error_logger_handler:log_report:72]
=========================CRASH REPORT=========================
  crasher:
    initial call: supervisor_cushion:init/1
    pid: <0.233.0>
    registered_name: []
    exception exit: {abnormal,3}
      in function  gen_server:terminate/6
    ancestors: [child_ns_server_sup,ns_babysitter_sup,<0.58.0>]
    messages: []
    links: [<0.73.0>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 2584
    stack_size: 24
    reductions: 2365
  neighbours:

Windows firewall works, but since I installed the same version of couchbase on another machine with the same version of Windows without any problems, I cannot imagine that the firewall is causing this problem.

I have no options, I don’t know why I can’t get this to work.

In the meantime, I deleted 2.2 and tried to return to 2.1 (with the same result) and moved forward to 2.5 (with the same result). In all cases, I turned around anti-virus software and stopped the Windows firewall to eliminate this cause.