Assistance with (command "-PUBLISH" [filepath]) Routine

[lfrost]

Hello All,

I've been creating LISP routines now for 3-4 years and never experienced what I'm about to describe. I'm hoping someone in our community here can help.

Out of the (11) work stations, including my own, there is (1) work station which is failing to perform the (command "-PUBLISH" [filepath]) routine. What happens on this work station is as follows:

1. The lines of coding feeding into it complete (at 100%)
   1. Part of the code leading to the "-PUBLISH" line is the creation of a DSD file that outputs a filepath for the "-PUBLISH"
2. When (command "-PUBLISH" [filepath]) executes:
   1. ACAD "twitches" as it would any other publish routine (manual or automated via LISP)
   2. The publish progress dialog pops up
   3. Screen flashes as if it's about to begin the publish process
   4. The publish dialog disappears and no files were ever opened; PDF never created
3. Rest of LISP executes in its entirety with no issue (at 100%)

When I use the same DSD file created prior to the "-PUBLISH" operation manually in the PUBLISH command, it works perfectly fine. Secondly, it was working on his work station some 6-8 weeks ago when he last used the particular routine.

Also, this work station will perform as described above using the (command "-PUBLISH" [filepath]) approach on any DSD file. It's not just the DSD file created by my LISP earlier in the code.

To provide some feedback on the experiences outside of ACAD and to elaborate on why I'm stumped on this one:

This user is also very... To be frank, computer illiterate. He does nothing but figure out ways to break not only my LISP, but other applications on his work station as he is one of the rare users who will go through press every button, change every setting, uninstall/reinstall twice, and much more before he asks for any assistance in the matter.

I state all of this because I feel like it's something outside of LISP. When he uses his work station, he manages to make Windows unable to completely shut down almost every night. However, when I or other users use his station... It shuts down perfectly fine every time.

Unfortunately, I cannot share the code. Am I maybe missing a variable that I've never had to contend with before? Something that would make publish work manually but fail via LISP? I have FILEDIA and the BACKGROUNDPLOT flipping off upon initialization so it publishes without any user interaction.

Please provide any feedback you can on the subject. I'm hoping someone out there has experienced this issue in the past and know show to resolve it.

[maratovich]

A background publication may be included.
This was checked?

[lfrost]

Thanks for the quick response maratovich, but unfortunately yes it was.

The LISP routine is putting publishing in foreground and there were/are no background plots at the time.

[cadffm]

First: Check the product version, is it the same like the other 10 stations?

command: _vernum

"there is (1) work station which is failing to perform the (command "-PUBLISH" [filepath]) routine. "
"The publish dialog disappears and no files were ever opened; PDF never created"
So, what say the publish-log? command _VIEWPLOTDETAILS



"When I use the same DSD file created prior to the "-PUBLISH" operation manually in the PUBLISH command, it works perfectly fine. "
And when you start your intern routine with this prior created DSD?
What happen if you try it in commandline with (command "-PUBLISH" "D:\\mypath\\my.dsd") ?

[lfrost]

Good quesiton CADffm,

It's a variety of various versions as well as ACADs (vanilla ACAD and ACAD Mechanical, years 2017 thru 2019).

This particular user is using ACAD Mechanical 2019, but another user is using the same product and version without any issue.

[maratovich]

Your Lisp creates a .dsd file
Have you checked this file?
What's inside this file?
Attach your .dsd file

[lfrost]

maratovich,

Everything you'd find in a DSD file if you were to save a publish list manually. At least, I used a saved DSD file from 2017 to create the current DSD structure.

I attached one of the DSDs (renamed to a txt file for the site) I used in the debugging of his station. Note that this same DSD was able to be used on all other work stations.

A key note to make about the DSD:

I created a DSD manually via AutoCAD's publish dialog. Running (command "-PUBLISH" . . .) on the saved DSD file results in the same behavior.

[cadffm]

And my other question? What display the publish-log after your commandline test with (command ....) ?

[lfrost]

That's actually a really good question CADffm,

I just ran another test on it and it doesn't create a log. I didn't think much of it because it wasn't there to begin with.

One thing funnier about today rather than yesterday and Friday is that I couldn't even execute the (command . . .). It was generating one of the "error:  <#sub....>", or whatever the crazy error message was reading. Unfortunately, ACAD fatal error'd prior to me capturing a screen shot on my 2nd attempt at the code. Upon restarting, it was acting as it was noted in my original post.

[lfrost · Accepted solution]

Sorry for the late delivery on this conclusion post,

So, it turns out some ACAD files/drives were corrupted and only a uninstall/reinstall would properly repair the issue. To make sure, we installed AutoCAD 2019 on the individual's machine with the code unchanged and it worked flawlessly as it had some weeks prior to the issue described in the post.

We uninstalled and reinstalled... It works fine again.

Thanks for everyone's time and assistance on the matter!