Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Critical error V 5.3.1Critical error V 5.3.1
Previous
 
Next
New Post
3/28/2010 3:20 PM
 

 

 I updated to 5.3.1 and now I have an error across my instance 

A critical error has occurred.
Object reference not set to an instance of an object.

 

Any ideas?

 

Peter

 
New Post
3/29/2010 4:53 AM
 
did you try restarting the application by re-saving web.config file?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/29/2010 11:26 AM
 
Yes I even rebooted the server. Here is some info from the event log. AssemblyVersion: 5.3.1 PortalID: -1 PortalName: UserID: -1 UserName: ActiveTabID: -1 ActiveTabName: RawURL: AbsoluteURL: AbsoluteURLReferrer: UserAgent: DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider ExceptionGUID: b93b98f0-97de-4ecd-980d-8c2378683374 InnerException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4) FileName: FileLineNumber: 0 FileColumnNumber: 0 Method: System.Threading.ReaderWriterLock.AcquireWriterLockInternal StackTrace: Message: System.ApplicationException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4) at System.Threading.ReaderWriterLock.AcquireWriterLockInternal(Int32 millisecondsTimeout) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.AddToScheduleQueue(ScheduleHistoryItem objScheduleHistoryItem) Source: Server Name: NET Also AssemblyVersion: 5.3.1 PortalID: -1 PortalName: UserID: -1 UserName: ActiveTabID: -1 ActiveTabName: RawURL: AbsoluteURL: AbsoluteURLReferrer: UserAgent: DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider ExceptionGUID: b93b98f0-97de-4ecd-980d-8c2378683374 InnerException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4) FileName: FileLineNumber: 0 FileColumnNumber: 0 Method: System.Threading.ReaderWriterLock.AcquireWriterLockInternal StackTrace: Message: System.ApplicationException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4) at System.Threading.ReaderWriterLock.AcquireWriterLockInternal(Int32 millisecondsTimeout) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.AddToScheduleQueue(ScheduleHistoryItem objScheduleHistoryItem) Source: Server Name: NET
 
New Post
3/29/2010 11:40 AM
 
there seems to be a performance issue with your sql server, maybe caused by an exaggerating transaction log or eventlog table.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/30/2010 8:44 AM
 
Any way to fix the sql with this data?
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Critical error V 5.3.1Critical error V 5.3.1


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out