Program starts in layer freeze command

[Anonymous]

I have searched and searched and cannot find any information on why this is happening or how to fix it, so hopefully one of you CAD wizards will have an answer or suggestions for me.

I'm currently running AutoCAD 2014, but this was happening in my 2012 too, which leads me to believe it is something in my custom settings.  Whenever I open CAD, it starts up in the Layer Freeze command with the cursor being the 'pickbox' and I have to escape out of this command before I can do anything.  It's not a huge deal, but after dealing with this for years and trying to find a solution, I've finally had enough and thought I'd reach out.  

When I open a new drawing (or any existing drawing) the command bar history has this:

Substituting [simplex.shx] for [Lucida Sans].
Regenerating model.
AutoCAD menu utilities loaded.
Initial load, please wait...layfrz
Current settings: Viewports=Vpfreeze, Block nesting level=Block
Select an object on the layer to be frozen or [Settings/Undo]: A-CLNG-*
*Invalid selection*
Expects a point or Settings
; error: Function cancelled
Loading ScaleListDel.lsp Version 0.7... SCALELISTDEL SCALELISTDELALL SCALELISTDELINCH SCALELISTDELXREF SCALELISTDEL_ SCALELISTDELINCHXREF SCALELISTDELINCH_ SCALELISTMETRIC SCALELISTMETRICTEMPLATE SCALELISTINCH SCALELISTINCHTEMPLATE commands loaded.
Type SX to execute...
Select an object on the layer to be frozen or [Settings/Undo]: ._layer
*Invalid selection*
Expects a point or Settings
Function cancelled
Select an object on the layer to be frozen or [Settings/Undo]:

I'm not sure why it loads layfrz command.  Any thoughts?

Thanks.

[Alfred.NESWADBA · Accepted solution]

Hi,

I guess you have a file like ACAD.LSP or ACADDOC.LSP that contains that calls, look for that filetypes, if they exist look into them if you can see the calls to the commands.

Good luck, - alfred -

[scot-65 · Accepted solution]

Reset the profile and baby-step the customization loads until the problem file is found.

???

[Anonymous]

Thank you!  It seems there was an actual individual LSP file that someone put in our office LSP folder that was causing it.  Not sure why anyone would want that and no one seems to know where it came from.  Bizarre.  Thanks for your help.  I wouldn't have figured that it was a LSP because why would anyone do that?!