User profile in target not loading

[simon_m_harris]

Is there a known issue with loading user exported profiles from the target in properties dialogue?

we dont seem to able to get a profile that has been exported from one station to then load on another station either via network or copying the .arg to the station itself, has anyone experienced this issue?

Maybe my target text has an error?

"C:\Program Files\Autodesk\AutoCAD 2023\acad.exe" /product ACAD /language "en-US" /p "C:\Users\xxxx\Desktop\2023.arg"

This workflow has worked for us for a number of years in the past and i am not sure what has changed

Thanks

Simon

[Johanna_Esteban]

Hi @simon_m_harris, 

Can you share your profile for test?
In my experience always works well.

[Valentin_CAD]

@simon_m_harris ,

Try the suggestion from this link:

• Default profile loads in AutoCAD instead of a custom profile

[simon_m_harris]

Thanks for the replies, 

@Johanna_Esteban i have attached my .arg file, i think the file in itself is ok, as i can import it and set current and the profile change is visible (this .arg is a basic profile change purely changing background colour to blue as a tester)

@Valentin_CAD i have tried the topics in the article but to no success.

This seems to be an issue with trying to load a profile from the target box?

Our workflow that used to work was to create profile on one station then export to a network location and then set the target of the other stations to the network location and then the profile would be able to be used, this worked fine up unitl ACAD 2020.

[simon_m_harris]

Im currently testing this on a fresh/clean install of autocad 2023.

[cadffm]

Color setting is pretty ugly, but it works without any issue,

I opened my 2023.0.1 with your *.arg and the <<unnamed profile>> was the current one.

Note: It doesn't sound very clever to use a profile with the standard name "<<unnamed Profile>>"

1. It is not a well name

2. In  most cases like a standard installation there is already a Profile with that name

and you start switch /p loads the *.arg file only, if no profile with the same name (<<unnamed profile>>) is present.

Change the profile name to a more sensful and think abou that the start switch loads your arg just one time,

one time = every time while there isn't a profile exist with that name.

[cadffm]

---

@simon_m_harris  schrieb:
Im currently testing this on a fresh/clean install of autocad 2023.

---

In that case it is clear: There is a profile with the name <<unnamed Profile>>,

in this case AutoCAD doesn't load the *.arg file (because the profile name is also <<unnamed Profile>>)

It works in 2023 the same way as in the last 22 Versions before.

[simon_m_harris]

Could you try the new attached arg? this has its own profile name '2023_new'

Not sure how the last one i attached had the profile name <<unnamed Profile>>

[cadffm · Accepted solution]

Same..

I kstarted my 2023 with that 2023_new.arg file and AutoCAD loaded the Profil 2023 as current one.

Here is my string

"C:\Program Files\Autodesk\AutoCAD 2023\acad.exe"  /product ACAD /p "d:\2023_new.arg" /language "en-US"

Perhaps your problem is in the point you hide... "C:\Users\xxxx\Desktop\"

Test it again on your side, this trime

1. Make sure there is noch profil "2023_new" in your 2023

2. Move the 2023_new.arg file into a folder what are not on the network, not controled by a cloudserve like onedrive  or others,

for example: Move it to c:\temp

Edit the path to your arg what is now c:\temp\2023_new.arg

and try it again.

[simon_m_harris]

@cadffm when exporting the profile i need to 'add to the list' first so it gets its own 'name' and doesnt adopt the <<unnamed Profile>> title in the export.

I dont remember having to do this prior to 2020 but maybe i did it without realising in autopilot!

Thanks for all the replies,

Simon