I have a DLL developed in VB running under one Component Services application on customers machines
The system uses MS Access reports. Basically the VB DLL opens an MS access report using automation, and sends it to a snapshot file. That all works fine and is installed on lots of customers server machines.
The Component Services application runs under a local user, not the system account.
That user has to have a default printer setup, otherwise access won't produce reports. The printer doesn't have to exist, we usually just set one up as a "hp laserjet 4L".
The problem is, on a couple of customer install sites, the process keeps forgetting its default printer and the MS Access automation software raises an error. Rebooting fixes the problem.
Has anyone else seen the problem where Component Services configured identity users forget their default printer ???