Cannot Create PDF Files

you have to install acrobat from the console or use:
mstsc /console to log in to the console remotely.
If you install it from a session it will not work.

Comment by VND (http://www.vndx.com)

I manage 2 ASP (1500 Microsoft Environments) with Win2K/Citrix XP FR3 and another brand new W2k3 R2/PS4 and this situation still exists with Adobe Actobat 6 Professional. I have realised that porting to desktop and to my documents, Test Page is correct from ICA/RDP session. In the other hand, if I map a network drive Z: for example, my test page looses I dont know where, but I go to server console, acceding by DameWare and I use to find Distiller in the Task Bar running, trying to find specific path.

Does anyone know which path is Adobe trying to find.

The only one way to print to network drive is to open Word/Excel and convert it throught the add-in Verisigned macros included with Microsoft Word first execution over citrix/terminal server profile or console/xp new profile.

Besides I find myself in your situation, all I can do is invite you to a coffee if you come to Barcelona.

Can e-mail me to: javier@itconsult.es, web: www.itconcult.es

NOTE:

To whom it may concern from "Adobe Corporation", you have a real bad solution. I deploy hundreds of applications and I hope that Acrobat 8 may be better, because we're all in false.

XVC, Barcelona, Spain
MCSE Security CCA Citrix

having issues as well when we remap 'my documents' to a network location under WIN XP. Acrobat simply falkes because the program is coded to add an extra \ to the path, as described in this text i found on this adobe 'in design' forum. (truuth is i find that it really applies to ALL adobe programs more or less.)

"In Windows 98, Me, 2000, and XP, InDesign saves files to the My Documents folder by default. When InDesign saves files to the My Documents folder, it adds a trailing backslash to the path ("\"), followed by the filename (for example, C:\My Documents\\filename.indd). If the path to the My Documents folder ends in a backslash, InDesign can't save files because the two backslashes break the path to the folder. Targeting the My Documents folder to its default location ensures that the path doesn't end in a backslash."

so what if my 'default' location is a 'my documents' folder that is remapped to a drive other than the C:\ drive?

it just won't work, reliably. sometimes yes, sometimes no. when it fails it just stalls the acrobat assistant.

Dear Adobe: This isn't a very unusual circumstance - for network administrators to remap users 'my documents' folder. your software should work with that without issue. as it is with version 6.0.4 it does not do this reliably and it's causing a lot of us network oriented types a lot of unecessary headaches.

please fix this. as a matter of fact don't specify the default locations, don't even use the last location saved to option. simply give us a blank line with an empty location when the save or save as command is called.

let us choose, that is good software design.

OKey, I have the same failure.. This is what I have found out:

No one using Terminal Services are having "My documents" at the lokal TS/Citrix Server. They redirect it to another location on the network.

At my company we have the "My Documents" folder redirected to the network drive mapped as P:.

The interesting part is that whereever you try to print using the default Adobe PDF Port (my documents\*.pdf) The destiller shows in my case "P:\My documents". I do not have this "My documents" folder on my P drive (every users personal drive), because its much more convenient to have them directly on the root of P.

So I tried to create a new Adobe PDF Port printing to local disk C:\Temp (Actually I remapped using Citrix, but thats not important here)

Then when trying to print it says: "P:\C:\Temp". So anyway you try, Acrobat puts the value for your "My Documents" infront..

My solution was to create a "My documents" folder on each users "P:" drive.. Worked!..

Hope you find this information usefull, and if someone comes up with a registry fix or configuration fix, I'll be happy to here from you..

Best Regards Christian Alexander

I'm getting the same error.... Anyone know how to correct this... problem...? Would appreciate any help... Thanks....

Are your users able to write to the desktop?

Sabian

Rocky,

When I experienced this issue I was running it as an Application server.

Jon

With WTS... is anyone running as an Application Server? If not, then give it a try.

Rocky

Hi!

I've ended up completely removing Acrobat 6 downloading and installing a free pdf file creater that is working without problems - cute pdf writer 2.1, you also need to download and ghostscript first. It's had no problems and is a lot faster and less memory intensive on the servers as well. Go back to acrobat reader 5 if you can as well - acrobat reader 6 is a bloaty pig on a terminal server.

Karen