3 replies to this topic

[Steve Kiernan]

We use bus and task and use PROIV reports to report back down the API - so in most we have the output set to API, but in some we use RPTOPT to achieve this.

Occassionally, we experience the dreaded error in opening print file error in the event viewer application log, and the task just ends - we don't know which report we are in or even why we got the problem.

Does anybody know what we can, either to resolve the problem, or in terms of defensive coding to at least trap and report the error back down the API?

[Ian Blew]

I presume you're running on a Windows Server.

Does the "PROIV Server" service login as a local administrator, or is it set to use the LocalService account?

We have 100+ Windows customers, many of whom have had the exact same error message (just printing thorugh our application, not specific to just Bus & Task) . It's due to the fact that when running as LocalService, PROIV doesn't always have access rights to create print files - it depends how the Windows Server is configured and whether file access is restricted.

[Steve Kiernan]

Thanks Ian - yes, it's on a Win2003 server and it's a LocalService account.

I'm going to try to see if the client will change to a local administrator account and see if that works.

Do you have any experience of running as a local admin account? Does it remove the errors? Are there any knock on effects?

Steve

[Joseph Bove]

Steve,

FYI: We used to always setup our Windows sites to login as the administrator. There was a whacky Windows issue with the way that we did printing that required this.

We have never seen any issues caused by using the administrator account.

hth,

Joseph