Jump to content

Recommended Posts

Posted

I am trying to move Safecom to a new server but have hit a snag straight away.

 

When installing Safecom on the new server it installs but I cannot connect to the server. The admin console just shows the server as "not known to be running". All the services and SQL are running.

 

This is on Server 2016 which installs SQL 2008 R2.

 

Anyone give me some pointers?

Posted (edited)

(I don't know anything about Safecom as I don't use it)

 

Do you need to create firewall exceptions?

Have you got the latest SQL patches installed?

 

Edit - see page 55 here for a list of inbound/outbound ports that need to be open

Edited by computer_expert

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...