SIMS Help... urgent

[PEO]

We've setup a new sims server and migrated all data over from the old one.

 

Everything is set the same as the old server such as IP address, permisions and a trust has been established.

 

We can login to the sims directly at the server but if we try from a client machine we get the following error.

 

SIMS connection failed for login kevin : reason 0

 

any ideas?

 

cheers

 

Kev

[creese]

There are a number of reasons for Reason 0

 

Have you checked the Connect.ini has the correct server and database names?

[PEO]

yep its pointing to the correct drive. I've gone as far as uninstalling sims on a client and reinstalling it to see if that helps.. no joy

[creese]

Try also running DBUpgrade make sure all upgrades have run

[PEO]

from the server?

[creese]

Try stopping and starting the SQL

[creese]

from the server?

 

Yes

 

And then run SimsApplicationSetup.exe on the local machines

[laputa01]

As Creese says, check which version you are on and then run nesscary updates.

[PEO]

ok brb

[bossman]

@PEO:

 

Have you ran the simsperm.bat from one of your workstations?

[BatchFile]

If you're using full SQL have you adjusted the surface area thingy to accept connections from outside the local machine?

[Mcshammer_dj]

copy the client from the server(C:\program files\sims\sims .net) to one of the clients and then try to open sims

[localzuk]

If you're using full SQL have you adjusted the surface area thingy to accept connections from outside the local machine?

 

This would be my first thought with a new SQL server.

[PEO]

Thingy? can you explain a tiny bit more?

[localzuk]

Thingy? can you explain a tiny bit more?

 

We're referring to 'SQL Server Surface Area Configuration'.

 

How to configure SQL Server 2005 to allow remote connections

[Mcshammer_dj]

what was the old server Os and what is the new one?

 

When moving to 2008 you will need to check the firewall as sims does not always use the standard SQl ports .

[Janit]

I always start with connect.ini's when I get reason 0. The connect.ini on the workstation, particularly if it's been a sims workstation since the last migration, can sometimes contain too much bumph. It should ideally just have:

 

[sIMSConnection]

Redirect=s:\sims

 

And then the central connect.ini in s:\sims should have the correct servername and database name in it. e.g.

 

[sIMSConnection]

ServerName=whatevercomputernameis\sims2008

 

If connect.ini's are correct and they contain the server name rather than IP address, check that you can ping the server by name from a workstation.

 

Shouldn't really need to reinstall any SIMS client on the workstations or adjust the network config on a new sql install.

[localzuk]

Shouldn't really need to reinstall any SIMS client on the workstations or adjust the network config on a new sql install.

 

Not true. A default SQL install has remote connections disabled by default. So, as part of setup, you have to allow them access.

[creese]

I always start with connect.ini's when I get reason 0. The connect.ini on the workstation, particularly if it's been a sims workstation since the last migration, can sometimes contain too much bumph. It should ideally just have:

 

[sIMSConnection]

Redirect=s:\sims

 

All our connect.inis are like this:

 

[sIMSConnection]

ServerName=PServer\SIMSSQL

DatabaseName=simssdatabasename

Commandtimeout=100000

 

No redirects.

[BatchFile]

The only problem with that is if you have to move SIMS to another server in a hurry:eek: with a redirect on the local machine and the full [sIMSConnection] as above on a mapped drive, all you have to do is change the login script to map the drive to a different server, edit the connect.ini on the mapped drive and you're away. After you've set up another server, of course:)

[creese]

Or copy the connect.ini from the S:\sims directory.

 

Redirects have always caused us problems.

[Janit]

Not true. A default SQL install has remote connections disabled by default. So, as part of setup, you have to allow them access.

 

I've never had to change that setting after a new install. Have only taken advantage of disabling it myself for upgrades.

[BatchFile]

Or copy the connect.ini from the S:\sims directory.

 

Redirects have always caused us problems.

 

That would depend on how many workstations you've got and how urgent the situation is

[creese]

That would depend on how many workstations you've got and how urgent the situation is

 

Urgent would be about 1 or 2 workstations at most. How many people urgently need in a school.

[jcollings]

Urgent would be about 1 or 2 workstations at most. How many people urgently need in a school.

 

Well in our school all staff need SIMS "urgently" as it is used for registration every lesson, report cards & logging of behaviour incidents etc. I'd say if it didn't work here it would be considered urgent!