Over the last week I have worked hard trying to solve the problems causing the site to recycle 5-10 times per hour (ann error Microsoft told me years ago could not be resolved unless changing some of the code which I do not have access to unless I pay to upgrade the platform = very expensive!). And it actually looks like it has been resolved. We’re still getting errors, but the site doesn’t recycle anymore. And that’s very good news!
But it looks like a caused effect is that many users have problems when logging into the site, or even accessing information on the site. And you may even see the problems if you’re not logged in.
The problems can be solved by clearing the browser cookies. Or try logging in with a different browser to verify (one you didn’t use for browsing DUG) that clearing it will solve it.
If you’re still having problems, please let me know. Email: webmaster at our domain name.
I’m very sorry about the inconvenience, but it will hopefully mean that most the performance problems we had for the last 3 years are mostly resolved. [:)]
The status is right now, that I had to revoke some of the changes I did. That has caused the original error to get back, but hopefully it’s now easier to log in.
So while existing users now should be able to login, then it’s currently not possible to register new accounts!
That’ means that I’m continuing my quest to make the errors on the website disappear!
Now it’s again possible to create new user accounts.
After creating a new account, then if you’re not receiving a notification on the screen that an email has been sent, then please use the request email function, to receive a new password to login.
The email you receive looks something like this:
Your username and temporary password are as follows:
This temporary password will expire after 3 hours. If this happens then you need to request a new temporary password again.
Here it’s import that you copy/paste the full password. If it spreads over two lines in your email client, then please make sure to remove the spaces before copy and paste.
On a little different notice, then tonight I had one of the foremost experts in Community Server from Telligent to give our server a full check-up. And among others, then he have fixed the issue causing the IIS server to recycle sometimes several times per minute, giving huge timeouts. Right now it’s 2 hours since the last time the server recycled! And that’s good news.