Using Microsoft.Ink in ASP.NET on Windows Server 2008
I am developing an ASP.NET web application. The site generates PDF files containing images of handwritten content (signatures, etc.). Bitmaps are created by some of the methods of the Microsoft.Ink library, converting MS Ink data (generated on a tablet PC and transmitted to the site.).
Now it works like a charm on my Vista development machine, but not on the production server, a 64-bit Windows Server 2008 machine. There is some unmanaged code for Microsoft.Ink beyond the .NET compilations that I deployed. So I installed Tablet PC SDK 1.7 on the server, but I still get some COM component errors in ASP.NET (COMException 0x80040154):
Retrieving the COM factory class for components with CLSID {937C1A34-151D-4610-9CA6-A8CC9BDB5D83} failed due to the following error: 80040154.
I read that Windows Server 2008 R2 has the ability to install handwriting recognition . Is there a package for Windows Server 2008? I have searched on Google but I could not find a solution.
Thank!
source to share
Have you tried recompiling for x86 only? You may find that one of the components is 32-bit and incompatible with 64-bit code. I recently had a similar experience when I upgraded to a new laptop running Vista 64-bit - a project that used to compile just wouldn't get bigger. It turned out that the Crystal Reports components in it are only 32-bit and will not work with 64-bit code. I changed from "Any Processor" as the active platform of the solution to "x86" and it worked fine. Unfortunately, this means that your application will not fully utilize the 64-bit capabilities of the server, but it will work.
source to share
I did a bunch of google posts and found this post on another group. I don't know if this will help you, but here it is ...
On a 64-bit Vista environment, as Steve Goodwin says in his post, WISPTIS.EXE is not available in C: \ Windows \ SysWOW64 \, but it is in C: \ Windows \ System32. I copied it and heck it finally works.
This is a long shot, but there are other comments in the thread with other ideas for different operating systems. but it won't immediately become clear why I decided to post something from this group, since your mistake is not mentioned. here is how I got there.
I first looked at the CLSID you listed above. I found that this leads to results indicating that the file associated with the registry setting is WISPTIS.EXE, so I searched for it and came up with the fact that WISPTIS.exe is a Snipping tool ... So there was more a few pages of searching I go to this which most likely I need ONLY because I have had enough trouble with my Vista 64 bit looking for files in the wrong location, which looks like the likely culprit.
Anyway, here's a link to the thread where I dug this answer.
http://adilhindistan.blogspot.com/2007/07/vista-snipping-tool-error.html
source to share