DMS closes when scan is pressed

Nobody has anything to say??? HELP!!!!!!!!!!!!!!!!

You might try calling technical support first in the future as they can probably troubleshoot this better.

That error corresponds to the WIA Device Manager. StiSvc is also another name for the Windows Image Acquisition (WIA) service. The message says, though, that WIA is enabled and running. It could be a bogus error and that something else is the problem, or perhaps one of the WIA devices has a service of it's own, like the Fujitsu we use creates a service of it's own. That maybe when WIA was trying to initialize the WIA device, that WIA device tried to start the driver's service and the driver's service failed to start for whatever reason which would have cascaded that particular "service cannot be started" error back up through and made it seem like WIA couldn't start, when in reality, WIA itself did start, just one of it's drivers failed. My recommendation would be to uninstall all scanner drivers, uninstall and re-install DMS. Then run DMS and go to the Scan screen and see if you get the message that DMS could not find any scanners. If you don't see that message, then there's still some scanner driver installed or maybe partially installed or something like that that's messing up the system, or it's actually something wrong with WIA itself. You might also check system policies to see if the user in question has access to WIA (I'm pretty sure that's something you can turn off in policies, but I'm not exactly sure where the setting is). Anyway, so if you get the "no scanner installed" message, then go through an iterative process of closing DMS, installing the latest version of one of your scanner drivers, re-opening DMS and going into the Scan screen, until you've re-installed all your scanner drivers and everything is OK, or you find which driver is messing up.

Actually, the problem did turn out to be an previous scanner's driver. Only thing is is that scanner was a only installed on this system because it was part of an HP AIO that we installed the driver for remote access from this other guy's system.
That printer DIED about the same time as the error started popping up. Only thing is, this person rarely remoted in anyway so still can't figure out what difference it made to DMS opening. Uninstalled old printer's driver (since no one else remote has one like it anymore). and the problem appears to be fixed.