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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Fixing Damaged/MIssing Stored Proceedures and ASP.net TablesFixing Damaged/MIssing Stored Proceedures and ASP.net Tables
Previous
 
Next
New Post
10/25/2010 11:18 AM
 
Can anybody offer some insight as to how one can force a re-install or fix an existing DNN installation that will fix missing stored proceedures and damaged ASP.net tables?

To give a little explaination, through a series of circumstances (most of them my own fault) I have a power interuption and a UPS failed. To make matters worse I don't have a recent backup and commerically available SQL repair products have failed to recover the database.

The only saving grace is that my content hasn't changed that much and for the most part only a few tables were affected weren't system critical (except the ASP.net tables).

I have sucessfully managed to import the table structure, stored proceedures, etc into a new database using the wizard within Management Tools and replace the damaged tables with those from my most recent backup to produce a workable database that allows me to browse my sites (with the exception of some html content and a few pages I added recently but I'll deal with that once later. I'm still seeing some errors that suggest that I still have issues with stored proceedures and possibly ASP.net tables (less likely). For example. I can't create new users. The result is no error but the user isn't created.

I've also tried updating the working installation to the latest version my current configuration allows (4.09.05). That install completed successfully but didn't help the situation.

Any assistance or ideas would be greatly appreciated.


 
New Post
10/25/2010 11:56 AM
 
You could try a new installation of of DNN under a new database name. MAKE SURE TO HAVE A BACKUP.    

If using SQL server, right click the database, click tasks,then generate scripts.
Now select select specific database objects , then select stored procs.

Select Save to new query window.

Click through to finish.

Once the query is created click finish, change the USE [database] name to the currupted database name.

GL

Thank you,
James Campbell
MCP,MCSA,MCSE,Sec +
http://jamesecampbell.blogspot.com
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Fixing Damaged/MIssing Stored Proceedures and ASP.net TablesFixing Damaged/MIssing Stored Proceedures and ASP.net Tables


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