Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
> From: Tony Hoyle [mailto:tmh at nodomain.org] > I'm guessing what's happening is that sspi_protocol.dll is > there, but you're missing a system DLL somewhere which it relies on. I know this particular problem's been solved, but... As a general tool for debugging such things, I suggest Filemon, available from http://www.sysinternals.com/ as free software. This allows you to watch all file operations by a specific process, including DLL opens. Look out for failed file opens. That site is, in general, an excellent resource for sysadmins and developers. Other highlights include a similar tool for monitoring registry accesses, a way of capturing blue screens of death for analysis, and a cornucopia of similar stuff. Some of the bigger packages are now only available for a fee, but the small stuff such as filemon and regmon remain free. - Peter