I received an unhandled error after installing a custom module (Just after a fresh install of DNN 3.0.9). Log entry:

AssemblyVersion: 03.00.09
Method: System.Web.FileChangesMonitor.FindDirectoryMonitor
FileName:
FileLineNumber: 0
FileColumnNumber: 0
PortalID: 0
PortalName: DNN
UserID: 1
UserName: host
ActiveTabID: 35
ActiveTabName: Start
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer:
ExceptionGUID: dc479d3c-36ba-4d67-95ad-23110cd3ce24
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
InnerException: Verzeichnis <path>\Host\File Manager\tabid\19\ctl\Edit\mid\323\ftype\Module\rtab\18\portalid\0\App_GlobalResources' existiert nicht. Das Überwachen der Dateiänderungen konnte nicht gestartet werden.
Message: Verzeichnis '<path>\Host\File Manager\tabid\19\ctl\Edit\mid\323\ftype\Module\rtab\18\portalid\0\App_GlobalResources' existiert nicht. Das Überwachen der Dateiänderungen konnte nicht gestartet werden.
StackTrace:
Source:
Server-Name: <ServerName>


Could be solved by restarting the application (just did dummy changes of the web.config).

I get the same error in a lot of pages.
It happenes after beeing inactive some time.

Logged as an issue

see

http://support.dotnetnuke.us/ViewIssue.aspx?id=541

I have the same problem.
I think I have solved it for now with disabling the caching feature.

In my last post I have thougt the problem could be solved with disabling the chache.
Sorry it does not solve the problem.

If there is a while with no activity on the Website the error:

"An unhandled error has occurred"

allredy occured.


For now I will deinstall the new Beta Version !

I think you can temporary fix this if you change in IIS.
Change the time for timeout in IIS.

It seems to crach after the worker processes are ended.

Change to what time .

My actual Connection timeout is setup to 120 seconds.
But the error did not appear after that period.

Or is there another timeout which do you mean..

Thanks in advance

I talk about the worker process.
In my case I set it in Pool properties - Perfomance - Timout for inactivity.

This in a Server 2003 IIs6 enviorment.

Jan O

Jan thanks,
I have now for test puproses disabled the Timeout for inactivity.

I will give it a try.

Seems to be an issue with components\Localization\Localization.vb line 543:
Dim filePath As String = Path.Combine(Common.Globals.ApplicationMapPath, Localization.SupportedLocalesFile.Substring(2).Replace("/", "\"))

It is returning, for example, D:\DNN\Home\tabid\35\App_GlobalResources\Locales.xml and not D:\DNN\App_GlobalResources\Locales.xml

As a 'quick fix' I have commented line 543, uncommented line 542 and re-compiled. Seems to work ok now.

Rather than use the previously commented out line can those of you experiencing this issue try this fix.

Replace the offending line in Localization.vb with

Dim filePath As String = Common.Globals.ApplicationMapPath & Localization.SupportedLocalesFile.Substring(1).Replace("/", "\")


There are good reasons not to use the Context.

"Rather than use the previously commented out line can those of you experiencing this issue try this fix.

Replace the offending line in Localization.vb with

Dim filePath As String = Common.Globals.ApplicationMapPath & Localization.SupportedLocalesFile.Substring(1).Replace("/", "\")


There are good reasons not to use the Context."

That didn't work. Happy's solution did the trick.

Charles

Made the change you suggested, and has been working fine for a while now. Will keep you posted.

[Edit] Hector's post displayed after mine.

Charles' suggestion is working fine for me, but obviously causing issues for others.

Change failed in the usual way with File Manager! Going back to HttpContext works.

I get the same error. It seems to be "fixed" by going back and reapplying the global permissions of NETWORK SERVICE to the DotNetNuke directory and child objects. Though after futher editing the new portal, the problem eventually returns and I have to reset the permissions again.