The latest MLS update (April 2005) with new dialup numbers and settings broke my Windows 2000 installations of MLS. Whats the solution since we probably can dial up to get an update fix?
Q: What are some basic trouble shooting steps that can be done before we call Salt Lake? We have problems with “MLS” connecting with the Church. The branches that I work with are 300 to 800 miles from the District office. Q: The Wards and Branch in our Stake are now caught in a never ending loop, with every Send and Receive Changes headquarters servers are re-attempting 2.4.1 update, the version that the Wards and Branch have is already 2.4.1. And when clicking on any of the membership menu options MLS reports an error. Q: The Stake MLS after downloading and updating the MLS to 2.4.1 cannot be logged into. At the 2.4.1 MLS login screen, selecting the user, typing in the password, and clicking login the MLS 2.4.1 login screen freezes.
Related Questions
- I have changed the settings of the RealTek adapter using Windows Network Properties and then started ClearSight Analyzer and my system Blue Screens. How do I prevent this from happening?
- The latest MLS update (April 2005) with new dialup numbers and settings broke my Windows 2000 installations of MLS. Whats the solution since we probably can dial up to get an update fix?
- How do I find out the local dialup numbers for the Bell Nexxia.IP Connect service?
