E_G_R2 Posted November 6, 2015 Posted November 6, 2015 Hi, build new 2012R2 server with SQL2012, Successfully migrated database. Tested install on its own standalone network, Server and a couple of PC. No problem the PC’s accessing SIMS on the server. Closed down old server and added new server to the domain. Think I have replicated the permissions for the SIMS share. Change login script to point at new server and changed local connect.ini (as a redirect to s:) with the connect.ini on the server beineg servername\instance + database name PC tries to connect and gets sims connection failed for reason 0 OK I can see the wood for the trees
rrrrr Posted November 6, 2015 Posted November 6, 2015 Firewall? Sql service all running ok? Can you login to sims directly on server still?
E_G_R2 Posted November 9, 2015 Author Posted November 9, 2015 The SIMS client works fine on the server on the test rig or live on the Domain. Its just the workstations that get the error. If I re install SIMS on the workstation and create the connect.ini via the setup (that should be correct?) they still get the error. No firewall. SQL service is working because it works on the test network. Got to be something looking at me in the face
rrrrr Posted November 9, 2015 Posted November 9, 2015 Have you checked "SQL server network config" in "sql server config manager" and checked TCP/IP is enabled?
3s-gtech Posted November 9, 2015 Posted November 9, 2015 Check the SIMS.ini file in C:\Windows on the workstation to check it is correct and properly formed.
DavetheITguy Posted November 9, 2015 Posted November 9, 2015 Are you mapping the Sims drive on the workstations ?...
E_G_R2 Posted November 9, 2015 Author Posted November 9, 2015 Can't try any of these out yet as it works on the test network but not live, will give it a go 'live' tonight with these suggestions.
Ghostgame Posted November 9, 2015 Posted November 9, 2015 Is the SQL Server Browser service off in Services.msc?
E_G_R2 Posted November 10, 2015 Author Posted November 10, 2015 Many thanks for the tips, in the end it was TCP and a port added to the connect.ini
PotNoodleTech Posted November 11, 2015 Posted November 11, 2015 Figures, Reason 0 seems to be "can't connect to the database"
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now