Remote desktop : error running Lisp

[hanslammerts]

Hi, i am experiencing the BASE.DCL error when running a .vlx on a remote

I can't get find a sollution for this error. Does this have anything do do with the fact that i run it on a remote desktop?

.. maybe AutoCAD gets confused about the whereabouts of my roaming profile..(?)

[rkmcswain]

Without regard for your RDP session, that error message is a good indicator that you are missing some support paths.

Have you checked the "Working Support File Search Path"?

[hanslammerts]

That is the obvious reason i checked

[hanslammerts]

Both 2017 and 2018 as new install gave me it. Profile reset did not help either

[rkmcswain]

While you are in a remote session, compare the "Support File Search Path" to the "Working Support File Search Path".

Any differences?

Base.dcl is located in %appdata%\Autodesk\<product>\<lang>\Support\

[hanslammerts]

Thanks! I will get back to you if that's it..

[hanslammerts]

No luck, both have C:\users\<user>\appdata\roaming\autodesk\<product>\rXX.X\enu\support  in support file.. and working support file..

[hanslammerts]

This problem is occuring on local machines in 2018 as well. Strange.

[hanslammerts]

Vlide opened in different AutoCAD versions (2017 / 2018) resulting in different behaviour when previewing the a DCL.

What's wrong?

john.vellek has embedded your image(s) for clarity

[john.vellek]

Hi @hanslammerts,

I am unable to do a RDP in my corporate environment but I will try tonight when I am on my home network.

Is it possible to share your lisp routine and the DCl file that is giving you  problems?

Please select the Accept as Solution button if my post solves your issue or answers your question.

[juan.c.ayala]

If you do a (findfile "filename") what does it return? Does it find the file or does it report back NIL?

[hanslammerts]

I could not run a .lsp or .vlx which has a dcl definition

I think i figured what could be causing this, is when AutoCAD is not run 'As Administrator'

Seem that it can't build a temporary .dcl file. As a matter of fact i can now run the .vlx programm on both 2017 nd 2018 machines locally

But not on the virtual machine. Could make sense, since i maybe not be able to run that as admin.

Can that be the case?

nb.

When i use the (findfile "lsp/dcl") command it indeed returns nil.

Both on local and virtual machines.

Is that a good thing or bad?

[juan.c.ayala]

Check your secureload settings. You may have it set to not run lisp files fi they are not in a trusted path.

When using the find file command, you need to specify the file name, not file type. Lets say I want to see if AutoCAD finds my DCL file named JAtest, I would enter (findfile "JAtest.dcl") in the command line. If it returns NIL then it can not find the JAtest.DCL file which would explain why its failing.

[john.vellek]

HI @hanslammerts,

I haven't yet had a chance to try the RDP on my home network but I am wondering what happens if you create a unique folder on the remote computer and add it to the support and Trustedpaths. Are you then able to run the routine that calls the DCL file?

For instance, create  a folder  called MyLisp on c: drive (C:\MyLisp) and add it to your paths.

I am wondering if the Roaming profile is what is causing this to malfunction.

Please select the Accept as Solution button if my post solves your issue or answers your question.

[hanslammerts]

---

@hanslammertswrote:

I could not run a .lsp or .vlx which has a dcl definition

I think i figured what could be causing this, is when AutoCAD is not run 'As Administrator'

Seem that it can't build a temporary .dcl file. As a matter of fact i can now run the .vlx programm on both 2017 nd 2018 machines locally

But not on the virtual machine. Could make sense, since i maybe not be able to run that as admin.

Can that be the case?

nb.

When i use the (findfile "lsp/dcl") command it indeed returns nil.

Both on local and virtual machines.

Is that a good thing or bad?

---

not the answer.

[hanslammerts]

---

@john.vellekwrote:

HI @hanslammerts,

I haven't yet had a chance to try the RDP on my home network but I am wondering what happens if you create a unique folder on the remote computer and add it to the support and Trustedpaths. Are you then able to run the routine that calls the DCL file?

For instance, create  a folder  called MyLisp on c: drive (C:\MyLisp) and add it to your paths.

---

I have the following path's assigned locally and let a .vlx run.

At this point is conclude it has little to do with the path definitions, dcl or lsp code.

It helps to be administrator, but it's not my cure here.

It concernes how the vlx behaves dealing with dcl support.

The fact that i test it on virtual machines is not really matter, because It doesn't work on other installs locally either.

It ONLY run on 1 install.

Here is the code which sets my environment and other stuff

It perfoms checks on paths etc.

The code

(load "C:\\_Data\\Heijmans\\AutoCAD_Tool\\support\\Heijmans_AutoCAD_2018.VLX")

runs it but dcl's defined in it are not working on other machines.

[hanslammerts]

@john.vellek. the company i work for has a kind of support agreement with Autodesk. Maybe this can be used to dive into this deeper?

[john.vellek]

Hi @hanslammerts,

I made a video that shows in both AutoCAD 2017 and AutoCAD 2018 (installed locally), a VLX file being manually loaded and run which calls a DCL and then runs the routine based upon the variables set in the DCL dialog. I do not see any difference between versions. Both applications have the same exact local folder added to the File Search Path and Trusted locations path.  In th evideo, the exact same VLX and DCL are being run.

Please try setting these manually as I suspect the lisp routine you shared to create the paths is failing somewhere in the process. You could add some prompt in your LSP to verify that each section is getting run.

I see in your subsequent post that you also have a support contract. If you would like to pursue that avenue, please contact support through your Account page.

Please select the Accept as Solution button if my post solves your issue or answers your question.

[hanslammerts]

I see it works at your end. I Will try to get this tru to support.

"Please try setting these manually as I suspect the lisp routine you shared to create the paths is failing somewhere in the process. You could add some prompt in your LSP to verify that each section is getting run."

Looking at the promptline i see the stuff is loaded and recogniced....

However, if i run the functions, ALL dcls 'inside the vlx' do not work. Picture shown beneith .

Working begin with *base.dcl * etc etc . So my questions are..

- how does vlx work with dcl 'inside' them?

[john.vellek]

Hi @hanslammerts,

Very good.  I will try to do this in an RDP session this evening as well. In the mean time, I encourage you to try setting the paths manually as a test to see if that resolves the issue.

Please select the Accept as Solution button if my post solves your issue or answers your question.