Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 4262 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Adobe Acrobat failing to print to network share

l8rg

When I try to print to the Adobe PDF printer (aka convert something to PDF via the printer interface), it gives an error in the queue if the file is being saved on the network drive. If I instead provide a local path, the file "prints" fine.

After much troubleshooting with Adobe and on my own I have discovered that the problem is somehow related to Sophos.

If I go into msconfig and I disable all services that relate to Sophos, and any startup items that relate to Sophos...   i am now able to print to network shares....

As soon as I enable the sophos services, I once again can no longer print and adobe pdf file to a network share.

Any ideas how I can fix this problem?

:36185


This thread was automatically locked due to age.
  • 0

    Hello l8rg,

    is this a managed installation and is Data Control enabled? What is the error you get (and do you get any message from Sophos)?

    Christian

    :36187
  • 0

    managed installation? yes i believe so

    we have the enterprise console installing the software... we also install manually sometimes from a package we created...

    data control enabled? yes, but it only looks for credit cards or social security numbers

    no errors from sophos, no notifications...  just notice the print job fails.  when i disable sophos... it doesnt fail

    :36195
  • 0

    actually... the checkbox for Enable data control scanning is not checked... so i dont think its actually scanning but there is a policy

    :36197
  • 0

    Hello l8rg,

    if the polocies are applied from the console it is a managed install. so i dont think its actually scanning but there is a policy The enabled/disabled is also part of the policy (but can be locally overridden). Desktop messaging is also part of the policies so you might not get an alert on the client even if Sophos "knowingly" intercepts the write.

    Turning off  "everything" just shows that Sophos is somehow involved but won't get you to the bottom of the problem. An intentional action by Sophos should usually result in a message to SEC, an entry in the applicable log and the Windows Application Event log. I'd also expect and error from the application and/or Windows.

    If there is apparently none I'd give Sysinternal's Process Monitor a try - I'd start with activity on the desired output file, if this doesn't help then file system activity of the Adobe process.

    Christian.    

    :36217