[sims] Reason 0 Error on workstation

[kshah58]

Hi,

 

I've been trying to resolve this issue on a workstation for the last 2 hours. Been through the Capita workarounds and still no luck.

 

The school's IT support has been preparing for a server migration and would like to move the SIMS and FMS database from the main office workstation to the new server. The only peculiar thing that comes to my mind is that the IT support changed the IP range so the curriculum network and admin network are on the same range. The admin workstations were on 10.81.90.xx range and were moved to 10.81.92.xx range. The SIMS and FMS database would have been installed on the 10.81.90.xx range.

 

Could the change in IP range cause issues with connections to the SQL Server?

 

Thank you.

 

Kunal.

[Cazale]

Sounds like a connect.ini issue. If you've thought of that, it's worth searching for the file (i.e. don't just look in the SIMs folder). I've seen one cached in a local profile/appdata before that was causing all sorts of headaches!

[Michael]

Hi,

 

I've been trying to resolve this issue on a workstation for the last 2 hours. Been through the Capita workarounds and still no luck.

 

The school's IT support has been preparing for a server migration and would like to move the SIMS and FMS database from the main office workstation to the new server. The only peculiar thing that comes to my mind is that the IT support changed the IP range so the curriculum network and admin network are on the same range. The admin workstations were on 10.81.90.xx range and were moved to 10.81.92.xx range. The SIMS and FMS database would have been installed on the 10.81.90.xx range.

 

Could the change in IP range cause issues with connections to the SQL Server?

 

Thank you.

 

Kunal.

 

Several possibilities - the hostname would have changed (main office workstation) and new server name. Alternatively sometimes the IP is specified instead of the hostname. Thirdly, the database name/instance could have changed also. Fourthly, make sure DNS is all up-to-date and working and can resolve the server hostname.

[splattthecat]

Worth checking that the Connect.ini files are pointing correctly to the new server name/sql instance, that the clients are resolving the new server name to its correct IP address, that the SQL Browser service is running on the new server and that any firewall in place isn't blocking SQL traffic.

[Greg]

Is you're connect.ini a redirect to mapped drive or UNC path on the workstation.

Other than that, firewalls, SQL Browser, permissions

[superfletch]

As others have said this is usually a connect.ini issue:

 

Does it work OK on the server?

Does it work OK on other workstations?

 

The main connect.ini (not redirected) should normally look something like this:

 

[sIMSConnection]

ServerName=simsserver\sqlinstance

DatabaseName=sims

Commandtimeout=100000

 

 

Note the lack of 2 backslashes for the servername line

 

If the server works, but workstations don't then you're probably looking at one of the things @Greg has mentioned.

 

Edited February 22, 2016 by superfletch

[kshah58]

Hi all,

 

Thanks for your inputs. The Connect.ini is pointing to the correct server name. I've also used the Server IP Address instead plus with a dynamic port. Added a command time out line on the connect.ini file as well. Still no luck!!

 

I have also disabled the firewall and also put an exception for SQL in the firewall. The workstation which contains the SIMS and FMS database works perfectly fine with no errors.

 

Also I just found out that there has been a domain created and the admin users have new profiles for the domain, with the files from their previous profiles been transferred across. Would this have any implications on connecting to the SIMS and FMS database?

 

Thank you.

 

Kunal

[kshah58]

Issue has been resolved...Did all the workarounds, plus a reboot and the workstation can log into SIMS.

 

[jinnantonnixx]

Error messages, 1980s style.

 

That's inexcusable these days.

[PotNoodleTech]

It's not even as good as that - even the 80s gave you a short succinct description of the problem as well as more than one option. Maybe one day capita will catch up with the 80s.

 

http://core0.staticworld.net/images/idge/imported/imageapi/2014/10/15/13/slide_abort_retry_fail-620x465-100525018-gallery.idge.jpg