Hi ,

I am facing errors in ASP web service code while publishing it. i am attaching the screenshot for your reference.

Hi,
I'm testing ACE on a CentOS7 VM hosted on ESXi. I deployed ACE with the following process:

1. Install docker and necessary dependencies with yum install
2. Install docker-compose and run docker
3. Install nginx
4. Install ACE:
   
5. In ace.env: change WEBSERVER_IP with the ip of my CentOS VM
6. ./start.sh

I've encountered a connection problem when trying to access ACE web interface from my windows PC which is in the same subnetwork with CentOS. By browsering to https://IP_OF_CentOS, I'm getting the error 113: no route to host in "docker-compose logs".
I've added a firewall rule in CentOS "

", bus it wasn't of help.

Another issue I found is that line 203 in start.sh (docker-compose build) is not building dockerfiles in containers, for example it cannot copy nginx.conf to the nginx directory as supposed. A not-so-good solution I found is to launch docker build for every dockerfile. I believe it is a issue of docker itself, please refer to: docker/compose#3148

Please tell me if I've missed some important deploying step, because there are things that I'm not sure about, such as the right WEBSERVICE_IP and the subnet docker0.

Thanks in advance,

Start-AceDiscovery fails to discover Windows computers for a given Windows domain. Start-AceDiscovery produces a 404 error on ACEWebService - $(URI)$/ace/discover/domain. Same error can be produced using FQDN of the Windows domain.

Start-AceDiscovery Output:

ACEWebService Output:

HI,

i am facing this error when i am installing ACE Docker.

in short i am getting error related to MS-SQL.

SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..

Error: The evaluation period has expired.
This program has encountered a fatal error and cannot continue running.
The following diagnostic information is available:

   Reason: 0x00000001
   Signal: SIGSEGV - Segmentation fault (11)

Stacktrace: 000056441d52fce7 00007fd80764b390 000056441d53ef52
000056441d5286db 000056441d527e59
Process: 6 - sqlservr
Thread: 18 (application thread 0x1028)
Instance Id: e623d85c-8194-4f4a-8c4e-fba2871e25e4
Crash Id:
Build stamp: a37664e45e4156e76a53fa282fd694cb49f70c2037515f5684e3ce6dfa7549bc
/usr/src/ace/import-data.sh: line 4: 6 Aborted (core dumped) /opt/mssql/bin/sqlservr > /dev/null
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login timeout expired.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : TCP Provider: Error code 0x2749.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..

},

"ConnectionStrings": {
Error: The evaluation period has expired.
This program has encountered a fatal error and cannot continue running.
The following diagnostic information is available:

   Reason: 0x00000001
   Signal: SIGSEGV - Segmentation fault (11)

Stacktrace: 000056441d52fce7 00007fd80764b390 000056441d53ef52
000056441d5286db 000056441d527e59
Process: 6 - sqlservr
Thread: 18 (application thread 0x1028)
Instance Id: e623d85c-8194-4f4a-8c4e-fba2871e25e4
Crash Id:
Build stamp: a37664e45e4156e76a53fa282fd694cb49f70c2037515f5684e3ce6dfa7549bc
/usr/src/ace/import-data.sh: line 4: 6 Aborted (core dumped) /opt/mssql/bin/sqlservr > /dev/null
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login timeout expired.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : TCP Provider: Error code 0x2749.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..

}
}

==========================================================

===============================================================
| Thank you for provisioning ACE with Docker!! |
| Please use the following information to interact with ACE |

$settings = @{
Uri = 'https://192.168.28.131'
Error: The evaluation period has expired.
This program has encountered a fatal error and cannot continue running.
The following diagnostic information is available:

   Reason: 0x00000001
   Signal: SIGSEGV - Segmentation fault (11)

Stacktrace: 000056441d52fce7 00007fd80764b390 000056441d53ef52
000056441d5286db 000056441d527e59
Process: 6 - sqlservr
Thread: 18 (application thread 0x1028)
Instance Id: e623d85c-8194-4f4a-8c4e-fba2871e25e4
Crash Id:
Build stamp: a37664e45e4156e76a53fa282fd694cb49f70c2037515f5684e3ce6dfa7549bc
/usr/src/ace/import-data.sh: line 4: 6 Aborted (core dumped) /opt/mssql/bin/sqlservr > /dev/null
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login timeout expired.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : TCP Provider: Error code 0x2749.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible

PS: if i do netstat -antp for active connections and open ports i can see port number 1433 is open but when i do telnet or nc to check the connectivity it shows Connection Refused.

the script is failing as some directories and files are missing like
ace-app
ace-web
ace-mssql-linux/ace.Template.sql
ace-app/appsettings.Template.json

Hey thanks for making this tool. I have the basic setup up and running. I can add new users to my ACE instance via the PS scripts. I'm looking to do some minimal development on the web service side if I can get everything figured out, and I'm having some trouble fitting all the pieces together. I finally got a dev copy of the WS running with the Visual Studio plugin Conveyer and IIS Express. This way I should be able to debug, and I can get to it via network IPs which was initially difficult to setup.

I think there are a few fundamentals I'm missing that have made this tricky to get started:

• Does the web service need to be on the AD domain?
• Does the user/machine running the ACE management scripts need to be on the AD domain?
• I noticed a lot of code commented out of some of the Services - some of the Active Directory functionality. Is this not working currently?
• I saw in another issue there's a video posted, but I can't quite follow the end of it without narration. Is there any plan for a quick runthrough of what you can do against machines on the domain?