Link to home
Start Free TrialLog in
Avatar of TTechies
TTechies

asked on

SBS 2003 InAspi32 service failed to start

I just took over IT Services for a small business.  They are running a single Small Business Server 2003 on thier network.  I have been able to get rid of all of their errors in the event log except the following.  On every reboot an event ID 7000 is posted in the System event log stating "The InAspi32 service failed to start due to the following error: The data area passed to a system call is too small".  I have not been able to find any information on this error I am hoping one of the experts here can help.
InAspi32-Error.png
Avatar of Cris Hanna
Cris Hanna
Flag of United States of America image

Based on a google search, they must have some sort of copier/ scanner software installed on the server.   Find out what it is and then suggest you contact their tech support
Avatar of TTechies
TTechies

ASKER

They do not have any printers or scanning software installed on the server.  They use all USB printers hooked up to their desktops.  I also believe you might have searched for aspi32 and not InAspi32.  I doubled checked and made sure no printer ports or drivers were left by old printers and none were found.  Let me know if you have any other thoughts and thanks for the post.
No I searched in inaspi.sys  and found this link http://forums.kofax.com/viewtopic.php?f=68&t=8094  Here's a different one:  http://www.runscanner.net/lib/InAspi32.sys.html
My suggest would probably be to disable the service via Administrative Tools...and then see what's not working for the users.
I asked today and they said they have never had a scanner or printer hooked up to the Server.  Their server is racked in a locked cabinet in a Com Closet and would not make sense to hook a scanner up to it or printer unless they were networked and the client states they have only used HP laserjet printers hooked directly to the PC.  They also only have 4 PCs on the network.  I have looked over the server and have not found any issues caused by this driver.  I also went into the services management console and could not find the service that references InAspi32.sys.  In the registry it is located under HKLM_CurrentControlSet_Services_InAspi32.  It loads a driver from c:\windows\system32\drivers\InAspi32.sys.  I also went into harware manager and looked at hidden devices and could not find any device that referenced InAspi32.sys.  My only thought right now is that maybe it was installed from their last tech in printer mappings while using Terminal Servies.  The only option I see right now is to wait until I can take the server off-line, image the server, and then manually remove all references to the service from the registy.  Let me know if you have any other ideas.
ASKER CERTIFIED SOLUTION
Avatar of Cris Hanna
Cris Hanna
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I checked the properties and have included a screen shot.  It appears it does mention Initio ASPi32 driver for Windows NT.  After doing some research on that I found this PDF www.xeroxscanners.com/en/us/support/vrs/kofaxvrsinonetouch.pdf which mentions the InASPI32 driver on page 13.  I also found this website http://www.visioneer.com/vrs/ about Kofax VRS.  It appears to be a software that can go over scanned images and improve their quality, a so called Virtual ReScan.  Maybe their last IT tech had tried this software and it was not removed incorrectly.  So, it appears with you help I have found where it probably came from.  However, do you have some suggestions on steps to make sure of a complete and proper removal.  I usually image the server, then backup the registry, rename the file, search the registry and delete all references to the file, then reboot.  Let me know if that is the method you would use since there is nothing in the add remove programs referencing Kofax, VRS, or anything out of the ordinary.  I also installed the windows cleanup utility and found no unusual installs listed.
InAspi32-Properties.png
I think you're clean up strategy make sense
I will try this out this weekend.