invalid insertion point xref

invalid insertion point xref

Anonymous
Not applicable
2,902 Views
11 Replies
Message 1 of 12

invalid insertion point xref

Anonymous
Not applicable

I am trying to insert an x-ref file to a new drawing, but I get an error message I have never had before "invalid insertion point". So it won´t insert at all.

I've tried different path alternatives, change the value of the insertion point etc, but does not help. I can open the file itself without trouble. I do need the xref to arrive at its own coordinates, the rest of the drawing will depend on it. I've purged both new document and x-ref. Does not help.

After googling I cannot find the same issue, most seem to have got the x-ref into the drawing before they get an error-message.

I'm importing in modelspace, and do as I always do. So fairly confused now. 

Appreciate any advice 🙂

0 Likes
Accepted solutions (1)
2,903 Views
11 Replies
Replies (11)
Message 2 of 12

pendean
Community Legend
Community Legend
To work with Absolute Coordinates (#) Dynamic input (F12) must be on.

Or is the XREF from a newer ACA version (2018 and newer) and you are using an older version of ACA (2017 and older)?
0 Likes
Message 3 of 12

dbroad
Mentor
Mentor

Post a screencast or at least a command log.  Is the problem just with attaching a particular drawing?

Quote:

"most seem to have got the x-ref into the drawing".

Are others attaching the same DWG file? 

Are you inserting, importing, or xattaching?  

Architect, Registered NC, VA, SC, & GA.
0 Likes
Message 4 of 12

Anonymous
Not applicable

When I tried to find others experiencing the same problem, I did not find anyone. Those who had insertion point  issues are managing to get their files into the drawing before a message arrive whereas I never get that far even. I'm trying to attach an x-ref. Now I got another error message too. attaching that one as well even though I got rid of it again.

Thank you for your time!

0 Likes
Message 5 of 12

Anonymous
Not applicable

The version I use is ACA 20, so that should not be the problem.

I am not sure what you mean by F12 needing to be on? I pressed the F12 button and tried to import the file after, but same result. 

Thanks for your time!

0 Likes
Message 6 of 12

dbroad
Mentor
Mentor

When you get the error pop-up, move it so it isn't blocking the underlying dialog before using print screen. Otherwise, we can't see the setting that might be rejected.

Architect, Registered NC, VA, SC, & GA.
0 Likes
Message 7 of 12

pendean
Community Legend
Community Legend

So the problem is limited to this one top file then? it alone will not accept these XREFs but any other file, including a new file you create, will accept these same XREFs?

 

Have you tried to ensure none of your files have issues? RECOVER command on each and every one is a good place to start.

 

BTW, are you mixing DWG files with various scales? This is an unusual error message:

Capture.PNG

0 Likes
Message 8 of 12

Anonymous
Not applicable

Error message 2 AutoCAD_3.JPG

 

0 Likes
Message 9 of 12

dbroad
Mentor
Mentor

It looks like you entered 1,00 rather than 1.00 for the x-scale.  That doesn't work unless you are using a localization that uses the comma for a decimal point. Your other decimal points look like periods.

Architect, Registered NC, VA, SC, & GA.
0 Likes
Message 10 of 12

dbroad
Mentor
Mentor
Accepted solution

Thanks.  Once I blew it up, I have the same comments. You are using commas for decimal points in some locations. Use periods instead.

https://docs.microsoft.com/en-us/globalization/locale/number-formatting

Architect, Registered NC, VA, SC, & GA.
Message 11 of 12

Anonymous
Not applicable

I have until today not had a problem. But now when I try to attach other files as x-ref into a drawing, the same messge appear (just tried that), not just this file into the new drawing. 

I will try the rocovery command!

 

Yes, we usually use various scales. The architects draw in mm while we who work with the exteriors work in m. 

 

 

0 Likes
Message 12 of 12

Anonymous
Not applicable

Thank you!
I will watch out for that 🙂 
Today it worked, I didn´t change any settings, but probably it was the comma/period difference. I appreciate it a lot!

0 Likes