We have a custom service that we originally wrote for Server 2000. This service essentially performs some file manipulations, and then drops the finished product into a local user's (local to the server, not a domain user) default print queue, causing the document to print.
This service ran fine on Server 2000 (the service is run-as that local user), but on Server 2003, the printer portion of it fails (it still does the document processing).
The two items that have changed are:
1) Server 2003 instead of 2000
2) Active directory is now being used as the user registry instead of LDAP.
My gut feeling is that the service is now unable to work with this local user's profile; it may however, be something else.
Any ideas?
-Thanks
"I would rather have a free bottle in front of me, than a pre-frontal lobotomy..."
-Shrubble
This service ran fine on Server 2000 (the service is run-as that local user), but on Server 2003, the printer portion of it fails (it still does the document processing).
The two items that have changed are:
1) Server 2003 instead of 2000
2) Active directory is now being used as the user registry instead of LDAP.
My gut feeling is that the service is now unable to work with this local user's profile; it may however, be something else.
Any ideas?
-Thanks
"I would rather have a free bottle in front of me, than a pre-frontal lobotomy..."
-Shrubble
