Sorry, I should have been more specific in my initial email.
>>What version of mojoportal?
The latest .Net 1.1 version (I downloaded it yesterday)
y
>>A release or did you compile it yourself?
A release. I did not download the source.
>>Is this on Windows or Mono?
Windows
>>Which db are you using?
Sql Server. I'm not sure what version, but it is probably 6.5 or 7
>>Did your host make the Data folder writable as it needs to be?
When I look at the attributes using FTP, I can see that it is writeable for all, which I assume would include the asp.net user.
>>Are you sure your connection string is correct?
Yes, but I will check again to make sure.
>>Did you get any errors creating the tableson the db at the host?
Not when creating tables, but I did get permission issues on the stored procs.. see below..I will try and explain after all the questions.
>>Does anything change if you restart the app?
Not right now..but I did have some issues related to the question above. Let me explain what has happened:
The first time I ran the application I got the Object reference error. After editing the web.config (I just changed custom errors, so I could see what was going on) I got an error saying that I do not have execute rights on one of the stored procedures. I gave my user rights on it..applied..and then got the same error, but on a different SP. (This makes me think the conn-string is correct). I found that about half of the SP's had owner of DBO..and the other half had owner of my current user. Those SP's where the owner was my curr user had the correct execute permission. Those SP's that had the owner of DBO had *no* execute rights. I modifed all of the DBO SP's to have execute rights for my SQL user. (I did not change ownership).
After I refreshed, I was back at the Object reference error.
Since then, I have restarted it several times, but the errors stays the same.