My alt is banned from one of my own properties but only by TP!

Odd thing. I have a property on the mainland where I have located a shop. To test the classified ad, I logged in with my alt and tried to go there. Turns out my alt is banned from the property - even though I have it set to public access.

The land is not in a mature area and I don't have ANY access restrictions set for the property.

One time I even added the alt's name to the access list. Still couldn't teleport to the property.

Now - I can FLY to the property and land there. No problem.

This is getting frustrating. Help!

Sounds like you are not banned, but have a corrupt SL user profile. Try deleting the secondlife userprofile cache. It's in the secondlife cache subdirectory named after the avatar.

I'm running the Linux client if that makes any difference. Which directory? The 'hidden' .secondlife directory or the directory where the application resides?

UPDATE: Well, tried both. Made hold directories and moved all files from the .secondlife/cache directory to .secondlife/cache/hold - no effect. Then moved all files from .secondlife/<avatar name> to it's corresponding hold directory - no effect.

There is no reference to the avatars (by name) in the install directory.
There is no reference to the avatars (by name) in the .secondlife/cache directory.
There are no files containing the word/name "cache" in the .secondlife/<avatar name> directory

Things might be different under a Windows install. Don't run that setup.

ADDITIONAL DATA:

Flew to the location and landed. No problem. After a minute or two, client crashed out (probably not related - sometimes happens even with my main avatar regardless of location) and when I logged back on, my alt was able to materialize there with no problems.

Seems to be closely related to the teleport event.

Verified (again) that the land is set to open access - no restrictions, no bans, even when my alt is examining the permissions.

Well - the problem was diagnosed by Linden Labs.

The parcel in question was once part of a larger lot - I had apparently set a landing point on one of the parcels which I've since sold.

Resetting the landing point to the specific parcel solved the problem.

Thought it would be a good idea to report this as I can imagine it might happen to others.