[SIMS] New SIMS install not letting users log on

[John_Howarth]

I had this problem the other day with a 64bit Windows 2008 server.

It turned out to be the Windows Firewall on the server. The school's genius tech added an exception for port 1433 (SQL default, apparently) and it worked after that.

He also did the NamedPipes thingy (can you tell I'm not a technician?!).

I'll email him a link to this thread to see if he has any other suggestions.

[Number6]

is firewall on by default on server 2008

This could be the post of the century!!!

I don't know but I'm going to check right now! Why didn't I think of that?

Thanks

It was the post of the century!! It was on, it's not now and it works!

May the blessings of a thousand virgins be showered upon you!!

I originally turned it off but forgot that I reinstalled the server and didn't recheck. Things like this make me feel like a right pillock.

A thousand thanks.

[mrtechsystems]

Well at the end of the day that is IT for you at least you learn something from it...

[matt40k]

Few thoughs:

Check sims.ini, make sure setups is point to the new servers setups
Make sure the user has access rights to the s drive (sims share)
Make sure the firewall is opened up. (MSSQL,HTTP:8080(DMS),File sharing)
If you installed MSSQL 2005 standard\enterprise, enable TCP\IP
Checking the connect.ini (c:\program files\sims\sims .net\connect.ini)

*Cough*

[Number6]

Interestingly, the firewall is configured exactly the same on both servers and SQL is named as an exception on both. Obviously on the new server SQL is using different ports so I'll have to track that down now.

[Number6]

*Cough*

Shut up!!!

[Number6]

*Cough*

It is actually configured with SQL as an exception but it's not working. I've had to turn the firewall off completely for the time being.

[John_Howarth]

Taken from Capita's SupportNet (KB72234):

If your Named Instance is called 'SIMS' and is installed on the D:\ drive

D:\Program files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG.

(Please note the above file has no extension, but can be opened in Notepad.)


Look for a line ending in the following: -

SQL server listening on 127.0.0.1: xxxx

xxxx is the port which your installation of MS SQL Server is attempting to listen on, and this is the port which you need your Firewall to be aware of.

Hope this helps.

[Number6]

Taken from Capita's SupportNet (KB72234):

If your Named Instance is called 'SIMS' and is installed on the D:\ drive

D:\Program files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG.

(Please note the above file has no extension, but can be opened in Notepad.)


Look for a line ending in the following: -

SQL server listening on 127.0.0.1: xxxx

xxxx is the port which your installation of MS SQL Server is attempting to listen on, and this is the port which you need your Firewall to be aware of.

Hope this helps.

Yes, I checked the log earlier, it says port 49193 but opening that through the firewall makes no difference, it still errors.

[John_Howarth]

My technical colleague at the school I was working at earlier this week sent me the following message:

Number6 is right. I did create the firewall exception that you mentioned, but that alone wasn’t sufficient so I turned the firewall off completely pending investigation of other port usage (I apologise for not making that clearer on Tuesday).

At some point next week I want to sit down with TCPView and figure out exactly what SIMS clients are making use of. It’s possible that they’re using randomly-assigned high-range ports, in which case you’d have to create firewall rules on the server that allowed SQL and any other SIMS server-side binaries to accept connections on any port.

I’ll let you know what I find out.

I'll post here again with any further information that comes my way.

[Number6]

My technical colleague at the school I was working at earlier this week sent me the following message:

Number6 is right. I did create the firewall exception that you mentioned, but that alone wasn’t sufficient so I turned the firewall off completely pending investigation of other port usage (I apologise for not making that clearer on Tuesday).

At some point next week I want to sit down with TCPView and figure out exactly what SIMS clients are making use of. It’s possible that they’re using randomly-assigned high-range ports, in which case you’d have to create firewall rules on the server that allowed SQL and any other SIMS server-side binaries to accept connections on any port.

I’ll let you know what I find out.

I'll post here again with any further information that comes my way.

Thanks for that.

I'm away now for two weeks but I'll be interested to see what crops up here.

[vikpaw]

I know it's an old thread but for the sake of posterity in case it helps anyone, as i've spent ages on it here is what worked for me:
Windows Server 2008 R2, with SQL 2008 R2:

Allowed 2 inbound rules through the firewall, specifically for application, rather than any particular port and all works fine:

%ProgramFiles%\Microsoft SQL Server\MSSQL10_50.SIMS2008\MSSQL\Binn\sqlservr.exe

and

%ProgramFiles% (x86)\Microsoft SQL Server\90\Shared\sqlbrowser.exe

The first one isn't needed for SIMS to work, but i haven't fully tested to see if everything works yet without it.