Yes, that is possible. Set allow user registration to yes.

Ok, I just spoke with someone about this on the phone and I was told to do the following:

• Set Allow User Registrations to Yes
• Set Allow Anonymous Users to No

We have done that, but when a new users attempts to register, the following error appears in the System Log:

Invalid value for 'encryptedTicket' parameter. at System.Web.Security.FormsAuthentication.Decrypt(String encryptedTicket) at CounterSoft.Gemini.Presenter.GeminiHttpModule.Application_AuthenticateRequest(Object source, EventArgs e)

The user is typing her network password as the registration screen requires a password to be supplied.

They don't need to put in thier network password, just a random one. Is that the only place where you get that error.

We just tried a random password, and we don't get the error, but it doesn't ever go past the registration screen. We just did the installation yesterday and started playing around with it.

Do you get any fields in red?

No, the screen just blinks...

Can you send a screenshot of before and afetr to support at countersoft dot com?

Well, now it worked...the only thing I can think of is that maybe the password the user was typing did not meet network password complexity rules. Is it possible that something like that may cause the error we were seeing?

No, but it might be that the passwords did not match (confirm password)

Ok, but wouldn't it have told us that (or made one/both of the password fields red) rather than the error in the system log? This just isn't making sense. Has anyone looked into the error I posted for a root cause?

The error you have posted suggest a problem with your server's machine key.

Ok, so what can be done to prevent the issue going forward?

Check the application pool is not recycling too often and try and clear their browser's cache.

The application pool is set to recycle every 1740 minutes, so I don't think that is the issue. As for clearing the browser cache, we have a very limited user base at the moment due to the fact that we are evaluating the software. If the issue occurs again, we'll give that a try and I'll update the post. In the event you have any other recommendations, let us know. Thanks for your help!