We have moved some of the larger sites to a different data center entirely, we are still moving some domains to new servers we have deployed today. Please read this thread http://community.ihostasp.net/forums/t/55.aspx

 Users that were affected by the outages related to congestion on mssql03.ihostasp.net are eligible to have their domain and the database moved to a new network free of charge. If you would like to have your database and domain moved, please open a support ticket by e-mailing to support@ihostasp.net with account and domain name. Please note, we will make a judgment call whether domain is moving to new server or not based on specific usage profile we have identified.

skozyuk:

We are working on resolution, you may see various exceptions while we work on things.

I beg to differ regarding your claim of downtime. We treat any interruption of service with all importance, but please lets not exaggerate things.

No exaggeration. Even when the site does come up it is still taking an unacceptable amount of time. I put in a ticket to have us moved yesterday but have received no response.

We have been in contact with webmasters that are affected by the process blocking on mssql03.ihostasp.net database server, and are currently moving domains to new mssql server. We have already moved a good number of domains and as result the overall load has dropped off resulting in much smaller amount of process blocks per second.

We will continue moving domains and databases between servers in order to re-balance the work load that has spiked over the last two days and has caused a disproportionate amount of traffic accessing one particular server. We apologize in advance as we may not be able answer all of your your support ticket raised during the last 48 hours related to this issue.

All relevant information regarding this issue will be posted in this forum, please feel free to ask questions and we will attempt to address them in a public forum so that we do not have to waist time and replying the same answer individually.

Morning Guys (UK Time!),

I put a support ticket in the other day ref server timeouts, My site problem has now escalated from intermittent timeouts to site not available at all for the past 9 hours. Would you mind posting an update so we know how much more downtime to expect.

Regards,

Peter

1. DNN EvenLog truncation.
2. DNN SiteLog truncation.
3. Database health check and repair
4. Index rebuild.
5. Query plan optimization.
6. Database shrink.

Appreciate the Info but I have now been down 16 hours, Varying from 11+ hours where IE7 just continually tried to access unsuccessfully to the last couple of hours where it is connecting but displaying DotNetNuke Upgrade Error Could not connect to Database. Is this what we should expect to see?

Also it's a real heartstopper when you eventually get in to Helm Control Panel and it tells you there are no files in your Folder (Gulp!!) on File Manager, (Can't get through on ftp)

Cheers,

Peter

petecee:

Appreciate the Info but I have now been down 16 hours, Varying from 11+ hours where IE7 just continually tried to access unsuccessfully to the last couple of hours where it is connecting but displaying DotNetNuke Upgrade Error Could not connect to Database. Is this what we should expect to see?

Also it's a real heartstopper when you eventually get in to Helm Control Panel and it tells you there are no files in your Folder (Gulp!!) on File Manager, (Can't get through on ftp)

Cheers,

Peter

I'm not sure if the behavior you described is related to the MSSQL03 issue. If you have already opened a support ticket with all the relevant info, please PM me a ticket ID and we'll take a closer look.

Many Thanks for the response. I'm up and running again.

Cheers,

peter

Has this process almost completed?  My site has been completely down since yesterday.  :-(

kgartly:

Has this process almost completed?  My site has been completely down since yesterday.  :-(

It is still running, the index rebuild is taking longer than what we have anticipated. It would have likely completed within several hours if we set database server to a single user mode, but that would completely blocked access to all database users for entire duration.

Looks like we got a handle on this issue. After rebuilding indexes and running query optimization plans for the most of the day yesterday, we also moved several larger databases from mssql03 server. The results became apparent this afternoon after we moved one particular database, the CPU utilization dropped from 100% to average of 17%. Furthermore, there are no longer process locks and lock delays registering on the server statistics. This is good news considering that we spent last 36 hour working on this issue.

  We ask all of you that have been affected by this outage and are still using mssql03.ihostasp.net database server to try accessing your site report back your findings in this thread.

 I tried accessing my site and it works.  It's not slow either.

Mine are up and running again as well.

Site is running again, seems normal.