This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

No client connectivity after database change

Hello, we are having a problem after changing the db from the SQL express as was setup by our provider to full fledged SQL 2012 where the clients no longer are communicating to the server when trying to synchronize. I'm brand new to this product so not quite sure what's needed, but took a crack at changing the db connection string in Iis, changing the db connection in enterprise console then creating a new client package, and reinstalled client but it's still not talking to server; still get "failed to contact server" messages when clicking "synchronize" on client; any ideas what I've missed?
:51446


This thread was automatically locked due to age.
Parents
  • Surprised no one has come across this already...but the fix was to create a server configuration package with the server configuration already in place containing the newly updated database connection info, then install that package on the server. Once that was done, the clients can immediately connect.

    :51838
Reply
  • Surprised no one has come across this already...but the fix was to create a server configuration package with the server configuration already in place containing the newly updated database connection info, then install that package on the server. Once that was done, the clients can immediately connect.

    :51838
Children
No Data