|
#1
|
|||
|
|||
|
I have installed the latest version or Mirth on a windows 2008 64 bit Virtual server. My network admin then creted a second server using a copy of the first one. We use the initial one as the live and the copied one as Test. Everything has been wrking for the past couple of months.
The problem that we have now is in the live mirth engine, sometimes we cannot login to the mirth admin console. We get the followin error: "There was a problem authenticating the information that was entered. Please verify that the sever is up and running and that the user information is valid." I did create 2 other users, but they too give the sme error. However, when we re-start the server, everything works wihtout any issues for a day or so then the problem comes back. We have not installed / updated ay applications on the server. I searched on the forum and could not find any answers to this. Another interesting thing is the Mirth test environmnt was created from the live one and we never see this issue. Test server works like a charm. The server config parameters are exactly the same. We have installed SQL server for as the backend. Could anyone suggest anything to fix this please? Any help is gretly appreciated. |
|
#2
|
|||
|
|||
|
Usually that error is due to connectivity problems with the database. Are your SQL Server instances local to each VM, or is Mirth reaching out to a different server where the database is hosted?
|
|
#3
|
|||
|
|||
|
SQL server is local to each VM.
|
|
#4
|
|||
|
|||
|
It sounds like a database maintenance issue... The next time that happens, try to get into the database through the backend and see if there are any issues. Do you guys regularly maintain/audit your SQL servers?
|
|
#5
|
|||
|
|||
|
I was having a similar problem and the answer was found in
...\Mirth Connect\logs\mirth.log |
|
#6
|
|||
|
|||
|
I checked and there are no issues with the SQL server.
kt7277 : How did you fix your problem? |
|
#7
|
|||
|
|||
|
When you attempt to log in, are there any errors that appear in mirth.log?
|
|
#8
|
|||
|
|||
|
Don,
As Nick suggested, I found log in errors related to SQL server in mirth.log. Expired password was the problem. As always, anytime you install a new version of Mirth Connect remember to clear the Java cache. Kevin |
![]() |
| Thread Tools | |
| Display Modes | |
|
|