1.1 to 20.1.19

2.1 to 20.2.26

2.49

iMIS 2017 SP A to SP U

However, there are potential Issues to watch out for: If you are patching the iMIS instance on some versions, you will get a JS script error on the home page of the iMIS Desktop client. You can work around this by removing the charts in the staff site and republishing the home page of the desktop client. There may also be some changes with the UI in the staff site after the patch, but these are purely cosmetic changes with colors and themes. Service Pack W may have issues running some iMIS specific database tools and maintenance utilities. You will have to run those procedures manually if it is necessary. At E-Tech, we have over 25+ years of experience with consulting, managing, and maintaining iMIS. Feel free to Contact Us if you have any questions.>

This patch cannot be applied to early adopter versions of iMIS, or the default iMIS 2017 release. If you are on iMIS 2017 you will need to have a service pack applied before the patch can be used. There are different versions of the patch for different versions of iMIS. If you are using iMIS 20.1 you must use the version of the patch for your instance. There are patches for the following versions:

• 1.1 to 20.1.19
• 2.1 to 20.2.26
• 2.49
• iMIS 2017 SP A to SP U

However, there are potential Issues to watch out for: If you are patching the iMIS instance on some versions, you will get a JS script error on the home page of the iMIS Desktop client. You can work around this by removing the charts in the staff site and republishing the home page of the desktop client. There may also be some changes with the UI in the staff site after the patch but these are purely cosmetic changes with colors and themes. This patch also requires and older security patch to also be applied first to iMIS versions 15.2 to 20.2.49 Applying the patch: Instructions on applying the patch are inside the readme file and are different for each version of the path. Generally, you just have to move the .exe file to the iMIS Net and/or ASI Scheduler directory and run the patch. If possible it is best to upgrade to SP V or newer, but if this is not possible the patch is essential to your iMIS security. At E-Tech, we are iMIS experts with over 20 years of experience. We share our expertise with users who are having any issues with iMIS through our contact at contact@etechcomputing.com. Please reach out for more information.>

actually happened. One of the first places to look is the Windows Event Viewer on the server the iMIS Application is hosted on. You can check for any application errors that iMIS encounters here. You may find errors related to the SQL server, or the web server itself. Make sure the error time matches up with the time you recorded when something went wrong. Next you can find the errors related to iMIS Desktop inside your own AppData folder under AppDataLocalTempasiTemp. There will be logs located there with information on things that may not have loaded or worked correctly on iMIS Desktop. On iMIS Desktop, you can sometimes have various script errors that tell you what the issue is. If the script error starts with line 0 character 0, it is usually related to permissions with the Internet Explorer browser. If you are applying a service pack or doing an upgrade, there will always be logs located in the folder that is created when you run those upgrades. If you are on the website and something is not working, then make sure the site, content and related items are all published correctly. You can check if something has been published correctly if there is no red bar next to the content or site in the staff site view when viewing the content or site. If the content has trouble publishing, you can always check under Rise->Maintenance->Publishing Servers->Error Log for any messages if it failed to publish correctly. This information will usually be enough for you to understand what issue is happening and how to proceed in order to resolve it. Sometimes, the error message is vague and non-descriptive and other times it will be obvious what the issue is. These are just the first steps to try when encountering an issue. For our iMIS expertise, please Contact Us should you need help troubleshooting common issues!>

With iMIS Cloud coming out soon, it’s looking like iMIS Desktop will no longer be supported by ASI. What does this mean for all the users still using iMIS Desktop? You’re going to run into some issues and bugs that are no longer going to get fixed. Of course, upgrading to iMIS Cloud may not be ideal, so if you are still using iMIS desktop here are some common issues and how to avoid them.

1. You want to open the system information for iMIS but did not log in. You have the information you need, but now the information window will not close when you click OK, and iMIS will not shutdown. When you try to exit, it will tell you to finish what you were doing.

The correct way to get out of this situation is to press the Esc button. This will close the login screen and then you will be able to close the system information window. You can then close iMIS or open the login screen again to login by clicking on “Logon->Logon to host”

2. Managing Batching under the A/R Tab. When opening a batch, it will be open on edit mode, but it will still allow navigation to other tabs. If you do not enter any input and navigate to another tab, it will glitch out and not allow you to do anything or close the application.

To resolve this, click the exit button to get the “you must complete or cancel your task” prompt and press the Esc button twice. This will cancel the editing mode and allow iMIS to continue doing other things. This issue may occur on other editing options and tabs so if iMIS is ever stuck in this situation the Esc button may get you out it.

3. Logging into a recently upgraded iMIS Desktop. You may encounter an error that tells you your iMIS application and database versions are different.

The first thing to check is to make sure you can log onto the staff site, then make sure iMIS desktop, the iMIS application and the iMIS database are all on the same version. If this is the case, then your issue is most likely the VirtualStore files for iMIS. These files are automatically loaded when opening iMIS desktop and the older version of iMIS has created those files. The simple solution would be to delete the iMIS VirtualStore files inside C:\Users\<Your Username>\AppData\Local\VirtualStore.

4. iMIS Desktop issues with Internet Explorer security settings. If you are getting script errors, unable to run reports, unable to view the pages or even unable to login, this may be due to various Internet Explorer security settings.

If there have been changes to the settings, a recommendation would be to reset them to the default settings. The higher the security the more things that can go wrong. If you want to be sure it’s not related to these security settings, turn the security to the lowest possible settings and try using iMIS desktop again.

BONUS: iMIS Staff Site Issue and Advice

We advise not to delete any communication templates you may use in the future. In iMIS any communication templates sent to the recycle bin are not currently able to be reverted through the staff site. Before you delete any communication template, make sure you really don’t need it. Otherwise, to restore it you will have to go into the database and update the DocumentStatusCode to 40 for the deleted communication template.

>