We have users reporting an error message (Error: -100) when trying to connect with our databases (184.108.40.20694). Yesterday the MS updates have been automatically applied in the server and the branches also reported internal network issues with their communication service provider.
After a few exploratory steps, we noticed that the SASRV.INI had today’s date/time stamp and all the server connections have been wiped out from the file. The issue was solved after we found a workstation that connected fine with our application via SQLANY12 where the SASRV.INI had not been changed. However, from ISQL the "Find" feature does not list any of the available network services even after fixing the INI file.
Is there a way to avoid the SASRV.INI to be wiped out? If we set the file to READ-ONLY, would it prevent the issue to happen in the future? Are there any side-effects on doing so?
This question is marked "community wiki".
asked 15 Jan '14, 13:51
While I have no idea why the file would have been emptied, the sasrv.ini file is a cache of addresses, used to speed up the search for previously used servers. It is solely for convenience and should not be relied upon. It is not intended to be edited by users.
Bottom line: If you can't connect once the sasrv.ini file has been removed or truncated, then your connection string does not contain enough information.
answered 15 Jan '14, 14:32