TCP error code 10013, how to solve?

Hello everybody,

at first of all, the cmc docs are not very enlightening, just contain setup steps / screenshots (everybody knows how to run a setup) but further details or a troubleshooting section is missing *thumbs down*.

Well, let's go - the cmc setup runs successfully, without any errors, then I've set up a new site under the iis manager at port 81:




The Management Server (Serivce) is running without any errors:




Management Server Administration is configured on port 4502:




clientaccesspolicy.xml:




The site starts perfectly, but the first abnormal thing is visible in the background of the following screenshot, it seems that the words "Trial" and "Activated" are drawn to the same position, the next row contains the same problem.

However, if I try to activate the license, I will get an error message: "... Could not connect to net.tcp://domain:4502/ManagementService. ...":




The port range 4502-4534 is opened and the configured domains are at every configs the same.

Don't know what to do here, I guess it's an novastor "insider" affair and it's not solvable for "outsiders".

What a glorious doc, smile benignly:




The logs:

C:\Program Files\NovaStor\NovaBACKUP Central Management Console\WebRoot\log.txt is empty
C:\Program Files\NovaStor\NovaBACKUP Central Management Console\Service\Logs\trace.log does not conatins any errors


The environment:

Windows Server 2008
MSSQL Server 2008 R2
IIS 7
Novastor Storage Server 12 + cmc


Thanks for any help and greetings from munich, germany.

Greetings;
We had a similar problem on server 2003 IIS6, I think it turned out to be that we couldn’t browse to localhost using a web browser on the server. In IIS6, I added MyLocalIP, port 80, and localhost to the “Advanced web site Identification” applet. (website properties, website tab, advanced) Don’t know about IIS7 though. There may have been more to it, but it’s sadly lost to a bad case of CRS.

[farmboy]

why your clientaccess shows: socket-resource port="4509-4534" protocol="tcp"?

By default it mus be : socket-resource port="4502-4534" protocol="tcp"

farmboy: why your clientaccess shows: socket-resource port="4509-4534" protocol="tcp"?

Sorry for that mistake, we've tried to solve the problem by switching the port range, at this moment the screenshot was created. Sure, we've also tested the socket-resource port="4502-4534", but luckless.

aldva: We had a similar problem on server 2003 IIS6, I think it turned out to be that we couldn’t browse to localhost using a web browser on the server ...

Thanks a lot for this hint, but we've tested it already, the silverlight application is starting without any problems, by local / direct call of ManagementServer.html on the server. ... the same error message appears.

Very frustrating...