Unable to log in on any workstations...please help

I am operating SBW on an Windows 7 platform, networked from our server to 4 workstations. On Tuesday (1/14/14), the program worked flawlessly, as usual. On Wednesday when we began our day and attempted to open BW, we got the following message...
Unable to connect with the System Manager Database. (BTRVLoginError(7025): Failed to connect to the server (server not found) (Server: SERVER; dB: BWSYSTEM1400))

Most likely, if you name it, I have tried it in an attempt to remedy this issue, all to no avail. The only thing I have yet to do is reinstall the program.

Any help would be much appreciated.

Thank you very much in advance.

Drew

Ridgeline Metal

Parents
  • 0

    Several things can cause this error.  

    1. Can you get in on the server?   May need to reboot the workstations and the server

    2. There may be an issue with the workstation not being able to get name resolution to the server.  Can you ping the server and get the correct IP address of the server?

    3. A windows firewall or Windows defender may be blocking access.  Try temporarly disabling the firewall or disable windows defender and see if you can access

    4. The workstation may be infected with a Rootkit virus.  Run a through virus scan with updated virus scan files

  • 0 in reply to CShular

    I can log on to BW on the server. We have rebooted workstations and server alike multiple times, and nothing.

    Correct IP address, yes. I have clean resolution to the server from each station.

    We tried pulling down the firewall and defender both from the server and from the workstations and then rebooting and that didn't do it.

    No Rootkit, all clean.

Reply
  • 0 in reply to CShular

    I can log on to BW on the server. We have rebooted workstations and server alike multiple times, and nothing.

    Correct IP address, yes. I have clean resolution to the server from each station.

    We tried pulling down the firewall and defender both from the server and from the workstations and then rebooting and that didn't do it.

    No Rootkit, all clean.

Children