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. if they install the desktop on other pcs it works fine. we are using terminal services to link to the server for this.
ASI solution
Found this in an ASI techlet. Thought it might be useful to put it here, in case anyone else was looking for the solution. (In our case, I had to change the ASP.NET connection string.)
The "13 Type Mismatch" Error
When logging into iMIS 15, if you ever receive the error message “13 Type mismatch”, try the following items to resolve it:
* In IIS Manager, right click the iMIS 15 virtual directory > Properties > ASP.NET and make sure the .NET version is 2.0 and not 1.1. Then while still in the ASP.NET tab go to Edit Configuration and look at the connection string - verify that it's using the correct database server name. Now do the same for the iMISPublic virtual directory, then restart IIS and test iMIS.
* Try logging into the iMIS staff site via a web browser (ie http://myappserver/imis15 - replace 'myappserver' with your server name). Does that work? If not, do you get a different error?
NOTE - You can disable the custom error handler for more informative .NET error messages. To do this go to IIS Manager > Right click the iMIS 15 virtual directory > Properties > ASP.NET > edit configuration > Custom Errors tab > change 'custom error handler' to No.
* Check to see if the AsiWorkflow Service has started. It will show under Control Panel > Administrative tools > Services > AsiWorkflow15.
* Lastly, try rebooting the Application server.