Hello,

I am getting the following error in my log viewer repeatedly. I am wondering if anyone would be able to assist in interpetting what I need to do to correct the problem.

Thanks in advance...

AssemblyVersion: 04.05.03
PortalID: 0
PortalName: Harlequin Meadows Association
UserID: -1
UserName:
ActiveTabID: 36
ActiveTabName: Community
RawURL: /ScriptResource.axd?d=aTMmimGZTKlB8j-WYGCjU8MgENKeeRVf0MsMMdniMuXYsq_TrmUnmGTTLLa8D9HWJCOMkd3gZt8gqJ5nmj9ioClmAaqqet2s0&t=633147577781063750
AbsoluteURL: /ScriptResource.axd
AbsoluteURLReferrer: http://www.harlequinmeadows.org/Community/tabid/36/ctl/Login/Default.aspx?returnurl=%2fdefault.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; iOpus-I-M; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.2; .NET CLR 3.0.04506.30)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 6aff5d7e-2537-4f41-b2fc-fda4d4e3508b
InnerException: Unhandled Error:
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.HttpNotFoundHandler.ProcessRequest
StackTrace:
Message: System.Exception: Unhandled Error: ---> System.Web.HttpException: Path '/ScriptResource.axd' was not found. at System.Web.HttpNotFoundHandler.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---
Source:
Server Name: DEDI471

I get the same error, and yes I am on version 04.05.03. But I used the Upgrage installation package. Shouldn't that take care of the web.config file too? How can I fix this error? I would guess that I have to modify the web.config, but what modifications do I need to make?

As Erik said above, the upgrade package comes with release.config instead of web.config (same thing, different name) in order to prevent accidental "overriding" of your production web.config.So

first back up your "old" web.config file and then copy your connection strings and machine keys (and other additions to web.config you may have made) to release.config, which then becomes your new web.config.