We have changed our SQL Server sa password in our iMIS 15.0.3 database. User logins to the back office and web\public view components no longer worked. Found and changed the sa password embedded in the IIS Virtual Driectories \iMIS15 and \iMISPublic in the .NET configuration. Also changed in the ODBC connections to test out the connection, though appears that it would be the user's invidual credentials that would be used to authenticate through ODBC . The web\public views logins now work. The back office login still does not, still invalid sa password error. Is there somewhere else that the sa password is embedded that needs to be changed?

this should be very simple. I install iMIS on the internal server, desktop, casual i15 and public i15. everything is working great. when i log in to the server and log in to iMIS desktop it works great. public view and casual work great. when someone else logs in to the server they get the type 13 mismatch error on the desktop although the other 2 work fine. the desktop on this server works only for my log in.

Hi all,

I was wondering if there is an option to enable E-mail redirecting to a single account to prevent Customers in the database from receiving test E-mails?

Thanks.

I am trying to install an iMIS15 eSeries site and continue to get the MembershipWebservice Error when I login.

Any ideas what I left out?

Thanks,
Terry

I upgraded my iMIS 10.6 VM image to iMIS 15. Everything works except for email. I discovered the smtp services were not installed and installed them. The email feature is still not working preventing the web components from working. Anyone knows what is missing. I'm sure this is a windows configuration issue.

We are going to deploy iMIS15 for this first time in our environment. We are leaning towards a terminal server clustered environment for about 90% of our users.

Has anyone ran across issues deploying/running iMIS15 in a clustered terminal server environment? Can anyone give us an example of the load balance they are using on multiple TS boxes.

Mark Pellicore

Over the last 18 months or so as we have deployed the iMIS .NET server at clients and then tried to roll out components like IQA, etc to certain users, we (sorry, I wiped out the authors name accidentally) have experienced a variety of environment-related problems to which we have employed a variety of environment-related solutions. I was hoping that somewhere there existed or we could create (here perhaps) a definitive list of things to investigate / try when the rather inexpressive iMIS .NET error page pops up.

Is your training database still using a copy of data from last year? No-one got around to refreshing it with a current copy of your iMIS production database.

Spend an hour to refresh your training database with current data. Then write up some steps so that you can make sure it gets done more regularly in the future.

Steps to complete:

TBC

Of course you know that you can customise the home page of iMIS. In fact, iMIS ships with a number of example executive dashboards that give you some ideas.

But for many users it becomes a habit to skip straight past the home screen and onto the day's work.

Why not put up a new home page executive dashboard (or even your very first one) - something a litle different? Change the colours?

Attention: iMIS System Administrators, iMIS Technical Staff and iMIS Consultants

Have a spare hour or two, or is it raining outside so you have some time to spend on iMIS instead?

There are many things you can do to tune iMIS with an hour, or just a few hours, of time.

But what exactly would you do?

These book pages are designed to give you some ideas, and each one is planned to include a checklist of the specific action steps you should take to complete the steps.