Hi, all.

What would be the problem if I can not login as host or admin after live hoster restored my locally generated database file?
There is no possibility that I lose the passwords for the host and admin because I use the same name and password combination all the time.
My localhost works just fine, but I have difficulty uploading to a live host; I guess the hoster do not seem to have DNN support or exprerience.

Does it have to do "setup permission" thing after database restore request?
I just asked them to restore my locally generated database backup file.

Thank you.

Kimchi

Are you having trouble logging into the DotNetNuke site, or are you having trouble logging into the database as a database user?

If everything is working fine, but you can't log in as host or admin to the DotNetNuke site, did you make any changes to your web.config file? Your web.config file must have the same machineKey setting as when you created the database. If they are different (compare the web.config file on localhost with the remote one) you must change your remote web.config to match the local one.

jncraig,

Thank you for your response. To describe what is happening with my hosting service, here is the sequence that I followed.

(1) Downloaded DNN 4.5.5 and followed wizard to install onto my localhost running MS SQL Server 2005 Express. It works fine in everything. The host and admin let me log in and just fine.
(2) I made a backup flie after I attached the App_Data\Database.mdf file. The backup default name is Database.mdf.BAK.
(3) After I changed local web.config I was able to login back to my localhost. That means I now direct the DNN to use the MS SQL Server 2005 Express. See my attachment at the end of this posting for my local web.config file's ConnectionString part.
(4) I created a datbase file for a hoster's remote MS SQL Server 2005. Of course I have created Login user for the server and assigned roles (asp_net.* and db_owner). Again the uid and pwd in the ConnectionString is appended at the end for your reference.
(5) After I uploaded the DNN 455 installation files and the backup file, I request a restoration service for my database backup file. They said "It is complete," which, I guess they mean they restored my backup file to my remote, hoster's SQL Server 2005.

Now, when I login to the hoster (http://www.woogonchung.net) the home page comes up. BUT, THE PROBLEM is that I can NOT login as host or admin. Again, trust me. I know my passwords for the host and admin account, because I use them all the time.

Below I have appened two web.config files; the first for the localhost version of my computer and the second is for the remote, live host version.

I will appreciate your help on this long-lasting trouble.

(Note: I blocked the password part of my web.config file with xxxxxxxxx .)




--------------- localhost, web.config ------------------


    <!-- Connection String for SQL Server 2005 Express -->
   
    <!-- Connection String for SQL Server 2000/2005
          name="SiteSqlServer"
      connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;"
      providerName="System.Data.SqlClient" />
   -->
 
 
    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules   -->
   
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules
   
    -->


----------- remote, live host; web.config  ----------------------

 
    <!-- Connection String for SQL Server 2005 Express
          name="SiteSqlServer"
      connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
      providerName="System.Data.SqlClient" />
    -->
    <!-- Connection String for SQL Server 2000/2005 -->
          name="SiteSqlServer"
      connectionString="Server=67.36.254.131;Database=woogonchung_dnndb2;uid=dnndbuser2;pwd=xxxxxxxx;"/>
 
 
 
    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules  
   
    -->
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->
   

The web.config files didn't post correctly because of the < and > in all of the tags.

You need to check the machineKey setting in each of the two web.config files. They should be the same. Having the wrong machineKey setting is the most common reason that you can't log in. Do you get a message that the password is wrong when you try to login?

The fact that your site is running on the host system indicates that the connection strings are correct.

I made it. Thank you for your info. The machineKey values and their persistancy have been mentioned in the Video turorial series, though.

Kimchi

Hi,
Thanks alot it solved my problem.

Me also hosted my published files on intranet server. After hosting everything is woring fine except DNN login.
After copting the same machinekey which I used for development version it worked

Thanks,
ProArch.