For some time now I have been experiencing a problem with our websites which use the Deshi skin. I have explored all other aspects in terms of additional modules and hosting, but none seem to provide the answers. I'm wondering then if this is a skin issue. Perhaps someone in the community can help...?

The problem we have is that we keep getting an error - which upon investigation showed that somehow our database is becoming full.
The error is:
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".

<!-- Web.Config Configuration File -->







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.

<!-- Web.Config Configuration File -->







Our server guy investigated and found that if he truncated or cleared the logs then the error was resolved. BUT if we then access the site and make any changes either in images or text - even the slightest change - then the error reoccurs and our server guy has to again truncate/clear the logs to fix it.

He had a quick look and there’s nothing obvious in the site config that suggests there is a limitation there and so his assumption is there must be something somewhere that is hard coding a limit.

We have an unlimited Database size with our hosts, Godaddy, so having this issue doesn't make sense at all.

Can anyone help - ASAP?

Cheers,

Pete

Obviously, something is filling up your database -- without doubt it is the EventLog table. So, you'll want to look at that table and see what is being logged. If you can let us know what errors are there, we might be able to help.

As for "unlimited" database size, your site is definitely going to perform poorly when the EventLog table gets large, and keeping it to a reasonable size is good for permormance. I would get that the problem that is producing the "/" error is related to a timeout accessing the database.

There are not any hard coded limits.

It not directly related to the skin, though the skin might contribute to filling the EventLog.

Which version of DNN are you using?

Hi Joseph - thanks so much for your feedback. Apologies for this delayed response. It's my first time posting on the forum and I assumed that I would get an email notification when someone replied to my post. But as I didn't I thought no one had replied!!

Anyway, the DNN version I'm running is 7.3.4

I have a friend who works on servers and he manages to clear the fault temporarily for me by truncating the log. He did this just recently and it was fine for a couple of days but the error came back this morning.

The only changes that took place between him truncating the log and the error recurring was that I changed some text on the site, deleted a couple of photos, and the twitter feed updated. But even with that done the site was accessible for another day or two until the error returned.

Any advice you can offer would be very much appreciated. As with most one-man-bands out there I operate on a shoestring budget so I haven't got the funds available at present for a DNN company to figure this out for me...

Cheers

Ahh.. just spotted a check box at the bottom of this box for me to receive email notifications. Doh!!

Joseph, I replied previously and it went off for moderation before being published. Then I replied again after I noticed the check box for email notifications. The second reply was made using this 'quick reply' facility.

Anyway, in case my initial reply doesn't come through for sometime, I'll buzz it out here - as best as I can remember it.

Thanks for your feedback Joseph - much appreciated. This is my first time using the forum and so apologies for my delayed response as I was expecting an email notification when someone replied. I didn't receive a notification so I assumed no one had replied!

The DNN version is 7.3.4

The friend who works on servers is able to temporarily clear the error by truncating the log. He did this last Friday and I was able to access the site and make a few minor changes such as change some text and delete a couple of photos. Since then the only thing to change is the Twitter feed - with a couple of new posts coming in.

Since Friday the error hasn't recurred and I haven't made any more changes. However this afternoon I tried to access the site and the error was back! It was even fine this morning.

Any advice or further feedback is very much appreciated...

Cheers,

Pete

You will want to take a look at the Event Log. You can go to Admin, Event Log.

Look at there errors that are logged there. If you can't figure out what they mean, please post the most frequent one here and we'll help you decipher it. Then we can work our way down.

Thanks Joseph,
I'll request the details from my server friend and then I'll post it here.
Thanks so much once again!

Pete

Okay - here's some info from my server friend.

The common theme appears to be:
InnerException:Unable to create Lucene writer (lock file is in use). Please recycle AppPool in IIS to release lock.

I can only screenshot at the moment, but "general exception" seemed a bit tricky.. The scheduler stuff appears to be the bulk of the errors.

Here's the screenshot Joseph....

Thanks again for your support!

Hi Joseph,
Here's some more data that might help:

1. 6/11/2015 8:16:40 AM
General Exception
AssemblyVersion 7.3.4 PortalID -1 PortalName UserID -1 UserName ActiveTabI
AssemblyVersion:7.3.4
PortalID:-1
PortalName:
UserID:-1
UserName:
ActiveTabID:-1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProviderotNetNuke.Data.SqlDataProvider, DotNetNuke
ExceptionGUID:cffe82a4-aaeb-48c7-9119-76fe69c6af50
InnerException:Unable to create Lucene writer (lock file is in use). Please recycle AppPool in IIS to release lock.
FileName:
FileLineNumber:0
FileColumnNumber:0
Method:System.IO.__Error.WinIOError
StackTrace:
Message:
DotNetNuke.Services.Exceptions.SearchException: Unable to create Lucene writer (lock file is in use). Please recycle AppPool in IIS to release lock. ---> System.IO.IOException: The process cannot access the file 'G:\PleskVhosts\peteblay.com\httpdocs\App_Data\Search\write.lock' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalDelete(String path, Boolean checkHost)
at System.IO.File.Delete(String path)
at DotNetNuke.Services.Search.Internals.LuceneControllerImpl.get_Writer()
--- End of inner exception stack trace ---
at DotNetNuke.Services.Search.Internals.LuceneControllerImpl.get_Writer()
at DotNetNuke.Services.Search.Internals.LuceneControllerImpl.Delete(Query query)
at DotNetNuke.Services.Search.Internals.InternalSearchControllerImpl.DeleteSearchDocumentInternal(SearchDocument searchDocument, Boolean autoCommit)
at DotNetNuke.Services.Search.Internals.InternalSearchControllerImpl.DeleteSearchDocumentsByModule(Int32 portalId, Int32 moduleId, Int32 moduleDefId)
at DotNetNuke.Services.Search.SearchDataStore.StoreSearchItems(SearchItemInfoCollection searchItems)
at DotNetNuke.Services.Search.SearchEngine.IndexContent(DateTime startDate)
at DotNetNuke.Services.Search.SearchEngineScheduler.DoWork()
Source:
Server Name: P3NWVPWEB131


2. /11/2015 8:16:40 AM
Scheduler Event Failure
THREAD ID 117 TYPE DotNetNuke.Services.Search.SearchEngineScheduler DOTNET








THREAD ID:117
TYPEotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
EXCEPTION:Unable to create Lucene writer (lock file is in use). Please recycle AppPool in IIS to release lock.
RESCHEDULED FOR:6/11/2015 8:17:08 AM
SOURCE:STARTED_FROM_TIMER
ACTIVE THREADS:0
FREE THREADS:1
READER TIMEOUTS:0
WRITER TIMEOUTS:0
IN PROGRESS:0
IN QUEUE:4
Server Name: P3NWVPWEB131

My server friend also sent this -

I found this:
https://support.godaddy.com/help/article/6378/recycling-your-application-pool-with-windows-hosting-accounts

So, I’ve recycled the app pool now. HOWEVER, on IIS it should do this every 1740 minutes, and it’s certainly been longer than that, so I think the error might be a bit of a red herring.

Are the write lock error occurring over a period of hours?

Is this site on multiple web servers? From Googling, this is often associated with web farms. The solution is to make sure that the indexing task runs on only one of the webservers.

You might also want to triple-check file permissions. Especially the permissions for the file in question.

If not multiple servers, you might want to slow down the frequency of the site reindexing to make sure that you don't have multiple tasks running simultaneously.

Thanks Joseph. I'll pass on your questions and advice to my friend. I'll let you know how we get on.
Cheers,

Pete