 Knowledge Is Power |
|
| Sections on this page: |
|
||
|
Companion pages: |
|
Looking for a host ? Learn from my mistakes. My horrible experiences with
Blueberry Hill, WestHost, Interland, and CI Host.
I originally hosted my Going To Vegas site (www.goingtovegas.com) with Blueberry Hill Communications (aka BH Com - $15.83/mo). In the first year I can't begin to count the number of times I had to call and e-mail them regarding problems with my server not responding. One particularly bad problem was that, while the server did not go down completely (in which case they would have gotten a notification from their monitoring software), it would stop responding to HTTP requests. In effect, my site would be down but they never knew it. Less-than-honest host providers do not count this in their "down-time" calculations, but if a Web hosting server is serving Web pages it would seem to be down to me. I typed up a letter to Craige Campbell, president of Blueberry Hill, and sent it to him using Federal Express asking that my domain be moved to a more reliable server. I never received a response from him and my domain was never moved. The search was on for a new host.
I then signed up with WestHost ($8.95/mo). Don't believe their claims of "24/7 technical support" or "99.9% uptime". In the first month my site went down twice. The first instance was like the above, where the server did not respond to http requests but I could ftp into it. The second time it went down completely. (They claimed it was a router problem on the back-bone, but my site didn't receive any hits from anywhere. If it was a back-bone problem a lot more sites than just mine would have been down and it wouldn't have taken over 6 hours to discover/resolve it.) My site went down around 10 pm, I discovered it around 12:30 am and promptly sent an e-mail to their "24/7 e-mail technical support" address. I did not receive a response until 6:35 am and my site as not back up until 7 am. My first outage was not as long, but in another way was much worse. I had spent the entire weekend e-mailing organizations asking them to take a look at my site. When most of them opened up their e-mail Monday morning and clicked on the link in the e-mail message they got a "server is not responding" error. An entire weekend's worth of work down the drain. My site had gone down at 3:30 am and they knew nothing about it until I e-mailed them at 8:30 am. It then took them another hour to get the site up and running. Again, all this within the first 30 days.
I then decided to go with Interland ($17.95/mo) because they had a good reputation. However, when it comes to shared hosting Interland is one of the worst. They don't monitor the servers hosting shared accounts very closely. I know this because on my fourth day with them my site was down for 8.5 hours. I also frequently experienced "port cmd failed" and "blocking call error" messages when trying to ftp files to my site. That, along with the fact that their "On-Line Support Wizard" is so slow it's down-right painful to use set me on a search for another host. I also got the impression their shared accounts are merely a vehicle for selling their higher-priced accounts. They would even pitch them in support responses. Despite this eagerness to sell, they're not very eager when it comes to the opposite. It was very difficult getting my refund.
CI Host ($18/mo) was very strange. If you visited the Bestdam Logger pages you know that this script sends a report at the first hit of a new day. Four times in my first month with CI Host I received these reports several times a day. For some reason the server clock was changing and they never knew it until I brought it to their attention. They could never offer an explanation for this and had a "business as usual" attitude about it. I also found out they were hosting my site on a server which also hosted three different domains with "mp3" in the domain name. File downloads put the heaviest load on a server of any Internet-related function. Having three sites serving up MP3 files obviously would have affected the response of my site. I also experienced instances where I would try and go to my site only to get an error saying the "server is not responding". A few minutes later I would try it again and it responded fine. This type of problem is maddening because it's almost impossible to track down due to it's short-term, intermittent nature. The best indication that there truly was a problem was the fact that my hit count on the home page increased by 50% when I switched to a new host. They were also even worse than Interland when it comes to giving refunds. It took a month and a half of countless e-mails and telephone calls to get my refund from them. Based on the BS I encountered when I tried to get my refund, I'd stay as far away from these folks as possible.
A word of warning about Burlee. While I never formally hosted with them I did sign up for their $12.95/mo "Unlimited Plan" because their Web page said it includes htaccess support. When I uploaded my files to their server the .htaccess file kept disappearing. When I asked technical support about it they said I'd have to upgrade to their $19.95/mo plan to use htaccess. Clearly false advertising, which I let them know about when I immediately cancelled the account. But it's still listed as a feature on their Unlimited Plan Web page.
I'm now with Hostway ($13.95/mo for 200 MB of disk space and 6 GB of monthly bandwidth) in Chicago. They have been a welcome change from the others. I often FTP in to check the logs generated by the Bestdam Logger script. I have yet to run into a situation where I couldn't connect or where there was a big gap in the date/time stamp of log entries indicating my site was not available. They also have an $8.95/mo plan (when paid annually) that includes most everything the higher-priced plans do. You just get less disk space and a lower monthly bandwidth allotment(5 MB/1 GB respectively). This account is not real prominent on their "Web Hosting" page so be sure to look for the "Value" link under the list of Unix plans. If you're looking a host they may be worth a look. (Note that the links to HostWay in this paragraph are "affiliate" links tied to my sales-free GoingToVegas.com site which is hosted through them.) www.hostway.com
The first thing you have to decide is how important reliability is to you. Don't be fooled by up-time percentages. Those are usually monthly percentages. A 99% monthly up-time means your site can be down for 8 hours each month, or 4 days each year.
The sad fact is that, as my experience shows, it doesn't matter how much you spend, you're not going to get good reliability with a shared hosting account. The more expensive, big operations may have 24/7 voice support, but you basically have to monitor your site yourself. CI Host brags about hosting 70,000 Websites. How much attention do you think your site gets? The smaller, less expensive outfits my give you better service, but they typically don't have live humans monitoring the servers 24/7, just some monitoring software that probably only pings the servers. That doesn't tell them if just the Apache Web server software stops responding. And even if you do notice your site is down and you send them an e-mail, it could be the next weekday morning before you get a response or any action taken to fix it. My hope behind this lack of serious service to customers is that some vendor will start selling "plug-and-play Web servers" that people can connect to their broadband Internet connections which will put most of these hosting companies out of business. Setting up your own server using Linux isn't hard, but it's not quite "plug-and-play" either (yet).
"Shared" hosting means really shared. It's not uncommon for 300 or more domains to be hosted on a single Linux server. If a CGI script on any one of those domains goes renegade and takes down the server all 300+ sites will go down. Since most hosts have different shared hosting packages, ask how many domains are hosted per server with each one of the packages. If it's the same for all of them, then a higher price won't get you better reliability. As a sales rep with Interland told me, in the hosting game servers are real estate, and the more domains you can fit on a server the higher your returns will be. File downloads really load down a server. If your domain is hosted on the same server as a sites offering software downloads, your site performance will suffer.
If very high reliability is important to you, you have two options; go with a "dedicated" hosting plan where your domain is the only one hosted on the server which will cost you over $300./month; or set up your own server. If you have a broadband connection to the Internet at the office or at home, setting up your own server is not as nearly as complex as you may think. On my Beginners Guide to Linux page I show you how easy it is. (Besides higher reliability due to only hosting one domain on a server, having your own server means you can give yourself a lot of the bells and whistles listed below.)
Usually, the more features you have the more you will pay. Look for a "Compare Plans" link on a host's Website. Comparison tables are helpful in that they usually lay out most of the features available and which of those features are included in the plan you are considering. Here are a list of some features to look for in case you may need them, and some questions to ask:Web hosting has become an extremely competitive business. There are a ton of hosting services out there. As such, you can afford to be picky and shop around. These places track things like "average wait times" (on hold) for voice calls and e-mail support response times. Ask for a number for these wait time and response time stats. If they give you a wishy-washy non-numeric answer, remind them you asked for a number. If they're evasive, go somewhere else. If they claim "24/7 e-mail support", be sure to ask if someone is actually on staff 24/7 to respond to the e-mails. If they only offer a 15-day trial period, go somewhere else. If their Website is out-dated or has problems - go somewhere else. It's an indication of their attention to detail and level of quality. As you saw above, the reliability of the servers with my first four hosts was worse than the free Web space I get with my ISP dial-up account (that this page is hosted on). That's purely pathetic. You're paying for a service and you deserve to get what you paid for.Lets also look at CGI-related features and questions to ask:
- telnet (remote terminal) access in addition to FTP *
- sufficient hard-drive space and bandwidth for your needs
- anonymous FTP access to your site (visitors can download files)
- SSL capability for secure connections
- number of POP accounts
- your own dedicated IP address
- database support for use with CGI (UNIX/Linux) and ASP (NT) scripts
- 24/7 voice support
- 30-day money-back guarantee **
- access to error logs ***
- How many domains do you host on a single server?
- Is your up-time percentage (if one is given) monthly or yearly?
- What is the average "wait time" for (voice) technical support calls? (Get a number - they know what it is)
- What is the average turn-around time for technical support e-mail responses? (Get a number - they know what it is)
- How much of a discount do I get if I pay annually instead of monthly?
- If I pay annually, do I get a pro-rated refund if I cancel my account early?
* If you wish to set up password-protected directories on your site, either you must have telnet access or your host must provide the ability to create and manage them using their "control" or "admin" page. This is because you have to use a Linux command-line utility to create and modify the password file.
- your own CGI-BIN directory (including NT servers)
- SSI support (including NT servers)
- Do my pages have to have a .shtml extension if they contain SSI directives?
- If the above is 'Yes', do you allow the use of htaccess and XBitHack (allows you to modify the Apache configuration)
- ASP and ASPMail support (Windows only)
** Why is a 30-day guarantee helpful? There are many different ways hosts can set up servers and they can have many different requirements and you may come across something that limits you. The ability to "try before you buy" is always helpful.
*** Having access to error logs is nice because you can look for errors when a script you're trying to use isn't working. However, if you have telnet access you can telnet into your server and try running the script from the shell prompt to see errors. Not having either access to error logs or telnet access will make troubleshooting scripts difficult.Note: Not having either access to error logs or telnet access if very bad news. There's no way to test or troubleshoot your scripts. Even worse, there's no way for the 300+ other Webmasters on your server to test or troubleshoot their scripts. This increases the likelihood that your site will be taken down by someone else's script.
Hostway isn't perfect. The following is tool you can use to compare them to other plans. However, if up-time is your primary concern they're the way to go based on my experiences. Due to bandwidth usage I had to upgrade to their Gold Plan ($13.95/mo). However, if your site needs are small, they do have a $8.95/mo Value Plan that's not very prominent on their Website, but is worth looking for. Note that they only offer telephone support for their higher-end plans. Lower-end plans only get e-mail support but I've always gotten a response within a few hours, even at all hours of the night.
- telnet access
- 200 meg hard-drive space
- 6 Gig/month bandwidth
- anonymous ftp
- SSL capability
- 5 POP accounts
- no dedicated IP address
- mySQL database access
- 24/7 staffed e-mail support only
- 30-day free trial
- no access to error logs
- unknown domains per server
- no up-time percentage stated
- $13.95/mo when paid annually (10% discount)
- personal CGI, SSI, & htaccess support
There are always unknowns when switching to a new host. With a 30-day guarantee you can activate your account on the new host but not cancel your account on your old host immediately. This will keep your Website active on your old host a bit longer while you test out your new host using an IP address. There's a bit of work involved in switching to a new host. The two main tasks are:Don't perform Step 2 until you're satisfied that your new host will meet all of your needs.
- Move your site files to the new host's server
- Change your domain's DNS settings to use your new host's DNS servers
Moving Your Site
Moving (actually copying) your site's files to a new host's server involves:Once you get your files FTPed to your new host you can test out your setup by using the IP address in place of the 'www.<yourdomain>.com' (provided you have your own dedicated IP address). For example:
- If you use CGI scripts you'll have to update the following path information if a script uses it
- change the path to the Perl interpreter (the "shebang line" at the top of the script)
- the "system path" to your Web root and/or cgi-bin directory
- the path to your new host's Sendmail installation
- FTP all of your page and CGI script files to your new host (be sure to use ASCII mode for all of the CGI script files)
- After transferring the script files, you'll have to set the appropriate permissions in the cgi-bin directory
http://199.99.99.99/index.html
or
http://199.99.99.99/cgi-bin/myscript.pl
If you find that your new host doesn't offer something your old host did, and that something is important to you, ask your new host if they will provide it. If not, cancel your new account and tell them to refund your money.
Changing Your Domain's DNS Settings
Your new hosting service will likely offer to "move" your DNS for you. This is the easy way to go. However, you would't have any control over when they do this and they may do it immediately not giving you any time to test out your new site. Changing the DNS yourself is very easy (see below) so you may want to tell them you'll handle it.
If you let the new hosting provider switch your DNS you will get an e-mail message from Network Solutions saying that someone (your new host provider) has submitted a change to your domain record. Dealing with the Network Solutions e-mail is outlined in the Network Solutions Process section below.
If you find you don't like your new host for some reason you just never reply to the Network Solutions e-mail and no changes are ever made.
If you do respond to the Network Solutions e-mail they will update your domain record in their database with your new host's DNS server names and IP addresses. You, your new host, and your old host (provided your hosts are listed as the before-and-after "technical contacts") will receive an e-mail from Network Solutions when this update is done. However, it will take some time for your site's new DNS information to propagate to all of the DNS servers around the world so don't pull the plug on your old host's server right away. Your site should be operational on both servers for at least 72 hours after receiving the confirmation message from Network Solutions. Monitor the traffic on your old host to make sure all traffic to it has stopped before you cancel your service with them.
If you decide to handle the DNS changes you specify the new DNS servers and then Network Solutions will send e-mails to your new host and old host and letting them know they need to update their DNS servers (your old hosting removes your domain DNS records from their DNS servers and your new hosting service adds them to their DNS server)."DNS" stands for Domain Name Service. It is the process that takes a domain name and translates it to the IP address of the server which is hosting that domain. Most ISPs have set up two DNS servers (one for backup) and they must frequently update their DNS servers with new information from Network Solutions. You may recall entering a "DNS search order" in your TCP/IP Properties window when you set up your system for Internet access. You could actually still surf the Web without any DNS entries on your computer, but you'd have to enter IP addresses for every site you wanted to visit.
To change your DNS settings yourself:
Once you've completed changing your DNS settings you'll get an e-mail listed in the Administrative Contact section for the domain. Responding to this e-mail is covered in the next section. Note that no changes will be made until you respond to the e-mail.
- Get the names and addresses of your new host's DNS servers (at least two).
- Go to the Network Solutions Website and click on "Account Manager Login" in the upper right corner of the page and log into your account.
- Click on "View Domain Name List" on the menu on the left side of the page.
- On the next page click on the domain name you're moving (not on the EDIT DNS button).
- Click on the Edit link next to "Designated DNS".
- Click on the Continue button at the bottom of the box labeled "MOVE DNS TO A NEW NAME SERVER".
- Disregard the scare tactic warning that you may lose Network Solutions services. It's intended to scare those who currently use Network Solutions from going with a different hosting provider. You don't have your Web site hosted by Network Solutions. Click on the Continue button.
- Enter the names of your new hosting provider's DNS servers and click on the Continue button to complete the process. (If you drop down the lists you'll notice that your current host's name servers are listed.)
Network Solutions offers three levels of security for you to choose from to protect your domain record. NS calls them "Authorization Schemes". They are also called "Guardian Methods".
- MAIL-FROM is the default level. They send you an e-mail letting you know someone (could be you) has requested a change to your domain record and you respond to the e-mail saying it's OK.
- CRYPT-PW is pretty much like the MAIL-FROM except that you select a password to use with your account. In your e-mail response to them you must include this password.
- PGP is an electronic key that is normally only used by ISPs and hosts who deal with Network Solutions a great deal.
For most instances the MAIL-FROM scheme is sufficient. However, if you're concerned about security (such as with a disgruntled former employee who served as Webmaster) you can go to the NS Website (www.networksolutions.com) and use their "Make Changes" page. There's a "Change my authentication scheme" selection in the drop-down list of changes you are allowed to request.
Now lets take a look at what I mean by "your domain record". There are actually a couple of records in the NS database involved here. You yourself have an NS record which is identified by your "handle" and your e-mail address. Your handle is a randomly generated ID that looks something like WA3509. These personal records can either be "individual" or "role" records. Each domain name also has a separate record with the Registrant, DNS, etc. information. Your domain record is associated to your personal record because you are listed as the administrative "contact" in the domain record. If you have more than one domain you still only have one personal record (and one password with CRYPT-PW). Likewise, a host will only have one record, but will be listed as the technical contact in many domain records. Also, in most cases of personal Websites, the "Registrant" is also the "administrative" contact, but this doesn't have to be the case. The Registrant (who owns the domain name) could list a third-party Webmaster as the administrative contact.
The process is a little different depending on who submits the change. If you, as the administrative contact, submit the change using the NS Website as we detailed in the previous section, the process is:If someone other than the administrative contact submits the request, most likely your new host, the process is a little different:
- You, as administrative contact, submit the change using the form on the NS Website
- NS e-mails you the resulting Service Agreement with the word MODIFY in the Subject: line.
- You reply to this e-mail sending the Service Agreement back to them.
- This generates a "tracking number" that is e-mailed to you, along with a message saying your request is being processed.
- If no problems are encountered with your request you will receive an e-mail a short time later saying that the requested modifications "...have been completed".
- Someone, using either an e-mail "form" or the Network Solutions Website submits a change to your domain record, which is actually a request to NS to change the record and a Service Agreement is generated.
- Network Solutions sends an e-mail containing the Service Agreement to the listed "administrative" contact letting them know this request has been submitted and asking for permission to proceed. (The administrative and technical contacts listed in the domain record are the only parties who can authorize the change.) When someone other than the administrative or technical contact is requesting the change (your new host), the word NOTIFY will be in the Subject: line.
- The change is authorized by responding to the e-mail as shown below.
- If no problems are encountered with your request you will receive an e-mail a short time later saying that the requested modifications "...have been completed".
In the case of switching to a new host the request will come from your new host because they will send an e-mail form to NS with the new DNS information. You and your old host will receive the NOTIFY e-mail (provided your old host is listed as the technical contact). The e-mail is long and confusing but the part you're interested in looks like this:************** Please DO NOT REMOVE Version Number ************** Notify Version Number: 4.0 Authorization 0a. Auth Scheme.............: 0b. Auth Info...............: Acknowledgment 1a. (Y)ES (N)O......: 1b. Comments........: Object 2a. Identifier......: MYWEBSITE-DOM 2b. Type............: D 2c. Tracking Number.: 000720.1372c 2d. Message ID......: 831c01b2bd60$0200a8c0@whmain 2e. Notify..........: 2f. Notify ID.......: nsh5mzN6414799132197
If you want to see exactly what changes are being requested, look further down in the e-mail message. If the existing administrative or technical contact made the request, the information being changed will be shown in sections 3 through 8. If it was someone else (your new host), the original request is included further down in the NOTIFY e-mail message in a commented fashion and typically looks like this:
> > > > Authorization > > 0a. (N)ew (M)odify (D)elete.........: M > > 0b. Auth Scheme.....................: MAIL-FROM > > 0c. Auth Info.......................: > > > > 1. Comments........................: > > > > 2. Complete Domain Name............: mywebsite.com > > > > Organization Using Domain Name > > 3a. Organization Name...............: ReallyBig Corp. > > 3b. Street Address..................: 101 Nerd Way > > 3c. City............................: Big City > > 3d. State...........................: NY > > 3e. Postal Code.....................: 10101 > > 3f. Country.........................: US > > > > Administrative Contact > > 4a. NIC Handle (if known)...........: WA3509 > > 4b. (I)ndividual (R)ole?............: Individual > > 4c. Name (Last, First)..............: > > 4d. Organization Name...............: > > 4e. Street Address..................: > > 4f. City............................: > > 4g. State...........................: > > 4h. Postal Code.....................: > > 4i. Country.........................: > > 4j. Phone Number....................: > > 4k. Fax Number......................: > > 4l. E-Mailbox.......................: > > > > Technical Contact > > 5a. NIC Handle (if known)...........: FYI809-ORG > > 5b. (I)ndividual (R)ole?............: Individual > > 5c. Name(Last, First)...............: > > 5d. Organization Name...............: > > 5e. Street Address..................: > > 5f. City............................: > > 5g. State...........................: > > 5h. Postal Code.....................: > > 5i. Country.........................: > > 5j. Phone Number....................: > > 5k. Fax Number......................: > > 5l. E-Mailbox.......................: > > > > Billing Contact > > 6a. NIC Handle (if known)...........: WA3509 > > 6b. (I)ndividual (R)ole?............: Individual > > 6c. Name (Last, First)..............: > > 6d. Organization Name...............: > > 6e. Street Address..................: > > 6f. City............................: > > 6g. State...........................: > > 6h. Postal Code.....................: > > 6i. Country.........................: > > 6j. Phone Number....................: > > 6k. Fax Number......................: > > 6l. E-Mailbox.......................: > > > > Prime Name Server > > 7a. Primary Server Hostname.........: ns1.hostinem.net > > 7b. Primary Server Netaddress.......: 199.99.99.998 > > > > Secondary Name Server(s) > > 8a. Secondary Server Hostname.......: ns2.hostinem.net > > 8b. Secondary Server Netaddress.....: 199.99.99.999 > > > > > > END OF AGREEMENT > >
No changes will be made to your domain record until you respond to this NOTIFY e-mail with the correct information added. To respond to this e-mail to approve the change you would:
- Click on "Edit" on your e-mail program's menu bar and select "Select All" to select the text of the entire message NS sent to you.
- Click on the "Reply" button to respond to the message and a blank e-mail composition window should appear.
- Click on "Edit" on this window's menu bar and select "Paste" to paste the text of the NS message into your message composition window.
- Chances are the "header" information also got pasted in which is the To:, From:, etc. information. You can select that and delete it if you wish.
- If you are using the MAIL-FROM authorization scheme you only need to enter the two items indicated in red below:
************** Please DO NOT REMOVE Version Number ************** Notify Version Number: 4.0 Authorization 0a. Auth Scheme.............:MAIL-FROM 0b. Auth Info...............: Acknowledgment 1a. (Y)ES (N)O......:YES 1b. Comments........: Object 2a. Identifier......: MYWEBSITE-DOM 2b. Type............: D 2c. Tracking Number.: 000720.1372c 2d. Message ID......: 831c01b2bd60$0200a8c0@whmain 2e. Notify..........: 2f. Notify ID.......: nsh5mzN6414799132197
- If you are using the CRYPT-PW authorization method you only need to enter the three items indicated in red below:
************** Please DO NOT REMOVE Version Number ************** Notify Version Number: 4.0 Authorization 0a. Auth Scheme.............:CRYPT-PW 0b. Auth Info...............:your-password Acknowledgment 1a. (Y)ES (N)O......:YES 1b. Comments........: Object 2a. Identifier......: MYWEBSITE-DOM 2b. Type............: D 2c. Tracking Number.: 000720.1372c 2d. Message ID......: 2e. Notify..........: 831c01b2bd60$0200a8c0@whmain 2f. Notify ID.......: nsh5mzN6414799132197
- When you've entered your items just click on the "Send" button.
After sending your e-mail response approving the change you'll get a reply from NS either saying your changes have been made or that they could not process the request due to an authorization failure. In the case of the later, it's most likely that the wrong scheme was entered in 0a or that the password entered in 0b was incorrect.
However, as mentioned in the previous section, if you get an e-mail from NS saying that your domain record has been successfully updated with new DNS information, you don't want to pull the plug on your old host right away. It will take some time for the changes to propagate to all of the DNS servers around the world so you'll want to keep your site operational on both servers for at least 72 hours.
Naturally, if you ever get an e-mail from Network Solutions with the word MODIFY or NOTIFY in the subject line, and you haven't requested any changes or are not in the process of switching hosts, something funny is afoot. NEVER reply to a Network Solutions MODIFY or NOTIFY e-mail if you are not in changing anything related to your Website.
|
|
|
|
Bestdam Logger + Counter Home Page Free Lite Edition |
Tips, info, diagrams, tutorials, links, and live cams on my Going To Vegas! site |
Apollo 11 Mission Free multi-media screensaver with wallpaper options |
IN NO EVENT WILL KEITH PARKANSKY OR VOYAGER, INCORPORATED. BE LIABLE TO ANY PARTY (i) FOR ANY DIRECT, INDIRECT, SPECIAL, PUNITIVE OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF PROGRAMS OR INFORMATION, AND THE LIKE), OR ANY OTHER DAMAGES ARISING IN ANY WAY OUT OF THE AVAILABILITY, USE, RELIANCE ON, OR INABILITY TO USE THE INFORMATION, METHODS, COMPUTER EXECUTABLE CODE, OR "KNOWLEDGE" PROVIDED ON OR THROUGH THIS DOCUMENT, EVEN IF KEITH PARKANSKY OR VOYAGER, INCORPORATED SHALL HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT, TORT, OR OTHERWISE; OR (ii) FOR ANY CLAIM ATTRIBUTABLE TO ERRORS, OMISSIONS, OR OTHER INACCURACIES IN, OR DESTRUCTIVE PROPERTIES OF ANY INFORMATION, METHODS, COMPUTER EXECUTABLE CODE, OR "KNOWLEDGE" PROVIDED ON OR THROUGH THIS DOCUMENT.
