We have an issue where IWP users will periodically get the error "Database Unavailable" when trying to log in. If they keep trying the error goes away in < 30 seconds. I don't have a bunch of data points on which to build an accurate model, unfortunately, because it is intermittent, and because our IWP users aren't logging in on a very regular basis. This error doesn't come up for client users.

Curiously, when this error happens and you clear the message, it drops you back to the 'Database Homepage' screen. This is the screen that FMS generates dynamically that lists your available databases. According to the documentation this is supposed to prevent users from trying to log into a DB that ISN'T available by only showing them the ones that are. However, the DB in question DOES show up on this list. If they click the link for that DB again, it again gives them the "unavailable" error.

You can keep going in this circle until whatever is locking it out expires and it does let you in. (You don't have to provide additional login credentials, assuming that you entered them correctly the first time. It appears to remember your login even though it never actually let you in.)

Does anyone have ideas on where to look and how to track down what the conflict might be? Or any ideas about what is causing the problem?

Thanks,

J

Well I'm in the process of switching over to Server 12 all my IWP a presenting the same problem. In search of an answer too.

reinstalling resolved this.

We fixed our problems with IWP and/or CWP reporting the error above:  we got a new key from FMI (they should give you a new one for free). 

 

We had problems because we were trying to use IWP to serve some web based users, and also had a couple of CWP connections going on in the background:  one was a plugin, another was a script that was using an FMXML connection.  Also, if you use PHP for anything, that is CWP. 

     We didn't get crashes or complete stoppages of IWP & CWP, but we would get an error that 'the Database was unavailable'.  If you kept trying it would eventually work again.

 

Installing the new license keys instantly stopped all problems we had with this.

 

--  J