Wiki editors forcibly logged out of Wiki on Save.

I when a registered user is give rights to edit the wiki, they can edit the page but when they click save

1. it will either not save the changes and log them out.  or just log them out.

if I log in as site administrator I can log in -- as soon as I switch to Edit mode I am forcibly logged out.

the host account seems to work fine. 

This site is going to beta testing next week. 

so please help!!

This was not just on my computer. 

Thank you for your quick reply!

i am using DNN 4.7

I deleted cookies, cleared cache, restart the application. 

I tried to see if I could just get the site admin in using every possible combination of module settings or administration settings but every time I logged in as site admin and switched to edit mode, i would be kicked out.   Well not entirely. 

The edit view options at the top of the page is still visible.

The event viewer reveals 3 errors around a bit before but close to the time i noticed the problem.

The domain app shut down.
          Shutdown Details: The AppDomain shut down because of the hosting environment.

Then restarted.

Then  an exception occured.

EventQueue.ProcessMessage: Message Processing Failed
ProcessorType: DotNetNuke.Entities.Modules.EventMessageProcessor, DotNetNuke
Body:
Sender:
BusinessControllerClass: DotNetNuke.Modules.Media.MediaController, DotNetNuke.Modules.Media
DesktopModuleId: 75
UpgradeVersionsList: 03.02.00,03.02.03
ExceptionMessage: Object reference not set to an instance of an object.
Server Name: GENERIC25

in the modules table moduleid  75 is UserAccount Module. 

I am going to reinstall the module since we are using it out of the box.

I do not have the media module installed anywhere on the website.

This issue has apparently gone away all on its own over night.  I did reboot my local machine, and perhaps something on the host server refreshed. 

Perhaps being logged into sql from my machine.   

I did have some Dcom failure errors to my hosts server on my machine and had some viewstate errors later.

I also was logged into sql the whole time.

I just do not know for sure but since the module was working fine for us for days and is working now fine.

I am thinking it was something to do with some temporary cache or overloaded resources or network issues. 

who knows,  its working,

so I am moving on. 

thanks for your time.