dnn error:An unhandled error has occurred writing to the exception log.

R

rayday12

Guppy
Hello,

I run DNN 2.1.2 and i get the follwing error when users try to register of login: An unhandled error has occurred writing to the exception log.

And another error i get is:
An IO error has occurred writing to the exception log.

I believe it has to do with log file being locked or otherwise.
log.resources.xml seems to occupied or locked by som sort.

Please help, I have paying subscribers who now get this error.
Maybe someone can give me any pointers.

I believe i'm on win5.
 
Please advice! My customers are running away from me.
And I see alot of issues on Win6, but i'm on win5.

Also userticket 31964 is not responded to!?
 
Could you please let me know your ticket ID? I just checked a few DNN portals on Win5 and they are running fine.
 
hi,

the ticketnr is 31964

I had this problem before and then you upgraded to asp.net 1.1 and it seemed fine. Now i the problem occures again.

Try to register yourselve into my site, log out and log in again.
then you will see the error:

An unhandled error has occurred writing to the exception log.

Please help or give me pointers.
My paying customers are not returning.
 
When a user logs in the following error occurs:
"An unhandled error has occurred writing to the exception log"
Hit Back twice and you see that you're logged in.

I found out that when a user logs in, logs out and logs in again. quickly after eachother. the following error occurs:
"An IO error has occurred writing to the exception log"
Hit Back twice and you see that you're logged in.

Also i found that the module users online does'nt show the people online. Also the module where are they, does'nt work.

In asp.net forum i found it had to do someting locking up log.resources.xml

Also "keep alive" had something to do with it.

Anyhow, for a portal this is one of the core features and it is not good show for my subscribers.
Hope anyone can give me pointers.

running DNN 2.1.2, mssql db, host at jodo win5
 
One of your modules is causing an exception. However because it can not write a log entry to it therefore you are only seeing the error when it can not write the exception. What you'll need to do is clear out the log files and make sure DNN can write log entries. before you are able to determine which module is causing the problem.
 
You must log in or register to reply here.
Back
Top