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.

Things that I have seen our team do include (some of which are documented):

• Add the .NET server to the trusted sites on the client browser(/li>
• Change the cookie security to a lower setting
• Change to .NET server URL in imis system setup to an IP address due to issues in the environment with Domain name resolution
• Turn off pop up blockers for the domain with imis .NET
• Other

These are things CSI has seen work:

• Make sure IIS is running .Net 1.1 on the .NET Website
  1. Typically, this results in a white screen when logging onto iMIS
  2. Right click on your website and if you have an "ASP.NET tab, make sure it is set to use version 1.1, if not change it. If you do not have an ASP.NET tab run the below command
  3. Run aspreg_iis.exe -i from C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
• Make sure IIS allows .NET to be running in the extensions list (IIS 6.0 only) - This can also result in a blank screen
• If you get a "Server Error in 'XX' Application right click on your iMIS.Net install in IIS, click Properties, and click "Create" on the (Virutal) directory tab if you have a create button.
• Make sure your server name does not have in underscore in it, if it does and you run DNS you can change your server name, by making an alias to your server without an underscore, and either editing a couple of files to the new server name (do a search for your old server name) or reinstall iMIS.NET
• If you can get into iMIS and everything looks kind of strange, and you are missing the IE Web Controls
  1. They are located in "InetPub\wwwroot\webctrl_client"
  2. If they are not there, install them from the iewebcontrols.msi file located on the iMIS.NET server CD
  3. If after installing them, you still cannot see them, make a virtual directory in the root of your iMIS.NET website, call it "webctrl_client" and point it to the webctrl_client directory in Inetpub\WWWRoot
• In IE: Change Trusted Sites security to low by clicking Custom...Selecting Low, Clicking Reset, and then clicking OK twice
• In IE: Make Sure "English (United States) [en-us]" is the first language listed in Tools...Internet Options Languages... (if it is not there add it and make it the first in the list)
• Don't let anyone tell you that installing Framework Version 2 over 1.1 on the clients or the server will cause issues, 1.1 can exist side by side with 2.0

If there is already a definitive list, could someone please point this to it. If people have more detail as to why one or more of the above work, please add relevant pages. If there are more things to try, please add them

‹ New Custom Tab Feature in 10.5up