Results 1 to 3 of 3

Thread: Bad Argument

  1. #1
    100 Club
    Join Date
    2001-11
    Posts
    162
    0 Did you find this post helpful? Yes

    Default Bad Argument

    I have the following errors after opening AutoCAD 2009.
    How can I locate the files which has the errors?
    Windows Explorer could not locate the word "lentityp nil" or "stringp nil" with the the "A word or phrase in the file" option.

    ERRORS:
    AutoCAD menu utilities loaded.; error: bad argument type: stringp nil
    AutoCAD menu utilities loaded.Loaded...; error: bad argument type: lentityp nil

  2. #2
    Certifiable AUGI Addict ccowgill's Avatar
    Join Date
    2004-08
    Location
    Hartford, Michigan
    Posts
    3,095
    0 Did you find this post helpful? Yes

    Default Re: Bad Argument

    Quote Originally Posted by omorah View Post
    I have the following errors after opening AutoCAD 2009.
    How can I locate the files which has the errors?
    Windows Explorer could not locate the word "lentityp nil" or "stringp nil" with the the "A word or phrase in the file" option.

    ERRORS:
    AutoCAD menu utilities loaded.; error: bad argument type: stringp nil
    AutoCAD menu utilities loaded.Loaded...; error: bad argument type: lentityp nil
    you wont find those lines within a file, they are error codes, it means:
    ((= ErrorMsg$ "bad argument type: stringp nil") "String variable not defined.")
    ((= ErrorMsg$ "bad argument type: lentityp nil") "entget passed a nil.")
    meaning you have some sort of a custom routine that is being loaded that is not coded properly, or not being called properly. the only way to really figure it out is to load your custom routines one at a time and trace the error. At our offices, I added print lines to the startup routines that allow me to determine where in the order our startup failed. It adds a lot of extra text to the startup, but it makes it a heck of a lot easier to troubleshoot.
    Christopher T. Cowgill, P.E.
    WIGHTMAN & ASSOCIATES, INC.
    ENGINEERING <> SURVEYING <> ARCHITECTURE
    AutoDesk Infrastructure Design Suite Premium 2014 x64
    Windows 7 Pro x64

  3. #3
    Active Member
    Join Date
    2002-12
    Posts
    77
    0 Did you find this post helpful? Yes

    Default Re: Bad Argument

    One of the things that I did here (at work) was to add to line to all of out major lisps (acad.lsp, acaddoc.lsp, company.lsp as well as any .mnl)

    (princ "\n Loading xxxx.lsp") at the begining
    (princ "\n xxx.lsp loaded succefully....") at the very end

    This way I can tell were in the load process I get a failure. This allow me to track it from there.

Similar Threads

  1. Help with Defun Argument
    By jeff.richards in forum AutoLISP
    Replies: 4
    Last Post: 2011-08-03, 04:23 PM
  2. bad argument type: lentityp nil
    By moshira_hassan in forum AutoCAD General
    Replies: 1
    Last Post: 2009-04-15, 07:09 AM
  3. Presentation Argument
    By mjdanowski in forum Revit MEP - General
    Replies: 2
    Last Post: 2007-12-04, 01:22 PM
  4. bad argument type: FILE nil, help plz
    By jgroh in forum AutoLISP
    Replies: 11
    Last Post: 2007-10-30, 01:15 PM
  5. AN INVALID ARGUMENT WAS ENCOUNTERED
    By khanson-3b in forum Revit Structure - General
    Replies: 5
    Last Post: 2007-08-23, 06:58 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •