Thanks Hank and Dragan,

Yes it is "Run with highest privileges"

>re: security
>
>Exactly: is the task being "run as administrator"? There's a checkbox for that.
>
>>>>>I am using the wonderful tool by Marat Chariev, Frx2Any.
>>>>>I had occasion to rebuild an exe which uses it and now that app throws an exception:
>>>>>Error #125 in program ANYPRINTER.INIT on line #0
>>>>> Printer is not ready.
>>>>>
>>>>>Frx2Any.app and the companion iSEDQuickPDF.DLL are in the root of the application.
>>>>>the application is run via Task Scheduler.
>>>>>it starts up in the sub folder with the path fully qualified to the root.
>>>>>
>>>>>nothing of substance has changed in the app from the previous version to this new one other than insuring a date not be null.
>>>>>
>>>>>any clues?
>>>>
>>>>Is there any printer installed, and if, is the default one online, connected ,etc?
>>>
>>>Thanks Lutz,
>>>
>>>If this were an isolated application i would be looking to issues with the printer. However there is a (shall we say) Flag Ship application which uses the same instance of Frx2Any and sharing the same folders and files and this application has no issues generating PDF output. The only real difference, other than the size and scope, is that the Flag Ship is run from a shortcut on the desktop.
>>
>>This smells of security police meddling. A scheduled task runs under the environment assigned to the account whose credentials it uses. Now if it doesn't start in its exe's folder (and then doesn't find the dlls - but I guess this would have happened long ago then), or if the accounts doesn't have proper rights over the folder where the .pdf is to be created, or it lacks some other permission... well, that's what I'd check first. Quite possible that the administrators have checked the rights of various accounts, and these accounts used mostly for scheduled tasks are somehow their favorite victim, as they are forgotten first and look like a security hole. I've had a similar utility running (another doc-to-pdf converer) in various large environments, and had this happen several times.
>>
>>In your case, also possible that they marked the previous version as okay and now this new version is suspect, so just restrict its rights until verified - and of course you wouldn't know that because these guys just do it and tell nobody.