hi!

i have a problem with my dotnetnuke site. It is in my localhost and the database is in the server. I login as host, it is ok then i logout and now here is the problem:

i login as a user it would show a page that says "An error has occured" and in the url : http://localhost/dotnetnuke/Default.aspx tabid=80&error=Input+string+was+not+in+a+correct+format.&content=0  and then when i now login as host i also get that error. Also clicking on any page or link that also happens. But when i close IE and open a new one, I login again as host and now I could enter!

Hope someone could help or explain this .. Thanks! 

The only time I have come across problems on localhost is if you have 2 DotNetNuke installations open.

If you login as host in the first and then login as host into the second you may get an error of Bad Data. - But I haven't come across the problem you mention here. - Does it happen with any of your other DNN localhost installations or is it just this version?

Has anyone else come across this problem?

Thanks,

i have a problem DotNetNuke site. It is my localhost in the DataBase in the Server. I login at Host or Admin it is ok but the different account user is "An error has occured" "http://localhost/DotNetNuke/Default...&content=0" and also clicking any page or link that also happen. it also one installation DotNetNuke open.

Hope someone could help..Thanks

Hello,

I have not come across this problem before. - Perhaps it would be worth trying a different browser? - I find www.firefox.com to be the best browser for working with DNN in a localhost test area.

Thanks,

Lee,

Did anyone ever resolve the above mentioned problem? I have several DNN portals in various versions that will run on my localhost (took a while to sort it all out). Now, I have an older version 4.4.1 running, but I cannot login to the application. I see the same error reported above.

On my 4.9.1 sites and 5.0 sites, if I enter an incorrect ID or password, I see this, " Login Failed, remember that Passwords are case sensitive." On this 4.4.1 version, I see this error no matter what I enter in the login fields: "An error has occurred.
An error has occurred" I intend to upgrade this install to 4.9.1, but it seems like I should get this working before I procede with the upgrade effort (would you try to upgrade it?).

I'd probably try to solve the problem first.

I don't know what this error is, either ... but you might want to try registering a new user and seeing if that user can login. If so, I'd think that something is wrong with your machine keys.

But, if you can get a new user registered, you can then manually go into the database and try setting that user as a superuser. Then you can have a superuser login.

Joe,

Thank you. BTW....I did not alter the machine key when I brought that 4.4.1 live site to my localhost (did I miss a step?).

I saw a note on the web that describes a password reset procedure using the code below. Do you think that will work? I am not sure where to put the snipet or how to do it (my db skills are so elementary).

create procedure uap_ResetPassword
@UserName NVarChar(255),
@NewPassword NVarChar(255)
as
begin
Declare @PasswordSalt NVarChar(128)
Declare @Application NVarChar(255)

Set @Application = (SELECT [ApplicationID] FROM aspnet_Users WHERE UserName=@UserName)
Set @PasswordSalt = (SELECT PasswordSalt FROM aspnet_Membership WHERE UserID IN (SELECT UserID FROM aspnet_Users WHERE UserName=@UserName))

Exec dbo.aspnet_Membership_ResetPassword @Application, @UserName, @NewPassword, 10, 10, @PasswordSalt, -5
end

If you brought you live site to localhose, and you also copied the database and web directory (including your web.config), you wouldn't have had to alter the machine key.

If you are not having trouble logging in, then you don't have a problem.


As for the stored procedure ... if you don't know where to use it, it's probably best NOT to try to use it.

Oh, sorry ... you ARE having trouble logging in.

Do you still have the version of web.config that existed when you moved the site?  If so, you can still copy the machinekey from that to the new web.config, and you should be able to login.

Logging in...is precisely my trouble. I copied db and all the files over. Went through the procedure to get everything running locally. I browse the site and it works on all public pages, but I cannot login.

If I cannot login, I have a problem. The question is fix it or upgrade it and hope it will fix itself. I think your advise is to fix it.

Towards that end, I suspect the password needs to be reset. I think you are thinking maybe not.

So, what do I do to diagnose and repair this issue? Should I collect another backup of all the files and start all over?

Hmmmm ... I tried this and is doesn't seem to work. 

Yes, I recommend fixing.

When you moved the site, did you create a new web.config, or did you simply change the connection strings in the existing one? 

If you have the old/original web.config, the first step will be to compare the machinekey in the old/original to what you have now.  If they differ, try copying the old/original machinekey to the current web.config.

If that doesn't work, your going to have to try resetting the password.  I'll give you instructions for that if you need them.