The April 14, 2011 update related to the Fax Cover Sheet Issues documented in the recent security bulletin have broken an application called vservice.exe which is part of SCO Termvision (a terminal emulation program). The vservice.exe program checks for licenses and also authorizes the terminal emulation client itself. Now from my perspective a Fax update should not affect this program at all, however when KB2506212 is installed the vservice program will execute and run but will not load properly (no splash screen on loadup) and the terminal emulation program will not function. When KB2506212 is removed the application works perfectly. This is confirmed in windows XP SP3 and windows 7. Windows XP does present an additional error about unable to connect to WWCOMMS database but this error does not appear on windows 7. I realize that termvision is a totally dead product (along with SCO for the most part) but a fax update still should not affect an application that has nothing to do with faxing, so to speak. If anyone could shed some light as to what is going on in this situation or if i am just stuck hiding updates and praying they do not release one that superscedes it and breaks the application again.

Does the other app rely on a dll that the fax update is changing? I'd call 1-800-microsoft or 1-866-pcsafety and work with Microsoft to see if there's a fix.

Hi, According to your description, your program vservice.exe of SCO Termvision does not work after installing KB2506212. Remove this KB will solve the issue. That seems this KB has incompatibility issue with your program. Since SCO Termvision is not the product from Microsoft, I suggest to contact SCO for further help. Furthermore, in order to use that program properly, you can temporally remove that KB. Thank you for your understanding. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, Did your issue solved? Please feel free to give me any update. Thanks. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, We had the same problem with dbserve.exe (Xvision) and found this solution: 1. Uninstall patch KB2506212 2. Copy ( don't move) file C:\Program Files\Common Files\Vision\dbserv.exe to C:\Windows\System32\ 3. Restart machine to apply patch again, might take a while before the wsus has updated the machine again. XVision should now start again Might work for vservice.exe as well Regards

Well for right now all the customers are removing the kb2506212 update and hiding it in windows update. How to restore functionality was not really in question here, I am more concerned about a "fax" update breaking applications that are not related to faxing at all. Better yet is the last response by Peterpilemalm, if it was as simple as a "fax" update then this workaround should not work at all. Though his solution does make me suspect that the update also does something to the execution of tiles in the "common files" directory in windows 7. there is something similar in XP i just remember it off the top of my head. I am trying this on my home PC today and will let you know if it works.

Hi, We had the same problem with dbserve.exe (Xvision) and found this solution: 1. Uninstall patch KB2506212 2. Copy ( don't move) file C:\Program Files\Common Files\Vision\dbserv.exe to C:\Windows\System32\ 3. Restart machine to apply patch again, might take a while before the wsus has updated the machine again. XVision should now start again Might work for vservice.exe as well Regards Hi, We're experiencing the exact same problem with XVision in our company. We'll test this "workaround" and let you know if it works. Just for curiosity sake, where did you find this solution? Regards

Hi, Copying dbserve.exe didn't work for us, but we found a fix, compatible with KB2506212 installation, by copying the old versions of mfc42.dll and mfc42u.dll to the C:\Program Files\Common Files\Vision folder. For Windows XP, these files are dated 2010/09/18 and located in: C:\WINNT\$NtUninstallKB2506212$ following KB2506212 installation, or C:\WINNT\system32 prior to KB2506212 installation. Reboot to launch vservice after file copy. Note: we have vservice launched at PC boot. If mfc42.dll is called by some other program prior to vservice, then vservice may use the already loaded updated version from system32 and fail. Haven't tested this scenario. Hope this works for you too.

mdj2011, I will have to try your answer but it seems the most logical. I also have the vservice file running at bootup (startup item in start menu), though I would say that updating those core dll files is a bit more than a "fax cover page update." If it works, I will come mark your answer. I am encouraged though. I also did try the suggestion of copying the vservice.exe file to %windows%\system32 and that did not work. sorry to say.

Hi wirefire2002, Did your issue solved by the suggestion of mdj2011? Please feel free to give me any update. Thanks. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi there, We tested, copying the file from C:\Program Files\Common Files\Vision\dbserv.exe to C:\Windows\System32\, but XVision won't start. Regards

Hi, Copying dbserve.exe didn't work for us, but we found a fix, compatible with KB2506212 installation, by copying the old versions of mfc42.dll and mfc42u.dll to the C:\Program Files\Common Files\Vision folder. For Windows XP, these files are dated 2010/09/18 and located in: C:\WINNT\$NtUninstallKB2506212$ following KB2506212 installation, or C:\WINNT\system32 prior to KB2506212 installation. Reboot to launch vservice after file copy. Note: we have vservice launched at PC boot. If mfc42.dll is called by some other program prior to vservice, then vservice may use the already loaded updated version from system32 and fail. Haven't tested this scenario. Hope this works for you too. Hi mjd2011, This workaround worked out perfectly! Thanks for the help. Cheers!

I’m glad to hear that the workaround worked for you. And I will mark his reply as an answer, It could help other communities here who have the same issue. Thanks for your understanding. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.