Notifications
Clear all
Topic starter
We just migrated to a new database server and want to configure MIK for Patient Portal and Secure Messaging. We go into Server Setup and try to configure, and get a "Can't log in" or a crash. GE is still researching. The DB server is server 2012 and SQL 2012 standard.
Any hints?
Posted : August 23, 2016 5:56 am
the windows username used on that computer need access to the database.
try it.
i have had the same issue, ge could not figure it out.
Posted : August 23, 2016 6:02 am
We had an issue where it needed the fully qualified domain name for the server, rather than the short name.
Posted : August 23, 2016 7:23 am
Topic starter
Thanks for your quick replies! The "can't log in" error is gone, but serversetup still crashes. 🙁
Posted : August 23, 2016 7:43 am
In which part are you getting the crash? at the beginning or the setup of the MIK settings? or when it ask you for the Database username and password?
Posted : August 23, 2016 10:25 am
I have had this happen while trying to login with sa. I end up just using the Windows login to access the DB server instead. I know GE best practices suggest the use of sa here but they don't have an answer for when it just errors out. Windows authentication has worked for me every time. The best practices per Microsoft are to disable the sa account anyway. As David B wrote, the permissions need to be set in SQL for the windows user for this to work.
Mike Zavolas
Tallahassee Neurological Clinic
Posted : August 24, 2016 9:10 am
Topic starter
No joy! I finally got all the way through the security part where I put in the database credentials and then selected e-forms, then next to the Configuring the MIK NT Service screen, then it crashed with "Centricity Practice Solution DLL has stopped working"
Anything special for SQL 2012 that you know of?
Posted : August 24, 2016 9:44 am
Julie,
Try this:
1. Go to the Server where you have MIK installed
2. Open Registry
3. Navigate to HKLM/SOFTWARE/Wow6432Note/GE/MIK/MIK-AIG
4. Create two String Values as shown below and enter the appropriate values for each String
DBPassword
DBUserName
5. Stop MIK service and then Start service again
See if that works, I have seen MIK crash before for various reasons and this was one of them. Another thing is to make sure that when you run ServerSetup to get to MIK, you are Right-Clicking and selecting "Run as Administrator".
Hope this helps.
Posted : August 31, 2016 7:47 am
Topic starter
Thanks to all who replied. The main thing that seemed to make it stay stable was to move it off the DB server with 2012 and onto a machine with DTS and 2008.
Posted : August 31, 2016 8:16 am
