If you attempt to start Cubit Estimating and are met with the Cubit Estimating Login error or receive the error "No connection could be made because the target machine actively refused it", Cubit Estimating may have an issue accessing the database on startup.
Fig 1. No connection could be made error
To resolve this issue, you can try and reboot your PC to force your Windows services to restart including the database service.
If after a reboot you continue to get the same error above, please try the following to try and start Cubit Estimating database service.
1. Click the Windows icon and type Services.msc to locate Windows Services. Click Services to launch it.
Fig 2. search and start Windows Services.msc
2. Locate PostgreSQL service as shown below and click Start.
Fig 3. Start PostgreSQL service
3. Launch Cubit Estimating again.
Should you continue to experience a problem in using Cubit Estimating after performing the above steps, Please Submit a Support Ticket
This error is a network-related error occurred while establishing a connection to the Server. It means that the error is occurring because there is no server listening at the hostname and port you assigned. It literally means that the machine exists but that it has no services listening on the specified port .
Generally, it happens that something is preventing a connection to the port or hostname. Either there is a firewall blocking the connection or the process that is hosting the service is not listening on that specific port. This may be because it is not running at all or because it is listening on a different port. So, no connection can be established.
Hello Danel, Thank you for your comment.
Yes, you are right the error can be network/firewall related in case you are working with the Cubit network licence.
This article was initially aimed to assist with connection problem with Cubit standalone licence in which case the database is locally installed.
Please sign in to leave a comment.