Hmm, this is an odd one... I just downloaded the gomaps PA and tried installing it into my DNN 4.4.1 installation, and had a big SQL error showing up along the lines of:

I took a look at my schema and theres definitely no aspnet_Profile table, there is an aspnet_Profiles table however, but I can't see anyone else here with a reference to this problem, and can't imagine it would be an issue with my installation... it's just a stock standard install as far as I know. It's not on any hosting provider or any such, it's my local server.

Any ideas why it would bug out in such a way? Is there a pre-required module that it's supposed to 'plug in' to that I missed somewhere?

Not sure what I should do now, it looked like such a funky module, was looking forward to having a play with it.

Thanks in advance for any help,
Max

In this version of DNN, this table is unused; the best option is to rename this table to aspnet_Profile (without 's') without any risks.
I am at a loss for why this table is named with an 's' at the end; aspnet_profile is a core dnn table that is no longer used, as profile information is now stored in the userprofile table.

Just for verification, your aspnet_profile table should have the following colums:
UserId
PropertyNames
PropertyValuesString
PropertyValuesBinary
LastUpdatedDate

Let us know.

Regards.

Hi Romain, thanks for the reply.

I took another look at my database and this table seems to be the one you are referring to, it has all those columns that you posted above. I'm not sure why it came to be named aspnet_Profiles, but oddly all the other dev/test/live databases we've been using have it correctly named aspnet_Profile! I guess somewhere along the line it was renamed on my version, and never noticed because like you say, it's no longer used.

Ah well, sorry for the inconvenience, I'll just trundle off and sit in the corner

Cheers,
Max