Skip to main content
Solved

port 20000 does not run when configuring index server for Exhange


Forum|alt.badge.img+1

Good afternoon everyone,

As it says in the title, my problem is that when creating an index server to configure online Exchange backups, I assign a client with Index Store installed, but when accepting it remains loading for a long time to finish skipping an error for the 20000 that seems not to be working, it is a laboratory that I have set up so the Windows Firewall I have it disabled and I do not know well what this problem may be due to.
Possible solutions? I am beginning to despair as I do not stop testing but nothing.

Greetings and thank you very much in advance.

 

Best answer by Anthony.Hodges

On a side not, I have found that if the Index Server doesn’t have enough free memory that the datacube won’t start.  Similar problem occurs with the Command Center if there is insufficient free memory.

View original
Did this answer your question?

6 replies

Chris
Vaulter
Forum|alt.badge.img+6
  • Vaulter
  • 25 replies
  • May 19, 2021

Jose Maria, 

 

When creating an index server please make sure whatever server you are using as a web-server and Commserve are able to reach the server you are attempting to add as an index over port 20000. 

 

Please also make sure the index gateway package is installed onto the index server you are attempting to use as the Index node.


Forum|alt.badge.img+1

Hi @Chris 

First of all thank you very much for your reply.

I have checked the connection from the Commserver to the index server with telnet through port 20000 and it connects perfectly,

In addition, installing the gateway package that actually did not have it installed on the index server, but it still does not work for me, I keep getting the same error.

Greetings and thank you!

 


Chris
Vaulter
Forum|alt.badge.img+6
  • Vaulter
  • 25 replies
  • May 19, 2021

Jose Maria, 

 

At this point I would have to most likely suggest a Ticket Request with our support staff to take a look at what is causing the error and where it is coming from. 


Forum|alt.badge.img+1

Hi @Chris 

I will have to do it, I have been with this problem for several days and they ask me to solve it now.

In one of the event viewers I have also seen that it talks about Data Cube Service, that I make sure that it is working and is locatable, could this be the problem?

Greetings!


Chris
Vaulter
Forum|alt.badge.img+6
  • Vaulter
  • 25 replies
  • May 20, 2021

@Jose María ,  

Yes, datacube is an essential part of the index server services.  Without an actual configured index running on the server its not going to tell you much. 


Anthony.Hodges
Commvault Certified Expert
Forum|alt.badge.img+10
  • Commvault Certified Expert
  • 87 replies
  • Answer
  • May 21, 2021

On a side not, I have found that if the Index Server doesn’t have enough free memory that the datacube won’t start.  Similar problem occurs with the Command Center if there is insufficient free memory.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings