Reason 3

[amvc]

Hi

I have a laptop which after a SIMS upgrade won't log in due to Reason 3.

I'm Running the latest (re-released) version of SIMS, with a CommandTimeout=10000 line in the Connect.ini file.
The laptop has .net Framework 2.0 installed and Windows SP3.

Capita's KB article Kb72431 offers some sound advice on this one...
"Log in again and the error message should not appear."

And there I was thinking capita were useless.

Any ideas anyone?

[cromertech]

We had this problem after the upgrade to SQL. Your connect.ini file should look something like this

[SIMSConnection]
ServerName=10.97.28.6\sims2005
DatabaseName=SIMS
[ExternalApplications]

The first line is the IP or hostname of the SIMS server followed by the SQL server name

You can put the connect.ini on the server in which case you can rewrite the local connect.ini to read

[SIMSConnection]
redirect="server connect.ini location"

[superfletch]

Have you got the commandtimeout setting in your connect.ini(s)

If so the timeout needs to be of a suitably high value to allow the workstation to communicate to the SIMS Server and for the SIMS Server to pass the request to the SQL2005 DB Engine recieve a response, translate it into something useful and pass it back to your workstation.

Usually I'd suggest commandtimeout=10000 but you might even need it higher than this especially if you have any weak links (bottlenecks such as old switches or even hubs) between your workstation and your database server.

As Matt said - are both your connet.ini files correct?

Also - Is the database server man enough to handle the SQL2005 Database if it is underpowered or recieving lots of other non SIMS requests too it could be taking an age to send the data back to you?

Some things to be thinking of anyway?

Recommended Spec by Capita (for DB Server):

1.5 GHz processor or higher (Dual Core 2.4 GHz recommended for optimum performance in secondary schools)

1024 or higher (4GB recommended for optimum performance in secondary schools).

[amvc]

Thanks to all who had a look into this for me.

The problem was with DNS for that laptop. It seems that the owner of the said laptop had been trying to get home braodband working and had fiddled with DNS.

Removed a DNS prefix and it all works.

I'm still no wiser what Reason 3 means though, it could still be a timeout error I suppose!