Error: Device Not Found When Using Overrides from SSM and DWGToPDF.pc3

[Jason.Piercey]

Using vanilla 2016, anyone else having same error?  2015 works fine.

Manually plotting using the pagesetup defined in the template works fine.  Using SSM overrides pointing to same template/pagesetup produces the error.

I'll have to go back to 2015 until this is resolved in 2016.

[thejac]

Crap, thought I had it, but broken again.  Your move Autodesk.

[SteveBennettTD]

We were getting the same "Device not found" error when trying to use SSM to Publish using Page Setup Overrides on a project upgraded from 2014 to 2016. The workflow works just fine in 2014, breaks in 2016. Ensuring the ootb 2016 DWGtoPDF.PC3 file was in our Plotters folder did not resolve things. Editing the DWT file used for page setup overrides to ensure it was pointing to the new PC3 file did not resolve either. The ootb PC3 file has no associated PMP file for us in both 2014 and 2016. Creating a new PMP file for the 2016 PC3 file and associating the PMP with the PC3 file made the error go away. Hope this helps...

[ahoffpauir]

Thanks i tired this and it worked for me. this has been a problem for me for awhile

[thejac]

Can you please give specific steps for what you did to fix it?  I tried what I thought you mentioned, but I still can't get it working.  Can you list folder paths, and what you did when creating the PMP please. We have our PC3 files on a mapped drive location.

Thanks

[ahoffpauir]

This is what I did I hope it work for you.

1. Delete both DWG to PDF.pc3 and DWG To PDF.pmp form you netowrk location

2. Copy DWG To PDF.pc3 from C:\Users\userlogon\AppData\Roaming\Autodesk\AutoCAD 2016\R20.1\enu\Plotters

3. Open the plot dialog box in Autocad, select DWG to PDF.pc3, and click properties.

4. Click  Modify Standard Paper size. Dialog box to save a pmp should apprear. Save the pmp file. If you have to modify the paper sizes do it now.

5. Dont noe filer paper paper sizes. ( I think filtering the paper sizes causes the problem)

6. Click ok and save both pmp and pc3 files

Batch plotting form both the sheet shet and the publish command should work now, aleast it work for me I hopw it works for you.

Alvin Hoffpauir, Cad Manager

Liftech Consultants Inc.

www.liftech.net

[SteveBennettTD]

The steps Alvin listed are essentially what I did, I went through a few extra steps. 

You can enter the following line in windows explorer address path and hit enter to go directly to the path Alvin lists in step 2.

%userprofile%\AppData\Roaming\Autodesk\AutoCAD 2016\R20.1\enu\Plotters

Here are the steps I took just in case you are looking for an alternate method...

1. Browse to %userprofile%\AppData\Roaming\Autodesk\AutoCAD 2016\R20.1\enu\Plotters
2. Copy the ootb DWG to PDF.pc3 (I did not find a matching PMP file) to your matching mapped drive location in your support folder paths.
3. I used an un-modified install of 2016 to edit my DWT file being used for the page setup overrides in the SSM project settings. I'm not sure if this makes a difference or not, if it doesn't work following this on a modified install of 2016, try it with unmodified.
4. In the DWT, enter Page Setup Manager, edit the page setup needed (we use DWG to PDF.pc3 as the device). 
5. Select Properties button (to right of printer selection pull down) for the printer device.
6. Select the PMP File option in list, then select Save PMP...
7. Save the PMP to your mapped drive location where the rest of your company standards live.
8. OK/Close/Save all the way out of DWT file so its closed.
9. Switch over to the modified version of 2016 that is configured to read all your standard paths and so on, open the DWT file for page setups and go back into page setups and modify the printer properties.
10. Select the PMP option in the list, click Attach... and select the previously saved PMP file.
11. OK/Close/Save all the way out of DWT file so its closed.
12. Try Publishing with Page Setup Overrides from SSM with a few sheets selected to see if it worked.

Hopefully, one of these methods works out for you and others!

[thejac]

I tried both of the solutions outlined, but I'm still getting the ERROR: Device not found message.  This is really frustrating, seems like they have broken this in several times in past releases. 😞

[Anonymous]

We are having similar problems at our office.  I have been going through extensive testing and figured out that if you go through the publish dialog box, and choose the Publish to PDF option (not the Publish to Name Page Setup), and choose the dwgtopdf.pc3 it WILL create a multi-sheet PDF.  But using the same PC3 file in a page setup override from the sheet set manager will fail every time.

[SteveBennettTD]

Sorry to hear that Jesse, I agree with you, frustrating! What I find frustrating is having to make a work around for something that, in my opinion, should just plain work. 

Are you on subscription? If so, I'd open a support ticket with Autodesk via your online adsk account and reference this thread. https://accounts.autodesk.com

[thejac]

Yep, that is what I am advising people to do as a work around. Have to make sure they have all of their defaults correct.  Highly annoying.

[thejac]

I saw a person mention they had a ticket filed regarding this and I was hopeful that I would find a viable workaround.  Since I can't get it to work, I'll file a ticket as well referencing this thread.

[ahoffpauir]

I filed a ticket on this before and Autodesk said they would address it with a hotfix or in the next service pack. When plotting using sheet sets, I used Publish to PDF instead of using overrides as a workaround. This worked, but all page setups within each drawings needed to be the same or I would have to replot those sheets. Most of my page setups were the same already, so it was a good workaround for me.

Alvin Hoffpauir, Cad Manager

Liftech Consultants Inc.

www.liftech.net

[itregistrations]

I also just filed a support ticket, hopefuly the more voices they get on this, the better the chances it will get fixed.

[SteveBennettTD]

Same here, would be nice to get closure...

[Anonymous]

I too just submitted a ticket (and linked it to this thread).  The louder we are the more likely the issue will be addressed.

[zalant · Accepted solution]

OK gang, try this!

Assuming that the Plotters folder you're using does NOT contain the 4 new PDF-related PC3 files, copy those files from the AutoCAD 2016 default Plotters folder and paste them into whatever is your current Plotters folder.

That should alleviate the 'Device not found' error. Here's why:

AutoCAD 2016's default PDF PC3 file is "AutoCAD PDF (General Documentation).pc3". This is a change from previous versions of AutoCAD. If this file is not found in the Printer Configuration Search Path by AutoCAD 2016, then Publish will error out. This is because Publishing using a Page Setup Override first loads the default configuration and then updates it from the named page setup. The act of pointing AutoCAD 2016's Printer Configuration Search Path to an earlier application's Printer Configuration Search Path means that there is no "AutoCAD PDF (General Documentation).pc3" found when Publish is attempting to load the default configuration.

I hope this works for you, as it did for me. Please give it a shot and post back here your results (if you get a minute). 

[Anonymous]

I was working with Zac, and confirmed that this does fix things.  All I had to do to make it work was to copy the file "AutoCAD PDF (General Documentation).pc3" to the folder named in my Plotter Configuration Search Path.

After 9 months of this not working, we now have a solution.  Thank you Zac.

[Jason.Piercey]

Beautiful! I also just copied the General Documentation PC3 file to my server based plotter folder and the error has disappeared using 2016.

[Jason.Piercey]

As a side note: creating a shortcut to the stock plotter folder and placing it in my server based location also worked.

[Jason.Piercey]

Anyone having issues with textmasks plotting as large black blobs, only on some sheets, and some pen weight issues after applying this fix? Neither of these have ever been issues for me but are now. Only thing that has changed is the modification noted here.