We would like to thank all of the users who let us know via emails and the blog of the login issues they were experiencing. We would also like to thank you for your patience as we investigate this issue. After testing for nearly a week we have not been able to replicate the issue in our offices which is making the problem very difficult to diagnose. It is only effecting some users while others are able to login just fine.
So that we can continue to diagnose the problem we would like to talk to some of you who are having the issue and walk you through some steps so that we can better understand what the issue is on your particular computer. If you have the login error from the alternate login page that reads “Error: A license violation has occurred and the application is presently locked. Please see your administrator.” please call us at 1-877-445-6271 and speak to Brent at extension 118 today, 2/21/08 between 3:45 PM EST and 4:45 PM EST or tomorrow, 2/22/08 between 9:00 AM EST and 5:00 PM EST.
We appreciate your help in diagnosing this issue and we look forward to having MilSpouse.com accessible to as many spouses as possible as soon as possible. Thanks again.
Ryan Cieslak
Web Director
MilSpouse.com
5 Comments
Yay! I’m back in…thanks for getting this resolved!
I’m still not able to log in….
It’s wierd….I can log in at work, but not at home???
Armywife0218
I am getting a different runtime error when trying to login using the latest version of Internet Explorer or a windows xp sp2 box.
Server Error in ‘/’ Application.
——————————————————————————–
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a “web.config” configuration file located in the root directory of the current web application. This tag should then have its “mode” attribute set to “Off”.
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the “defaultRedirect” attribute of the application’s configuration tag to point to a custom error page URL.
i am gonna show this to my friend, dude